Corporate card reconciliation: how to stop chasing receipts at month-end

On the third working day of October, the finance manager of a distribution company in Surabaya opens the September statements for the company’s six corporate cards: 142 transactions, Rp 186,420,000. Receipts have come in for 101 of them. The rest are in a director’s wallet, a ride-hailing app, someone’s email and the memory of a general affairs officer who is on leave this week.

By working day 5, 23 lines still have no receipt. They go into a suspense account, as they did in August and in July. That account now holds Rp 61,300,000 that nobody can explain line by line, and the auditors will ask about it at year-end.

Unlike almost any other spend, card spend leaves the bank before anyone has approved it, which makes corporate card reconciliation the control that catches up. This guide covers what it involves, a worked example of one card statement, why it drags and how to keep it current all month instead of rebuilding it at month-end.

What is corporate card reconciliation?

Corporate card reconciliation is matching every transaction on a company card to its evidence, coding and approval, and then checking that what you’ve recorded agrees with the card statement. It works at two levels:

• Each transaction has a receipt or invoice, a business purpose, a category and cost centre, and an approval from someone other than the cardholder.
• Each card account agrees: the statement total equals what’s posted in the ledger, and the payment the bank takes on the due date clears the balance.

It’s the mirror image of a reimbursement. There, the employee has paid with their own money and is in a hurry to be paid back. With a card, the company has already paid, so the cardholder has no reason to hurry, and finance does the chasing.

How card reconciliation works, step by step

1. Spend. The cardholder pays with the company card.
2. Capture. The receipt is photographed or forwarded when the purchase is made, not collected at month-end.
3. Match. Each transaction from the bank, by feed, download or statement, is matched to its receipt on amount, date and merchant.
4. Explain and code. The cardholder adds the business purpose, and the line gets its category, cost centre or project and tax.
5. Approve. The cardholder’s manager, or whoever your approval rules name, approves the line.
6. Post. Approved lines are posted to the ledger, against the card’s liability account.
7. Close the account. At the end of the period, the statement agrees with the ledger, and personal or disputed charges are recovered or raised with the bank.

A worked example: one card statement

Here is the marketing manager’s card, one of the six, on working day 3. The statement runs from 26 August to 25 September:

Statement lines	Lines	Rp ’000
Receipt matched and approved	31	39,140
Receipt found, amount differs	4	6,212
No receipt yet	5	2,618
Personal	1	650
Total	41	48,620

Three-quarters of the lines are done. The rest is where the days go:

• Four lines that will never match on amount. They’re software subscriptions billed in US dollars. The invoices are in dollars, and the statement shows rupiah converted at the bank’s rate on the day it processed the charge, so a match on the rupiah amount fails every month. Match these on the dollar amount, the date and the merchant instead, and record the rate the bank used.
• Five lines with no receipt. Two e-money top-ups for tolls, a ride whose receipt is still in the app, a print shop and a coffee meeting: Rp 2,618,000 that takes more chasing than the other 36 lines together.
• One personal charge. Rp 650,000 at a supermarket on a Sunday: the wrong card, taken out of the wrong wallet. The cardholder flags it and transfers the money back, but only because someone asked.

Even once all 41 lines are explained, the statement isn’t September. It includes 26 to 31 August, and it leaves out Rp 7,940,000 spent on this card between 26 and 30 September, which will appear on October’s statement. If card spend is booked from the statement, every month borrows a few days from the month before. Booking each line by its transaction date, from the transactions themselves, puts the cost in the right month.

Why card reconciliation drags

• Nobody is waiting for the money. The cardholder isn’t out of pocket, so the receipt can wait, and it does.
• Receipts are collected at month-end. From wallets, inboxes and apps, weeks after the purchase, when some are already lost.
• Shared cards. One card used by several people, such as a general affairs card or a director’s card used by an assistant, so nobody owns each line.
• Subscriptions nobody owns. Software renews every month on a card, long after the person who signed up has left.
• Foreign-currency lines that never match. The amount on the invoice and the amount on the statement are different numbers, so automatic matching on amount fails.
• The statement cycle isn’t the month. A statement that closes on the 25th mixes two months, and someone has to split it by hand.
• Personal charges that are “paid back later”. With no record of whether they were.
• A suspense account that only grows. Unexplained lines are parked “for now”, and next month’s join them.
• Cardholders who approve their own spend. Most often the most senior ones.

Corporate cards in Indonesia

• Cards in a director’s name. Many companies run their card spend on cards held by a director, sometimes a personal card used for the business. Decide which cards are company cards, and make sure the directors’ spend has a reviewer too, agreed in advance, rather than being approved by the cardholder.
• Overseas software and advertising. Cloud services, software and online ads are often paid by card to overseas providers, in dollars. Keep the provider’s invoice, not just the card line: it shows what was bought and any VAT charged, which the statement doesn’t. Have your tax adviser confirm how VAT on these foreign digital services is treated.
• Rates and charges. The bank converts foreign charges at its own rate and may add a fee. The rupiah amount on the statement is what the company pays, so it’s the amount that has to be posted.
• E-money top-ups. Topping up a toll or parking card by credit card moves money to a prepaid balance; the cost is the tolls and parking it pays for. Treat top-ups like a small cash advance, settled with the usage.
• Personal charges. Agree in writing, in a card agreement each cardholder signs, how personal charges are repaid and by when, before the first one happens.

Signs your card reconciliation needs work

You probably need to look at how you reconcile cards if any of these sound familiar:

• Finance spends the first days of each month asking cardholders for receipts.
• A suspense or card clearing account never gets back to zero.
• Nobody can say who owns each software subscription on the cards.
• Foreign-currency lines are matched by hand, or not at all.
• Cardholders approve their own transactions.
• Personal charges are repaid “later”, with no record of whether they were.
• The last week of each month’s card spend shows up in the following month’s numbers.

With a reimbursement, the employee chases finance. With a corporate card, finance chases the employee.

How to keep card reconciliation current

1. Give every card one named holder. No shared cards. Give general affairs or IT their own card, with a named owner and a limit, and put each recurring subscription in someone’s name.
2. Write a card policy cardholders sign. What the card is for, how soon a receipt is due (for example, within five working days), what counts as personal, how it’s repaid and what happens when receipts are missing. It can sit inside your expense policy.
3. Get transactions weekly or daily, not monthly. Import card transactions as they post, so each one is matched while the receipt is still in a pocket and month-end only covers the last few days.
4. Capture at the till, match automatically. Match on amount, date and merchant, and on the original currency for foreign charges, so people only look at what didn’t match.
5. Approve every line, including the directors’. By someone other than the cardholder, through your normal approval matrix.
6. Close each card every month. The statement agrees with the ledger, nothing sits in suspense for more than a month and each line is in the month it was spent.
7. Review subscriptions every quarter. List every recurring charge with its owner, and cancel the ones nobody claims.

---

How Procapy helps

In Capy Expense, card transactions are imported into Capy and matched to the receipts employees capture. The cardholder picks a card transaction in the Capy app or photographs the receipt, and ProcAI reads the merchant, date, amount, tax and currency, so the statement is reconciled by attaching evidence rather than retyping lines. Card and bank statement lines are matched to claims automatically on amount, date and merchant, and your team reviews only the ones that didn’t match.

Foreign-currency receipts are converted at the rate for the transaction date or the booking date, according to each entity’s policy, with the original currency, the rate used and the converted amount stored on the line. Card spend is then tagged, policy-checked and approved like any other expense, through ProcApprove, and nobody can approve their own claim. Duplicate receipts are caught across employees, reports and card feeds, so a card charge can’t come back as a reimbursement.

Finance can see which card transactions are still missing a receipt, and a period close checklist lists unsubmitted card transactions before the period is locked. Approved spend is posted to Dynamics, SAP, Xero, QuickBooks or ABSS with the receipts attached. The finance team resources page covers the rest. Book a 30-minute walkthrough, bring your close checklist and chart of accounts, and we’ll map the manual steps to Procapy live.