Best practices for reconciling prepaid card transactions
Prepaid cards give individuals and businesses a practical way to control spending, distribute funds, and separate expenses by employee, project, or department. Their flexibility also creates a responsibility: every purchase, refund, fee, and load must be recorded accurately in the accounting system.
A reliable reconciliation process compares card activity with bank funding records, receipts, invoices, and the general ledger. When performed consistently, it helps finance teams identify errors quickly, maintain clean books, and understand available cash without relying on an outdated card balance.
Establish a clear transaction workflow
Start by defining how a card transaction moves from authorization to final accounting. A pending purchase may later settle for a different amount, while a reversed authorization can temporarily reduce the available balance without becoming a completed expense. Your procedure should explain when each event is recorded and which status is treated as final.
Assign responsibility for each stage. Cardholders can submit receipts and business purposes, managers can approve expenses, and accounting staff can match settled transactions to ledger entries. Clear ownership prevents unexplained charges from remaining unresolved at month-end.
Capture complete supporting details
A transaction record should include the cardholder, merchant, date, amount, currency, expense category, project or cost centre, and receipt. Descriptions such as “office supplies” are more useful than generic notes like “purchase,” especially when a company manages several cards or recurring vendors.
Set a deadline for receipt submission, such as two or three business days after a purchase. Digital receipts should be stored with the corresponding transaction rather than in a separate inbox. This creates an audit trail and reduces the time spent searching for documentation during a review.
Match settled activity instead of authorizations
Reconciliation should focus on settled transactions because authorizations are temporary. Compare the settled amount against the receipt and the card statement, then investigate differences caused by tips, foreign exchange, shipping, taxes, or partial refunds. Keep pending items visible, but do not treat them as completed expenses.
A daily or weekly review is suitable for high-volume teams, while smaller businesses may reconcile several times per month. A regular schedule is safer than waiting until the reporting deadline, when missing receipts and forgotten purchases are harder to resolve. Guidance on managing business cash flow can also help connect card controls with broader cash planning.
Use consistent accounting treatment
Create rules for common prepaid card events. A card load is generally a movement of funds into the prepaid account, not an expense. The expense is recognized when the cardholder makes an eligible purchase. Fees, refunds, chargebacks, and foreign currency adjustments should have their own accounts or clearly defined coding rules.
QuickBooks and Xero integrations can reduce duplicate data entry by synchronizing transactions with the accounting ledger. Even with automation, review the mapping of expense categories, tax treatment, payment accounts, and tracking classes. Incorrect rules can spread the same error across many transactions before anyone notices.
| Transaction type | What to verify | Typical accounting action |
|---|---|---|
| Card load | Funding source, date, and amount | Record as a transfer or prepaid balance movement |
| Settled purchase | Receipt, merchant, category, and tax | Post to the appropriate expense or asset account |
| Pending authorization | Status and expected amount | Monitor without treating it as final |
| Refund | Original transaction and refund date | Reverse or reduce the related expense |
| Card fee | Fee description and billing period | Post to bank or service fees |
| Foreign transaction | Exchange rate and final settlement | Record the settled local-currency amount and any FX difference |
Reconcile loads, transfers, and fees
Many reconciliation errors occur outside ordinary purchases. Compare every card load with the originating bank account or payment method. Check that the load date, amount, and reference agree in both systems, and investigate duplicate funding entries or loads that appear on one statement but not the other.
Review monthly service fees, ATM charges, foreign exchange costs, and payment processing fees separately. A fee may be deducted from the available balance without appearing beside a purchase. Separating these charges makes financial reporting more precise and helps identify unexpected changes in the cost of using the program.
Handle exceptions with an ageing process
Create an exception report for unmatched, missing, duplicated, disputed, or unusually large transactions. Include the owner, date identified, amount, reason, and next action. Sorting exceptions by age ensures older issues receive attention instead of disappearing beneath newer activity.
Escalate transactions that remain unresolved beyond a defined period. A cardholder who repeatedly misses receipts may need tighter approval limits or temporary suspension, while a suspected duplicate or unauthorized charge should follow the organization’s dispute and security procedure. Keep notes about the resolution so the same issue does not require investigation again.
Build practical review controls
Use approval limits and merchant restrictions to prevent avoidable errors before they reach reconciliation. Separate cards by purpose where appropriate, such as travel, purchasing, subscriptions, or project expenses. This makes transaction coding easier and gives managers a clearer view of spending patterns.
Apply these operating recommendations consistently:
- Reconcile settled card activity against the statement and ledger on a fixed schedule.
- Require receipts, business purpose, and category codes for every eligible purchase.
- Review pending, refunded, disputed, and duplicated items in a separate exception queue.
- Reconcile card loads and fees to the originating bank or funding account.
- Restrict access and review unusual transactions through approval and notification controls.
A monthly close should include a final check of outstanding authorizations, unresolved receipts, unused balances, refunds in transit, and account totals. Document who completed the review and when. This evidence supports internal controls, audit requests, and accurate management reporting.
Consistent reconciliation turns prepaid card data into dependable financial information. Configure your card controls, accounting integration, and review schedule around the way your organization spends, then begin resolving outstanding items through a documented workflow today.