BlogCommerce
Matching payments to orders: references, differences and review
A smaller payout may include fees and refunds without creating customer debt. Reconcile orders and bank deposits using their own references.
Order and deposit reconciliation tests
Ten synthetic charge, fictional-fee, refund, ambiguous-reference and repeated-file reconciliation cases.
Compare orders, payments and deposits in separate views
Matching a payment to an order means verifying which purchase it belongs to and how much it covers, using reference and currency. Reconciling the provider’s bank deposit answers a different question: which charges, fees, refunds and adjustments form the amount reaching the bank. Mixing the tasks can make you charge a provider fee to a customer or mark an order paid merely because an amount matches.
Stripe documents that its payout reconciliation report matches a payout with a batch of transactions and is designed for automatic payouts; manual or instant payouts have different conditions. Its balance transaction record distinguishes gross amount, fee and net impact. These are Stripe capabilities. Verify your provider’s references and reports before designing matching rules.
| View | Compares | Useful outcome |
|---|---|---|
| Order | Agreed total against allocated payments and corrections | Paid, partial, excess or under review |
| Provider | Gross charges, fees, refunds and adjustments | Net balance explained per movement |
| Bank | Deposit against settlement batch and date | Identified deposit or open difference |
Worked example: a smaller deposit does not mean unpaid customers
| Movement | Gross or refund | Illustrative fee | Net impact |
|---|---|---|---|
| PAY-A for PA-50 | 1,200 | 36 | 1,164 |
| PAY-B for PB-51 | 800 | 24 | 776 |
| Refund RE-A | − 200 | 0 | − 200 |
| Batch total | 2,000 − 200 = 1,800 | 60 | 1,740 |
| Bank deposit BAN-8 | 1,740 | Already included above | Batch difference = 0 |
PA-50 retains its original 1,200 payment and 200 refund as separate records; net retained collection is 1,000 after the authorized correction. PB-51 retains 800 paid. The 1,740 deposit is explained by 2,000 collected minus 60 fees and 200 refund. Comparing only 2,000 against 1,740 creates an apparent 260 shortfall that does not represent buyer debt.
For the demonstration, link PAY-A and PAY-B to orders, RE-A to PAY-A and BAN-8 to LIQ-8. Retain charge time, provider availability date and bank date too. Stripe states that the report uses estimated arrival date and reconciliation data may become ready after a deposit arrives. Temporary absence in a report does not prove that the buyer failed to pay.
An amount-only match can be ambiguous
Reset with two separate 500 orders and one 500 transfer without enough reference information. Do not assign money to the first row. Record it as received but unidentified, gather permitted evidence and request collections review. Once one order is identified, allocate 500 to that order once. The other remains pending; importing the same transfer again cannot pay it too.
In a separate test, a 900 order receives an identified 600: it is partially paid with 300 outstanding. A 950 payment creates a 50 difference requiring an authorized decision; do not conceal it by changing the order price. Decide whether a small difference is reviewed, retained as credit or corrected and who may authorize it. These operational rules belong to the company.
Identify which record has authority
- Order: accepted version, amount, currency and customer.
- Payment: provider or bank, receiving account, unique reference, amount, currency and confirmed outcome.
- Allocation: receiving order, allocated amount, owner and evidence.
- Deposit: batch, net components, date and bank movement.
- Review: reason, responsible person and next action; a screenshot does not replace all these records.
Separate test environments from real charges, as well as different accounts and currencies. The same number in MXN and USD is not the same amount. When multiple currencies are involved, retain amounts and conversions reported by each source and review scope with the account owner. A first stage can use authorized files while integration access remains unverified.
Tests before marking orders as paid
- Normal: an identified confirmed payment covers an order with a reconstructable allocation.
- Exception: ambiguous references or different currency remain under review rather than matched by amount alone.
- Retry: importing the same payment or batch twice retains one allocation and one linked deposit.
- Correction: a refund retains the original charge and changes net value through a separate record.
- Closing: every deposit is explained by its components; differences retain an owner and evidence rather than disappear through anonymous adjustments.
The free worksheet includes ten synthetic tests. Use anonymized exports and record observations; it contains no actual rates or accounting recommendations. The collections guide covers customer balances, and repeated payment notices distinguishes duplicate notification from a second charge. When assessing retail software, begin with a discrepancy your team cannot currently explain.
Frequently asked questions
Not when several purchases could match. In the two 500-order test, a transfer without a reference stays unidentified until its destination is resolved.
The customer paid in full in this example. The fee affects the provider’s net balance rather than becoming buyer debt.
Retain the payment and allocation, show the remaining or excess amount and record the authorized decision. Do not change prices to conceal a difference.
Not necessarily. Check the authorized payment result and each report’s date or cutoff; retain a review state while evidence is missing.
Sources
Last updated: