MCA Document Expiration Tracking: Keep Packages Current Without Starting Over
A practical MCA document expiration workflow for tracking statement periods, IDs, approvals, and refresh requests before stale files delay a deal.
Track freshness at the document level
Store each file with its document type, covered period, received date, source, and the business or owner it belongs to. Where a document includes an expiration date, capture that date without replacing the original file. Bank statements need statement-period fields rather than a generic upload date, while identification and other dated records may need different fields. A single package-level “documents received” status cannot show which item is becoming stale.
Keep partner requirements separate from document facts
The statement period printed on a file is a fact; whether a particular funder will accept it is a current requirement. Keep those two ideas separate. Record partner-specific freshness rules, required periods, and exception notes in the appropriate partner workflow, then evaluate the package against the destinations under consideration. Do not label a document universally expired when it may still be usable elsewhere, and confirm unclear requirements with the receiving partner.
Start the refresh before the next handoff
Use the expected submission, resubmission, or closing date to identify documents likely to age out before the next step. Create a refresh task with an owner, due date, requested item, and reason. That task should appear while the team still has time to act, not after a lender rejects the package as stale. If timing changes, recalculate the review date instead of sending repeated requests on a fixed calendar schedule.
Ask only for what changed
Before contacting the merchant, compare the current package with the requirements for the next review. Request the missing statement period, renewed identification, updated debt information, or other specific item rather than reopening the entire intake checklist. Explain which business or owner the request applies to and give a secure upload path. A narrow request is easier for the merchant to understand and easier for operations to verify.
Preserve versions without mixing the package
Save refreshed files as new versions and keep the earlier documents attached to the deal history. Mark which version is current for the active package, but do not silently overwrite what supported a prior underwriting review, submission, or approval. When a new statement changes a key financial value or reveals a new obligation, route that change back through the appropriate review rather than treating the upload as a clerical replacement.
Revalidate the package before sending it again
A refresh is complete only after the new file is matched to the right merchant, account, owner, and period. Check that required periods are continuous, duplicates are not counted twice, and the package still agrees with the application and deal record. If the requested amount, ownership, bank account, existing positions, or other material details changed, assign the correct reviewer and document the decision before resubmission.
Manage exceptions instead of chasing the whole pipeline
A practical daily queue should show documents approaching their review date, expired items on active deals, refresh requests with no owner, merchant requests past due, new files awaiting validation, and packages blocked by a partner-specific rule. Sort the queue by the next real deal milestone and keep one named next action on each exception. This gives sales and operations a shared view of which packages are current, which need attention, and why.