The servicer report is where a securitization lives or dies each month. It sets the reserves, tests the triggers, and tells the agent whether the pool still supports the funding. Olycor builds it from source data instead of a spreadsheet.
A servicer report is the periodic report a seller-servicer delivers in a receivables securitization. It reconciles the pool through a roll forward of sales, collections, dilution, and defaults, reports delinquency and pool composition, and computes the reserves and required credit enhancement that determine how much funding the pool supports and whether triggers are tripped.
In a trade receivables securitization the seller keeps collecting its own invoices, so the buyer of the receivables sees the pool only through the servicer report. That makes it more than a status update. It is the mechanism that proves the roll forward closes, recomputes the reserves, retests eligibility and concentration, and certifies the ratios the amortization triggers watch.
A borrowing base certificate answers one question: how much can we borrow. A servicer report answers a harder set: did the pool behave the way the structure assumed, and is the credit enhancement still adequate. Getting it wrong in either direction is costly. Overstate the pool and you have a misreporting problem. Understate a ratio and you can trip an amortization event that did not need to happen.
Beginning pool balance, plus sales, minus collections, minus dilution, minus write-offs, equals ending pool balance. If that identity does not hold at the invoice level, something upstream is wrong, and Olycor stops the run rather than plugging the difference.
Cash received against pool receivables in the period, reconciled to bank activity and applied at the invoice level, with unapplied cash tracked separately.
Receivables generated and added to the pool. Together with collections and dilution, this is what makes the roll forward close.
Credit memos, rebates, disputes, and other non-cash reductions. The dilution ratio drives the dilution reserve and often an amortization trigger.
Receivables written off or aged past the transaction's default horizon, feeding the default ratio and the loss reserve.
Aging buckets against contractual due dates: 1 to 30, 31 to 60, 61 to 90, 90 plus days past due, plus the delinquency ratio the documents define.
Obligor concentrations, excess concentration, jurisdiction and currency mix, and the eligible versus ineligible split as of the cutoff date.
The funded amount is not based on the gross pool. Each period, every receivable is retested against the transaction's eligibility criteria: aging limits, obligor jurisdiction, currency, contract terms, dispute status, and the rest of the schedule in your documents. A receivable that was eligible at sale can become ineligible at the next cutoff, and the report has to catch that movement.
On top of eligibility sits composition. Obligor concentrations above the transaction limits become excess concentration and reduce the net pool, with obligors matched into groups first so an entity that bills under three names is measured as one counterparty. Olycor runs these tests deterministically at the invoice level, so the eligible pool number on page one is the sum of identifiable invoices, not an estimate.
Reserves translate pool performance into protection. A simplified example on an eligible pool of $52,000,000, using illustrative rates. Your transaction defines its own formulas, stress factors, and floors, and those definitions are what get configured.
| Component | Basis | Rate | Amount |
|---|---|---|---|
| Dilution reserve | 3.1% avg dilution x 2.0 stress | 6.20% | $3,224,000 |
| Loss reserve | 1.4% peak default ratio x 2.25 stress | 3.15% | $1,638,000 |
| Yield and servicing reserve | rate + fees carried over the liquidation period | 2.10% | $1,092,000 |
| Sum of reserves | on an eligible pool of $52,000,000 | 11.45% | $5,954,000 |
| Enhancement floor | per the transaction documents | 10.00% | $5,200,000 |
| Required credit enhancement | greater of the two | 11.45% | $5,954,000 |
Each input above is itself a calculation with lineage: the dilution reserve rests on twelve months of classified credit memos, the loss reserve on the default ratio history, and the yield and servicing reserve on rates and turnover. If the dilution history is wrong, the reserve is wrong, which is why classification happens at ingestion, not at reporting time.
Every run is validated before anyone signs. Control totals from source files must match the mapped detail. The roll forward must close to the cent. Ratios are compared to prior periods, and a dilution ratio that jumps from 3.1 percent to 5.4 percent gets itemized down to the credit memos that moved it, not waved through. Duplicate invoice numbers, negative aging, obligors with no group assignment, and unmapped document types all become exceptions.
Exceptions go to a person with context attached: what the system saw, what it expected, and what resolving it changes. The resolution is recorded and applied consistently the next month. What never happens is a silent judgment call inside a formula, because the difference between a report you can defend and one you cannot is whether the judgment calls are on the record.
Servicer report errors are expensive because the report feeds reserves and triggers, not just disclosure. These are the breaks Olycor validates against every cycle.
| Where it breaks | What it looks like | The consequence |
|---|---|---|
| Ratio definitions | The dilution ratio computed same-month when the documents define it on a one month lag | Every reserve derived from the ratio is wrong, and restating it means restating the enhancement calculation |
| Cutoff collections | $400,000 received after the cutoff applied inside the period anyway | The roll forward closes this month by borrowing from next month, and the agent eventually asks which report was right |
| Dilution coding | Customer disputes booked as write-offs instead of credit memos | The default ratio climbs toward its trigger while the dilution reserve runs short, both from one coding choice |
| Obligor rollup | Three subsidiaries of one parent carried as separate obligors | $6,000,000 of excess concentration above the transaction limit stays in the funded pool until a review catches it |
| Roll forward plugs | A $250,000 difference forced into the reconciliation as an adjustment | A backup servicer review finds it, and every prior report the transaction funded against becomes suspect |
| Trigger arithmetic | A three month average ratio computed over the wrong three months | A trigger that should have tripped is masked, or one that should not have trips, and either way the documents were not followed |
The agent, trustee, and sponsor bank fund against this report, so it is built to be retested by them, not just read. None of this replaces their review; it changes what the review has to work with.
Beginning pool balance plus sales, less collections, dilution, and defaults equals the ending balance the prior report certified.
Delinquency, default, and dilution ratios are sums over identifiable invoices and credit memos, each linked to its source file and row.
An ineligible receivable shows the test that fired and the limit in the transaction documents that it failed.
Each obligor group displays its limit, its share of the pool, and the excess removed, after entity rollup rather than before.
The dilution and loss reserves open to their ratio histories and stress factors, and required enhancement shows the formula tested against the floor.
Balances on page one are the sums of the attached invoice-level detail, and the configuration that ran is versioned to the transaction documents.
When the agent asks why the delinquency ratio moved 80 basis points, the answer should be a list of invoices, not a shrug. In Olycor every reported figure links to the invoices behind it, each invoice to the source file and row it came from, and every calculation to the rule version that ran. The full mechanics are on source-level auditability.
This matters most when things go wrong. Backup servicers, auditors, and agents reviewing a stressed transaction all ask the same question: show me how this number was produced. A report built from lineage answers in minutes. A report built from a spreadsheet that has been edited monthly for four years may not be able to answer at all.
Or browse the full receivables finance glossary and the eligibility rule library.
Last updated July 9, 2026. Olycor does not provide legal, tax, accounting, or credit advice. Facility terms, eligibility criteria, and reserve mechanics vary by credit agreement; your agreement governs.
Olycor is onboarding seller-servicers who are done maintaining the monthly report in a spreadsheet only one person understands.