To connect a restaurant sale to a bank payout, follow the payment transaction ID from the POS or payment report to the processor’s settlement record, then follow the settlement or payout reference to the bank deposit. Check dates at each step: the sale date, settlement date, payout date, and bank posting date can differ.
The amounts matter, but they are not enough on their own. A deposit may combine many payments, subtract refunds and fees, or cover a different period from your POS business day. The goal is to identify the records behind the deposit and explain each adjustment, rather than force two daily totals to agree.
Collect reports that can be joined
Start with one bank deposit and work backward. For that deposit, collect the processor’s payout detail, its settlement or batch detail, and the POS transaction export for the relevant period. Also gather refund and fee records if they are not included in those reports. Download the underlying rows, not just daily summary screens.
The POS export should show each payment’s date and time, amount, payment method, and transaction or payment reference. An order number is useful for finding the guest check, but it may not be the reference the processor uses. If a check has split tenders or multiple card payments, look for a separate payment record for each part.
The processor’s records should show which payments entered a settlement or batch and which settlements or adjustments entered a payout. Look for the transaction reference, settlement or batch ID, payout ID, gross amount, refunds, fees, and net amount. Names vary by provider, so ask for a sample export and a field description rather than assuming that two fields with similar names are identical.
Finally, get the bank statement or deposit activity showing the amount, posting date, and any deposit reference. Bank descriptions can be abbreviated, so the processor’s payout report is often the better bridge between the deposit and individual payments. Protect these exports: use approved access and avoid sharing full card details when asking for help.
Before buying or changing systems, ask whether the restaurant POS and payment provider can export these fields for every payment channel you use. For restaurant integrations, ask which reference survives the handoff and whether refunds appear in the same export or a separate report.
Map the identifiers and timing rules
Think of the records as a chain. An order or check ID identifies what was sold. A payment transaction ID identifies a payment against that check. A settlement or batch ID groups payments or adjustments for processing. A payout ID identifies money the processor sends to the bank. One order can have more than one payment, and one payout can contain more than one settlement.
Use the exact reference when the same value appears in two reports. If the POS shows one ID and the processor shows another, ask for the cross-reference or integration mapping. Amount and time can help locate a candidate record, but they do not prove a match when two guests pay the same amount close together. Note whether a refund references the original payment, has its own transaction ID, or both.
Dates need their own map. A sale timestamp tells you when the payment occurred; a settlement date tells you when it was grouped or processed; a payout date tells you when the processor sent the payout; and a bank posting date tells you when the deposit appeared. Your POS business day may also close at a different time from the processor’s cutoff.
Ask the processor for its cutoff time, time zone, weekend and holiday schedule, and treatment of payments that miss the cutoff. Ask whether payout dates mean initiation or expected arrival. Then compare the bank’s actual posting date. Do not assume a Monday deposit represents only Sunday sales or that every provider follows the same schedule.
For a practical handoff, write down the field names from each export and the rule used to join them. For example: “POS payment reference equals processor transaction reference; processor payout ID equals payout detail ID.” If a link is unavailable, mark it unresolved rather than filling it in from an amount alone.
Work backward through a hypothetical payout
Suppose a processor payout report shows payout P-41 for $378, and the bank posts a $378 deposit with a reference that points to P-41. The payout detail lists three settled payments, one refund, and a processing fee. The amounts below are hypothetical; they illustrate the match, not any provider’s pricing or payout schedule.
| Record | Reference and date | Amount | Connection |
|---|---|---|---|
| Payment | T-101, sale Monday | +$200 | Settlement S-7 |
| Payment | T-102, sale Monday | +$140 | Settlement S-7 |
| Payment | T-103, sale Tuesday | +$80 | Settlement S-7 |
| Refund | R-12, Tuesday | −$30 | References T-102; included in P-41 |
| Processing fee | F-4, payout detail | −$12 | Included in P-41 |
| Bank deposit | P-41, posted Thursday | $378 | Matches payout detail |
The table shows a complete chain for this example: the POS payment references match the processor transactions, settlement S-7 appears in payout P-41, and the bank deposit points to P-41. Gross payments are $420. Subtract the $30 refund and $12 processing fee, and the payout is $378. The fee shown is a processing deduction, not an all-in operating cost. No fixed charges or other exception costs are included in this example; add them only if the relevant records show them.
This also explains why Monday’s POS total of $340 does not equal the Thursday deposit. P-41 includes a Tuesday payment and adjustments as well. The dates are example inputs, not a rule that these days must always be grouped together.
Now suppose T-103 is absent from the POS export but appears in S-7. Do not call the $80 an extra sale or remove it from the payout calculation. First expand the POS date range and check the business-day cutoff. Then search by the processor reference and review the relevant payment channel. If it remains missing, keep the payout matched to the bank but mark that transaction’s POS link unresolved.
Likewise, do not add an estimated fee just because a deposit is smaller than gross sales. Find a recorded deduction or ask the processor to explain the difference. A refund should be matched to its own record and, where available, to the original payment; it may appear in a later payout than the sale.
Assign unresolved items and choose a workable process
Keep an exception log alongside the matched records. For each item, record the payout ID, transaction or order reference, amount, relevant dates, what has already been checked, owner, and next follow-up date. Separate a missing POS-to-processor link from a payout-to-bank difference. They may need different people and different evidence.
- Missing POS payment: Ask the POS provider or integration owner to locate the payment by order ID, timestamp, amount, and any processor reference. Include the channel and location.
- Missing settlement or payout link: Ask the payment processor which batch and payout contain the transaction, or whether it is still pending or was excluded.
- Unexplained deduction or refund: Ask the processor for the adjustment reference, date, and payout in which it appears. Check the POS refund record separately.
- Payout sent but bank deposit not found: Confirm the payout reference, amount, and destination details with the processor, then ask the bank to trace the deposit using the available reference.
Give each item one owner even when several providers must help. Close it only when the missing link or documented explanation is attached. If a provider cannot supply a durable cross-reference, decide how much manual searching your team can support before signing the agreement.
During a buying discussion, request sample exports covering a sale, a split payment, a refund, a settlement, and a payout. Ask how long the records remain available, whether exports include all locations and channels, and who investigates a broken link between systems. The integration questions and this guide to direct integration or middleware can help frame the handoff discussion.
Next, take one recent payout and its related reports to a POS provider. Ask the provider to show which fields connect the sale, settlement, payout, and bank deposit, and to identify who owns any missing link. Discuss those requirements for your locations and payment channels before choosing a setup.
Frequently asked questions
Is an order ID the same as a payment transaction ID?
Not necessarily. An order ID identifies the check or order; a transaction ID identifies a payment. One order can have multiple payments, so retain both references when they are available.
Why does a payout differ from the POS sales total?
The payout may cover a different time window or include recorded refunds and deductions. Match the individual records and dates before deciding that the difference is an error.
What should I do when a payout has no matching bank deposit?
Confirm the payout amount, date, reference, and destination with the processor. Then provide the available deposit reference to the bank for tracing, and keep the item open until it is explained.
