Backup Servicer Requirements: What Your Lender Will Ask For
If a lender has sent you a term sheet with a backup servicer requirement, or if you are structuring a facility and want to get ahead of it, this page covers what institutional lenders actually expect and what separates a credible appointment from a box-ticking exercise.
Why lenders require a backup servicer
When a debt fund or bank lends against a pool of receivables, their repayment depends on those receivables being collected and reported on correctly. If the originator fails, that does not stop being true. Someone still needs to run the book.
That is the logic behind the backup servicer requirement. It has nothing to do with distrust. Every institutional capital provider in European structured credit takes the same position, and it mirrors what US asset-backed finance has required for decades. The Dechert ABF primer covers the facility mechanics in useful detail: The ABCs of ABF: Basic Financing Structures.
Without a pre-appointed backup servicer, a wind-down creates an operational gap: no collections, no borrowing base, no investor reports, no waterfall payments. That destroys value for the lender and the originator alike. Getting a backup servicer in place early is as much in your interest as theirs.
What a backup servicer covenant in a term sheet actually looks like
Before getting into what lenders require operationally, it helps to know how the requirement is typically expressed. Backup servicer language appears in term sheets in varying forms. Here is a representative example of the kind of clause you will see:
"Prior to first drawdown, the Borrower shall appoint a backup servicer acceptable to the Lender, on terms approved by the Lender, and shall deliver a fully executed backup servicing agreement to the Lender. The backup servicer shall have access to all portfolio data necessary to assume the servicing function within [5] Business Days of a Servicer Termination Event."
The exact wording varies by lender and counsel. But the core obligations (named appointment, lender approval, data access, and defined transition timeline) are consistent across LMA-based and bespoke documentation. Any term sheet that includes a backup servicer covenant should be reviewed for these four elements before you engage a provider.
What lenders typically require: the term sheet reality
The backup servicer requirement almost always appears in the term sheet before it appears in the facility agreement. By the time you are negotiating the long-form documentation, the lender has already decided what they want. Understanding the standard requirements early saves renegotiation cost later.
Named appointment before financial close
A specific, identified backup servicer must be in place before the facility is signed and funded. "We will find someone" does not work at closing. The backup servicer is either named in the servicing agreement or explicitly referenced in the facility agreement, with defined handover obligations attached.
A data access agreement
The backup servicer must be able to pull your portfolio data without your cooperation. In a wind-down, you may be in administration or simply unable to help. The arrangement needs to work independently. Some lenders require live data feeds before closing. Others accept a documented escrow mechanism. The practical test: could the backup servicer get the data they need if your entire team stopped answering the phone tomorrow?
Warm standby versus cold standby
Cold standby means a signed agreement and nothing else. Warm standby means the backup servicer has ingested your data, mapped your asset-level fields, understood your eligibility criteria, and can produce your standard investor report from the received data. Most European debt funds and bank conduits ask for warm standby now, particularly above EUR 20 million. Some include a transition SLA: typically 5 to 10 business days from trigger to full operational handover.
A servicer transition plan
A written document covering trigger event definitions, notification sequences, data transfer protocols, and the timeline from trigger to first operational report. Usually prepared jointly by the originator and backup servicer before closing and attached as a schedule to the servicing agreement.
Regulatory and operational standing
Lenders want to know the backup servicer can actually operate in your jurisdiction and asset class. Do they hold the licences needed? Have they been through an activation before? A newly formed entity with no track record will not pass most institutional credit committees.
How lender requirements differ by facility type
Not all backup servicer requirements are the same. Lenders calibrate what they ask for based on the structure and size of the facility.
Bank conduits and ABCP programmes
These tend to have the most prescriptive requirements: named backup servicer, warm standby with demonstrated data access, periodic testing at least annually, and often a requirement for the backup servicer to hold or be able to obtain relevant servicer qualifications. These requirements are driven partly by the conduit's own regulatory obligations and partly by rating agency criteria if the programme is rated.
Debt funds and private credit managers
These vary considerably. Larger, more institutional funds often replicate bank-level requirements: warm standby, documented transition plan, lender approval of the provider. Smaller or more entrepreneurial funds may accept a cold standby appointment, particularly at smaller facility sizes or for originators with strong track records. The direction of travel is toward stricter requirements as the European private credit market matures.
Bank bilateral facilities
Direct lending from a regulated bank rather than through a conduit tends to be driven by the bank's internal credit and operational risk policies. German banks operating under MaRisk have explicit obligations around continuity of outsourced functions, which flow directly into what they require from their borrowers. Expect warm standby as a baseline for any BaFin-regulated lender.
Syndicated facilities
These add a layer of complexity: multiple lenders may have different views on what constitutes an acceptable backup servicer, and the agent bank must coordinate approval. Propose the backup servicer as early as possible in a syndicated deal, before individual lender credit committees form independent views.
What to look for in a backup servicer: a practical checklist
- Asset class experience: verified, not claimed. Ask for specific references: which facilities have they served as backup or primary servicer, in which asset class, and who was the lender? BNPL receivables, SME term loans, equipment leasing, trade receivables, and solar or green asset portfolios each have distinct data structures, debtor profiles, and reporting conventions. A servicer who knows one does not automatically know the others.
- Data ingestion capability. The backup servicer's ability to take over your portfolio depends entirely on how quickly they can ingest, validate, and operate on your loan-level data. Ask them to walk you through their data onboarding process: what formats do they accept, how long does field mapping take for a new asset class, and what happens when there are data quality issues in the handover package? The answers reveal whether their capability is operational or only contractual.
- Borrowing base and calculation agent experience. Many backup servicers can handle collections and borrower communication. Fewer have genuine experience running the calculation agent function: computing borrowing base utilisation, applying eligibility criteria and concentration limits, running covenant tests, and producing the lender report in the format required by the facility agreement. If your facility has a calculation agent function, confirm explicitly that the backup servicer can handle it.
- Investor reporting templates. Ask to see a sample investor report. It should reflect the complexity of a real facility, not a generic template. If they cannot show you a report for a structure similar to yours, that is a signal.
- Fee structure transparency. Backup servicing fee structures vary materially: some providers charge a flat annual retainer, others charge AUM-based fees (basis points on outstanding portfolio balance), and most charge a separate activation fee if the backup servicer is actually called upon. Understand all three components before signing. The retainer pays for readiness; the activation fee pays for the operational work. Both should be proportionate to the complexity of your structure.
The negotiation: what you can push back on and what you cannot
Most backup servicer requirements are non-negotiable in their core structure: a named provider, lender approval, data access, and a defined transition SLA. These are credit conditions, not commercial preferences, and lenders do not compromise on them.
What is negotiable is the implementation detail.
The warm standby SLA
The 5 to 10 business day window is a starting point, not a fixed standard. For simpler structures with clean data, 3 to 5 business days is achievable and gives the lender more comfort. For complex multi-asset structures, 10 to 15 days is a more realistic commitment and a more defensible one. Agree a number you can actually deliver, not one that looks good in the term sheet.
The testing frequency
Lenders sometimes ask for quarterly or semi-annual testing of the warm standby. Annual testing is standard and sufficient for most structures. If a lender asks for quarterly, push back with a documented annual testing protocol and an ad-hoc test right before signing.
The scope of data access
Some lenders ask for real-time data access, which may be technically complex depending on your loan management system. A daily or weekly batch feed, combined with a defined data escrow mechanism, is operationally equivalent and easier to implement. Make the case for it early.
The approval process for replacing the backup servicer
Facility terms sometimes require lender consent to replace the backup servicer, with no defined timeline for that consent. Negotiate a deemed-consent mechanism: if the lender does not object within [10] business days of notification, the replacement is approved. This avoids situations where a lender inadvertently blocks a servicer change by not responding.
Common mistakes originators make
Treating it as a formality
The backup servicer requirement is a legal condition precedent. Leaving it to the last minute before closing creates lender friction and occasionally kills deals when a proposed provider is rejected at credit committee. Raise it early.
Choosing on price
The cheapest provider is usually the one with the least operational depth. An entity that has signed backup servicing agreements across multiple asset classes but has never onboarded to any of them, never produced a real investor report, never been through an activation: that is a letter in a drawer, not a backup servicer.
Signing the data access agreement and never testing it
This is the most common operational gap in European backup servicing arrangements. The agreement gets signed at closing, no one tests whether the data can actually be delivered in a usable format, and the problem only surfaces when it matters. Test it before closing if possible, within 90 days if not.
Not putting backup servicer scope in the facility documentation from the start
Retrofitting it into a live facility is expensive. Build it in from the beginning: calculation agent functions, data access protocols, transition SLAs, and the regulatory notification sequence should all be in the servicing agreement, not a side letter.
Underestimating the approval timeline
Lenders run their backup servicer review in parallel with credit committee approval. If your proposed provider has not been approved by the time you are at signing, you are delaying the close. Propose your backup servicer at term sheet stage, not documentation stage.
What happens if you close without one
It happens. A deal closes without a backup servicer in place: either because the condition precedent was waived by the lender at closing, or because an interim arrangement was agreed pending a formal appointment.
The consequences depend on the facility terms. In some cases, closing without a backup servicer triggers a covenant breach that must be cured within a defined remedy period (typically 30 to 60 days). In others, it is an event of default that gives the lender acceleration rights, though in practice lenders rarely accelerate for a curable operational breach if the relationship is otherwise intact.
The more common consequence is reputational: it signals to the lender that operational diligence is not a priority for the originator. That affects the relationship at the next amendment, the next facility increase, and the next refinancing. Lenders have long memories about closing conditions that were not met.
If you are in a post-closing cure period, appoint a backup servicer immediately rather than treating the remedy period as runway. The cost of speed (accepting a slightly higher retainer to close quickly rather than running a lengthy selection process) is almost always worth it.
The regulatory dimension
The backup servicer requirement is partly contractual and partly regulatory. The EU Securitisation Regulation, DORA, and MaRisk all bear on it, depending on the structure and the regulatory status of the originator. For the full treatment, see Regulatory requirements for backup servicers in Europe.
Need a Backup Servicer for your facility?
Credibur is operational as Backup Servicer on facilities across Europe. If your lender has sent you a term sheet with a backup servicer requirement, or you are structuring a new facility, the fastest path is a short call.
Book a 30-minute call