Revenue Doesn’t Match Finance: A Step‑by‑Step Reconciliation for eCommerce and Omnichannel

If your sales dashboard shows one number while the general ledger (GL), bank, or processor reports show another, you’re not alone. This tutorial walks you through a repeatable, audit‑friendly reconciliation from operational sales to GAAP revenue, cash, AR, and deferred revenue—grounded in ASC 606 and practical payment settlement flows.

• Difficulty: Intermediate (accounting familiarity helps)
• Time required: 2–6 hours for a monthly cycle (varies with volume and tooling)
• Prerequisites: Access to sales/order exports, payment processor settlement reports, bank statements, GL/accounting system, and (if used) a revenue recognition subledger
• Good to know: Under ASC 606, revenue is recognized when performance obligations are satisfied (timing matters), not necessarily when cash settles—see the five‑step model in Deloitte’s revenue recognition roadmap (2024–2025) and the timing objective for Step 5 in Deloitte DART’s timing discussion.

Note: This guide is practical education, not legal/audit advice. For complex scenarios (bundled POs, loyalty programs, principal vs agent), consult your Controller or CPA; the high‑level frameworks in EY’s ASC 606 overview (2025) and KPMG’s revenue recognition handbook (2024) are helpful references.

First, align on definitions

Before you reconcile, make sure everyone means the same thing by “revenue.”

• Gross sales / GMV: Operational sales value before discounts, returns, and taxes. Often what BI dashboards show.
• Net sales: Gross sales minus discounts and returns (and sometimes shipping/taxes depending on the report definition).
• GAAP revenue (ASC 606): Recognized when performance obligations are satisfied. This may differ from order date or cash date—see the five‑step model in Deloitte’s roadmap summary.
• Cash: Bank deposits or processor balance transfers. Presentation and classification in the cash flow statement should follow ASC 230; see KPMG’s Statement of Cash Flows handbook (2024).
• Accounts receivable (AR): Amounts billed or earned but not yet collected.
• Deferred revenue (contract liability): Cash (or billings) received for goods/services not yet transferred; see contract liabilities discussions in EY’s ASC 606 guidance.

Why this matters: Mismatches often come from timing (recognition vs cash), fees/chargebacks, taxes/shipping classification, or incomplete data.

---

Step 0 — Frame the mismatch

What to do

1. Identify the exact gap(s):
   • Sales dashboard vs GL revenue
   • GL revenue vs bank cash
   • Processor payouts vs bank deposits
   • AR or deferred revenue vs operational schedules
2. Quantify by period (e.g., monthly) and by channel/tender.

Why

• Precise framing narrows the data you need and speeds troubleshooting.

Sanity check

• Can you state: “In July, dashboard sales exceeded GL revenue by $X; processor payouts were $Y lower than dashboard due to fees/refunds.” If no, refine the scope.

---

Step 1 — Collect the source data (completeness first)

What to do

• eCommerce platform(s) (e.g., Shopify, marketplaces): Export orders with at least
  • Order/Invoice ID, order date/time (with timezone), fulfillment/shipping date, payment status, tender type
  • Gross sales, discounts, shipping income, taxes collected, refunds/returns
  • Currency and exchange rate if multicurrency, channel/location, processor reference
• Payment processor(s) (e.g., Stripe, Adyen, PayPal, Square): Export settlement/payout reports. For Stripe, the Balance summary report and Payout reconciliation report provide charges, refunds, disputes, fees, reserves, and payout‑to‑transaction linkages. Stripe’s guidance on reconciliation is summarized in Payment reconciliation 101.
• Bank: Statement (CSV/PDF) with posting date, amount, description; include weekends/holidays.
• GL/accounting system: Trial balance and account activity for revenue, cash (by bank), undeposited funds/clearing, AR, deferred revenue/contract liability, sales tax payable, shipping income, merchant fees, chargebacks.
• Revenue recognition subledger (if applicable): Contract assets (unbilled AR), contract liabilities (deferred revenue), schedules.

Why

• Without complete datasets, you’ll chase ghosts. Processor and bank coverage for every day in the period is crucial; settlement timing varies—see Stripe’s payout and settlement timing explainer.

Sanity check

• Do transaction counts per channel match your BI? Are all processor payout days present? Any missing bank days around weekends or month‑end?

---

Step 2 — Normalize and segment your data

What to do

• Build a reconciliation template (spreadsheet or database) with columns like:
  • Date, Source system, Channel, Tender type, Transaction ID, Order/Invoice ID
  • Gross sales, Discounts, Tax, Shipping income
  • Processor fees, Chargeback fees, Refunds, Chargebacks, Adjustments/Reserves
  • Net to settle, Payout ID, Payout date, Bank deposit date
  • GL posting reference, Status (matched/unmatched), Notes
• Standardize identifiers (order IDs, payout IDs). Normalize timezones.
• Segment by tender type (card, PayPal, BNPL, COD) because settlement timing differs.

Why

• A consistent schema enables deterministic matching rules.

Sanity check

• Spot‑test a day: Do gross sales minus discounts/refunds equal the processor gross less refunds (before fees)? If not, flag timing or data gaps.

---

Toolbox — Software you can use (neutral, parity‑based)

• WarpDriven — ERP/operations platform that integrates sales channels, processors, bank, and GL for multi‑channel reconciliation and automation. Disclosure: WarpDriven is our product.
• NetSuite general ledger — ERP/GL with bank and account reconciliation features and audit trails; see also NetSuite’s account reconciliation overview.
• Oracle Fusion Cloud ERP — Enterprise ERP with revenue management and reconciliation tooling (vendor documentation applies).
• QuickBooks Online or Xero — SMB GL systems with bank feeds and reconciliation workflows.
• Payment processors: Stripe/Square provide detailed payout and fee exports; see Stripe’s Balance summary and Payout reconciliation docs; Square’s fees are described in Square’s fee guide.
• Reconciliation platforms (e.g., BlackLine) — Close orchestration, certifications, and auto‑matching templates useful for high‑volume teams.

Selection tips

• Consider transaction volume, number of channels, required audit trail, learning curve, and integration coverage. Enterprise ERPs reduce swivel‑chairing but require implementation effort; SMB systems are fast to adopt but may need add‑ons.

---

Step 3 — Tie sales to processor settlements

What to do

1. Match orders to processor transactions using:
   • Order/Invoice ID (or metadata), amount, and a date window (±2 days) to account for authorization vs capture timing.
   • Separate by payment method to reflect different settlement cadences.
2. Reconcile components:
   • Start from operational gross; subtract discounts and refunds.
   • Compare to processor charges less refunds; then isolate fees, disputes, and reserves to arrive at net to settle.
3. If you use Adyen or similar, leverage invoice/payout reports (e.g., Adyen’s IPAR) to categorize fees and adjustments; see Adyen’s invoice reconciliation (IPAR) overview.

Why

• Processor statements reflect fees, disputes, and reserves that explain why payouts differ from sales. Stripe’s payout recon report explicitly links payouts to underlying transactions; see Stripe Payout reconciliation report.

Sanity check

• Does sum(processor gross less refunds) ≈ operational gross less refunds for the period, aside from timing? If not, investigate partial captures, cancellations after shipment, duplicate orders, or missing methods (e.g., PayPal off‑Stripe).

---

Step 4 — Tie processor settlements to bank deposits

What to do

• Group transactions by payout ID and match each payout’s net amount to a bank deposit.
• Allow for weekend/holiday delays and failed payouts that are reissued on a later date.

Why

• The bank is the cash truth. Payout‑to‑bank matching confirms funds actually arrived; timing nuances are common—see settlement timing in Stripe’s explainer.

Sanity check

• Can you account for every payout ID with a bank deposit of the same amount (date may vary within 1–3 days)? Any extra bank deposits without a payout reference are red flags.

---

Step 5 — Tie bank to GL cash

What to do

• Run bank reconciliation in your GL and ensure the sum of matched deposits equals bank statement totals for the period.
• Investigate entries in undeposited funds/clearing or suspense accounts; clear duplicates and mispostings. For general concepts and process, see NetSuite’s cash reconciliation overview.

Why

• This confirms recording of cash in the accounting system. Presentation in the statement of cash flows should align with ASC 230—see KPMG’s Statement of Cash Flows handbook (2024).

Sanity check

• Do GL cash movements equal reconciled bank deposits for the period after timing differences? Any residuals should be in a clear reconciling‑items list with due dates.

---

Step 6 — Align GL revenue with ASC 606 (recognition timing)

What to do

• Confirm when performance obligations are satisfied (transfer of control) for your goods/services. If you recognize on shipment or delivery, align orders accordingly; principles summarized in Deloitte DART’s timing objective for Step 5.
• Review contract assets (unbilled AR) and contract liabilities (deferred revenue). Update schedules and compare to operational data; over‑ or under‑recognition will create gaps—see KPMG’s revenue handbook (2024).
• Estimate and recognize variable consideration and returns liabilities with appropriate constraints; judgment guidance appears in KPMG’s Topic 606 executive materials and EY’s ASC 606 materials.

Why

• Operational “sales” can differ materially from GAAP revenue because recognition follows satisfied performance obligations, not order or cash dates.

Sanity check

• Do deferred revenue movements and revenue recognition entries explain the gap between operational sales and GL revenue? Compare returns liability to actual return rates for the period.

---

Step 7 — Post adjusting entries (JEs) and reclasses

What to do

• Prepare JEs for fees, chargebacks, timing differences, reclasses (taxes/shipping), and deferrals/accruals. Obtain reviewer approval before posting.

Examples (illustrative; adapt with your CPA/Controller):

# Processor fees netted in payouts
Debit  Merchant Fees Expense       XXX
  Credit Cash (Bank/Processor)        XXX

# Chargeback recorded by processor
Debit  Chargeback Expense          XXX
  Credit Cash (Bank/Processor)        XXX

# Refunds (if not already captured via returns workflow)
Debit  Sales Returns (Contra Rev)  XXX
  Credit Cash / AR                    XXX

# Deferred revenue recognition (monthly)
Debit  Deferred Revenue            XXX
  Credit Revenue                     XXX

Why

• Clean postings make the reconciliation sustainable and audit‑ready. Keep support from processor reports (fees/chargebacks) and rev‑rec schedules (deferrals).

Sanity check

• After posting, do your tie‑outs close? Residual immaterial items should be documented with a plan to resolve.

---

Step 8 — Document the reconciliation package and controls

What to do

• Archive: source exports (orders, processor reports, bank statements), matching evidence, JE support, and a reconciling‑items log with owners and due dates.
• Sign‑offs: preparer and independent reviewer with dates. Maintain segregation of duties where feasible. Systems like NetSuite and reconciliation platforms help retain audit trails—see NetSuite account reconciliation overview.
• Frequency: High‑volume cash/processor accounts often merit weekly review; many organizations document monthly as a minimum per internal policy examples such as the U.S. VA’s reconciliations policy on frequency and documentation.

Why

• Auditors should be able to reperform your reconciliation from the package alone.

Sanity check

• Could a new reviewer replicate your tie‑outs using only the package? If not, add missing evidence or explanations.

---

Step 9 — Prevent recurrence: harden your process

What to do

• Data discipline: Standardize identifiers across systems, enforce timezone norms, and ensure daily completeness checks.
• Cutoffs: Document month‑end cutoff rules for late settlements and weekend/holiday delays.
• Automation: Where volume is high, consider auto‑matching and certification workflows (e.g., ERP or reconciliation tools). Stripe provides APIs/report automation; see Stripe’s report options.
• Reviews: Schedule periodic variance reviews by channel/tender to catch drift in fees, disputes, or return rates.

Why

• Consistency reduces month‑end surprises and speeds close.

Sanity check

• Are open reconciling items aging down each month? If not, add owners and deadlines.

---

Troubleshooting matrix: symptoms → likely causes → actions

---

Quick reference: fields to export (checklist)

• Orders/sales: Order ID, order date/time (TZ), fulfillment/shipping date, payment status, tender type, gross, discounts, shipping income, tax, refunds, channel/location, currency, FX rate, processor reference.
• Processor settlements: Transaction ID, order/invoice reference, gross, refunds, disputes/chargebacks, processing and chargeback fees, adjustments/reserves, currency, FX rate, available_on date, payout ID/date, net amount.
• Bank: Posting date, amount, description; ensure complete coverage across weekends/month‑end.
• GL: Revenue, cash (by bank account), undeposited funds/clearing, AR, deferred revenue, merchant fees, chargeback expense, sales tax payable, shipping income/expense activity.
• Rev‑rec subledger: Contract assets (unbilled AR), contract liabilities (deferred revenue), recognition schedules.

For payment‑specific guidance, see Stripe’s reconciliation resources and their detailed report documentation. For GL concepts and reconciliations, see NetSuite’s GL overview.

---

FAQs and pro tips

• Should I reconcile weekly or monthly? High‑volume teams benefit from weekly sales→payout matching and monthly GL tie‑outs. Daily spot checks around month‑end reduce close pressure.
• How do I handle multicurrency? Track transaction and settlement currencies and use processor FX rates when available; reconcile realized FX differences in GL.
• Where do sales taxes go? Generally outside revenue; ensure taxes collected are recorded to sales tax payable. Confirm classification with your Controller.
• What about shipping income and costs? Decide whether shipping income is part of revenue or other income; consistently classify shipping expense (COGS or operating) and reconcile to carrier invoices.

---

Next steps

• Operationalize this process with a standard template, monthly calendar, and reviewer checklist. If volume or channel count is growing, consider an ERP or reconciliation platform to automate ingestion, matching, and certifications.
• If you’re exploring integrated options, you can evaluate the tools in the Toolbox section above based on your size and complexity.

Thank you for taking the time to build a tighter, ASC‑606‑aligned reconciliation. A methodical approach now saves hours every month—and keeps auditors happy later.