Blog

In short: When a room full of nonprofit finance leaders was polled on their most painful manual process, credit card reconciliation won without much competition. The real problem isn’t accounting, it’s reconstruction: someone has to turn sixty anonymous line items into who bought what and why, weeks after the fact. Moving that coding to the cardholder at the moment of purchase, through a self-serve portal with automatic GL coding and photo receipts, removes the detective work entirely and frees finance to do the job they were actually hired for.

Before Kinley Graham was the Director of Pre-Sales at Sparkrock explaining ERP systems to nonprofits, he was the Director of Finance and CIO at a disability care organization in Ontario, running finance and IT for an organization with about 200 staff. He’s the one who actually had to open the corporate credit card statement every month. Not review it. Not explain it. Open it, and start the slow work of turning a list of merchant names and dollar amounts into something his auditors and his board would accept as accurate. 

In a recent webinar, Kinley talked through what that monthly ritual actually involved, and what changed when it stopped being his problem to solve by hand.  

This post draws on insights from that on-demand webinar: A Live Look at a Modern Finance System Built for Health Nonprofits. 

The poll that confirmed credit card reconciliation is the top pain point

Before Kinley or anyone else on the panel said a word about it, the webinar ran a quick poll. What’s the most painful manual process on your plate right now? Purchase-to-pay. Expense reimbursements. Credit card reconciliation. Financial reporting. 

Credit card reconciliation won, and it wasn’t close. Which probably isn’t a surprise to anyone reading this, but it’s worth sitting with for a second anyway, because an entire room full of finance leaders, polled cold, landed on the exact same answer without any prompting. Gary Servius, who’s spent fifteen years in this corner of the nonprofit world, called it flatly: probably the most time-consuming task an accounts payable person has to do, especially once you’ve got more than one corporate card in circulation and a decent volume of transactions running through it. 

What manual credit card reconciliation actually involves

To anyone who doesn’t do it themselves, credit card reconciliation sounds like one task. You get the statement, you match the receipts, you’re done. What it actually is, as anyone who’s sat in Kinley’s chair knows, is dozens of tiny investigations stacked on top of each other. A statement comes in from the bank with sixty line items on it, and every single one is a small mystery. Who bought this? What was it actually for? Is there a receipt anywhere, or did it walk out of someone’s car with the groceries? Which budget line does it belong to, and does that line have any room left in it?

None of that information travels with the transaction. The bank doesn’t know who swiped the card or why. It just knows a number and a merchant. So somebody — in Kinley’s case, him, or whoever on his small finance team had the unlucky job that month — has to go reconstruct all of it. And reconstructing means asking people. Which means emailing. Which means, more often than anyone wants to admit, walking over to someone’s desk for the third time about a receipt from three weeks ago that they genuinely do not remember anymore. 

That’s the part that doesn’t show up in any productivity report. It’s not just the hours of matching line items to receipts. It’s the social cost of being the person who has to keep asking. 

The real problem behind credit card reconciliation

The fix Kinley and Wendy walked through in the webinar isn’t complicated to describe, even though it took the industry a long time to actually build it well. The credit card statement comes in from the bank and lands directly in a purchase card journal, all the transactions together, with duplicates flagged automatically so nobody’s relying on a sharp eye to catch a charge that hit twice. From there, the whole thing turns into an invoice against the credit card company, and it sits in a purchasing card clearing account, waiting, instead of landing in the general ledger as an unexplained number someone has to chase down weeks later. 

But the real shift isn’t in any of that plumbing. It’s in who does the coding. Instead of finance trying to reverse-engineer sixty transactions after the fact, every cardholder sees their own purchases waiting for them in a self-serve portal. They pick the expense type, then the GL code fills in on its own based on that choice. They take a photo of the receipt right there with their phone, while they’re still standing at the counter and the purchase is still fresh in their head. They hit submit. Done. 

It moves the work to the one person in the entire chain who actually knows the answer without having to think about it. Not finance, reconstructing a stranger’s Tuesday from a merchant code. The person who was there. 

The Purchase Card Register: ending the chase for missing receipts

There’s one small tool from the demo that’s worth calling out on its own, because it’s the kind of thing that sounds minor until you realize what it replaces. Sparkrock calls it the Purchase Card Register, and what it does is simple: it shows finance exactly which transactions are still sitting there uncoded, with no receipt attached. Not a gut feeling about who’s usually behind. An actual, specific list. 

That’s the end of the vague monthly scramble Kinley would have recognized instantly from his own years doing this job — the part where you’re not even sure who to follow up with yet, so half your time goes into figuring out who’s missing before you can even start asking them. With the register, that step disappears. The list already exists. The follow-up, when there is one, takes a minute instead of an afternoon. 

What automated P-card coding actually gives finance teams back

It’s easy to talk about this purely in terms of time saved, and the time is real. But what Kinley’s old role actually needed more of wasn’t hours in the day. It was the ability to stop being a clerk and start being the person his organization actually hired him to be — someone who could forecast against grant budgets, tell a program manager honestly what they could afford before they committed to something, and walk into a board meeting with numbers he trusted instead of numbers he’d assembled in a panic the week before. 

There’s a second benefit that matters just as much for organizations like the ones Kinley used to run. Every transaction now arrives already coded, already receipted, already tied to a specific person who can explain it without anyone having to ask twice. That’s the difference between scrambling when an auditor or a funder asks a pointed question, and just pulling up the answer. 

The statement still lands every month 

Nothing about this changes the calendar. The bank is still going to send that statement on the same schedule it always has. What’s different is whether it arrives as sixty unsolved mysteries waiting for someone to play detective, or as a set of transactions that were mostly already sorted days earlier, by the people who actually knew what they were for. 

Kinley doesn’t have to open that statement and start guessing anymore. That’s really the whole point. 

Watch the on-demand webinar — A Live Look at a Modern Finance System Built for Health Nonprofits — or book a demo with Sparkrock to see what automated P-card coding actually looks like for your organization.

Frequently asked questions

Why is credit card reconciliation such a painful process for nonprofit finance teams? Because the bank statement carries no context — just a merchant name and an amount. Someone in finance has to reconstruct who made each purchase, what it was for, and which budget it belongs to, usually by emailing or tracking people down weeks after the purchase happened.

How does automated P-card coding change who does the reconciliation work? Instead of finance reverse-engineering transactions after the fact, each cardholder codes their own purchases through a self-serve portal at the time of purchase — picking an expense type, which auto-fills the GL code, and photographing the receipt on the spot.

What is a Purchase Card Register? It’s a tool that shows finance exactly which credit card transactions are still uncoded or missing a receipt, as a specific list rather than a guess. It removes the step of figuring out who to follow up with before the follow-up can even happen.

What does automating credit card reconciliation save besides time? It removes the social cost of repeatedly chasing colleagues for old receipts, and it means every transaction arrives already coded and explainable — so when an auditor or funder asks a pointed question, the answer is a lookup instead of a scramble.