A company card transaction already represents company spend. A personal outlay can create a claim for reimbursement. A receipt explains either one but is not itself a payment instruction. If those three records enter the ledger as separate expenses, a tidy-looking stack can book the same purchase twice.
Give each record one owner
| Layer | Source of truth | What the next layer needs |
|---|---|---|
| Card issuer or feed | Card charge, settlement and refund | Stable transaction ID and posted amount |
| Expense evidence | Receipt, business purpose, coding and review | Reference to the charge or reimbursement claim |
| Reimbursement authority | Claim, approval and disbursement status | Approved amount, employee ID and payout reference |
| Accounting | Ledger posting and reconciliation | References back to approved evidence and settlement |
For a card purchase, attach evidence to the issuer’s charge. Do not turn a receipt upload into a new payable employee claim. For an out-of-pocket purchase, create one claim and carry its ID to the payment and ledger. Record a refund as a related event, not as a deletion of the original transaction.
Pick where to consolidate
Ramp for a combined card and expense layer. Ramp’s receipt guidance separates matching evidence to an existing card transaction from starting a reimbursement request. Its reimbursement guide notes that finance has to enable the workflow and can pay outside Ramp. Evaluate the combined path if you use its cards, but ask who owns payout state when another tool sends the money.
Expensify as an expense review layer. The new Expensify approval documentation describes approval of reports and how supported card expenses can be pending until the merchant posts them. If you keep the current issuer, prove that the expense review system identifies the charge and distinguishes it from an employee claim. Confirm which card connection, report workflow and accounting export are supported in the offered package.
QuickBooks Online for ledger matching. Intuit’s bank-feed guidance distinguishes matching a feed item to an existing entry from categorising it as a new entry. For a stack that exports expenses and also imports bank feeds, demonstrate the match instead of assuming that a second connector is harmless.
Test the interfaces, not the receipt scanner
Use three synthetic transactions: a company card charge with a receipt, a personal purchase and a refund. Upload the company card receipt before the charge posts. Export the reviewed items, then import the bank feed. The company charge must reconcile without a reimbursement, the personal claim must be paid once, and the refund must link to the original purchase. Replay the export and check that the receiving system does not create another posting.
If finance cannot trace the result, record where the gap is: missing card identity, missing approval, missing payout status or unmatched ledger entry. A second app that also scans receipts will not solve those failures. Compare the offered cost of card connectivity, review, reimbursement rails and accounting export, including markets and entities.
Recommendation: Keep card and reimbursement processing together if it makes authority clearer, not merely because they share a screen. Retain one ledger interface per expense type and assign someone to reconcile exceptions.
Related: integration reconciliation ownership and consolidate or integrate.