An MCA reconciliation clause lets a merchant ask the funder to compare the fixed daily payments it collected against the agreed percentage of actual sales, then refund the excess or lower future payments. The merchant proves the sales with bank statements. A clause that works in practice is also central to treating the advance as a purchase.
What does an MCA reconciliation clause actually promise?
An MCA reconciliation clause promises that the merchant pays the agreed percentage of receipts, even though collection runs as a fixed amount. The funder debits a set daily or weekly figure estimated from past sales. When real sales come in lower, the clause gives the merchant a way to bring payments back in line with the percentage.
Most advances are sold as a purchase of a specified percentage of future receipts. Collecting an exact percentage every day is awkward unless the funder takes a split at the card processor. So many contracts set a fixed debit instead, worked out as the percentage multiplied by the merchant's average daily sales at the time of funding.
That fixed debit is an estimate. If sales hold steady, the estimate is close and nothing needs to change. If sales fall, the fixed debit becomes a larger share of what the merchant actually takes in. Reconciliation is the correction.
A typical clause covers four points:
- The specified percentage. The share of receipts the funder bought, such as 12%.
- The estimate. The fixed daily or weekly amount and how it was calculated.
- The request. How the merchant asks for a reconciliation, how often and with what proof.
- The adjustment. Whether the funder refunds the overpayment, lowers future debits, or both, and within how many days.
Some contracts also let the funder initiate a reconciliation, which can raise payments when sales rise. A clause that only runs upward, or only at the funder's choice, gives the merchant far less than one that runs both ways at the merchant's request.
Reconciliation clause arithmetic for a slow sales month
Reconciliation clause arithmetic multiplies the month's actual receipts by the specified percentage, compares the result with what the funder collected, and returns the difference. The same percentage applied to the newer, lower sales figure also gives the adjusted daily payment going forward, until the next reconciliation.
A worked example shows each step. The merchant, the figures and the contract terms are invented for illustration.
| Step | Example value | How it is worked out |
|---|---|---|
| Specified percentage | 12% | From the contract |
| Average monthly receipts at funding | $90,000 | From the statements in the original file |
| Business days a month | 21 | Assumed |
| Fixed daily debit | about $514 | 12% x $90,000 / 21 |
| Collected in the slow month | about $10,800 | $514 x 21 |
| Actual receipts in the slow month | $60,000 | From the merchant's bank statement |
| Amount owed at 12% | $7,200 | 12% x $60,000 |
| Overpayment to refund or credit | about $3,600 | $10,800 less $7,200 |
| Adjusted daily debit | about $343 | 12% x $60,000 / 21 |
The merchant in this example paid 18% of actual receipts in the slow month, not the 12% it sold. Reconciliation brings the effective share back to 12%. The refund or credit of about $3,600 is cash the merchant needs most in exactly the month it is short.
Two details change the result in practice. The first is the definition of receipts: the contract may count all deposits, only card sales, or deposits net of refunds, and each gives a different total. The second is timing. If the clause allows reconciliation only once a month and the funder takes ten days to respond, the merchant carries the overpayment for weeks before relief arrives.
Reconciliation does not reduce the total payback. The merchant still owes the full purchased amount. Lower payments stretch the time it takes to deliver it, which is the risk the funder accepted by buying a share of sales rather than lending a sum.
Bank statements a merchant sends to trigger reconciliation
The bank statements a merchant sends to trigger reconciliation cover the period being reconciled, usually the most recent full month, plus any processor statements the contract names. They have to show every deposit, so the funder can total receipts the same way it did at funding and apply the specified percentage.
Funders typically ask for:
- Complete bank statements for each account receiving business receipts, every page.
- Card processing statements when the contract counts card sales separately.
- A written request naming the period and the receipts figure the merchant claims.
- An explanation of the drop, such as a closure, a lost contract or a seasonal low, which some contracts require and others do not.
The funder's reviewer checks that the account matches the one on file, that deposits are complete and that transfers between the merchant's own accounts are not counted as sales. A merchant who has quietly moved deposits to a second account will show a sharp drop on the first account that is not a real drop in receipts. That is one reason the contract usually requires every receiving account.
Statement format matters less than completeness. Most merchants download PDFs from online banking, and funders accept them, subject to the same tamper checks used elsewhere in lending. The questions a reviewer asks about a downloaded statement are much the same as in a mortgage file, covered in whether digital bank statements are accepted for a mortgage.
Speed is the practical issue. A reconciliation that the merchant requests on the 3rd, with statements attached, and that the funder completes within a few business days helps. One that stalls for weeks while the funder asks for more documents mostly helps the funder. Clear, complete statements on the first request shorten that loop.
Why does the reconciliation clause shape an MCA's true-sale status?
The reconciliation clause shapes an MCA's true-sale status because a real purchase of future receipts leaves the funder exposed to the merchant's sales falling. Reconciliation is how that exposure shows up in practice: when sales drop, the funder collects less. Remove it, or make it hollow, and the deal behaves more like a fixed loan.
The distinction is not just a label. A loan carries interest-rate rules and other legal consequences that a purchase of receivables may not. The parties to an MCA usually want it treated as a purchase, and the contract is drafted to support that.
Several features commonly sit alongside reconciliation in that structure:
- No fixed term. Payment time depends on sales, so there is no due date for the full balance.
- No recourse for slow sales alone. If the business fails without breaching the contract, the funder takes the loss.
- A working reconciliation right. The merchant can actually obtain lower payments when receipts fall.
- Bankruptcy is not automatic default. A business closing in good faith does not by itself make the balance due.
Each feature is a way the funder shares the merchant's risk. Reconciliation is the one that touches every slow month, so a careful reviewer looks at how it works in practice, not just whether the words appear. Whether a specific contract will be treated as a loan is a legal question for counsel in the relevant state.
For a side-by-side view of how a purchase of receivables differs from a term loan in structure and cost, see merchant cash advance vs business loan compared.
Reconciliation clause wording that gives the merchant nothing
Reconciliation clause wording gives the merchant nothing when the right exists on paper but cannot be used. Common examples are a request window too short to meet, a discretion clause letting the funder refuse, document demands nobody can satisfy, or a rule that any request counts as a default. Funders and ISOs should read for these before quoting.
Drafting choices to watch:
- "Sole discretion." If the funder may decline any reconciliation for any reason, the merchant has no right, only a request.
- Impossible deadlines. A request accepted only within two days of month end, with full statements, rarely happens.
- One-way adjustment. The funder may raise payments when sales climb but need not lower them when sales fall.
- Default triggers. Language treating a reconciliation request, or the sales drop behind it, as a breach.
- Minimum payments. A floor below which payments never fall, which caps how much reconciliation can help.
A minimum payment is not always unfair, but it changes the economics. If the floor is close to the original fixed debit, the reconciliation clause barely operates. Disclosure rules in some states ask providers to state any minimum alongside the true-up terms, which is covered in the next section.
Hollow wording also changes what happens when a merchant falls behind. A funder that refused to reconcile and then declares a default for missed payments is in a weaker position than one that adjusted payments and was still not paid. How default clauses interact with reconciliation is covered in what happens when a merchant cash advance defaults.
Reconciliation disclosures in New York sales-based financing offers
Reconciliation disclosures in New York sales-based financing offers are set by the state's commercial finance disclosure rule. When a contract has a true-up mechanism, the offer summary must explain how the pre-set payment was calculated, describe the true-up and point to the contract section, and state any minimum payment terms.
The rule is New York's 23 NYCRR Part 600 commercial financing disclosure regulation from the Department of Financial Services. It defines a true-up mechanism for sales-based financing as an arrangement where the financer receives pre-set periodic payments and the contract allows the recipient to request, or the financer to initiate, adjustments, credits or charges so that the total paid more closely reflects a split rate in the contract. That definition maps closely onto a reconciliation clause.
The rule gives sample wording for the payment terms row. Its examples include a statement of how a preset daily payment was based on an estimate of a percentage of income, a statement that the recipient may receive refunds if payments exceeded that percentage in a month, with a reference to the contract paragraph, and a statement of any monthly minimum.
The rule also asks providers to include reasonably anticipated true-ups when estimating payments and the annual percentage rate. It applies when the recipient's business is principally directed or managed from New York, according to the rule's applicability section. Other states have their own disclosure rules, and funders operating across states check each.
For an underwriter or ISO, the disclosure has a practical use. The offer summary states the percentage, the estimate and the reconciliation terms in plain words, so a merchant can see before signing what relief is available in a slow month. Reading it alongside the merchant's own statement history, using a month-by-month deposit view such as the one TrueBankFlow produces, shows how often a reconciliation would likely have been triggered in the past year.