By Stefan Idriceanu, Co-founder

From Approval to Funded: The Handoffs Between Offer, Contract and ACH

Most MCA deals that die after approval die in a handoff, not in a decision. The fix is to make the approved offer the single source for the contract, the funding call and the ACH setup, so nobody re-types a number between them.

Last updated: 17 November 2026


Approval is the middle of the deal, not the end

Underwriting gets the attention because it is where the risk sits. The days between "approved" and "funded" get less attention, even though that is where a merchant with other offers on the table walks away.

A typical approved deal passes through four handoffs before the first debit clears:

  1. Offer to selection. The ISO presents options; the merchant picks one.
  2. Selection to contract. The chosen terms become a contract package and go out for signature.
  3. Signature to funding call. Someone confirms identity, terms and bank details with the merchant before money moves.
  4. Funding to collections. The merchant's account is enrolled and the payment schedule starts.

Each handoff usually changes hands between people, and often between systems. Each change of hands is a chance to re-key the purchase price, the factor rate, the holdback or the payment amount. Each re-key is a chance for the contract to disagree with the offer.


Handoff 1: offer to selection

The offer stage fails in two ways. The ISO sends terms the funder never actually approved, or the merchant accepts a version that has since been revised.

A clean offer stage has three properties:

  • Every term is labelled by origin. A term the funder stated in its approval is different from a term someone calculated from it. When payback is derived from purchase price and factor, say so.
  • One offer is marked selected. Not "the one in the latest email thread." A recorded selection that the contract is built from.
  • The offer matrix is the record. Program, term, factor, commission, payback and fees for each option live in one place, not in a PDF attachment that gets forwarded.

If you run a brokerage and a funder, you already know the pain of reconciling an ISO's offer screenshot against what underwriting approved. The screenshot should never be the input to the contract.


Handoff 2: selection to contract

Contract errors are expensive because they are signed. Common ones in funder operations:

  • Payment amount calculated on a different business-day convention than the offer.
  • Legal entity name copied from the ISO app instead of the Secretary of State record.
  • Bank account on the contract differs from the account that was verified during underwriting.
  • A revised offer selected after the contract package was already generated.

The rule: generate the contract package from the selected offer and the verified deal record, never from a template filled in by hand. When the offer changes, the package gets regenerated, not edited.

A short pre-send checklist still helps:

CheckCompare against
Legal name and entity typeSecretary of State result on the deal
Purchase price, factor, purchased amountSelected offer
Payment amount and frequencySelected offer and schedule
Deposit accountAccount verified in underwriting
Guarantor(s)Owners on the application
Signer emailContact on the deal, not the ISO's inbox

Handoff 3: the funding call

The funding call is a control, not a courtesy. It confirms the merchant understands what they signed, that the signer is who they claim to be, and that the account receiving funds is the account being debited.

Treat the funding call as a workflow step with a recorded outcome, not a phone call someone remembers making. A useful script covers:

  • Identity of the signer and their role in the business.
  • Purchase price, purchased amount, payment amount and frequency, read back.
  • Existing positions the merchant disclosed, compared with what underwriting found.
  • Deposit and debit account, last four digits confirmed.
  • Whether the merchant intends to take further financing in the near term.

If any answer contradicts the file, the deal goes back to underwriting as an exception. It does not get funded with a note in a comments field.


Handoff 4: funding to collections

Once the wire or ACH credit goes out, collections start. This is where a separate servicing system typically receives the deal by export, and where the payment amount gets typed in again.

Two practices remove most of the risk:

  • Enroll the collection account with bank-verified details, rather than routing and account numbers read off a voided check image.
  • Build the payment schedule from the funded structure, so returned payments, amendments and payoffs are all measured against the same terms that were signed.

Post-funding communications — the welcome notice, the first-debit reminder, the ISO confirmation — are best drafted from the deal record and reviewed before they go out. A wrong first-debit date sent automatically to a merchant is a support ticket at best and a dispute at worst.


A worked example (illustrative numbers)

Take a hypothetical approval: $50,000 purchase price, 1.35 factor, $67,500 purchased amount, 120 business-day term, daily ACH.

  • Daily payment: $67,500 / 120 = $562.50.
  • The ISO's presentation rounds to $563. The contract template, filled by hand, says $565 because someone used an older draft.
  • Over 120 debits, $565 collects $67,800 — $300 more than the purchased amount. Someone has to remember to short the final debit, and the servicing schedule now disagrees with the contract.

Nothing about this deal was a credit problem. It was a handoff problem, and it would surface months later as a payoff dispute. Building the contract and the schedule from the same selected offer removes it entirely.


How DueDeal handles the handoffs

DueDeal keeps the offer, contract, funding and servicing on one deal record, so each stage reads from the previous one instead of from a copy.

  • Offers. Offer terms are labelled funder-stated or calculated, merchant terms come from the funder approval, and the offer matrix holds program, term, factor, commission, payback and fees. See automated offer generation.
  • Contracts. Contract packages are generated from the deal and sent for e-signature through DocuSign, OpenSign or Adobe Sign.
  • Funding call. The funding call runs as a workflow step on the deal, alongside the rest of the activity trail.
  • Collections. After funding, ACH collections run through Actum, with the merchant's account enrolled via Plaid and debits scheduled automatically. Payment schedules, returned payments, balance transfers and amendments live on the same record.
  • Notices. Post-funding notices are drafted from the deal for a person to review and send; they are not sent automatically.

Because underwriting evidence stays attached, a contradiction found on the funding call can go straight back to the exception queue with the original evidence in view. For why that matters, read policy exceptions in MCA underwriting.


Try it on your own deals

Keep your CRM and your analysis provider. Give DueDeal 20 deals in a parallel pilot and measure decision-to-funding time and the number of times a term is re-typed between offer and first debit. Or book a demo and walk one deal from approval to collections.


Frequently asked questions

How long should it take to fund an MCA after approval? There is no universal standard; it depends on stips outstanding, contract turnaround and the funder's funding-call policy. Measure your own decision-to-funding time per deal and look at which handoff holds the most days rather than targeting a headline figure.

What is an MCA funding call? A funding call is a verification call with the merchant before funds are released. It confirms the signer's identity, reads back the key terms, confirms the bank account and checks for undisclosed positions or planned financing.

Why do MCA contracts disagree with the offer? Usually because the contract was filled in by hand from an email, a screenshot or an outdated offer version. Generating the contract package directly from the recorded selected offer prevents most mismatches.

Should ACH enrollment happen before or after funding? Account details should be verified before funding so the funded account and the debit account match. Collections themselves begin after funding, on the schedule built from the signed terms.

Does DueDeal send post-funding notices automatically? No. DueDeal drafts post-funding notices from the deal record, and a team member reviews and sends them. That keeps a person in control of what the merchant and the ISO receive.