A Practical Month-End Close Checklist for Corporate Card Spend

Card spend is one of the messiest parts of most closes — not because any single step is hard, but because it's a chase: chase the statement, chase the coding, chase the receipts, chase the approvers. Here's a checklist that turns the chase into a process, with notes on which steps automation can remove entirely.

Before close week

1. Verify every card feed is current. Confirm each card connection synced through the last business day. A silently broken feed found on day three of close is how books get reopened. (Automatable: sync-health monitoring should alert you when a connection breaks — you should never discover it during close.)

2. Clear the un-coded backlog weekly, not monthly. Coding 30 transactions every Friday is a coffee break; coding 130 in close week is an afternoon. A weekly 15-minute pass keeps close week for exceptions only. (Automatable: coding rules and AI suggestions can keep the backlog near zero continuously.)

3. Chase receipts while memories are fresh. Receipt requests sent two days after a charge get answered; requests sent three weeks later get "which dinner was that?" (Automatable: automatic reminders to cardholders with missing receipts, and email-forwarding so attaching a receipt takes ten seconds.)

Close week

4. Reconcile pending vs. posted. Confirm month-boundary transactions posted in the right period, and that no pending charges are stranded. (Automatable: platforms that track both states reconcile this for you.)

5. Review the exceptions, not the population. If rules and AI coded the routine spend, your review is the exception queue: unusual merchants, over-limit amounts, missing dimensions. Review those line by line; sample-check the auto-coded rest.

6. Run the policy pass. Missing receipts over your threshold, out-of-policy categories, split-looking transactions, duplicates across cards. (Automatable: policy checks, duplicate detection, and anomaly detection should run on every transaction as it arrives — close week is just reading the report.)

7. Close out approvals. Every transaction above your approval threshold should carry its approval before export — chasing approvers is the second-worst chase after receipts. (Automatable: approval workflows with reminders move this out of your inbox.)

8. Export to your ERP — once. Export coded, approved transactions to Sage Intacct or QuickBooks Online as a single batch. Item-level export errors (a deactivated dimension value, a closed period) should be surfaced explicitly so you fix and re-export just the failures. (Automatable: one-click export with per-transaction status.)

After close

9. Write down what you chased. Every manual chase this close is a rule, reminder, or policy you can set up before the next one. The teams whose card close takes an hour got there by converting one chase per month into automation.

10. Watch three numbers month over month. Un-coded transactions at close start, missing receipts at close start, and hours spent on card close. All three should trend toward zero.

The honest benchmark

With automatic sync, rules + AI coding, self-matching receipts, and in-system approvals, card close for a 30-person company is realistically an hour or two of exception review — not a multi-day chase. That's the bar to hold any process (or any tool) against.