Receivables finance reporting: what borrowers actually have to submit

The term sheet was the easy part. Somewhere around page 40 of the credit agreement sits a reporting covenant, and it is longer than you expected. A borrowing base certificate by the fifteenth business day. An aging that ties to the general ledger. A roll-forward. Ineligible detail by category, invoice by invoice. Miss a deadline or submit a package that does not reconcile, and most agreements let the lender pause new draws while they sort it out. So what does a borrower in receivables finance actually have to produce, and how often? Here is the full inventory.

What you submit depends on the facility type

Receivables finance is one asset class with at least three different reporting cultures. An asset-based revolver, a trade receivables securitization, and a factoring arrangement all lend against the same invoices, but each asks for different proof, on a different clock.

The frequency column is where borrowers get surprised. Most agreements ratchet reporting up when the facility gets stressed. Fall below a 15 percent excess availability trigger on a $25 million ABL revolver, and monthly certificates commonly become weekly. In securitizations, daily data files are moving from exception to default, because the conduit banks funding them want to see the pool move in near real time.

The AR aging: the report everything else reconciles to

Every facility type starts with the aging. It buckets every open invoice by how overdue it is, usually 0 to 30, 31 to 60, 61 to 90, and over 90 days. Lenders read three things from it: the trend in past due balances, how concentrated the pool is in a few customers, and whether the total ties to your balance sheet. That last one matters more than most borrowers realize. If the aging says $18.2 million and the general ledger says $18.6 million, that difference is a $400,000 question you will answer eventually, either in this month's package or in a field exam.

The trap is that the aging is a snapshot. Pull it two days after the cutoff and unposted cash or late credit memos shift the buckets. Most agreements require the aging as of the certificate date, so the discipline around when and how you export matters as much as the report itself. We have watched teams spend a full day chasing a tie-out that existed only because two exports were pulled 48 hours apart.

Invoice level data, collections, and cash application

Aggregates are no longer enough for many facilities. Securitizations have effectively standardized on invoice level pool files: one row per receivable with obligor, invoice date, due date, original amount, open amount, and dilution flags. ABL lenders increasingly ask for the same detail on request, and factoring runs on it by definition, since the factor is buying specific invoices.

Collections reporting is the other half. Lenders want to see cash in, mapped to the invoices it paid. Unapplied cash is a quiet red flag: a borrower with $600,000 sitting unapplied is either behind on cash application or has customers paying amounts that do not match invoices, which usually means disputes or dilution are on the way. A typical monthly package includes:

• AR aging as of the cutoff, tied to the general ledger balance.
• Sales journal or new invoice register for the period.
• Cash receipts by customer, with application detail down to the invoice.
• Credit memo and adjustment register, because dilution hides here.
• Ineligible detail by category, listing the specific invoices excluded.
• The roll-forward reconciling prior period AR to the current balance.

Eligibility, reserves, and the roll-forward

The certificate or servicer report is where raw data becomes lending math. Every invoice is tested against the eligibility criteria in the agreement: aging cutoffs, cross-aging, concentration limits, obligor type, jurisdiction, disputes, and contra balances. What survives is eligible collateral. Advance rates and reserves apply to that number, not to gross AR, which is why two borrowers with identical sales can have very different availability.

The roll-forward is the piece teams most often treat as an afterthought, and the first thing a field examiner checks. It has one job: prove that the AR balance moved for legitimate reasons.

If ending AR on the roll-forward does not equal gross AR on the certificate, the package is internally inconsistent, and many lenders will bounce it back before reading anything else. A roll-forward that ties every month is one of the cheapest credibility signals a borrower can send.

What does audit-ready actually mean?

Audit-ready is not a mood. It is a specific, testable property of the package: every number traces to source records, and the same inputs always reproduce the same outputs. In practice that means four things.

• Every ineligible amount resolves to a list of specific invoices, not a plug.
• Each rule applied matches the credit agreement, and you can point to the parameter: the over 90 day cutoff, the 10 percent concentration cap, the 25 percent cross-aging trigger.
• This period's certificate reconciles to the prior one through the roll-forward.
• The whole calculation is reproducible: rerun it on the same data and get the same answer, down to the dollar.

This is also where the tooling question shows up. Assembling this package by hand from ERP exports commonly takes a finance team 3 to 5 days a month, every month. Platforms like Olycor collapse that: AI interprets the raw exports, deterministic rules run the eligibility and reserve math, and the output is a signed, traceable package your lender can verify instead of re-checking line by line.

A reporting package is not finished when the numbers are filled in. It is finished when every number can defend itself.