Originator guide
BNPL Receivables
Draft for editorial review. Technical and final editorial approval are pending. Examples with invented numbers are labelled fictional.
Buy now pay later (BNPL) receivables put unusual pressure on operations because the money moves in several directions within days of a purchase. Merchant settlement, consumer instalments and refunds all land on different timetables, and the reconciliation between them is where reporting quality is won or lost.
Two products under one label
The BNPL label covers at least two structurally different products, and conflating them will confuse every conversation you have with a capital provider.
Short pay-in-instalments products split a purchase across a handful of payments over a few weeks, typically with no interest charged to the consumer. Revenue on these products usually comes from the merchant discount and from any late or missed payment charges you apply, though the mix varies by product and by market. Tenor is measured in weeks, balances turn over rapidly, and the receivable is small.
Longer instalment products run for months or longer, involve larger ticket sizes and look more like conventional unsecured consumer lending. Many charge interest to the consumer; some are offered on promotional no-interest terms with the merchant bearing the subsidy. Underwriting depth, disclosure expectations and loss emergence patterns all differ from the short-tenor product, and so does where your revenue comes from.
If you originate both, split them at the tape level. Blended reporting across products with different tenors and different revenue models produces ratios that describe neither.
Repayment capacity assessment, fraud exposure and operational controls are where scrutiny lands in short-term instalment products. How your products are classified depends on their terms, your licences and your jurisdictions, so ask counsel what applies to you.
Where the cash actually goes
The cash mechanics are the part most originators explain poorly. Work through a single fictional order in US dollars.
Exhibit 1
Cash movement on one fictional order
| Line | Amount | Note |
|---|---|---|
| Purchase value at checkout | 400 | Basket value agreed with the consumer |
| Merchant discount retained | 20 | Gross merchant revenue before all costs |
| Settlement paid to merchant | 380 | Cash out from your platform |
| Consumer payment at checkout | 100 | Received before settlement in this example |
| Receivable outstanding | 300 | Owed across the remaining instalments |
| Net cash funded on this order | 280 | 380 paid out less 100 received |
You pay the merchant 380 and collect 100 at checkout, so 280 of your own or borrowed cash funds this single order until the remaining instalments arrive. Multiply that across order volume and the working capital requirement becomes the defining constraint on growth, well before credit losses do.
The 20 is revenue, not yield
The merchant discount of 20 on a 400 purchase is gross revenue before funding cost, operating cost, fraud loss and credit loss. It is not an annualised yield. Scaling a few weeks of revenue up to an annual figure produces a headline that says nothing about what reaches equity, so present it with the full cost bridge underneath rather than on its own.
Refunds and the reconciliation that breaks first
Returns are ordinary retail behaviour and they collide directly with the receivable. A consumer who returns a purchase expects the payment plan to stop, and possibly expects money back.
The outcome depends on what the consumer has already paid and on the size of the refund relative to the remaining balance. Broadly, a refund reduces or cancels what the consumer still owes; where the refund exceeds the amount still outstanding, the difference is money owed back to the consumer. Separately, you are typically looking to the merchant to reimburse the settlement you already advanced. Those two legs move on different timetables and under different contracts, which is why process matters more here than any single worked figure. How the entries are recognised in your accounts is a question for your accountants against your own contract terms.
Design the process explicitly:
- Define who is notified when a merchant processes a return, through what channel, and within what window.
- Define how a partial return maps to a payment schedule, since a partial refund does not cleanly cancel a specific instalment.
- Define how merchant recoveries are pursued when the refund exceeds amounts still owed by the consumer.
- Define the daily reconciliation between merchant settlement records, consumer payment records and your receivable ledger, with a named owner and an escalation path for unmatched items.
Refunds and adjustments are dilution whether or not they are reconciled: they reduce the collectable receivable without any consumer defaulting, so they should be identified separately from credit losses. Check how your systems record them rather than assuming the separation is automatic. Poor reconciliation makes the problem invisible rather than causing it. Providers track it separately and often apply a specific reserve against the borrowing base when it runs persistently high. Report it as its own line rather than folding it into loss reporting.
Short tenor is not low risk
A six-week receivable is often presented as inherently safe because it repays quickly. Speed reduces the duration of any single exposure. It does not reduce the risk in the underwriting decision, and it introduces problems of its own.
At short tenor there is very little time to detect a deteriorating consumer before the balance is due. Underwriting decisions are made in seconds at checkout, frequently with thin data. Fraud is attractive precisely because the approval is fast and the goods are delivered immediately.
Rapid turnover also compresses your reporting cycle. Where the scheduled term is six weeks, a monthly reporting interval gives you very few observation points across the life of a cohort, and charge-off timing depends entirely on your own policy, which varies between providers. Report by origination cohort at weekly or biweekly age intervals rather than relying on portfolio snapshots, state your charge-off policy alongside the data, and use static pool discipline even though the pools are short-lived. Short cohorts are an advantage here: they give you a readable performance signal quickly if you are sampling often enough to see it.
Merchant concentration and settlement
Your merchant relationships are simultaneously a distribution channel, a counterparty exposure and a source of collateral risk.
Concentration in a single merchant or category means one commercial relationship drives a large share of your origination. If that merchant leaves, volume disappears. If that merchant has elevated return rates or fails to deliver goods, your receivables carry disputes that no consumer credit model predicted.
Merchant failure is the sharper exposure. If a merchant ceases trading holding undelivered orders, consumers stop paying for goods they never received, and your recourse against the merchant may be worth little. Track merchant-level return rates, dispute rates and delivery performance, and set internal concentration limits before a provider sets them for you through eligibility criteria.
Data gaps and payment stacking
Credit reporting practice for BNPL varies by provider, by bureau and by jurisdiction, and it has been changing. Some products are furnished to bureaus, some are not, and coverage differs between the short pay-in-instalments product and longer interest-bearing plans. The practical consequence is that a consumer may hold plans across several providers without each of them seeing the others, so your affordability assessment can be accurate on the information you hold and still understate total obligations.
Verify what your own data actually captures rather than assuming either full visibility or none. State which sources you query, which of your products you furnish and to whom, what you can and cannot observe about obligations held elsewhere, and what you do internally to detect a consumer opening multiple plans on your own platform in a short window. A clear description of the limitation stands up in diligence; a claim of visibility that a file sample contradicts does not.
Choosing a financing route
Working capital can be a binding constraint in BNPL, and the structural options follow from how well your receivable ledger reconciles. Availability depends on scale, product mix and counterparties, and none of these routes is open to everyone.
Exhibit 2
Financing routes for a BNPL book
| Route | What it funds | What the evidence has to support |
|---|---|---|
| Warehouse facility | Revolving advances against eligible receivables you retain | Daily reconciled receivable balances, dilution measured and reported separately, merchant concentration data, borrowing-base reporting at high frequency |
| Receivables sale or forward flow | Ongoing sale of receivables as generated | Consistent origination criteria, transferability of the consumer agreement, refund and merchant recovery obligations allocated clearly between the parties |
| Term ABS | Refinance of a pool through issued notes | Sufficient cohort history despite short tenor, stable charge-off policy, revolving structure work and disclosure scoped with counsel |
Short tenor cuts both ways structurally. It means a static pool amortises almost immediately, so term structures generally need a revolving feature to be worth doing, and it means your borrowing base moves daily rather than monthly. Eligibility usually turns on reconciliation quality and dilution: receivables that cannot be matched to a settled merchant order, or books where refunds are absorbed into charge-off statistics, attract exclusions or specific reserves. Where a rating is contemplated, methodology treatment of dilution, merchant counterparty exposure, revolving mechanics and charge-off policy is asset and deal specific and has to be reviewed with the agency against your data.
The warehouse, forward flow and term ABS material sets out how each works.
Build this before you finance the book
Exhibit 3
BNPL operational readiness checklist
| Control | What to evidence | Where it usually fails |
|---|---|---|
| Product separation | Short pay-in-instalments and interest-bearing books on separate tapes | Blended ratios across incompatible tenors |
| Daily reconciliation | Merchant settlement, consumer receipts and receivable ledger matched daily | Weekly or monthly matching that lets breaks accumulate |
| Refund process | Documented mapping of returns to schedules and to merchant recovery | Case-by-case handling with no written rule |
| Dilution reporting | Refunds and adjustments reported separately from credit loss | Refunds absorbed into charge-off statistics |
| Cohort reporting | Loss development by origination week at short age intervals, with charge-off policy stated | Monthly snapshots giving too few observations across a six-week term |
| Merchant monitoring | Return, dispute and delivery performance by merchant | Merchant identifier absent from the receivable record |
| Fraud controls | Checkout-level controls with measured first-payment default by channel | Controls described but outcomes never measured |
| Working capital model | Net cash funded per order scaled to projected volume | Growth plan built on revenue, not on funding requirement |
Reconciliation and the working capital model come first. One decides whether your reported collateral balance can be trusted, the other decides whether the growth plan is fundable at all. The servicing requirements guide covers the daily payment application discipline underneath both.