The Backup Servicing Agreement: Key Clauses Explained
Every facility with a backup servicer covenant produces the same document. The backup servicing agreement, BUSA for short, sets out what the backup servicer does before activation, what triggers a takeover, and who carries which risk. Most originators sign one under deal pressure, without knowing which terms are standard and which are negotiable. This guide covers the agreement clause by clause.
It is not legal advice. Every facility has its own documentation logic. The purpose here is preparation for the negotiation, not a substitute for counsel.
The parties
A BUSA has three parties: the originator as primary servicer, the backup servicer, and the lender or security trustee. The originator pays the fees. The lender holds the activation right. The agreement reads accordingly.
Instruction rights are the clearest example. After a trigger event, the backup servicer takes instructions from the lender or trustee, not from the originator. Originators sometimes attempt to soften this clause. Lenders do not accept it, for a structural reason: the arrangement exists for the scenario where the originator is the problem.
Standby duties
The standby clause covers the period between signing and activation.
A cold standby clause says "maintain readiness" and not much else. A warm standby clause is specific: loan-level data on a defined cadence, maintained field mappings, periodic test calculations, written readiness confirmation to the lender each quarter or half-year.
The cadence is where agreements diverge most. Monthly delivery is still common, particularly in older documentation. It is also the weakest defensible standard: a backup servicer activated mid-cycle starts a takeover with data up to a month stale, on a portfolio that may have deteriorated precisely because the servicer was failing. Daily synchronisation, typically via automated feed rather than manual file delivery, closes that gap and is increasingly what lenders require for revolving facilities with dynamic borrowing bases.
One check where the lender requires warm standby: the clause should oblige the provider to confirm the data is usable, not merely to receive files. A recurring pattern in negotiations is a provider accepting the data delivery clause readily and resisting any ingestion confirmation. That resistance is informative about the state of its onboarding.
Trigger events
Standard triggers: insolvency or an insolvency filing, loss of a required licence, material breach uncured within a defined period, missed servicing reports over consecutive periods.
Two points are commonly negotiated. Automatic trigger versus lender declaration: declaration is the standard, because automatic triggers leave the transfer date unclear, and date ambiguity in the middle of a servicer collapse is expensive. And how early in an insolvency the trigger bites: German facilities increasingly reference preliminary proceedings and the expert assessment stage rather than the formal opening of proceedings. The operational deterioration starts months earlier.
Activation and the SLA
Five to ten business days from trigger declaration to full handover is the typical window. Well-drafted clauses separate three milestones: data access confirmed, first borrowing base calculation on live data, full assumption of servicing.
The detail that matters is when the clock starts. An SLA running from "receipt of complete data" instead of from the trigger declaration lets the provider blame data quality for any delay. A provider that has tested the data has no reason to resist the harder version.
Liability
Two questions arise in every BUSA negotiation. One is settled, one is not.
Settled: no liability for anything before the transfer date. The pre-transfer exclusion is standard across European facility documentation. The backup servicer runs the portfolio from the state it is in; it does not warrant the past. This point is rarely worth negotiating.
Not settled: the cap on the backup servicer's own liability after takeover. Providers push for a cap at a multiple of annual fees, sometimes as low as twelve months of retainer. Lenders occasionally demand uncapped liability or a cap referenced to portfolio size. Both positions ignore the economics. A standby fee cannot price unlimited exposure on a portfolio several hundred times its size, and one year of retainer is trivial against the cost of a failed transition.
Market practice in European facilities is a cap at a multiple of total annual fees, standby plus activation, with carve-outs for gross negligence, wilful misconduct, and fraud. Where the multiple lands depends on portfolio size and asset class. A provider that refuses any cap above its annual retainer is making a statement about its confidence in its own transition capability.
Data access and testing
The backup servicer needs an independent path to the loan-level data: an automated daily feed via SFTP or API, not a data room refreshed on request. Access that depends on the originator's cooperation fails in exactly the scenario the agreement exists for. Insolvent originators do not answer data requests quickly.
Loan-level data alone is half the picture. The stronger arrangements also give the backup servicer live read access to the SPV's bank accounts and payment flows, via EBICS or open banking APIs. This allows continuous reconciliation of reported collections against actual cash movement, which is both an early-warning mechanism before any trigger fires and the fastest route to a reliable borrowing base after one does. Servicer-reported figures with no independent cash verification are exactly what fails in a fraud or insolvency scenario.
Testing: annual as a minimum, with a written test report to the lender as the defined output. Without a defined output, the test clause tends to be ignored by all sides.
Fees
Three components. A readiness retainer, monthly or annual. Sometimes an AUM-based component in basis points on the outstanding balance. An activation fee plus ongoing servicing fees if the takeover happens.
A frequent drafting mistake: leaving the post-activation servicing fee to "good faith negotiation upon activation." It should be agreed at signing or defined by formula. Otherwise the provider holds a monopoly position at the one moment no party can walk away.
Termination and replacement
While the facility is outstanding, the originator cannot freely terminate. The backup servicer is a condition of the facility; termination rights sit with the lender. The originator keeps termination rights for the backup servicer's own insolvency, material breach, or loss of capability, subject to a lender-approved replacement being in place first.
The backup servicer's own resignation clause deserves attention. Twelve months' notice, or resignation conditional on a successor, is the market position. A short, unconditional resignation right reserves the provider the option to leave when the mandate becomes real work.
Jurisdiction and coverage
Governing law follows the facility documentation, mostly English or German law in European private credit. The question that gets overlooked is operational coverage. A portfolio with receivables in several jurisdictions needs servicing capability in each: licensing, language, collections infrastructure. The governing law clause answers none of that. Coverage should be confirmed per jurisdiction, in writing, before signing.
Frequently asked questions
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 run through the SPV waterfall or are paid directly. 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.
Published by Credibur, a backup servicer and calculation agent operational on facilities across Europe. The criteria and market ranges above apply to any provider, including Credibur. For the broader topic, start with What is a backup servicer, the selection guide, and the whitepaper.
Negotiating a BUSA right now?
Credibur is operational as backup servicer and calculation agent on facilities across Europe. If you are working through a backup servicing agreement and want to know where the market sits on the clauses that matter, the fastest path is a short call.
Book a 30-minute call