06 Sep 2026

A Maturity Extension Is Not a Refinance: Why Private Credit Needs Loan-State History

US software borrowers are increasingly using amend-and-extend transactions to push debt maturities out by two or three years while lenders demand higher pricing, tighter covenants, stronger collateral protections and better reporting. The loan can remain the same legal asset while its contractual and economic state changes materially. That makes amendment history, consent provenance and effective-dated loan terms essential infrastructure for private credit.

Create a structured loan record

This starts a temporary private draft. It is not public, listed for sale or shared automatically.

Credit manager Secured loan Learn

A loan has a maturity date.

That sounds like one of the simplest fields in credit.

Maturity: 31 March 2027

Then the borrower and lenders agree to extend it.

The system is updated.

Maturity: 31 March 2030

The current field may be correct.

The asset history is now incomplete.

What disappeared?

The original maturity.

The extension date.

The lender consent.

The higher price the borrower may have agreed to pay.

Any new covenant.

Any additional collateral protection.

Any new reporting obligation.

Any amortisation introduced.

Any lender that did not participate.

And perhaps most importantly, the reason the extension was needed.

This is becoming a practical issue in US leveraged and private-credit software markets.

Financial Times reporting at the end of August 2026 described private-equity-backed software companies increasingly turning to amend-and-extend transactions that push existing maturities out by two or three years rather than completing conventional seven-year refinancings. Lenders are using the negotiations to demand higher yields, tighter documentation and stronger credit protections. Financial Times: Software companies pay steep price to buy time against AI threat

The timing is significant.

Apollo highlighted in March 2026 a $40 billion software maturity wall in 2028, concentrated in lower-rated credits and exposed to both refinancing costs and uncertainty around artificial-intelligence disruption. Apollo Academy: Software Maturity Wall

J.P. Morgan Asset Management has separately described AI as causing a structural reassessment of software credit risk and identified refinancing seizure as one of four channels through which disruption can move from business-model pressure into credit impairment. J.P. Morgan Asset Management: Disruption decoded—How AI is rewriting the software playbook for private credit investors

That creates an important infrastructure question:

If the borrower and facility remain the same, but maturity, pricing, covenants and collateral protections change, is it still the same asset?

Usually, yes.

But it is no longer the same state of that asset.

Amend-and-extend is not simply “change the date”

At its simplest, an amend-and-extend transaction changes the maturity of existing debt.

In practice, lenders may agree to extend in exchange for:

a higher margin;
an upfront or consent fee;
original-issue discount;
additional amortisation;
tighter financial covenants;
stronger information rights;
enhanced collateral protections;
additional guarantees;
restrictions on asset transfers;
restrictions on future debt;
liability-management protections;
or other creditor concessions.

The loan may therefore retain the same legal identity while changing materially as an economic object.

A database update from:

Maturity: 2027

to:

Maturity: 2030

captures only one part of the transaction.

A refinancing is a different lifecycle event

A true refinancing normally looks more like:

Old Loan
    ->
New financing raised
    ->
Old Loan repaid
    ->
Old Loan extinguished
    ->
New Loan begins

The new loan can have its own:

origination date;
principal;
maturity;
lender group;
pricing;
security package;
covenants;
and lifecycle.

An amend-and-extend is structurally different:

Existing Loan
    ->
Amendment
    ->
Same Loan
    ->
New effective terms

This is why a maturity extension should not automatically create a new asset record.

The better model is continuity plus a new lifecycle event.

Loans need effective-dated terms

A traditional portfolio table might show:

Borrower: SoftwareCo
Margin: SOFR + 475 bps
Maturity: 2030
Amortisation: 1%

That is enough to calculate current cash flows.

It is not enough for diligence.

A strong loan record should also be able to reconstruct:

What were the original terms?
What were the terms immediately before the amendment?
What changed?
When did the change become effective?
Who approved it?

For example:

Facility: Loan ABC

State 1
Effective from: 2021-09-15
Maturity: 2027-03-31
Margin: SOFR + 325 bps
Amortisation: 0%

State 2
Effective from: 2026-08-28
Maturity: 2030-03-31
Margin: SOFR + 475 bps
Amortisation: 1%

The current state remains simple.

The historical state remains auditable.

Proofpoint shows that time has a price

Proofpoint became one of the visible examples of the 2026 software refinancing cycle.

Financial Times reporting described approximately $4.3 billion of debt being refinanced at a yield around 9.3%, while another portion of the capital structure was left untouched because additional refinancing would have been more expensive.

The Wall Street Journal separately reported that Proofpoint and Gainwell Technologies completed major debt transactions after granting stronger lender protections, including provisions intended to constrain future liability-management transactions. Wall Street Journal: Select Tech Borrowers Pull Off Debt Refinancing Despite SaaSpocalypse Fears

The individual structures differ.

The broader signal is clear.

A borrower may ask for:

More time

The lender may answer:

Higher price
+
More control
+
Better information
+
Stronger collateral protection

The extension is therefore an exchange of contractual rights.

Sophos shows why proposed terms are not current terms

Sophos provides another useful example.

August reporting said its sponsor was considering concessions to existing creditors that could include:

a higher coupon;
scheduled principal amortisation;
and tighter covenants.

Those terms were still under discussion.

That creates four distinct states:

Proposed
Agreed
Consented
Effective

A system should not change the live maturity or covenant package merely because negotiations have begun.

A proposed amendment is an event.

An effective amendment is another event.

Consent belongs in the asset record

Loan amendments require authority.

Depending on the credit agreement, changes may require:

majority lender consent;
supermajority consent;
affected-lender consent;
unanimous lender consent;
agent execution;
guarantor acknowledgement;
or another specified threshold.

Maturity is often especially sensitive because it can fall within provisions commonly treated as lender-specific or sacred rights.

The exact legal rule depends on the loan agreement.

The infrastructure principle is broader:

A changed term should be connected to the authority that made it effective.

A useful record can preserve:

amendment document;
execution date;
effective date;
required consent threshold;
consenting amount;
consenting lenders;
non-consenting lenders where relevant;
agent confirmation;
and resulting terms.

One facility can split into different maturity states

Not every lender must necessarily extend.

Suppose a $1 billion facility has ten lenders.

Eight agree to an extension.

Two do not.

The facility may now contain:

$800m Extended Tranche
Maturity: 2030

$200m Non-Extended Tranche
Maturity: 2027

A single field called:

Maturity

is no longer sufficient at facility level.

The record needs a relationship between:

Facility
    ->
Tranche / lender position
    ->
Effective terms

This matters for valuation, secondary trading and refinancing risk.

“Performing” is not enough

Consider two loans.

Loan A:

Interest current
Covenants compliant
Maturity: 2030
Strong refinancing access

Loan B:

Interest current
Covenants compliant
Maturity: 2027
Refinancing negotiations difficult

Both can be classified:

Status: Performing

But the credit states are not equivalent.

A stronger private-credit record should distinguish:

payment status;
covenant status;
maturity proximity;
amendment status;
refinancing status;
market price;
and current lender engagement.

The purpose is not to manufacture a credit rating.

It is to preserve the facts around the asset.

The 2028 maturity wall is really a state-transition wall

The headline is that roughly $40 billion of speculative-grade software debt comes due in 2028.

Operationally, the important period starts earlier.

Borrowers will spend 2026 and 2027:

refinancing;
extending;
amending;
repaying;
exchanging;
issuing new debt;
raising equity;
selling assets;
or entering restructuring negotiations.

Each transaction creates new documents and new asset states.

The real workflow looks like:

Original facility
    ->
Refinancing analysis
    ->
Proposed amendment
    ->
Lender negotiation
    ->
Consent
    ->
Effective amendment
    ->
New term state
    ->
New valuation

The maturity date is only one event in a longer process.

AI risk makes historical underwriting assumptions important

Software was historically attractive to private-credit investors because many businesses had:

recurring revenue;
high margins;
low capital intensity;
strong customer retention;
and significant sponsor equity.

AI is forcing lenders to reconsider how durable those characteristics are.

J.P. Morgan Asset Management identifies four transmission channels from AI disruption into credit impairment:

revenue erosion;
margin compression;
valuation compression; and
refinancing seizure.

The fourth channel matters directly to amend-and-extend.

A company can still pay interest today and yet face materially higher credit risk if lenders are unwilling to refinance it in two years.

This means refinancing status can become important before default.

Amendment history can reveal risk that current terms hide

Consider two loans with identical current terms:

Maturity: 2030
Margin: SOFR + 475 bps

Loan A was originated on those terms.

Loan B originally matured in 2026, received a covenant waiver, and was later extended to 2030 after lenders demanded stronger collateral protections.

Their current fields look the same.

Their histories do not.

That history can matter to:

a new lender;
a secondary buyer;
a credit committee;
a servicer;
a restructuring adviser;
or an investor reviewing the portfolio.

Current state and path-to-current-state are different data.

Covenant history should not be overwritten

Suppose a leverage covenant changes from:

7.0x

to:

6.0x

If the database simply replaces the old value, an analyst reviewing prior reporting periods may apply the new covenant retrospectively.

That can create a false breach.

A covenant record should therefore include:

Threshold
Effective from
Effective to
Testing frequency
Test date
Test result
Source document

This is a broader rule for contract-backed assets:

terms need time.

Better reporting can be part of the lender’s compensation

Not every lender concession is economic in the narrow sense.

An extension may require better information.

That can include:

more frequent financial reporting;
liquidity reporting;
ARR reporting;
customer-retention data;
forecasts;
compliance certificates;
collateral reports;
or management access.

These rights do not increase principal.

They can still change the quality of the lender’s position.

A Loan Asset Passport should therefore treat information rights as part of the current contractual state.

Collateral protections can change without the loan changing identity

Recent software transactions have also focused on protections against liability-management transactions.

Lenders may seek tighter restrictions around:

asset transfers;
unrestricted subsidiaries;
intellectual-property transfers;
priming debt;
collateral releases;
amendment voting;
and new senior obligations.

The loan can have the same borrower, principal and maturity while the collateral perimeter becomes stronger or weaker.

A portfolio record that tracks only balance and coupon will miss this change.

New money should not disappear inside an amendment

Some transactions combine extension and new financing.

For example:

Existing loan: $1.0bn
Existing amount extended: $800m
New-money tranche: $200m

These are not the same asset event.

The system should distinguish:

Existing principal amended

from:

New principal originated

Otherwise new credit can disappear inside an amended facility balance.

Amendment fees are not loan principal

An extension can involve:

consent fees;
amendment fees;
original issue discount;
exit fees;
or incremental interest.

These amounts should not automatically be mixed into principal.

A useful record distinguishes:

Outstanding principal
Accrued interest
Cash amendment fee
Capitalised fee
OID
Market price

The numbers may all relate to the same transaction.

They represent different economic objects.

A Loan Asset Passport should treat amendments as first-class objects

For DaDepo, the amendment should not be buried in a document folder.

It should be a structured lifecycle event.

Facility identity

borrower;
facility ID;
original principal;
origination date;
governing law;
administrative agent;
original lender group;
guarantors;
and original security package.

Current terms

current principal;
benchmark;
spread;
floor;
maturity;
amortisation;
payment frequency;
and current fees.

Amendment event

amendment number;
proposed date;
execution date;
effective date;
maturity change;
pricing change;
amortisation change;
covenant change;
collateral change;
reporting change;
new-money component;
and fees.

Consent

required threshold;
consenting amount;
consenting percentage;
affected lenders;
agent confirmation;
borrower execution;
guarantor acknowledgement;
and supporting evidence.

Covenant state

covenant;
threshold;
effective period;
test frequency;
latest test;
and source.

Security state

collateral;
guarantor;
priority;
release conditions;
amendment history;
and current perimeter.

Position layer

lender;
principal held;
extended or non-extended status;
tranche;
maturity;
voting status;
and transfer history.

Provenance

original credit agreement;
amendment;
consent;
lender notice;
agent record;
covenant certificate;
public filing;
review status;
version;
and last updated date.

The PDF remains evidence.

The lifecycle event becomes data.

AI can compare agreements—but should not decide legal effectiveness

AI can be very useful when comparing versions of long credit agreements.

It can help identify:

changed maturity;
changed spread;
new covenant thresholds;
additional guarantors;
deleted baskets;
stronger reporting;
altered collateral language;
and new lender protections.

That can reduce review time.

But AI should not independently determine:

that the amendment was validly executed;
that the correct lenders consented;
that a sacred right was properly modified;
that security is perfected;
that the amended contract is enforceable;
or that the borrower is now a better credit.

AI can identify the change.

Authority determines whether the change is real.

What DaDepo can contribute

DaDepo’s role is not to negotiate extensions.

The opportunity is to preserve a private loan as a living financial asset.

A Loan Asset Passport can connect:

Original loan
    ->
Lender positions
    ->
Amendment proposal
    ->
Consent
    ->
Effective amendment
    ->
Current terms
    ->
Covenant monitoring
    ->
Refinancing process
    ->
Repayment / further amendment

That creates a cleaner foundation for:

private-credit portfolio management;
leveraged-loan diligence;
loan trading;
servicing;
restructuring;
amendment consent;
covenant monitoring;
and investor reporting.

The current state stays easy to use.

The historical state remains auditable.

What DaDepo does—and does not do

Creating or reviewing a Loan Asset Passport does not mean that DaDepo has:

authenticated every credit document;
determined that an amendment is legally effective;
verified lender consent;
interpreted sacred-right provisions;
determined voting rights;
verified security perfection;
valued the loan or collateral;
assessed AI disruption;
predicted refinancing success;
determined borrower solvency;
recommended an extension;
negotiated an amendment;
provided financing;
acted as administrative agent;
serviced or restructured debt;
assigned a credit rating;
recommended an investment;
or provided legal, accounting, tax, investment, restructuring, underwriting, credit-rating or valuation advice.

Important: DaDepo provides technology and information tools. It does not provide legal, financial, investment, tax, accounting, lending, loan-trading, servicing, restructuring, agency, underwriting, credit-rating or valuation advice or services unless a specific service is expressly identified and lawfully provided. The effect of an amendment, extension, refinancing, covenant change, consent or collateral modification depends on the transaction documents, governing law and facts of the relevant financing.

A practical amend-and-extend checklist

Before a maturity date is simply overwritten in a portfolio system, ask:

Identity: Is this still the same facility or has a new facility been created?
Original maturity: What was the contractual maturity before the transaction?
New maturity: What maturity is now effective?
Effective date: When did the amendment become legally effective?
Pricing: Did margin, floor, fee or OID change?
Amortisation: Were scheduled principal payments changed?
Principal: Was new money added?
Tranches: Did extended and non-extended positions split?
Consent: Which lenders were required to consent?
Participation: Which lenders actually extended?
Voting: Did voting rights or thresholds change?
Covenants: Which covenants changed and from what date?
Collateral: Was the collateral perimeter changed?
Guarantees: Did the guarantor group change?
Reporting: Were information rights expanded?
Liability management: Were new restrictions added?
Refinancing: Is this a long-term solution or a bridge?
Valuation: How did the loan reprice around the amendment?
History: Can prior effective terms be reconstructed?
Provenance: Can each current field be traced to the document and consent that created it?

If the answer to “what are the current terms?” is clear but the answer to “how did they become the current terms?” is not, the asset record is incomplete.

Private credit is becoming a market of changing states

The software maturity cycle illustrates a broader change in private credit.

A loan can be:

Originated
    ->
Syndicated
    ->
Transferred
    ->
Repriced
    ->
Waived
    ->
Amended
    ->
Extended
    ->
Split
    ->
Refinanced
    ->
Repaid

The borrower may remain the same.

The facility identity may remain the same.

The economic asset can still change materially.

AI disruption makes this particularly visible in software.

The lender is no longer asking only:

Will the borrower pay interest today?

It is also asking:

Will this business still support refinancing when the loan matures?

Amend-and-extend transactions buy time.

The price of that time can appear in:

yield;
fees;
covenants;
collateral;
reporting;
amortisation;
and lender control.

Those changes should not disappear into the latest version of a credit agreement.

They are the history of the asset.

For private credit, a maturity extension is not merely a new date.

It is a new state of the same loan.