A securitization program funds against the monthly report. If the report is a spreadsheet only one analyst understands, the program has a single point of failure. Olycor computes the entire package from invoice level data, deterministically.
Trade receivables securitization reporting is the monthly cycle where the seller or servicer tests the pool against eligibility criteria and concentration limits, calculates dilution and loss reserves, and delivers a servicer report to the trustee or conduit agent. The report determines funding availability and required credit enhancement for the period.
The pool is the unit of analysis: thousands of invoices across entities and currencies, summarized into the ratios and balances the program documents define. Every metric below is derived from invoice detail, never keyed in.
Beginning balance, sales, collections, adjustments, ending balance, reconciled to the cent.
Collection speed feeds loss horizons and reserve floors, so it is computed from actual cash application, not estimated.
Credit memos, rebates, and adjustments as a share of sales, tracked monthly with the history reserves depend on.
Ratio triggers are program kill switches. They are computed from aged invoice detail, with the population behind each ratio inspectable.
If you are earlier in the process, the primer on what AR securitization is covers the structure this reporting supports.
Program documents define which receivables can be funded: eligible receivables typically must be within aging limits, owed by obligors in permitted jurisdictions, free of disputes and offsets, not owed by affiliates or governments unless carved in, and denominated in approved currencies. A pool of $180 million in gross receivables might carry $158 million of eligible balance once the tests run.
Olycor runs every test against every invoice, every cycle. Each exclusion carries its reason code, the rule version, and a link to the source row, so the answer to "why did the eligible pool shrink $4 million" is a filtered list, not a hunch. Tests like cross-aging, where a heavily delinquent obligor takes its current invoices out of the pool with it, are exactly the kind of second order rule that spreadsheets get wrong quietly.
Programs cap how much of the pool a single obligor, group, country, or industry can represent, often on a grid keyed to obligor ratings: an AA obligor might be allowed 10 percent of the pool while an unrated obligor is capped at 2 or 3 percent. Anything above the cap is excess concentration and comes out of the funded base, even though the invoices themselves are fine.
The hard part is not the arithmetic, it is the entity resolution. Excess concentration is only correct if every subsidiary of a corporate group rolls up to the same parent. Olycor's obligor matching builds those groups from messy names across your ERPs, then applies the grid deterministically. The mechanics are covered in more depth in the rule library entry on customer concentration limits and the primer on concentration risk.
Credit enhancement is what protects investors, and in most trade receivables programs it is dynamic: recalculated monthly from portfolio performance. The dilution reserve stresses historical dilution (credit memos, rebates, pricing adjustments) by a factor, commonly around 2.0 to 2.5, and adds a volatility component. The loss reserve stresses the loss ratio over a loss horizon derived from turnover. The required enhancement is typically the greater of the dynamic formula and a floor.
Small input errors compound here. A misclassified credit memo inflates the dilution ratio, the stress factor multiplies it, and funding drops by more than the original error. Because Olycor computes reserves from classified transaction data with the full history retained, each month's ratio is reproducible and each spike is explainable down to the memo level.
The servicer report packages everything above into the document the trustee, conduit agent, and sponsor bank actually read: balances, activity, ratios, test results, reserves, and the resulting availability or enhancement position. Olycor generates it in the program's format, on the program's calendar, with ratio triggers checked automatically so a delinquency ratio drifting toward its trigger is visible weeks before it becomes an amortization event.
Preparation and approval are separated, the signing officer sees exactly what was reviewed, and the delivered report is versioned and immutable. If the agent asks a question in week three, you answer from the signed record.
A trustee, conduit agent, or sponsor bank reviewing an Olycor servicer report can retest the pool math without asking for anything. None of this replaces their review; it means the review runs against evidence instead of assertions.
A 3.4 percent dilution ratio opens to the credit memos behind it, each linked to its source file and row.
Beginning pool balance plus sales, less collections, dilution, and write-offs equals the ending balance, to the cent.
An ineligible receivable shows which criterion fired, for example a 90 day aging limit or a jurisdiction restriction, with the rule version attached.
Each obligor group shows its rating band, its limit, its balance, and the excess removed, so the agent can retest the arithmetic.
The dilution reserve opens to the ratio history and stress factor, and required credit enhancement shows the dynamic formula tested against the floor.
The configured criteria are versioned, so any historical report can be matched to the definitions that produced it.
Pool reporting fails in predictable places, and because reserves are formulas over the inputs, small breaks get amplified. Each row below is a validation Olycor runs every cycle.
| Where it breaks | What it looks like | The consequence |
|---|---|---|
| Dilution classification | Rebates and pricing adjustments netted into sales instead of coded as credit memos | The dilution ratio is understated, the stress factor multiplies the miss, and the reserve runs short by $1,000,000 or more on a mid-size pool |
| Obligor rollup | Three subsidiaries of one parent carried as separate obligors | $6,000,000 of excess concentration above an 8 percent limit stays in the funded pool |
| Cutoff discipline | Collections received after the cutoff date counted inside the period | The roll-forward closes this month and fails next month, and the agent asks which report was right |
| Default timing | Write-offs booked when finance gets to them, not at the documented default horizon | The default ratio understates, and a trigger that should be visible stays masked until it trips |
| Roll-forward plugs | A $250,000 unexplained difference forced into the reconciliation | A backup servicer or agreed upon procedures review finds it, and every prior report becomes suspect |
| Amendment drift | An amendment tightened a jurisdiction carve-in and the spreadsheet still runs the old list | Ineligible receivables are funded until the next agent review catches it |
A 3.4 percent dilution ratio is an assertion. The 812 credit memos behind it are evidence. Olycor keeps the link from every reported figure down to source records: the file received, the row, the mapping applied, the rule that fired, and who approved any exception. Agreed upon procedures reviews and rating agency data requests become exports instead of projects.
This is the same source-level traceability Olycor brings to borrowing base certificates on ABL facilities. One data spine, different rule sets per facility.
More definitions live in the glossary, and the tests themselves in the rule library.
Last updated July 9, 2026. Olycor does not provide legal, tax, accounting, or credit advice. Reserve formulas, eligibility criteria, and trigger levels vary by program and credit agreement; your program documents govern.
Olycor is onboarding sellers and servicers running trade receivables securitization programs who want the monthly cycle computed, not reconstructed.