Payment ReconciliationMerchant Operations

Gross to Net Settlement: Build a Bridge That Explains Every Difference

By PayEurasia Team · 11 October 2026 · 4 min read

Last updated 11 October 2026

Gross to Net Settlement: Build a Bridge That Explains Every Difference

Reconcile gross collections to a net settlement using signed fees, refunds and adjustments, with a worked example and exception checklist.

Header image: conceptual illustration.

Finance collected a large gross amount, but the bank received a smaller settlement. The difference is not automatically a loss or a hidden fee. It may contain refunds, fees, reserves, releases, timing differences or transactions excluded from that particular batch.

A gross-to-net bridge explains each component with a sign, source record and reporting scope. This article focuses on that bridge rather than the broader timing overview in the settlement cycles guide.

Start with the correct population

Define the provider, merchant account, settlement identifier, currency and reporting period before adding amounts. Gross collections for a calendar day may not be the population settled in one bank deposit. Some payments become available later or belong to another batch.

Use the provider's actual batch membership where available. If it is unavailable, document the alternative balance-based reconciliation rather than implying a precise transaction-to-deposit map exists.

Stripe's payout reconciliation documentation explicitly distinguishes its automatic-payout report from manual-payout and balance-report use cases. It also notes that instant payouts do not have the same transaction attribution. This is a useful reminder to select a report that supports the desired conclusion.

Build signed components, not one unexplained deduction

Begin with the gross value of the included successful collections. Subtract separately identified refunds, fees and other supported deductions. Add documented releases or credits. Then explain any reserve movement or other contractual adjustment using the provider's own records.

Every component needs a definition. A fee already included in a transaction's net amount must not also be subtracted from that net subtotal. A reserve hold is not automatically the same as an expense. Have finance apply the appropriate accounting treatment instead of letting an export label decide it.

Stripe's payout report schema documents currency and gross, fee and net fields. Read the selected report's units and signs; they are not interchangeable with amount representations in every API.

Following the signed amounts to the bank

Invented example: A fictional BDT settlement batch contains BDT 50,000 in gross included collections. It includes BDT 2,000 in refund adjustments, BDT 600 in fees and a BDT 1,000 documented hold. A prior BDT 500 hold is released into this batch.

The expected net is BDT 50,000 minus BDT 2,000 minus BDT 600 minus BDT 1,000 plus BDT 500, or BDT 46,900. These figures are invented arithmetic, not PayEurasia rates, reserve requirements or service terms.

If the bank credit is BDT 46,850, the remaining BDT 50 difference becomes a specific exception. Finance checks documented bank deductions, report completeness and posting dates. It does not invent an additional fee to force the bridge to balance.

The report retains the original rows and evidence for each component so another reviewer can reproduce BDT 46,900 without relying on a manually edited spreadsheet total.

Keep foreign currency out of a local-currency shortcut

Do not add BDT gross collections to USD refunds or fees. Reconcile each currency independently, then introduce an explicit conversion step only where a documented provider conversion occurred.

Record source amount and currency, settlement amount and currency, and actual provider adjustment. An internally estimated rate may help forecast cash, but it cannot replace the settlement record. Rounding residuals should be visible rather than hidden inside an invented fee.

For broker operations, preserve the separation between a customer's credited account and the merchant settlement. The broker reconciliation guide covers that account-matching context; a bank deposit is not itself a new customer credit.

Investigate a bridge that does not balance

Check completeness first: pagination, report readiness, excluded accounts, changed export columns and duplicated imports. Then check timing: a refund adjustment or fee may belong to a different settlement period from its original payment.

Inspect signs before changing data. Negative amounts can represent legitimate refunds or deductions. Taking the absolute value of every row destroys the financial meaning. Finally, verify bank posting and settlement identifiers instead of matching deposits solely by total amount.

Bridge review checklist

  • All rows belong to the defined account, batch and currency.
  • Gross, net and fee units are documented.
  • Every adjustment has a source identifier and sign.
  • Refunds and fees are not deducted twice.
  • Holds and releases receive approved accounting treatment.
  • Actual bank credits are matched separately from expected settlement.
  • Unexplained differences remain in the reconciliation exception process.

Before accepting a settlement difference

Can a lower net deposit still be correct?

Yes, if documented deductions and batch membership explain it. The bridge should demonstrate that explanation rather than presume it.

Should we tolerate small differences automatically?

Use an approved materiality policy, but retain the difference and reason. Repeated small unexplained amounts can reveal a systematic error.

Talk to PayEurasia

Working in a high-risk vertical across South Asia? We can probably help.

Request integration →

Related articles

View all articles →