Big Tuna Blog
MCA Funder Operations7 min read

MCA Account Adjustments: A Controlled Workflow for Servicing Teams

By Johnny Accardo · Founder & CEO, Big Tuna Solutions

A practical MCA account adjustment workflow for reviewing corrections, preserving the original ledger, updating future expectations, and closing the exception cleanly.

Open an adjustment request instead of editing the account

Create a separate adjustment record linked to the account and the source event that created the issue. Capture who raised it, when it was identified, the stated reason, the affected amount or date, and the evidence supplied. Keep the request in a proposed state until the organization's review is complete. An operator should be able to see the account as it currently stands and the requested correction side by side rather than discovering that a field changed with no explanation.

Classify what the adjustment is meant to correct

Use a concise set of internal adjustment types that reflects the team's actual servicing work. Examples may include a duplicate posting, an amount correction, a timing correction, an approved fee or charge correction, or a transfer from an unapplied queue to the proper account. Preserve the requester's original description, then add the internal classification separately. A reason code should help route and report the work; it should not replace the supporting facts or imply a decision that has not been approved.

Reconstruct the account position before deciding

Review the effective agreement data, current schedule version, source payment events, posted ledger activity, prior adjustments, returns, and any related remittance change. Identify the exact event that should remain, be reversed, or be supplemented. Keep values received from processors or bank records distinct from internal calculations. If the evidence does not reconcile to the proposed change, return the request for clarification rather than choosing the number that makes the account appear balanced.

Record the decision and its effective scope

Store the reviewer, decision time, evidence checked, approved amount, effective date, reason, and any limits on the change. Distinguish an approval to correct a historical posting from approval to change future payment expectations; one does not automatically authorize the other. If the request is declined or only partly approved, preserve both the requested and approved versions. The decision record should explain what the servicing system may change while leaving the organization's policies and authority with the responsible people.

Post a linked event without overwriting the original

Apply the approved change as its own ledger or servicing event linked to the affected source entry. Use the event direction, amount, effective date, posting date, and reference needed by the team's process. Mark superseded calculations as such, but do not delete the original event or silently edit its amount. Where a full reversal and corrected repost are required, keep both movements visible so another operator can reproduce how the account moved from the prior position to the corrected one.

Update future expectations only when the decision requires it

After posting, recalculate the current account position and determine whether the expected-payment schedule, next review date, payoff information, participation records, or reporting outputs also need an approved update. Create a new effective schedule version when future expectations change rather than rewriting earlier schedule rows. Notify the owners of affected downstream work and keep external requested, acknowledged, and completed statuses separate when a processor or other party must make a corresponding change.

Close the exception through a post-adjustment review

Compare the approved decision with the posted event, corrected account position, active schedule, external confirmation, and participation records where applicable. Record who completed the check and when, then close the request only when every required effect is accounted for or assigned as continuing work. Regular review queues should surface approved adjustments that were never posted, posted adjustments without a decision record, repeated corrections to the same source event, and adjustments that changed an account without updating the applicable future expectations.