MCA Syndication Tracking: Keep Deal Participation and Funding Records Aligned
By Johnny Accardo · Founder & CEO, Big Tuna Solutions
A practical MCA syndication tracking workflow for recording participation, controlling allocation changes, reconciling funding evidence, and managing open exceptions.
Start with the approved deal version
Create the participation record from the specific approval or closing baseline the team is using. Link the merchant, deal identifier, approved purchase amount, purchased amount, term or delivery schedule when relevant to the record, along with the source and version for each value. Keep participation details separate from the merchant-facing deal terms while connecting both to the same baseline. That prevents an allocation built from an earlier offer from quietly carrying into a revised closing package.
Record each participant and commitment separately
Use one record per participant rather than a single note listing names and percentages. Capture the participating entity, internal owner, stated commitment, allocation basis, confirmation source, confirmation time, and current status. Preserve the original communication or document instead of treating a typed summary as the source. Separate proposed, invited, confirmed, declined, withdrawn, and funded states so the team can see the difference between an expected allocation and an actual commitment.
Make the allocation math reviewable
Show the amount and percentage for every participation alongside the total expected allocation and the portion retained by the lead funder when applicable. Record the calculation basis and rounding method used by the team. Flag totals that are overallocated, underallocated, or based on a different deal amount. The point is not to hide the arithmetic behind a final percentage; it is to let an operator trace how each amount relates to the current approved transaction.
Control changes with effective versions
When a participant changes its commitment or the underlying deal changes, create a new allocation version with the effective time, reason, source, and person who recorded it. Keep the earlier version available for comparison. Route additions, removals, substitutions, and amount changes through the review path established by the organization. A current-total field alone cannot explain which participant changed, whether the revised allocation was confirmed, or which instructions were in effect when funds moved.
Keep instructions and movement evidence distinct
Track where the team obtained the applicable funding instructions, who verified them under the established process, and which allocation version they support. Then record the actual movement as a separate event with its date, amount, reference, and supporting evidence. Do not mark a participation funded merely because instructions were sent or a participant said funds were on the way. Keeping the instruction, confirmation, and movement records distinct makes partial or unmatched activity easier to identify.
Reconcile the syndication record after closing
Compare the final closing baseline, confirmed allocations, received or sent amounts, and recorded participation totals after the transaction closes. Identify missing evidence, partial amounts, duplicate entries, timing differences, and allocations tied to a superseded deal version. Assign each difference to an owner with a next action and review date. Keep this reconciliation separate from broker commission reconciliation: one confirms the funding participation record, while the other addresses compensation owed or received.
Hand off an exception-ready participation ledger
The completed record should show the final deal version, participant roster, allocation history, confirmation sources, funding events, reconciliation outcome, and every unresolved item. Review queues for unconfirmed commitments near closing, allocation totals that do not match the baseline, funding events without evidence, and closed deals with open differences. If servicing or finance teams need the participation record later, give them the final version and open exceptions rather than a flattened export that loses the decision trail.