Reconcile a corporate-card central bill to employee transactions

Reproduce the issuer balance before allocation

A central bill combines many cardholders into one amount due, so matching only the statement total can conceal unsupported employee activity. Preserve the issuer statement and record corporate account, billing cycle, currency, opening balance, purchases, cash or special transactions, credits, fees, interest, payments, adjustments, closing balance, minimum or full amount due, and due date. Capture card-level subtotals and the issuer’s stable transaction IDs. Do not distribute the total across employees before reproducing the issuer’s own roll-forward.

Tie the opening balance to the prior closing balance and trace payments to bank-supported settlement and issuer application. A payment in transit can appear on the company ledger but not the statement cutoff. Record value and application dates separately. Investigate unexplained prior balances rather than spreading them across current cardholders. Fees and interest need their own coding and owner review. AP should show the arithmetic and evidence; finance decides accounting and the card-program owner addresses preventable charges.

Match cardholder activity without hiding gaps

Match each issuer transaction to the cardholder feed, approved expense report, receipt, business purpose, date, amount, currency, and cost allocation. Preserve foreign-currency source amount and issuer conversion where shown. Similar merchant names or amounts do not prove identity. If employees combine several transactions in one report, retain the line mapping. If one transaction is split across cost centers, use the approved allocation and keep the source total visible. Missing support remains an exception rather than a plug to make the central bill reconcile.

Classify unmatched activity precisely: report not submitted, receipt missing, cardholder departed, merchant unrecognized, personal charge under review, duplicate feed item, timing cutoff, or system mapping error. Assign the next action to the employee, manager, card administrator, security team, or finance owner according to policy. Avoid asking every cardholder to review the whole statement. A focused request should include the transaction date, merchant, amount, and required evidence without exposing other employees’ purchases.

Handle credits, disputes, and timing differences

Credits should link to the original charge and expected return. Show merchant credit date, issuer posting date, employee report treatment, and any amount difference. Do not net a credit against an unrelated expense merely because both belong to one card. Disputes also need separate states: reported, provisional credit, issuer investigation, final credit, denied, or withdrawn. A provisional credit is not final resolution. Keep the charge and dispute evidence visible until the issuer outcome and internal ledger agree.

Account for timing between authorization, posting, statement cutoff, expense submission, and ledger import. A valid late-posting transaction may belong to the next statement even if the employee submitted it earlier. Conversely, a statement charge may be absent from the expense system because integration failed. Use transaction IDs and dates to locate it; do not create a second manual expense without checking staging and prior imports. Document the approved cutoff method so month-end reviewers understand what is accrued or carried forward.

Reconcile posting and payment as separate controls

Reconcile the approved allocation to the ERP posting by account, cost object, tax treatment, currency, and total. Then treat statement payment as a separate control. AP may prepare the payment packet and identify due-date risk, while treasury or the designated owner releases funds. Confirm the payment proposal uses the correct issuer account and amount and that no duplicate direct debit is expected. After settlement, link the bank evidence and issuer application without erasing open employee exceptions.

Close the cycle when statement roll-forward, cardholder allocation, ledger entry, payment, credits, and residual exceptions reconcile. Carry each residual with an owner and review date. Analyze patterns by exception cause and program rule, not by unsupported judgments about employees. An outsourced expense-review team can perform matching and follow-up with restricted card data. Program administration, disciplinary decisions, write-offs, and payment release remain with authorized company roles.

Use a statement case with disputes and late reports

A useful test statement includes an employee report submitted after cutoff, a foreign-currency purchase, a returned item with a credit on the next cycle, a provisional dispute credit, and a cardholder who has left. Reproduce the issuer total first, then give each item its own evidence and owner. The late report becomes a timing item, the currency charge retains issuer conversion, the return stays linked across cycles, and the dispute remains open until final. Departure changes follow-up ownership but does not make the transaction disappear.

Inspect the cycle after payment as well. Tie the bank settlement to the issuer account, confirm any direct debit did not create a second payment, and roll unresolved items to the next review with stable identifiers. Compare the expense-system posting with the issuer data to find duplicate imports or missing credits. Managers should see only the transactions within their scope. This final control keeps statement payment punctual without pretending that every employee exception was solved merely because treasury settled the central account.

Protect employee and card data throughout the review. Store full account numbers and receipts only in approved systems, use masked identifiers in follow-up, and limit managers to their authorized transactions. The central statement should not circulate as a convenient attachment. Evidence quality includes proving the allocation while keeping unrelated cardholder activity and personal information out of ordinary email.

For cards closed during the cycle, confirm final charges, trailing credits, recurring merchants, and issuer closure separately. A zero balance does not prove future merchant charges stopped. Preserve administrator closure evidence and carry expected credits until they post. Review the following statement for delayed items and link them to the closed-card case. If an issuer accepts charges after closure, the card-program owner decides the dispute or merchant action while AP preserves the accounting trail.