Backup Servicing Agreement (BUSA): Key Clauses Explained

A backup servicing agreement (BUSA) is a contract between a lender, a loan originator and a third-party servicer under which the third party stands ready to take over servicing of a loan portfolio if the originator fails. It defines the standby duties before a takeover, the events that trigger one, the deadline for completing it, and who carries which liability.

Lenders require a BUSA as a condition of most warehouse facilities and securitisations in Europe. Originators usually sign one late in the deal, under time pressure, without a clear view of which terms are standard and which are open. This guide goes through the agreement clause by clause and sets out where the market sits on each.

It is written for finance teams preparing for the negotiation. It is not legal advice. Every facility's documentation has its own logic, so use this to brief your counsel rather than to replace them.

The clauses at a glance

The table summarises where European facility documentation has settled on each clause and where the negotiation usually takes place. The sections below explain each one.

Market positions in European warehouse facilities and securitisations, as seen in practice. Individual facilities vary.
Clause	Market standard in Europe	Where it is negotiated
Parties and instruction rights	Originator pays. Lender or security trustee holds the activation right and instructs the backup servicer after a trigger.	Rarely. Lenders do not soften instruction rights.
Standby duties	Warm standby: loan-level data on a defined cadence, maintained field mappings, periodic test calculations, written readiness confirmation to the lender.	Data cadence (monthly versus daily) and whether the provider must confirm the data is usable.
Trigger events	Insolvency filing, loss of licence, uncured material breach, missed reports. Declared by the lender rather than automatic.	How early in an insolvency the trigger bites.
Activation SLA	Five to ten business days from trigger declaration to full handover, split into milestones.	When the clock starts: trigger declaration or receipt of complete data.
Liability	No liability for the period before transfer. Post-transfer cap at a multiple of total annual fees, with carve-outs for gross negligence, wilful misconduct and fraud.	The multiple.
Data access and testing	Independent automated feed over SFTP or API. Annual test at minimum, with a written report to the lender.	Bank account read access and the defined test output.
Fees	Standby retainer, sometimes a basis-point component, activation fee, post-activation servicing fee.	Whether the post-activation fee is fixed at signing.
Termination and replacement	Lender holds termination rights while the facility is outstanding. Backup servicer may resign on twelve months' notice or once a successor is in place.	Length and conditionality of the resignation right.
Governing law and coverage	Follows the facility documentation, mostly English or German law. Operational coverage confirmed per jurisdiction.	Rarely negotiated. Often overlooked.

The parties

A BUSA has three parties: the originator, which services the portfolio day to day; the backup servicer; and the lender, usually acting through a facility agent or security trustee. In German structures the trustee role is often a Sicherheitentreuhänder holding the security on behalf of the lenders. The originator pays the fees. The lender holds the right to activate.

The instruction clause follows from that allocation. Once a trigger event has been declared, the backup servicer acts on instructions from the lender or trustee only. Originators sometimes ask for a consultation right or a veto over activation. Lenders refuse, and the refusal is sound: the agreement exists for the case in which the originator can no longer be relied on, so an originator veto would defeat it. Concede this point early and spend your negotiating effort on the clauses below.

Standby duties

The standby clause governs the period between signing and any activation, which for most agreements means the entire life of the facility.

Three levels are used in the market. Cold standby means the provider holds a copy of the agreement, some portfolio documentation and little else. Onboarding starts after the trigger. Warm standby means the provider receives loan-level data on a defined cadence, keeps its field mappings current, runs periodic test calculations and confirms readiness to the lender in writing, typically each quarter or half-year. Hot standby means the provider runs a parallel servicing environment and can take over within days. Hot standby is rare in European private credit outside large securitisations because of its cost. Warm standby is what most lenders now specify.

Within warm standby, data cadence is where agreements differ most. Monthly delivery is common, especially in older templates. It is also the weakest standard a lender will accept. A backup servicer activated mid-month starts with data up to four weeks old, on a portfolio that may have deteriorated for the same reasons the servicer failed. Daily synchronisation through an automated feed closes that gap, and lenders increasingly require it for revolving facilities where the borrowing base is recalculated against live receivables.

One drafting point to check if your lender requires warm standby. The clause should oblige the provider to confirm that the data it receives can be loaded and reconciled, not merely that the files have arrived. Providers that have not built the ingestion sometimes accept the delivery obligation and push back on the confirmation. Ask to see a recent reconciliation output before you accept the softer wording. The requirements guide lists what else lenders check at this stage.

Trigger events

Facility documents usually call these Servicer Termination Events or Servicer Defaults. The standard list is an insolvency filing by or against the originator, loss of a licence the originator needs in order to service the loans, a material breach not cured within a defined period, and servicing reports missed over consecutive periods. Some agreements add a financial covenant breach or a rating downgrade of the originator.

Two points get negotiated. The first is whether a trigger fires automatically or has to be declared by the lender. Declaration is the market position. An automatic trigger sounds stronger for the lender but leaves the transfer date uncertain, and an uncertain date in the middle of a servicer collapse produces disputes about who was responsible for the portfolio on which day.

The second is how early in an insolvency the trigger bites. German facilities increasingly reference the filing of an insolvency application under section 13 InsO or the appointment of a preliminary insolvency administrator under section 21 InsO, rather than waiting for the court to open proceedings under section 27 InsO. The gap between filing and opening can be several months, and the servicing operation usually deteriorates throughout.

For STS securitisations, Article 21(7)(b) of the EU Securitisation Regulation requires the transaction documents to set out how a servicer default or insolvency is handled without servicing being interrupted. The trigger and transfer clauses of the BUSA are where that requirement is met. The regulatory guide covers the rule and the related Article 7 reporting duties in detail.

Activation and the SLA

Five to ten business days from trigger declaration to full handover is the typical window in European facilities. Shorter windows appear in hot standby arrangements. Longer ones appear in cold standby, where the first weeks go on onboarding work that should have been done at signing.

Well-drafted clauses break the window into milestones rather than setting a single deadline: data access confirmed, first borrowing base calculation on live data delivered to the lender, full assumption of collections and reporting. Each milestone has its own date and its own consequence if missed.

The point to watch is when the clock starts. An SLA that runs from "receipt of complete and accurate data" instead of from the trigger declaration lets the provider attribute any delay to data quality, and in an insolvency the data will not be complete. A provider that has been receiving and testing the data under warm standby has no reason to resist the stricter start date. If it does resist, ask what it has been doing with the data.

Liability

Two liability questions arise in every BUSA negotiation. One is settled in the market. The other is not.

Settled: the backup servicer accepts no liability for anything that happened before the transfer date. It takes the portfolio in the state it finds it and does not warrant the originator's past servicing, data quality or compliance. This exclusion appears in essentially all European facility documentation and is not worth negotiating time.

Not settled: the cap on the backup servicer's own liability after takeover. Providers push for a cap expressed as a multiple of annual fees, and some open at twelve months of standby retainer. Lenders sometimes ask for uncapped liability or a cap referenced to the portfolio balance. Neither extreme reflects the economics. A standby fee cannot price unlimited exposure on a portfolio several hundred times its size, and one year of retainer is immaterial against the cost of a failed transition.

The market position in European facilities is a cap at a multiple of total annual fees, standby plus post-activation servicing, with carve-outs for gross negligence, wilful misconduct and fraud. Under German law the carve-out for wilful misconduct is not a concession, because liability for intent cannot be excluded in advance (section 276(3) BGB). Where the multiple lands depends on portfolio size and asset class. If a provider refuses to move above its annual retainer, ask for its transition track record before you accept the cap. The two are related.

Data access and testing

The backup servicer needs its own route to the loan-level data: an automated feed over SFTP or an API connection, running on a schedule the provider controls. A data room that the originator refreshes on request does not meet the standard, because access that depends on the originator's cooperation stops working at the moment the agreement is for. An insolvency administrator has other priorities than answering data requests from a servicer it did not appoint.

Loan-level data is half the picture. Stronger arrangements also give the backup servicer read access to the SPV's bank accounts and payment flows, through EBICS or an open banking account-information connection. That lets the provider reconcile reported collections against actual cash on a continuous basis. Before any trigger it works as an early-warning signal. After one, it is the fastest route to a borrowing base the lender can rely on. Servicer-reported figures with no independent cash check are the first thing that fails in a fraud or insolvency.

Testing should be annual at minimum, and the clause should name the output: a written test report to the lender covering data completeness, reconciliation results and any gaps found. Test clauses without a defined deliverable tend not to be enforced by anyone.

Fees

Fees have three components. A readiness retainer, charged monthly or annually, covers standby. Some agreements add a volume-based component in basis points on the outstanding balance. An activation fee plus ongoing servicing fees apply if a takeover happens. The retainer is the main cost for most originators, and the selection guide covers how to compare providers on it.

The common drafting error is leaving the post-activation servicing fee to "good faith negotiation upon activation". Agree it at signing, or define it by formula against the outstanding balance or the number of active contracts. Otherwise the provider sets its price at the one moment when neither the originator nor the lender can walk away.

Termination and replacement

While the facility is outstanding, the originator cannot terminate at will. The backup servicer is a condition of the facility, so termination rights sit with the lender. The originator keeps a right to terminate for the backup servicer's own insolvency, material breach or loss of capability, usually conditional on a lender-approved replacement being in place first.

The backup servicer's resignation clause deserves the same attention. The market position is twelve months' notice, or resignation conditional on a successor having been appointed. A short, unconditional resignation right gives the provider a way out at the point where the mandate turns from retainer income into work. Check also what happens to data and documentation on exit. The agreement should oblige the outgoing provider to hand over to the successor in a usable format and within a defined period.

Jurisdiction and coverage

Governing law follows the facility documentation, which in European private credit mostly means English or German law. The SPV is often in Luxembourg, Ireland or the Netherlands, while the receivables and the borrowers sit in one or more other countries.

That split is why operational coverage matters more than the governing law clause. A portfolio with receivables in several jurisdictions needs servicing capability in each: the licences to collect, the language, the local collections infrastructure, the data protection arrangements. None of that is answered by the choice of law. Ask the provider to confirm coverage per jurisdiction in writing before signing, and attach the confirmation to the agreement.

Frequently asked questions

What is a backup servicing agreement?

A backup servicing agreement is the contract that appoints a standby servicer for a loan portfolio. The lender, the originator and the backup servicer sign it. It sets out the standby duties, the events that trigger a takeover, the activation deadline, the fees and the liability of each party. BUSA is the usual abbreviation. Some documents say back-up servicer agreement or BSA.

When is a backup servicer required?

When the lender requires one, which is the case in most warehouse facilities and securitisations in Europe. For STS securitisations, the EU Securitisation Regulation requires the documentation to provide for servicer replacement, and rating agencies expect a backup servicer in rated transactions. The requirements guide on this site covers the lender criteria in detail.

What is the difference between cold, warm and hot standby?

Cold standby means the provider is appointed but only starts onboarding after a trigger event. Warm standby means it receives portfolio data on a regular cadence, keeps its systems mapped to the originator's and confirms readiness to the lender. Hot standby means it runs a parallel servicing environment and can take over within days. Most European lenders now specify warm standby.

How much does a backup servicer cost?

The cost is a standby retainer, sometimes with a basis-point component on the outstanding balance, plus an activation fee and servicing fees if a takeover occurs. The level depends on portfolio size, asset class, data complexity and the standby level the lender requires. Compare retainers across providers on the same standby definition, or the comparison is meaningless.

Is the BUSA negotiable at all if the lender requires it?

The requirement is not negotiable. The terms are. Liability caps, fee levels, data cadence and SLA definitions all have market ranges, and lenders accept positions within them. What lenders will not accept is a weaker standby standard than the term sheet specified.

Who pays for the backup servicer?

The originator, in almost all European structures. The fees either run through the SPV waterfall or are paid directly by the originator. The economic burden sits with the originator either way.

Can the same firm act as backup servicer and calculation agent?

Yes, and it is often efficient: the calculation agent already ingests the loan-level data the backup servicer needs. The lender has to be comfortable with the concentration. Most are, provided the provider is independent of the originator.

About this guide. Published by Credibur GmbH, which acts as backup servicer and calculation agent on facilities across Europe. The market positions described here apply to any provider, Credibur included. For the wider topic, start with what a backup servicer is, then the requirements guide, the selection guide and the whitepaper.

The Backup Servicing Agreement: Key Clauses Explained