First-payment default is an origination defect, not a collections event
In short
First-payment default is a missed first contractual instalment on a newly funded loan, and it is a defect report on origination rather than the start of a collections case. A borrower who never makes payment one rarely deteriorated in 30 days: the mandate was never lodged, the due date fell before payday, the payment was never matched, or the income was overstated.
Key takeaways
- Fix the definition first: which instalment, what grace, and how a rescheduled first date is treated.
- A first-payment default measured on funded cohorts cannot be read until the cohort has aged 60 days.
- A payment that arrived unattributed shows in the data as a default and is a reconciliation fault.
- On 200 funded loans, 4 cases against 6 is noise; do not move policy on a single month.
First-payment default is the failure of a newly funded loan to pay its first contractual instalment. Treat it as a defect report on origination, not the opening of a collections case. Borrowers whose circumstances collapse inside 30 days of drawdown exist but are rare; the common causes sit behind the decision — an instrument never lodged, a due date set before the borrower is paid, a payment that arrived and was never matched, income that was never there in the size underwriting believed.
Four choices that decide what the number means
- Which instalment counts. The first contractual instalment, or any first collection attempt — including a part-period charge billed days after drawdown.
- How much grace. Unpaid at the due date, unpaid 5 days later, or unpaid at 30 days past due. Each produces a different rate on identical behaviour.
- What a partial payment does. An instalment paid short by 40 is either a default or a shortfall, and the choice changes the number more than most underwriting changes do.
- How rescheduled dates are treated. A borrower who calls before the first due date and moves it has not defaulted; a lender who books that as a cure has quietly removed the signal it most needed.
| Definition | What it counts | What it does to the reported rate |
|---|---|---|
| Unpaid at the due date | Every failed presentation, including retries that clear 2 days later | Highest, and dominated by collection mechanics not credit |
| Unpaid at 30 days past due | Genuine non-payment after the retry cycle has finished | Lower, comparable across products, and 30 days later to arrive |
| Unpaid, excluding pre-due-date reschedules | Non-payment where the borrower never engaged at all | Lowest, and the version most easily flattered by a servicing team |
Whichever you pick, fix the cohort as loans funded in a month and accept the observation lag. Loans funded in March cannot be assessed until roughly the end of May, so a review treating last month's figure as final is reporting a number that will be revised.
Most cases are setup failures wearing a credit label
- The mandate was never live. Direct debit and standing instruction setups take working days to lodge and are rejected outright on a name or account mismatch. Fund on Friday, bill on Monday, and there is no instrument to collect with.
- The first due date lands before payday. A borrower paid on the last working day of the month, billed on the 25th, misses instalment 1 and pays every one after it.
- The money arrived and was not matched. A transfer with no usable reference sits in unapplied cash while the loan reads as unpaid — the attribution problem solved by virtual accounts and per-payer references.
- The account is not the account. Disbursement went to one account and collection is set against another, or the mandate names a joint account the borrower does not control.
- The income was never there. Where affordability rested on inflows that were transfers, reversed credits or another lender's disbursal, instalment 1 is where arithmetic meets a bank balance — the failure in statement analysis that overstates borrower income.
- A condition was waived to get the file out. Check month-end approvals specifically, and check files that sat for weeks in conditions outstanding twice, because their evidence was stale before funding.
Send each case back to the decision that produced it
- Open every case within 5 business days of the missed instalment, while the borrower is contactable and the file is fresh.
- Classify to a cause from a fixed list: instrument, date, attribution, account, income, waiver, genuine deterioration. Free-text notes produce a year of unanalysable cases.
- Attribute the cause to a stage — verification, decisioning, documentation, boarding or payments — rather than to a person.
- Attach the decision snapshot: inputs, their as-of dates, rule and model versions, and the reasons recorded at the time — which exists only if it was captured then, as decline reason codes recorded at the moment of decision argues.
- Report weekly to the owner of the originating step, and require the fix to be a rule, a checklist item or a field validation — then measure the next 2 cohorts against it.
A first-payment default is the loan telling you something about the day it was written, not about the borrower's month.
What the number cannot carry
It is a small-denominator statistic. A lender funding 200 loans a month sees 4 cases one month and 6 the next, and neither supports a policy change. Read it as a trend across cohorts and watch the cause mix rather than the headline: 3 attribution failures in a month that normally has none matters more than a rate moving 1 point.
Nor does it predict eventual loss — many of these cure and pay to term — or say anything about arrears treatment, which is a separate ladder with its own owners. It earns its place by closing the loop between the book and the decisions that made it, the kind of small, high-yield internal tools and ops work that sits inside lending and credit operations, part of the finance systems we build.
Frequently asked questions
Short answers to the follow-ups this page tends to raise.
What counts as a first payment default?
A newly funded loan failing to pay its first contractual instalment. The definition has to be fixed in advance: which instalment counts, how many days of grace apply, whether a partial payment qualifies, and how a due date rescheduled before it fell is treated. One cohort reports materially different rates under 3 reasonable definitions, so this belongs in configuration rather than in a report.
Why is first payment default an underwriting problem rather than a collections one?
Because a borrower rarely deteriorates within 30 days of receiving money. The usual causes precede the loan going live: a mandate never lodged in time, a due date set before the borrower is paid, a payment that arrived without a usable reference, or income overstated because inflows were counted that were not earnings.
How quickly can a lender measure first payment default for a cohort?
Not until the cohort has aged past the definition's grace period — for a 30-day threshold, roughly 60 days after the month of funding. March's number is not readable until late May. Publish each cohort with its maturity stated and expect recent months to move, rather than treating the latest figure as final.
- lending
- credit risk
- origination
- servicing
The work behind this page
Builds from our portfolio that this page draws on.
LoanForge
An AI mortgage loan-origination platform that extracts borrower data from documents, auto-clears underwriting conditions, and drives every loan to clear-to-close.
Real EstatePipelineIQ
An AI SDR platform that scores every lead for fit, runs multichannel sequences across email, LinkedIn and call, drafts the replies, and books the meeting.
Sales AIChurn Radar
An AI customer-success platform that flags at-risk B2B accounts before they churn and prescribes the save-play to run.
Customer SuccessRead next
- The loan tape: whether your book is legible to anyone elseA loan tape is one row per loan, assembled to a counterparty's template. It is cheap to produce only if your servicing model stores state transitions rather than current status.definition
- Decline reason codes: what to record at the moment of the decisionA reason recomputed from today's data is not the reason the applicant received. Bureau values, balances and documents move, so the reason belongs in the same transaction as the decision.definition
- Underwriting conditions: the record shape that lets a rule clear oneA condition is a record, not a note. Evidence type, acceptable source, a checkable satisfaction rule, an owner and a stage gate separate a condition software can close from one only a person can.definition
- A promise to pay is a record with an expiry, not a note in a CRMAmount, date, invoices covered, channel, evidence, state. Six fields turn a collections commitment from a memory aid into something a system can act on.definition
- Invoices sit in approval for days: find the hop where it diedStop chasing approvers and start aging the hop. Time-in-hop, the resolved principal and the notification result identify the stall in minutes, and four of the five causes are configuration rather than behaviour.diagnostic
- Matching fails because the goods receipt has not been posted yetAn exception that resolves itself if left alone for two days is not a receipting failure. Measure the site's receipting lag, then let the system wait instead of a person.diagnostic
Working on something in this space?
Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.
Start the conversation