MCA reconciliation request: how to draft and deliver a formal invocation letter.
Reconciliation invocation is the operative workout mechanism when revenue has declined but default has not yet been triggered. Six components structure a defensible letter: contract clause citation with specific section reference and quoted language, revenue decline documentation with underwriting baseline vs current comparison, reconciliation calculation methodology applying Specified Percentage of receivables to actual revenue, proposed reconciled withdrawal amount with effective date, delivery method compliance with contract-specified requirements, and response deadline request typically 5-10 business days. Assembly protocol runs Days 1-3 (contract analysis prerequisite), Days 4-7 (revenue decline documentation and calculation), Days 8-10 (letter drafting and delivery). Five funder response scenarios follow — immediate engagement, negotiation dialogue, delayed response, refusal, or silence — each with specific follow-through protocol. Verbal reconciliation requests rarely produce enforceable outcomes; written letters with proper components produce meaningfully better results.
If you have documented revenue decline on an active merchant cash advance and want to formally request a reduced daily withdrawal amount before default is triggered, the reconciliation invocation letter is the operative mechanism. Reconciliation is the specific contractual right built into most MCA agreements — the theory being that funders purchase a Specified Percentage of future receivables rather than lend principal, so declining receivables should produce proportionally reduced withdrawal amounts. Whether reconciliation actually works depends less on the theory and more on how the invocation is drafted, documented, and delivered.
This guide is a procedural protocol for drafting and delivering a formal reconciliation request. Six components structure a defensible letter: contract clause citation, revenue decline documentation, reconciliation calculation methodology, proposed reconciled withdrawal amount, delivery method compliance, and response deadline request. Assembly takes 10 days when documented properly. Funder response falls into five recognizable scenarios (immediate engagement, negotiation dialogue, delayed response, refusal, silence), each with specific follow-through protocol. Cases that skip the drafting protocol and proceed with verbal reconciliation requests or informal written notes typically produce weak funder response regardless of underlying revenue decline documentation. The letter matters — the procedural quality of the invocation shapes funder disposition and downstream leverage.
MCA reconciliation request is a formal written invocation of the reconciliation clause requesting recalculated daily withdrawal amount based on documented revenue decline. Six components structure the letter: (1) contract clause citation with section reference and quoted language, (2) revenue decline documentation with underwriting baseline vs current comparison via bank statements and merchant processor records, (3) reconciliation calculation methodology applying Specified Percentage of receivables to actual revenue, (4) proposed reconciled withdrawal amount with effective date, (5) delivery method compliance with contract-specified requirements including certified mail or delivery-confirmed email, and (6) response deadline request typically 5-10 business days. Assembly runs Days 1-3 (contract analysis prerequisite), Days 4-7 (documentation and calculation), Days 8-10 (drafting and delivery). Five funder response scenarios follow: immediate engagement, negotiation dialogue, delayed response, refusal, or silence. Refusal escalates to Strategy 3 negotiated forbearance or Strategy 5 Subchapter V filing under 11 U.S.C. § 362. The April 2026 Subchapter V eligibility ceiling at $3,424,000 accommodates most closely held businesses when reconciliation cannot deliver resolution.
Six components of a defensible reconciliation request letter.
The reconciliation invocation letter is a procedural document. Its purpose is to invoke the contractual reconciliation right in a manner that funder counsel cannot procedurally reject, that funder underwriting cannot dispute on documentation grounds, and that produces enforceable outcomes when the funder engages. Six components structure the letter. Omission of any component typically weakens the invocation procedurally and reduces funder engagement.
Component 1: Contract clause citation with quoted language
The letter must specifically cite the reconciliation clause in the underlying advance agreement. Cite: contract origination date, contract reference number, section number and subsection where reconciliation clause appears, page number, and the specific language of the reconciliation clause quoted verbatim. The quoted language demonstrates the borrower's contractual right and forecloses funder counsel arguments that reconciliation is not a contract-specified mechanism. Contracts with strong reconciliation language (unambiguous right to request, objective methodology, enforceable obligation) produce the strongest citations. Contracts with weak reconciliation language (discretionary funder review, subjective determinations) still support invocation but with weaker leverage.
Cases with multi-MCA exposure require parallel citation across all contracts — each contract's reconciliation clause is cited separately in its own invocation letter. Funders cannot be aggregated into a single invocation letter because reconciliation is contract-specific.
Component 2: Revenue decline documentation
The letter must document revenue decline with evidence the funder can verify. Primary documentation is bank statements — the funder underwrote against historical bank statement analysis and can verify current statements against that baseline. Include: bank statements covering the underwriting baseline period (typically 3-6 months preceding advance origination), bank statements covering the current period (typically 3-6 months preceding invocation), and a comparative revenue analysis table showing average daily revenue during baseline vs current with dollar amounts and percentage decline.
Merchant processor statements provide additional documentation for card-processing revenue. Some cases benefit from additional documentation: accounting records (QuickBooks, Xero exports) showing revenue trends, evidence of specific causes for decline (customer loss, industry conditions, operational disruption), and forward-looking projections if requested by the funder. Documentation quality directly correlates with funder engagement — well-documented invocations produce meaningfully better response than general assertions.
Component 3: Reconciliation calculation methodology
The letter must show the reconciliation calculation methodology with all math steps. Step one: cite the Specified Percentage from the contract (typically 12-18 percent range in most MCA contracts). Step two: identify current average daily or monthly revenue from documentation with specific dollar figures. Step three: apply Specified Percentage to current revenue to produce reconciled withdrawal amount. Example calculation shown clearly: "The advance agreement specifies a Specified Percentage of 15% (Section 3.b). Current average daily revenue over the 90-day period ending [date] is $2,400 (see Bank Statement Summary Exhibit A). Application of Specified Percentage: 15% × $2,400 = $360 reconciled daily withdrawal amount."
Compare against current fixed daily withdrawal amount to show reconciliation delta. Some contracts specify methodology variations — Specified Percentage applied to gross deposits, net revenue, card processing volumes only, or other specific bases. Contract analysis (see companion guide Day 17) identifies specific methodology allowed. Calculation errors weaken the invocation — verify calculations before delivery.
Component 4: Proposed reconciled withdrawal amount with effective date
The letter states the specific proposed reconciled withdrawal amount and requested effective date. Format the request clearly: "Based on the reconciliation calculation shown above, [Borrower] requests reconciliation to a daily withdrawal amount of $360, effective [date typically 5-10 business days from letter date] and continuing until either revenue recovers to the underwriting baseline or the parties agree to further reconciliation." Some cases benefit from proposing a review period (typically 60-90 days) after which the reconciled amount is reevaluated based on updated revenue documentation.
Proposing an effective date matters procedurally — the request must transition from theoretical reconciliation to a specific operational request the funder can act on. Undefined effective dates weaken the invocation. Some cases propose a graduated reconciliation (initial reduction with subsequent adjustments) rather than immediate full reduction — this can produce better funder engagement in specific fact patterns.
Component 5: Delivery method compliance
The letter must be delivered per contract-specified requirements. Some contracts require certified mail with return receipt. Some require email delivery to specified funder addresses with delivery confirmation. Some require delivery to funder's counsel rather than funder directly. Some allow multiple delivery methods but specify which method establishes constructive receipt for procedural purposes. Contract analysis identifies specific delivery requirements.
Delivery method compliance affects procedural validity. Non-compliant delivery can support funder counsel arguments that the invocation was not properly presented and therefore not procedurally valid. Preserve delivery evidence — certified mail return receipts, email delivery confirmations, courier signature receipts. Multi-channel delivery (certified mail plus email plus courier) provides redundant evidence for cases where delivery becomes contested.
Component 6: Response deadline request
The letter requests a specific response deadline. Standard request: "[Borrower] respectfully requests written response within 10 business days from receipt of this letter, confirming acknowledgment of the reconciliation invocation and either accepting the proposed reconciled withdrawal amount or engaging in dialogue regarding alternative terms." Response deadline creates procedural framework for follow-through. Cases where funder does not respond within requested deadline route to specific follow-through protocols (see Section 03 response scenarios).
Include specific contact information for funder response: designated recipient (typically borrower's counsel or placement organization if involved), response methods (email, mail, phone), and any preferences for coordinated dialogue. Avoid inviting uncoordinated phone dialogue — written response is procedurally more valuable than verbal representations that are subsequently disputed.
The six-component output
Complete letter with all six components produces defensible invocation that funder counsel cannot easily reject procedurally. Assembly protocol in Section 02 covers the 10-day preparation timeline. Response scenarios in Section 03 cover how funders typically respond. Decision tree in Section 04 covers follow-through protocols.
Want your reconciliation invocation letter drafted with all six components?
The intake walks contract clause citation with quoted reconciliation language, revenue decline documentation assembly (bank statements, merchant processor records, comparative analysis), reconciliation calculation using Specified Percentage of receivables, proposed reconciled withdrawal amount with effective date, delivery method compliance verification, and response deadline framework. Coordination with commercial workout counsel available for cases requiring counsel review. No documents required to begin the call.
Assembly protocol: Days 1-3, Days 4-7, Days 8-10.
Assembly is stage-structured against a 10-day preparation window. Days 1-3 conduct contract analysis prerequisite (identifying reconciliation clause language and methodology allowed). Days 4-7 assemble revenue decline documentation and calculate reconciled amount. Days 8-10 draft and deliver the letter. Compressed cases can execute in 5-7 days but assembly quality decreases with compression. Multi-MCA cases require parallel assembly across all contracts.
Contract analysis (see companion guide Day 17) is prerequisite for reconciliation invocation. Identify: specific reconciliation clause language including section reference and page number, procedural requirements (documentation formats, timing, delivery method), reconciliation methodology allowed (Specified Percentage applied to what revenue basis), and any specific procedural provisions for reconciliation requests. Weak clause language does not preclude invocation but reduces expected leverage. Contract analysis by commercial workout counsel or bankruptcy counsel familiar with MCA cases typically requires 2-3 hours per contract for reconciliation-focused review.
Reconciliation invocation is procedurally strongest when default has not yet been triggered. If default has already been triggered or default letter has been received, reconciliation invocation is still available but combines with default letter response protocol (see companion guide Day 16) rather than proceeding as standalone workout. Verify current default status by cross-referencing recent ACH withdrawals against contract-specified daily withdrawal amount, reviewing recent funder communications for default notices, and assessing whether any default event definitions (missed withdrawal, bank account modification, additional advance) may have been triggered.
Documentation quality directly correlates with funder engagement. Assemble: bank statements covering underwriting baseline period (typically 3-6 months preceding advance origination — check contract for specific baseline period), bank statements covering current period (typically 3-6 months preceding invocation), and comparative revenue analysis table. Merchant processor statements for card-processing revenue if applicable. Accounting records showing revenue trends. Evidence of specific decline causes if applicable (customer loss letters, industry condition documentation, operational disruption evidence). Documentation should be organized as labeled exhibits referenced in the invocation letter — Exhibit A Bank Statement Summary, Exhibit B Merchant Processor Records, and so on.
Apply Specified Percentage from contract to current actual revenue. Show calculation with all math steps. Standard methodology: Specified Percentage × current average daily revenue = reconciled daily withdrawal amount. Some contracts specify variations — Specified Percentage applied to gross deposits vs net revenue, card processing volumes only vs total deposits, or other specific bases. Contract analysis identifies allowed methodology. Multi-MCA cases require parallel calculation across all positions with different Specified Percentages producing different reconciled amounts. Verify calculations before delivery — calculation errors weaken the invocation and can produce funder counsel objections that require re-invocation.
Letter drafting integrates all six components from Section 01. Standard structure: (1) header identifying borrower entity, funder entity, contract reference, and invocation date; (2) statement of purpose invoking reconciliation clause; (3) quoted reconciliation clause language with section reference; (4) revenue decline documentation summary with exhibit references; (5) reconciliation calculation with methodology and math steps; (6) proposed reconciled withdrawal amount and effective date; (7) delivery method compliance statement; (8) response deadline request with contact information; (9) preservation of rights statement (invocation does not waive any other contractual or legal rights). Draft review by counsel where possible improves procedural quality. Multi-MCA cases require parallel drafting with contract-specific citations.
Deliver via contract-specified method with delivery evidence preservation. Certified mail with return receipt is procedurally strongest for cases where delivery may be contested — return receipt establishes constructive notice. Email delivery with delivery confirmation may be primary or supplemental depending on contract requirements. Some cases use multi-channel delivery (certified mail plus email plus courier) for redundant evidence. Preserve all delivery evidence: return receipts, email delivery confirmations, courier signature records. Note delivery date carefully — response deadline runs from delivery date rather than letter date. Follow up delivery with courtesy call to funder or funder counsel (per any contact restrictions in existing correspondence) to acknowledge delivery and reference the letter — this can accelerate funder review.
Protocol completion at Day 10 produces delivered letter with delivery evidence preserved. Response window then begins running per requested deadline. Section 03 covers the five funder response scenarios. Multi-MCA cases with 3-5 contracts require 15-25 days total for parallel assembly across all positions. Compressed cases can execute in 5-7 days but with reduced documentation quality.
The proactive-vs-reactive framing
Reconciliation invocation is procedurally strongest when executed proactively — while revenue decline is documented but default has not yet been triggered. Proactive invocation demonstrates good-faith engagement with contract mechanisms and produces stronger funder disposition than reactive invocation after default. Cases that delay reconciliation invocation until after default has been triggered face compounded difficulty: the invocation combines with default response protocol, funder counsel is engaged in enforcement rather than workout dialogue, and timeline pressure reduces documentation quality. Borrowers with documented revenue decline should invoke reconciliation before default is triggered, even if funder response is uncertain — the invocation preserves procedural rights and creates workout dialogue opportunity that is unavailable after default.
Want the five funder response scenarios walked for your specific case?
The intake walks likely funder response scenario given your specific funder identity, contract language, and revenue decline documentation quality — immediate engagement, negotiation dialogue, delayed response, refusal, or silence. Follow-through protocol for each scenario prepared during initial drafting. Coordination with commercial workout counsel and Subchapter V evaluation if refusal or silence escalation becomes operative. No documents required to begin.
Five funder response scenarios.
MCA funder response to reconciliation invocation letters falls into five recognizable scenarios. Each scenario requires specific follow-through protocol. Understanding likely funder response before delivery informs invocation strategy and prepares for downstream decisions.
Description: funder acknowledges receipt within requested response deadline, agrees to reconciled withdrawal amount as proposed or engages substantive dialogue on reconciled amount with minor negotiation. Sophisticated funders with clear reconciliation clause language typically engage when documentation is credible and calculation methodology is correct. This scenario produces the cleanest workout resolution — reconciled withdrawal amount takes effect on requested date, business continues operating with reduced cash flow pressure, and no downstream mechanisms are triggered. Follow-through: document agreed reconciled amount in written communication, verify implementation on effective date (confirm ACH withdrawal amounts reduce as agreed), and preserve documentation for future reference. Some funders provide formal amended contract documentation; others simply implement modified withdrawal without contract amendment. Preserve either as evidence of agreed modification. Approximately 20-30% of reconciliation invocations produce this scenario when documentation is well-prepared.
Description: funder acknowledges receipt but proposes different reconciled amount, requests additional documentation, or proposes alternative terms. Common alternative proposals: reconciled withdrawal amount higher than borrower proposed (funder may accept partial reduction rather than full application of Specified Percentage), modified withdrawal amount with future obligations (extended contract term at lower daily withdrawal), or graduated reconciliation with periodic review. Dialogue can produce workable resolution when both parties engage constructively. Follow-through: evaluate funder counter-proposal against borrower's actual cash flow capacity, prepare counter-response with revised proposal or supporting documentation, and coordinate written response through counsel or placement organization. Verbal dialogue is acceptable during negotiation but written documentation of agreements is essential. Some negotiations require 2-4 rounds of exchange before reaching agreement. Approximately 25-35% of reconciliation invocations produce this scenario, and successful negotiation typically produces workable resolution.
Description: funder acknowledges receipt but delays substantive response beyond requested deadline. Some funders use delay as leverage — extending timeline may pressure borrower toward alternative concessions. Other funders need genuine internal processing time — underwriting review, counsel consultation, or portfolio management coordination. Follow-through: send written follow-up letter after deadline expires requesting substantive response within specified additional period (typically 5-10 additional business days). Escalate contact to funder counsel if funder direct contact does not respond. If continued delay combined with no default acceleration, delay is often benign and reconciliation dialogue continues in extended timeline. If continued delay combined with acceleration threats or default preparation, delay is adversarial and case escalates to Strategy 5 Subchapter V consideration. Approximately 15-20% of reconciliation invocations produce delayed response scenarios, with mixed outcomes depending on follow-through discipline.
Description: funder rejects reconciliation invocation citing contract language interpretation (arguing reconciliation is discretionary rather than mandatory), documentation deficiencies (funder claims documentation does not support requested reconciled amount), specific procedural objections (invocation timing, delivery method, format), or general refusal without specific basis. Aggressive funders with weak reconciliation clause language frequently refuse. Follow-through: analyze refusal basis — if funder cites specific procedural or documentation objections that can be addressed, prepare supplemental invocation with corrections; if funder cites contract language interpretation that borrower can rebut with contract analysis, prepare rebuttal response through counsel; if refusal is procedurally supportable, escalate to Strategy 3 negotiated forbearance or Strategy 5 Subchapter V. Refusal is not the end of workout options — it clarifies which downstream strategy fits. Approximately 20-30% of reconciliation invocations produce refusal scenarios, escalating case toward alternative workout mechanisms.
Description: funder does not respond within requested deadline or subsequently. Silence combined with continuing withdrawals and revenue decline typically escalates toward default and requires escalation. Silence is functionally different from delayed response — silence involves no acknowledgment of receipt at all, while delayed response acknowledges receipt without substantive engagement. Follow-through: verify delivery through preserved delivery evidence (return receipts, delivery confirmations), send written follow-up letter after deadline expires citing continued silence and reserving all rights, escalate to Subchapter V evaluation if continuing withdrawals produce cash flow pressure that voluntary workout cannot address. Some silence patterns reflect funder disengagement — funder has written off the position and expects downstream default without engagement. Other silence patterns reflect internal processing delays that eventually produce response. Discipline in continued follow-up combined with Subchapter V preparation preserves borrower options. Approximately 10-15% of reconciliation invocations produce silence scenarios, typically escalating to Subchapter V within 30-60 days.
Scenario distribution varies by funder — sophisticated funders with clear reconciliation clause language produce higher engagement rates (scenarios 1 and 2 predominate); aggressive funders with weak clause language produce higher refusal or silence rates (scenarios 4 and 5 predominate). Cross-reference our MCA debt settlement mechanics guide for downstream settlement dialogue after reconciliation resolution or refusal.
Decision tree: how to respond by scenario.
The five funder response scenarios from Section 03 each require specific follow-through protocol. Selection is driven by fact pattern — the specific combination of funder response type, borrower cash flow status, revenue trajectory, and downstream timing. Applying the wrong follow-through protocol to the wrong scenario consistently produces worse outcomes than disciplined analysis.
Fact pattern A: Immediate engagement with reasonable counter-proposal
Route to accept negotiated terms with written documentation. Funder proposes reconciled amount slightly higher than borrower requested but still meaningfully below current fixed daily withdrawal. Accept if borrower cash flow supports the modified amount. Document acceptance in written response confirming agreed reconciled withdrawal amount, effective date, and any conditions. Preserve documentation of agreed modification (some funders provide formal amended contract; others simply implement modified withdrawal — either is acceptable as long as written documentation of agreement exists). Verify implementation on effective date. This is the cleanest outcome and produces workable resolution without downstream mechanisms.
Fact pattern B: Negotiation dialogue with multiple rounds of exchange
Route to coordinated response with counsel. Funder proposes different reconciled amount, requests additional documentation, or proposes alternative terms. Evaluate counter-proposal against borrower's actual cash flow capacity and revenue trajectory. Prepare counter-response with revised proposal or supporting documentation. Coordinate written response through counsel or placement organization. Verbal dialogue during negotiation is acceptable but written documentation of agreements is essential. Some negotiations require 2-4 rounds before reaching agreement. Successful negotiation typically produces workable resolution. Failed negotiation after multiple rounds routes to Strategy 3 forbearance or Strategy 5 Subchapter V.
Fact pattern C: Delayed response with no default acceleration
Route to wait with disciplined follow-up. Funder acknowledges receipt but delays substantive response. Continuing withdrawals at current amount but no default acceleration indicates funder is processing internally rather than pursuing enforcement. Send written follow-up letter after deadline expires requesting substantive response within specified additional period (typically 5-10 additional business days). Escalate to funder counsel if funder direct contact remains unresponsive. Continue monitoring cash flow and revenue during delay period. Some delays resolve favorably; others require escalation. Prepare Subchapter V documentation during delay period as prudent backup even if immediate escalation is not needed.
Fact pattern D: Refusal cited to specific contract language
Route to Strategy 3 negotiated forbearance or Strategy 5 Subchapter V. Funder rejects reconciliation citing contract language interpretation (typically arguing reconciliation is discretionary rather than mandatory, methodology is different than borrower proposed, or procedural requirements were not met). Analyze refusal basis with counsel to determine whether procedurally supportable. If refusal is supportable under contract language, reconciliation strategy is exhausted and case escalates. Strategy 3 negotiated forbearance may still succeed if funder is willing to engage on modified terms outside reconciliation framework (extended cure period, modified withdrawal amount with future obligations, temporary payment suspension with resumption). Strategy 5 Subchapter V provides reliable stay protection regardless of funder disposition — the automatic stay under 11 U.S.C. § 362 is effective on filing day. April 2026 eligibility ceiling at $3,424,000 accommodates most closely held businesses.
Fact pattern E: Refusal cited to documentation deficiencies
Route to supplement documentation and re-invoke. Funder claims documentation does not support requested reconciled amount — specific objections include documentation format, comparative period selection, or revenue basis calculation. Evaluate whether documentation objections can be addressed with supplemental documentation. Prepare supplemental invocation letter addressing specific objections with additional documentation as required (extended comparative period, additional revenue source documentation, corrected calculation methodology). Re-invocation with corrected documentation frequently succeeds when original refusal was procedural rather than substantive. If supplemental invocation is also refused, case escalates to Strategy 3 or Strategy 5 as in Fact pattern D.
Fact pattern F: Silence with continuing withdrawals and revenue decline
Route to escalate to Subchapter V evaluation. Funder does not respond within requested deadline. Continuing full withdrawals at contract-specified amount combined with documented revenue decline produces compounding cash flow pressure that voluntary workout cannot address. Verify delivery through preserved evidence. Send written follow-up letter after deadline expires reserving all rights. Begin Subchapter V documentation preparation. If continued silence beyond 30-60 days combined with cash flow deterioration, file Subchapter V to invoke automatic stay halting all withdrawals and providing reorganization framework. Silence combined with funder disengagement (no response to follow-up, no processing indicators) frequently reflects funder writing off position and expecting downstream default — Subchapter V provides reliable protection when voluntary approach cannot succeed.
Fact pattern G: Silence with default acceleration triggered
Route to emergency response protocol. Funder does not respond to reconciliation invocation but subsequently triggers default acceleration (default letter received, ACH withdrawal amounts increased, COJ filed, or bank account levied). Reconciliation invocation is superseded by emergency response requirements. See companion guides Day 15 bank account frozen response protocol and Day 16 default letter response protocol. Strategy 5 Subchapter V is typically the operative mechanism because voluntary strategies cannot address active enforcement combined with acceleration. File Subchapter V for automatic stay effective on filing day. The 11 U.S.C. § 362 stay halts acceleration, ACH withdrawals, and enforcement actions regardless of default letter or COJ status.
The decision tree summary
Fact pattern A (immediate engagement) → accept with documentation. Fact pattern B (negotiation dialogue) → coordinated response with counsel. Fact pattern C (delayed response + no acceleration) → wait with follow-up. Fact pattern D (refusal cited to contract language) → Strategy 3 or 5. Fact pattern E (refusal cited to documentation) → supplement and re-invoke. Fact pattern F (silence + continuing withdrawals) → escalate to Subchapter V evaluation. Fact pattern G (silence + default acceleration triggered) → emergency response protocol. Related MCA operational context in our general MCA debt relief guide, MCA debt settlement mechanics guide, and stop MCA daily payments framework.
Three things worth remembering from this guide.
Six components make the reconciliation letter procedurally defensible.
The reconciliation invocation letter is a procedural document. Six components structure defensible invocation: (1) contract clause citation with specific section reference, page number, and quoted language demonstrating the borrower's contractual right; (2) revenue decline documentation with underwriting baseline vs current comparison via bank statements and merchant processor records; (3) reconciliation calculation methodology applying Specified Percentage to actual revenue with all math steps shown; (4) proposed reconciled withdrawal amount with specific effective date; (5) delivery method compliance with contract-specified requirements including certified mail return receipt or delivery-confirmed email; (6) response deadline request typically 5-10 business days with follow-through protocol. Component omission weakens invocation procedurally and reduces funder engagement. Verbal reconciliation requests rarely produce enforceable outcomes; the letter format matters. Multi-MCA cases require parallel letters across all contracts since reconciliation is contract-specific.
Assembly protocol runs Days 1-3, Days 4-7, Days 8-10 — proactive invocation is strongest.
Assembly is stage-structured against 10-day preparation window. Days 1-3 conduct contract analysis prerequisite (identifying reconciliation clause language, methodology allowed) and verify no active default status. Days 4-7 assemble revenue decline documentation (bank statements covering baseline period vs current period, merchant processor records, comparative revenue analysis table) and calculate reconciled withdrawal amount applying Specified Percentage to current actual revenue. Days 8-10 draft the letter integrating all six components and deliver via contract-specified method with delivery evidence preservation. Reconciliation invocation is procedurally strongest when executed proactively before default is triggered — proactive invocation demonstrates good-faith engagement with contract mechanisms and produces stronger funder disposition than reactive invocation after default. Cases that delay invocation until after default face compounded difficulty combining with default response protocol. Multi-MCA cases with 3-5 contracts require 15-25 days total for parallel assembly.
Five funder response scenarios each require specific follow-through protocol.
MCA funder response falls into five recognizable scenarios. Scenario 1 immediate engagement (~20-30% of cases with sophisticated funders and strong documentation): accept reconciled amount with written documentation. Scenario 2 negotiation dialogue (~25-35% of cases): coordinated response with counsel through 2-4 rounds of exchange. Scenario 3 delayed response (~15-20% of cases): disciplined follow-up with written follow-up letters. Scenario 4 refusal (~20-30% of cases with aggressive funders and weak clause language): supplement documentation if procedural, escalate to Strategy 3 forbearance or Strategy 5 Subchapter V if substantive. Scenario 5 silence (~10-15% of cases): escalate to Subchapter V evaluation particularly if combined with continuing withdrawals and revenue decline. April 2026 Subchapter V eligibility ceiling at $3,424,000 accommodates most closely held businesses when reconciliation cannot deliver resolution. 11 U.S.C. § 362 automatic stay provides reliable protection regardless of funder disposition when voluntary approach cannot succeed.
Frequently asked questions.
What is an MCA reconciliation request and when should I send one?
An MCA reconciliation request is a formal written invocation of the reconciliation clause in a merchant cash advance contract, requesting that the funder recalculate the daily withdrawal amount based on documented revenue decline. The theoretical basis is that MCA funders purchase a Specified Percentage of future receivables — if actual receivables have declined from the underwriting baseline, the reconciled withdrawal amount should adjust proportionally. Reconciliation invocation is appropriate when: documented revenue decline exceeds 15-20 percent from underwriting baseline (smaller declines typically produce weak reconciliation leverage regardless of clause language), contract language includes reconciliation provisions (nearly all modern MCA contracts do, though clause quality varies), and revenue decline documentation is available in bank statements or merchant processor records. Reconciliation invocation is typically appropriate proactively when revenue decline is documented and default has not yet been triggered — before receiving a default letter. Timing matters: invocation during smooth performance produces different funder disposition than invocation during active distress. The request is a written letter with specific components, not a phone call — verbal reconciliation requests rarely produce enforceable outcomes.
What are the six components of a proper reconciliation request letter?
Six components structure a defensible reconciliation invocation letter. First, contract clause citation — specific reference to the reconciliation clause in the advance agreement including section number, page reference, and quoted clause language demonstrating the borrower's right to request reconciliation. Second, revenue decline documentation — bank statements or merchant processor statements demonstrating the underwriting baseline period revenue vs current revenue with specific dollar amounts, decline percentage, and decline duration. Third, reconciliation calculation methodology — application of the Specified Percentage established at underwriting to actual current revenue producing the reconciled withdrawal amount, shown as specific calculation with dollar figures. Fourth, proposed reconciled withdrawal amount — the specific dollar amount the borrower requests as the reconciled daily withdrawal, with proposed effective date. Fifth, delivery method compliance — the letter must be delivered per contract-specified requirements (some contracts require certified mail, some require email with delivery confirmation, some require delivery to funder counsel rather than funder directly). Sixth, response deadline request — typically 5-10 business days for funder acknowledgment and substantive response, with follow-through protocol if response is not received. Component omission typically weakens the request procedurally and produces worse outcomes.
How do I document revenue decline for the reconciliation request?
Revenue decline documentation requires evidence the funder can verify. Bank statements are the primary documentation source — the funder underwrote the advance based on historical bank statement analysis and can verify current bank statements against that baseline. Assemble bank statements covering the underwriting baseline period (typically 3-6 months preceding advance origination) and current period (typically 3-6 months preceding reconciliation invocation) showing daily deposits, monthly totals, and comparative averages. Merchant processor statements (Stripe, Square, PayPal, or similar) provide additional documentation for card-processing revenue if the advance was underwritten against merchant processor volumes. Comparative revenue analysis should show: average daily revenue during underwriting baseline period, average daily revenue during current period, percentage decline, and specific dollar decline. Some cases benefit from additional documentation: accounting records (QuickBooks, Xero exports) showing revenue trends, evidence of specific causes for decline (customer loss, industry conditions, operational disruption), and forward-looking projections if the funder requests them. Documentation quality directly affects reconciliation success — well-documented requests with specific dollar analysis produce meaningfully better funder response than general assertions of revenue decline.
How do I calculate the reconciled withdrawal amount?
Reconciliation calculation applies the Specified Percentage established at underwriting to current actual revenue. Step one: identify the Specified Percentage from the contract — typical MCA contracts specify a percentage like 12 percent, 15 percent, 18 percent, or other figure representing the funder's purchase of that percentage of borrower's future receivables. Step two: identify current average daily or monthly revenue from documentation. Step three: apply Specified Percentage to current revenue to produce reconciled withdrawal amount. Example: if Specified Percentage is 15 percent and current average daily revenue is $2,000, reconciled daily withdrawal is $300 (15% × $2,000 = $300). Compare against current fixed daily withdrawal amount to identify reconciliation delta. Some contracts specify slightly different methodology — Specified Percentage applied to gross deposits, net revenue, card processing volumes only, or other specific bases. Contract analysis (see Day 17 guide) identifies the specific methodology allowed. Reconciliation calculation should show all math steps clearly in the invocation letter — funders review calculation methodology carefully and calculation errors weaken the request. Multi-MCA cases require parallel calculation across all positions since Specified Percentage may differ across contracts.
How do MCA funders typically respond to reconciliation requests?
MCA funder response to reconciliation requests falls into five scenarios. Scenario 1: immediate engagement — funder acknowledges receipt within response deadline, agrees to reconciled amount as proposed or engages in dialogue on reconciled amount. Sophisticated funders with clear reconciliation clause language typically engage when documentation is credible. Scenario 2: negotiation dialogue — funder acknowledges receipt but proposes different reconciled amount, requests additional documentation, or proposes alternative terms (modified withdrawal amount with future obligations, extended term with different structure). Dialogue can produce workable resolution when both parties engage. Scenario 3: delayed response — funder acknowledges receipt but delays substantive response beyond requested deadline. Some funders use delay as leverage; others need internal processing time. Follow-through with written follow-up letter typically resolves timing. Scenario 4: refusal — funder rejects reconciliation invocation citing contract language interpretation (typically arguing reconciliation is discretionary rather than mandatory), documentation deficiencies, or specific procedural objections. Refusal shifts case toward Strategy 3 forbearance or Strategy 5 Subchapter V. Scenario 5: silence — funder does not respond within requested deadline or subsequently. Silence combined with continuing withdrawals and revenue decline typically escalates toward default and requires escalation. Response scenario determines follow-through strategy.
What if the funder refuses my reconciliation request?
Funder refusal of reconciliation invocation is not the end of workout options — it clarifies which downstream strategy fits. First, analyze refusal basis: if funder cites contract language interpretation (reconciliation is discretionary, methodology is different, procedural requirements not met), evaluate whether refusal is procedurally supportable or whether contract language actually mandates reconciliation. Second, evaluate whether additional documentation could address specific funder objections. Third, consider negotiated forbearance dialogue — funders that refuse reconciliation sometimes engage on forbearance because forbearance is more clearly discretionary and provides funder more control. Written forbearance proposal with modified terms can produce workable resolution. Fourth, consider Subchapter V filing under 11 U.S.C. § 362 — the automatic stay halts all funder actions on filing day regardless of reconciliation refusal or acceleration threat. The April 2026 eligibility ceiling at $3,424,000 accommodates most closely held businesses. Cost $15,000-$50,000 typical for Subchapter V. Subchapter V is particularly appropriate when reconciliation refusal is combined with multi-MCA exposure, timeline pressure, or business viability at stake. Some cases pursue parallel strategies — reconciliation invocation and Subchapter V preparation simultaneously — to preserve options depending on funder response evolution.
Need your MCA reconciliation invocation letter drafted with all six components?
The intake line at MCA Alleviation is answered same-day for reconciliation letter drafting coordination. The intake walks contract analysis prerequisite during Days 1-3 (identifying reconciliation clause language, methodology allowed, and verifying no active default status), revenue decline documentation assembly during Days 4-7 (bank statements baseline vs current, merchant processor records, comparative analysis, calculation methodology using Specified Percentage), and letter drafting and delivery during Days 8-10 (six-component integration, contract-specified delivery method with evidence preservation, response deadline framework). Coordination with commercial workout counsel for cases requiring counsel review. Multi-MCA cases include parallel drafting across all contracts. Placement organization — not legal representation, though we work alongside counsel throughout. No documents required to begin the call.