Servicing Requirements

Servicing is where a financing structure meets reality every day. Payments arrive, get allocated, post to accounts, aggregate into reports and flow through a payment order to investors and providers. When that chain works, nobody mentions it. When it breaks, it breaks quietly, and you usually find out from a reconciliation weeks later or from a capital provider who found the discrepancy first.

Capital providers assess servicing capability during diligence as closely as they assess credit performance, because your loss data is only as credible as the operation that produced it.

The daily job is allocation, not collection

Collections are the visible part. Allocation is the part that determines whether your reporting is right.

Every payment received has to be split across principal, interest, fees and any escrow or third-party amounts according to applicable law, your contract terms and your documented allocation policy. Partial payments, overpayments, payments on delinquent accounts, payments received after charge-off and payments that arrive without a clear account reference all need a documented rule. The rules should be written down, applied by the system rather than by individual judgement, and consistent with what your loan agreements and the relevant consumer protection rules actually require. A capital provider's preference about allocation does not override either.

Where the servicer is you, this is your operational cost. Where it is a third party, it is still your contractual responsibility to the capital provider unless the documents say otherwise. Outsourcing moves the work, not the accountability.

When the bank and the ledger disagree

The following case is fictional and stated in US dollars for a single business day.

Your collection account receives 120k. Your servicing ledger posts 118k, allocated as 98k principal, 15k interest and 5k fees. There is a 2k difference between what the bank received and what the ledger applied.

That 2k is not income and it is not a rounding issue. Its classification is unknown until you investigate. It sits unapplied, in suspense, until you identify what it is. It might be a payment on an account number that does not match, a duplicate transfer, a payment from a borrower whose loan was already paid off, a merchant or partner remittance that belongs somewhere else, or a genuine posting failure. Until you know, you cannot say which of principal, interest or fees it would have increased.

Two things you must not do. Do not recognise it as revenue because the cash is in the account. Do not force an allocation across open accounts to make the ledger tie. Both create a reconciliation that looks clean and a data set that is wrong, and the second is materially harder to unwind six months later.

Note also that the 15k of interest receipts is cash allocated to interest under the loan terms. Whether all of it is income of the current period is a separate accounting question, since some may relate to amounts accrued previously. Keep the allocation and the recognition as two steps.

Borrower changes, hardship and complaints

Accounts do not stay static. Borrowers change bank details, request payment date changes, ask for deferrals, dispute charges, enter hardship, and occasionally complain. Each of these has to be handled consistently, recorded in a way that flows through to your reporting, and applied within the limits your facility documents permit.

That last point catches originators out. Facility agreements frequently restrict modifications to financed receivables, either outright, above a threshold, or without provider consent. A deferral granted with good intentions can change a receivable status, affect its eligibility, or breach an amendment covenant. Know your limits before your collections team grants them, and give the team a written matrix of what they can approve alone.

Complaints handling deserves its own process with logged intake, timelines, resolution and root-cause tracking. Whatever consumer protection rules apply to your product and jurisdiction is a question for your compliance adviser. The operational requirement is the same regardless: you need a record that shows what was raised, what was done and how quickly.

Reconciliations that prove something

Run three reconciliations on a defined cadence and keep the evidence. Set the frequency from your own risk profile, volumes and contractual requirements rather than from a generic rule; the cadences suggested below are illustrative.

Cash reconciliation compares bank receipts to ledger postings, daily. This is the one in the exhibit above.

Balance reconciliation compares the sum of loan-level balances in the servicing system to the general ledger control account. A break does not automatically mean one ledger is wrong: cutoff differences and timing on late-posted items produce breaks that resolve themselves. Investigate the cause rather than assuming an error, and clear or explain it before you certify anything.

Remittance reconciliation compares what was collected to what was remitted to the collection account and applied under the facility, per the required timetable. Where the documents require collections to reach a controlled account within a set period, this reconciliation is your proof that you complied.

Keep dilution separate from credit loss in all of these. Refunds, adjustments, cancellations and billing corrections reduce balances without any borrower defaulting, and providers track them separately because they hit collateral value without appearing in delinquency statistics.

Reporting and data access obligations

Your facility will specify reports, formats, frequencies and delivery mechanics. Servicing is the source system for almost all of them. Build the extraction once, with defined fields and documented logic, rather than assembling each report by hand. Manual assembly produces month-to-month inconsistency that providers notice, and it fails at exactly the moment when volumes rise. The calendar and control structure around those deliverables is covered in reporting and compliance.

Data access provisions are separate and easy to overlook. Providers typically require the right to access servicing data, to audit the operation, and to have data delivered to a third party if the servicing arrangement ends. Confirm what your systems can actually produce against what the documents promise, before you sign rather than after.

In-house, outsourced or backup: choosing a model

The three options are not strictly alternatives. A common arrangement is a primary model plus a contracted backup, and many facilities require one.

Plan a servicing arrangement across its whole life cycle: decide what you need before you shortlist, get the obligations into the contract, monitor performance against them, and know in advance how the relationship ends. Whatever the provider's marketing says about capability, verify it against your own asset type and volumes before you rely on it.

Rehearsing the transfer before you need it

A backup servicer appointment is worth what the transfer is worth in practice, not what the engagement letter says. Labels such as cold or warm standby describe an intention, not a tested capability.

Rehearse on a cadence you set from the risk and from what your contracts require. Test the transfer using authorised, secured channels, and start with synthetic or redacted data to prove the mapping before any personal data moves. Where a live file is needed, confirm the legal basis, the security arrangements and the scope of what is transferred first.

The test itself is straightforward: send the file in the agreed format, have the backup load it into their environment, and check that payment histories, allocation rules, fee schedules, borrower contact details and delinquency status all arrive intact and interpretable. The failures are mundane: a date format that does not parse, a status code the backup does not recognise, a payment history that arrives as a summary rather than a transaction list, missing consent records for how you may contact borrowers.

Document the test, log what broke, fix the mapping, and retest. Keep the evidence, because a provider asking about business continuity wants the test results rather than the appointment letter.

What to fix first

If you are building this from a standing start, sequence it this way.

• Write the payment allocation policy and configure it in the system rather than leaving it to individual judgement.
• Stand up the daily cash reconciliation with a named owner and a suspense ageing report.
• Document the modification authority matrix, aligned to what your facility documents permit.
• Build the monthly balance reconciliation between the servicing system and the general ledger.
• Automate the standard reporting extraction from defined fields with documented logic.
• Appoint a backup, run a live file test, and fix what the test finds.

Providers will diligence this operation directly, often by watching your team work rather than by reading a policy document. The preparation for that review is covered in what capital providers need. Build the operation to survive the observation, not the questionnaire.