Gross funding is one of the most consequential — and most frequently misunderstood — configurations in a merchant's payment setup. The model affects how revenue appears in bank statements, how fees are tracked, and how finance teams close their books each month. Understanding it in depth is essential for any merchant processing more than a few thousand transactions per period.
How Gross Funding Works
When a cardholder completes a purchase, the acquiring bank collects the funds from the card network and prepares a settlement file. Under gross funding, the processor forwards the full face value of each transaction to the merchant's bank account without subtracting any fees. Fees owed — interchange, scheme fees, and processor markup — are aggregated and invoiced separately, typically on a monthly or bi-weekly billing cycle.
Transaction Authorised
The cardholder's issuing bank approves the payment. The authorised amount is the gross transaction value — no deductions occur at this stage.
Batch Settlement Initiated
At the end of the processing day, the settlement batch is submitted to the card networks. The processor calculates the total gross value of all transactions in the batch.
Full Amount Deposited
The processor transfers the complete batch value — 100% of gross sales — to the merchant's designated bank account within the agreed funding window (same-day, next-day, or T+2).
Fee Invoice Generated
The processor compiles an itemised fee statement covering interchange pass-through, card-scheme assessments, and its own processing fee. This invoice is sent on a pre-agreed billing schedule.
Fee Collected Separately
Fees are collected via a separate debit to the merchant's account or through a dedicated fee settlement account, keeping the revenue stream and cost stream cleanly separated in the general ledger.
Reconciliation Completed
The merchant's finance team matches gross deposits against the transaction report and fee invoices against the fee ledger during reconciliation. Two documents, two line items — clear and auditable.
Why Gross Funding Matters
Merchants operating at scale need reliable, predictable cash flow and financial reporting that withstands audit scrutiny. Gross funding directly addresses both requirements by ensuring that revenue and costs appear as separate line items in the general ledger rather than as an opaque net figure.
Studies of enterprise merchant payment operations consistently show that reconciliation errors are a leading source of financial close delays. When fees are pre-deducted, finance teams must reverse-engineer the gross transaction value from a net deposit — a process that introduces rounding errors and increases reconciliation time. According to industry benchmarks, merchants using gross funding reduce monthly reconciliation time by an estimated 20–35% compared to those on net settlement arrangements, because the bank deposit matches the processor's gross transaction report directly.
Cash flow is also meaningfully affected. A merchant processing $2 million per month at a blended fee rate of 2.1% receives $42,000 in separate fee invoices each month rather than having that sum silently subtracted from deposits. That $42,000 remains in the operating account until the invoice is due, providing a short-term liquidity buffer. For merchants with tight working capital cycles, this structural float can represent meaningful financing value. A 2023 survey of mid-market e-commerce operators found that 61% cited gross funding as a "significant factor" in choosing a processor, primarily for cash-flow management reasons.
A third consideration is dispute and chargeback handling. Under gross funding, chargeback debits typically appear as explicit line items — separate debit entries rather than adjustments to a net settlement amount. This makes dispute trends far easier to spot and respond to in real time.
Gross Funding and Float
The time between receiving a gross deposit and paying the fee invoice constitutes a form of short-term float. Merchants should account for this in cash-flow forecasting — the fee liability accrues daily even though it is settled periodically.
Gross Funding vs. Net Settlement
Both models ultimately move the same dollars, but they differ in timing, visibility, and operational overhead. The right choice depends on your transaction volume, internal finance maturity, and processor relationships.
| Dimension | Gross Funding | Net Settlement |
|---|---|---|
| Amount deposited | Full transaction value | Transaction value minus fees |
| Fee visibility | Explicit separate invoice | Implicit — deducted before deposit |
| Reconciliation complexity | Higher (two documents) | Lower (one document) |
| Cash flow | Higher gross inflow, periodic fee outflow | Consistently lower net inflow |
| Preferred by | Enterprise, high-volume, multi-currency | SMB, marketplace, embedded finance |
| Audit trail | Cleaner separation of revenue vs. cost | Revenue and cost commingled |
| Chargeback treatment | Separate debit entries | Offset against net settlement |
| Finance team overhead | Slightly higher | Slightly lower |
The key insight is that gross funding does not reduce the total fees paid — it changes when and how visibly those fees are charged.
Types of Gross Funding
Not all gross funding arrangements are identical. Processors and acquirers offer several variants that differ in funding speed and fee billing cadence.
Same-Day Gross Funding deposits transaction proceeds to the merchant's account on the same business day the batch is submitted. This is common in high-urgency verticals such as travel and hospitality. Fee invoices are typically issued weekly or monthly.
Next-Day Gross Funding (T+1) is the most widely deployed configuration. Batches submitted before a daily cut-off are funded to the merchant account the following business day. It balances speed with operational simplicity.
T+2 Gross Funding settles two business days after batch submission. It is the default for many international transactions and cross-border acquiring relationships where interbank clearing requires additional time.
Rolling Reserve Gross Funding applies to higher-risk merchants. The processor funds the gross amount but retains a percentage (typically 5–10%) in a reserve account for a defined rolling period (e.g., 180 days) to cover potential chargebacks. The full gross amount is still deposited to the main account; the reserve is held in a separate sub-account.
Multi-Currency Gross Funding deposits transaction proceeds in the transaction currency before conversion. This allows merchants to manage FX exposure independently, converting currencies at a time and rate of their choosing rather than accepting the processor's default conversion.
Best Practices
Gross funding provides significant advantages, but it requires deliberate financial and technical processes to realise those benefits fully.
For Merchants
Keep a dedicated fee reserve. Because fees arrive as a separate invoice rather than being pre-deducted, merchants should accrue the fee liability daily using the processor's transaction report. Treat the fee reserve as a payable on your balance sheet from day one of each billing period.
Automate reconciliation with your processor's API. Most enterprise processors offer a settlement reporting API that delivers gross transaction files in real time. Connecting this feed directly to your ERP or accounting platform eliminates manual matching and reduces the risk of period-end errors.
Monitor interchange costs separately from processor markup. Under gross funding, your fee invoice will typically break down interchange pass-through, scheme fees, and processor margin as distinct line items. Review each component monthly — interchange rates shift twice a year in most markets, and unexplained increases in any category signal a pricing or configuration issue.
For Developers
Design your transaction database schema to store gross amounts as the canonical transaction value. Net amounts should always be computed fields derived from the gross amount and the associated fee record — never stored as the primary value.
Use idempotent fee matching logic. When reconciling fee invoices programmatically, match on the processor's transaction reference ID, not on amount, because duplicate or partial transactions can produce identical amounts for different records. Build deduplication into your reconciliation pipeline from the start.
Implement webhooks for fee invoice events. If your processor supports event-driven notifications for fee invoice generation, subscribe to those webhooks so your system can automatically post fee accrual entries when invoices are issued, keeping your books current without manual intervention.
Common Mistakes
1. Treating gross deposits as net revenue. The most common error is booking the full gross deposit as revenue in the income statement without accruing the corresponding fee liability. This overstates revenue until the fee invoice arrives and creates a reconciling difference at period end.
2. Ignoring the fee invoice until payment is due. Fees accrue from the moment transactions are processed. Waiting until the invoice arrives to recognise the expense distorts monthly P&L and can lead to budget overruns in high-volume months.
3. Mismatching periods in reconciliation. Gross deposits and fee invoices rarely cover identical calendar periods. A deposit received on the 1st of the month may contain transactions from the last three days of the prior month. Reconciliation logic must account for these cut-off differences — aligning on the processor's transaction date rather than the bank value date.
4. Failing to account for rolling reserve releases. Merchants on rolling reserve agreements often miss reserve release credits because they appear as separate credits rather than part of the regular deposit. Ensure your reconciliation process explicitly tracks reserve balances and expected release dates.
5. Using net settlement mental models for gross-funded reporting. Finance teams accustomed to net settlement sometimes build dashboards that back-calculate gross values from net deposits. When those same teams switch to gross funding, the dashboards break. Design reporting infrastructure around gross amounts from day one.
Gross Funding and Tagada
Tagada's payment orchestration layer is designed to support gross funding configurations natively across multiple processors and acquirers. Because Tagada sits between the merchant and the underlying processors, it can normalise gross settlement reports from different acquirers into a single unified transaction ledger — regardless of whether individual processor relationships use gross funding, net settlement, or a hybrid model.
Unified Settlement Reporting in Tagada
When routing transactions across multiple acquirers, Tagada consolidates gross funding data into one reconciliation feed. Your finance team sees a single gross transaction file and a single aggregated fee report, even when underlying settlement comes from three different processors on different funding schedules. This eliminates the need to reconcile separately per acquirer and significantly reduces month-end close time.
For merchants expanding into new geographies or adding payment methods, Tagada's orchestration layer also handles the nuances of multi-currency gross funding — presenting all transactions in the base reporting currency while preserving the original transaction currency for FX management purposes.