Expense reconciliation: the month-end guess

It’s the last week of the month. Finance has a long list of card transactions with no receipt and no code, so they send a reminder to everyone with an outstanding charge. Most people find their receipts. For the rest, finance picks the closest account from the merchant name and posts it.

The guesses go into the close. Some land in the wrong cost center, and nobody notices until a budget owner asks why their travel line moved.

Cards and expenses are the part of procure-to-pay that runs without purchase orders. With no order to match against, every transaction depends on a receipt and a code arriving on time.

What is expense reconciliation?

Expense reconciliation matches each card transaction and expense claim to its receipt, codes it to the right account and cost center, and checks it against policy before it posts to the ledger. Done daily, it keeps card spend current. Left to month end, it turns into a chase.

Why reconciliation slips to month end

1. Receipts are chased at month end. The reminder goes out weeks after the purchase, when the receipt is gone.
2. Finance does the coding. The person who knows what was bought isn’t the one choosing the account.
3. The card feed and the receipts live apart. Transactions arrive in one system and receipts in another, and finance matches them by hand.
4. Policy is checked after the spend. An out-of-policy charge is found weeks later, when it’s hard to undo.
5. Subscriptions renew on cards. A tool bought once on a card keeps charging, and nobody owns the renewal.

What it costs

Guessed codes make budget reports wrong in ways nobody can see. Late receipts push work into the close, when finance has the least time. Subscriptions on cards add spend that never went through approval or supplier review.

What to fix first

1. Ask for the receipt when the card is charged. Message the cardholder the same day, and let them reply with the receipt attached.
2. Suggest the code from the merchant and past spend. An AI agent can read the receipt and propose the account. The cardholder confirms it or changes it.
3. Match the card feed and the receipts in one place. Each transaction shows whether it has a receipt, a code and an approval.
4. Check policy when the transaction arrives. Flag a problem to the cardholder and their manager the same day.
5. Find the recurring charges. Send each one to an owner, and move the regular ones onto a purchase order.

The guide to building an expense and card feed sync has the prompts for each step.

Where it fits

Card spend skips purchase requisition approval and the purchase order, which is why a recurring charge belongs on an order. The rest of procure-to-pay matches invoices to orders. Card spend has only the receipt.

For the whole procure-to-pay process, from purchase request to paid supplier, see the procure-to-pay process.