Big Tuna Blog
MCA Broker Operations7 min read

MCA Commission Reconciliation: A Practical Post-Funding Workflow

A practical MCA commission reconciliation workflow for matching funded deals to partner statements, resolving discrepancies, and keeping broker payouts accountable.

Create the commission record when funding is confirmed

Do not wait for a partner statement to rebuild the deal. Once funding is confirmed, record the merchant, funder, funded date, funded amount, product or position, responsible rep or ISO, and the final terms used to calculate compensation. Attach the funding confirmation and keep the original deal identifier on the record. Mark the commission as expected, not earned or payable, until the conditions in the applicable agreement have been satisfied.

Keep the calculation inputs visible

Store the agreed commission method and the exact inputs used for the expected amount. That may include a percentage, points, a fixed amount, splits, fees, or other adjustments defined by the relevant agreement. Preserve the source agreement or schedule and its effective date. If a term is unclear, flag the record for review instead of choosing the interpretation that makes the numbers balance.

Separate expected, received, and payable amounts

These amounts answer different questions. Expected is what the team calculates from the confirmed funding details. Received is what the funder or upstream partner actually remitted. Payable is what the business determines should be released to the rep or ISO after required reviews and adjustments. Keeping separate fields prevents a forecast from being mistaken for cash received and gives accounting a clean explanation for any difference.

Match partner statements to individual deals

Reconcile each statement line to a deal using stable identifiers such as the partner deal number, merchant name, funded date, and funded amount. Record the remittance date, statement reference, and amount received. Do not silently combine unmatched lines or force a close match. Put ambiguous items into an exception queue so duplicate merchant names, amended fundings, and timing differences can be resolved with evidence.

Give every discrepancy a reason and an owner

When expected and received amounts differ, assign one controlled reason such as funding amount changed, commission schedule changed, split missing, fee or adjustment, duplicate entry, statement timing, or partner clarification required. Keep the supporting note and source document with the record, then assign a person and due date. A variance should not remain as unexplained math or disappear through a manual override.

Approve payouts from reconciled records

Build the payout list from records that have a matched remittance, reviewed calculation, confirmed recipient, and documented approval. Keep the approver, approval date, payment status, and payment reference in the audit trail. If the underlying funding is reversed, amended, or subject to another contractual adjustment, reopen the record and follow the applicable agreement rather than editing the original history out of view.

Review the exceptions before the totals

A useful weekly review should surface funded deals with no commission record, expected payments missing from a statement, statement lines that match no deal, unexplained variances, records waiting on approval, and approved payouts without a payment reference. Start with those exceptions before comparing summary totals. The goal is not merely to make two numbers equal; it is to show why every material difference exists and who owns the next action.