A rental booking total, the amount owed to the vehicle supplier and the money arriving in a bank account answer three different questions. Comparing them as if they were the same number creates false discrepancies and can hide real ones.
Quick answer: reconcile each reservation to its agreed partner amounts first, then reconcile those amounts to actual remittances. Separately match payment-processor transactions to bank payouts. Keep the currency, date basis and adjustment evidence visible at every step.
This is an operator's month-end checklist, not a traveler's refund-tracing guide. It uses rental-specific categories from Orcar's ERP product documentation and public payment documentation. No real customer record, partner rate or settlement schedule is disclosed.
1. Separate sales, partner entitlement and bank cash
| Record | Question it answers | What it does not establish |
|---|---|---|
| Customer sale and payment | What was charged, collected or refunded to the traveler? | How much the supplier is entitled to receive |
| Partner settlement statement | What is due under the agreement for the eligible rentals and adjustments? | Whether that amount has reached the partner's bank |
| Processor payout and bank entry | Which funds moved to which bank account? | That every rental or partner obligation is settled |
Stripe's payout reconciliation report matches bank payouts with the batches of payments and other transactions behind them. It separates gross amounts, fees and net amounts, as well as transactions not yet paid out.[8] A processor's payout to the selling business is not automatically that business's remittance to a rental partner.
Define “sales” before comparing reports: quoted booking value, collected customer payments and accounting revenue are not interchangeable. This article concerns operational reconciliation, not revenue-recognition or tax advice. Do not label the difference between a customer price and a partner amount as profit without checking all applicable costs and accounting treatment.
2. Build a reservation-level settlement worksheet
Start with one row per reservation for agreed rental amounts. Keep separate, linked rows for each refund, adjustment and remittance allocation. This preserves a one-to-many trail rather than overwriting the original booking total.
| Field group | Keep in the worksheet | Check before closing |
|---|---|---|
| Identity and scope | Internal booking reference, partner reference, channel, currency | Is the same booking duplicated or assigned to the wrong partner? |
| Date basis | Booking, payment, pickup, return and adjustment dates; settlement period and time zone | Which event makes this rental eligible under the agreement? |
| Partner amounts | Vehicle amount, agreed protection or extras, approved credits and deductions | Which party receives or funds each line? |
| Movement evidence | Payment/refund ID, remittance reference, amount allocated to this booking | Has the same movement been counted twice? |
| Resolution | Expected amount, paid allocation, outstanding amount, reason, reviewer | Is the remaining difference explained and supported? |
Orcar's ERP documentation organizes partner reporting around reservation counts, vehicle revenue, add-on revenue, refunds and net settlement amounts. Those categories are a useful starting point, not a universal formula. An operator must still establish the contractual basis and the bank evidence; a report export alone does not prove payment.
Keep protection charges and optional extras separate where their beneficiaries differ. A discount funded by the sales platform need not have the same settlement effect as one funded by the rental partner. Resolve the agreement rather than subtracting every customer discount from the supplier's amount.
3. Work through one fictional booking
Illustrative calculation only. These amounts are invented for teaching, not Orcar prices, commissions or a customer case. Assume one KRW booking, one partner, no currency conversion, and separately resolved taxes and processing fees.
The traveler paid KRW 300,000. The agreed partner vehicle amount is KRW 240,000, and the partner is entitled to KRW 12,000 for an extra. A later customer refund is KRW 30,000. For this example only, the parties separately approve a KRW 20,000 reduction in the partner amount; the remaining refund is borne by the selling business.
| Partner-side calculation | KRW |
|---|---|
| Agreed vehicle amount | 240,000 |
| Agreed partner extra | +12,000 |
| Approved partner adjustment | -20,000 |
| Total partner entitlement | 232,000 |
| Remittance already allocated to this booking | -100,000 |
| Outstanding amount to reconcile | 132,000 |
The customer's net payment is KRW 270,000, but the partner entitlement is KRW 232,000. Neither is the outstanding KRW 132,000. The KRW 38,000 difference between net customer payment and entitlement is not a demonstrated profit figure: this example does not calculate the selling business's full costs or taxes.
Do not deduct the KRW 30,000 refund again from the KRW 232,000 entitlement. The agreed partner adjustment already accounts for the partner's share. If the refund allocation has not been agreed, mark it unresolved instead of inventing a split.
4. Investigate differences in a fixed order
- Scope and currency: use the same partner, channel and currency. Keep customer currency and settlement currency separate when they differ; preserve the actual conversion record, not today's exchange rate.
- Cutoff: distinguish the booking month from the pickup, adjustment and remittance months. An item outside the selected period can be a timing difference, not missing money.
- Line ownership: establish who receives extras, bears discounts and pays each fee. Do not assume every deduction in the payment processor's report is a partner deduction.
- Refunds and reversals: match the customer refund to its separately approved partner adjustment and check whether money already transferred must be recovered.
- Cash and duplication: match remittance references and allocations, then check failed, pending or duplicated movements. Count reservations and transactions separately.
Stripe provides a concrete example of why the fourth check matters: with its separate charges and transfers integration, refunding a charge does not automatically reverse an associated transfer. The platform must reconcile recovery separately.[7] This is a documented payment architecture, not a claim that Orcar or every rental company uses Stripe Connect in that way.
For processor-to-bank matching, Stripe's automatic-payout report groups transactions into settlement batches. Its guidance points users of manual payouts to the Balance report; instant payouts require their own transaction-history reconciliation.[8] Choose the report that fits the actual payment flow.
5. Close the period with an exception list, not a forced match
For each unresolved line, record the amount and currency, reason, evidence still needed, responsible reviewer and next review date. Useful reasons include cutoff timing, unapproved adjustment, missing remittance reference and disputed contract allocation. An explanation is not the same as resolution: leave the amount open until evidence supports closing it.
A defensible close connects the original booking, the applicable agreement, approved changes and the bank movement. It does not simply change a total until two spreadsheets agree. Use booking references rather than customer names, and redact payment details before sharing a reconciliation example outside the authorized team.
Orcar's ERP reporting categories help frame that conversation. This checklist does not promise automated bank matching, a fixed payout date or a measured reduction in errors. For the underlying record structure, read inside a car rental reservation system. For the customer-side problem, use how to trace a missing rental refund.
Discussing an operational workflow with Orcar? Bring a redacted sample containing the columns above through the contact options on Orcar. Leave real customer documents and confidential partner rates out of the initial inquiry.
6. Frequently asked questions
Should booking sales equal the partner payout?
No. Sales, contractual partner entitlement and money remitted have different definitions. Reconcile the supported bridge between them instead of expecting identical totals.
Does refunding a traveler automatically recover a partner payment?
Do not assume it does. Check the payment architecture and agreement. Stripe's separate-charges-and-transfers example explicitly requires separate reconciliation of associated transfers.[7]
Can one bank transfer cover several bookings?
Yes. Keep the bank reference once and allocate its amount to the relevant bookings without counting the whole transfer repeatedly. Stripe's processor payout reports likewise group multiple transactions into batches.[8]
Is an unexplained difference a loss?
Not necessarily. First check scope, dates, currency, approved adjustments and cash evidence. Do not dismiss it as timing, or call it a loss, without supporting records.
Sources and scope: [8] Stripe: Payout reconciliation report. [7] Stripe: Separate charges and transfers. Checked September 23, 2026. Orcar product descriptions reflect documented reporting scope, not a live reconciliation audit. The generated hero is a conceptual ledger visualization, not an ERP screenshot or financial chart.