Top summary
Direct answer: For merchant-side BNPL sales, record revenue when the customer-performance obligation is satisfied under your policy, route the provider-funded amount through a BNPL clearing receivable, record merchant fees separately, and reconcile captures, refunds, disputes, settlements, and bank deposits.
- The shopper’s installment receivable usually belongs to the BNPL provider, not the merchant.
- Capture, settlement, and bank dates are separate control points.
- Refund fee treatment and negative-balance mechanics vary by provider and contract.
Who is this for, and what decision should it complete?
This method is for an ecommerce founder or finance operator offering Affirm, Afterpay/Clearpay, Klarna, or another provider that pays the merchant while collecting installments from the shopper. The decision is how to recognize the sale, classify the provider fee, prove the receivable or clearing balance, and handle refunds or disputes without posting the net bank deposit as revenue.
Current search results commonly give a three-line journal entry but omit authorization versus capture, unsettled transactions, asynchronous refunds, fee reversals, negative provider balances, bank lag, multiple currencies, and contract differences. Provider documentation explains settlement mechanics but generally does not design the merchant’s complete month-end control.
Does the merchant record the customer installment receivable?
Use this contract-boundary tree, the first original-value component. First, identify the legal seller and the entity promising the goods. Second, confirm who extends credit to and collects from the customer. Third, determine when the merchant becomes entitled to provider settlement—authorization, capture, shipment, or another event. Fourth, identify recourse, dispute, refund, reserve, and fee terms. Fifth, apply the entity’s revenue policy based on transfer of promised goods or services.
In the common third-party model described by Stripe for Afterpay/Clearpay, the full order amount less fees becomes available to the merchant’s Stripe account upfront while the customer repays Afterpay. That supports a merchant-side clearing or receivable from the provider rather than installments receivable from the shopper, but the signed contract and actual integration govern. If the merchant itself finances the customer, retains credit risk, or sells the receivable, this simplified model does not apply.
Revenue timing does not become the settlement date merely because BNPL funds arrive quickly. IFRS 15 ties revenue to transfer of promised goods or services. Authorization, capture, fulfilment, and settlement must remain distinct fields.
What accounts and events should the BNPL ledger contain?
| Event | Operational evidence | Accounting destination to assess | Main risk |
|---|---|---|---|
| Authorization | Provider/payment intent | Usually no completed sale by itself | Booking abandoned checkout |
| Capture | Capture ID and order | BNPL clearing/receivable when entitled | Duplicate platform sync |
| Customer fulfilment | Shipment/delivery/service evidence | Revenue and COGS under policy | Using cash date for revenue |
| Merchant fee | Provider transaction detail | Fee expense or policy-based classification | Netting away gross sale |
| Settlement | Settlement ID and lines | Reduce BNPL clearing | Calling net deposit sales |
| Refund/dispute | Original transaction and status | Reverse relevant amounts under policy | Assuming every fee reverses |
| Negative balance | Provider roll-forward | Payable or offset balance assessment | Hiding future payout reduction |
Maintain separate clearing accounts by provider, legal entity, and currency. Do not combine card, wallet, and BNPL settlements simply because they pass through the same processor.
How does the BNPL settlement waterfall work?
The second original-value component is a settlement waterfall. Begin with opening provider receivable or negative balance. Add captured amounts to which the merchant is entitled. Subtract merchant fees. Subtract refunds and disputes, add any provider-approved reversals or credits, and subtract settlements sent. The result should equal the closing provider balance, subject to clearly identified in-transit bank items.
Then run three matches: order to provider transaction, provider transaction to settlement line, and settlement to bank deposit. Use stable IDs, not dates alone. For refunds, retain requested, pending, completed, and failed statuses because some methods are asynchronous. For every fee, retain type, contract basis, refundable status, and original transaction.
Affirm’s public merchant documentation says its settlements can contain sales, refunds, disputes, and fee adjustments, with detailed reports showing transaction activity, merchant fees, and the net deposited amount. It also notes that negative balances can be offset against future loans. Those are current provider mechanics, not universal BNPL rules.
Worked hypothetical example: captures, fees, refund, and bank lag
Hypothetical example—not a customer result. Assume a furniture-accessories merchant captures 80 BNPL orders totaling $12,000 in September and fulfils all of them before cutoff. Its signed provider schedule charges 4.5% plus $0.30 per captured transaction. One fulfilled $300 order is fully refunded; under the assumed contract, its $13.80 fee is not returned. A $250 capture on the final day is not included in the September settlement. The provider sends one settlement that reaches the bank two days after month-end.
| Measure | Calculation | Amount |
|---|---|---|
| Gross fulfilled sales | 80 captures | $12,000 |
| Merchant fees | $12,000 × 4.5% + 80 × $0.30 | $564 |
| Completed refund | Original order | $300 |
| Net provider movement before timing | $12,000 - $564 - $300 | $11,136 |
| Unsettled captured amount, net assumed fee | $250 - ($11.25 + $0.30) | $238.45 |
| Settlement sent | $11,136 - $238.45 | $10,897.55 |
At cutoff, the bank can still be zero for this settlement while cash in transit is $10,897.55 and the provider clearing balance contains $238.45, assuming the provider reports these values consistently. The merchant separately records the revenue reversal for the $300 refund and retains the nonrefunded $13.80 fee as expense under the assumptions.
Interpretation: the bank deposit is neither gross revenue nor proof that all transactions cleared. Limits: this example assumes all performance obligations were satisfied, no sales tax complication, no reserves, no dispute, one currency, and the stated fee contract. It is not a claim about any provider’s standard fee or refund terms.
Which exceptions should be triaged first?
- Bank deposit with no settlement ID, or settlement with no bank deposit after the normal window.
- Captured order absent from settlements beyond its expected eligibility date.
- Settlement line with no valid order or duplicate capture ID.
- Refund completed in the store but pending, failed, or missing at the provider.
- Fee rate or fixed charge that differs from the signed schedule.
- Negative balance carried forward without a transaction roll-forward.
- Dispute loss, charge, or reversal without case evidence.
- Cross-entity or cross-currency settlement posted to the wrong ledger.
Classify differences as timing, mapping, contract-rate, customer-service, dispute, or unexplained. Timing is not a permanent resolution: add an expected clearing date and verify it in the next report. Escalate material or aged items to the provider and retain case IDs.
What monthly close checklist should finance follow?
- Freeze store orders, captures, fulfilments, provider transactions, settlements, refunds, disputes, and bank lines.
- Confirm the legal entity, provider, currency, and contract version.
- Exclude authorizations that were never captured.
- Apply revenue and COGS timing independently from payout timing.
- Recalculate provider fees from the signed schedule where feasible.
- Build the opening-to-closing clearing roll-forward.
- Match orders to provider transactions, settlements, and bank deposits.
- Age unsettled captures, pending refunds, disputes, and negative balances.
- Tie provider clearing, fee expense, refunds, cash, and revenue to the ledger.
Definition of done: every material capture ends as settled, legitimately pending, refunded, disputed, or documented exception; all deposits match settlement IDs; fee variances have an owner; and the provider roll-forward equals the general ledger.
Common failures include booking the net deposit as revenue, recording the shopper’s installments as merchant receivables, recognizing authorized but uncaptured orders, assuming all refund fees reverse, clearing a settlement by date rather than ID, and leaving a negative balance hidden until future deposits fall.
When does this guidance not apply?
Obtain specialist review when the merchant provides the financing, retains significant credit or recourse risk, sells receivables, uses a marketplace as merchant of record, offers subscriptions, operates across currencies or jurisdictions, faces material reserves, or needs a principal-versus-agent analysis. Consumer-credit regulation applies mainly to providers and programs but can still affect merchant contracts and operations; verify local obligations.
Provider terms can change and account-specific pricing is not public. Last checked 22 August 2026, Stripe documents asynchronous Afterpay refunds and provider-specific dispute processes, while Affirm documents settlement reports, fee adjustments, and negative-balance offsets. Confirm the current dashboard and signed agreement before posting.
Caigeek can combine order, fulfilment, provider, settlement, refund, dispute, bank, and ledger data to create a BNPL clearing roll-forward, fee-rate test, pending-refund schedule, and exception queue. Management and qualified advisers approve contract, revenue, tax, and regulatory conclusions.
Self-check before sign-off
- The title, H1, direct answer, and Article schema ask and answer the same question.
- Source records identify the legal entity, transaction, and cutoff period.
- Gross activity is not replaced by a net bank deposit.
- Quantity, value, and timing controls reconcile separately.
- The hypothetical example is labeled and its limits are explicit.
- Every material exception has an owner, evidence status, and next action.
- Accounting, tax, legal, and provider-specific boundaries are visible.
Sources and last updated
Last checked: 22 August 2026. Provider, platform, tax, and accounting rules can change; verify the current primary source and signed agreement before applying them.
- IFRS Foundation, IFRS 15 Revenue from Contracts with Customers
- Affirm, Understanding Merchant Portal Settlements
- Affirm, Merchant FAQs on fees, payment, and refunds
- Affirm, Why have I not received a settlement?
- Stripe Documentation, Afterpay and Clearpay payments
- Entertainment Accountants, how to account for BNPL sales
FAQ
Is a BNPL bank deposit the same as sales revenue?
No. The deposit is a net settlement that can include captured sales, fees, refunds, disputes, prior balances, and timing differences.
Does the merchant record the customer installment receivable?
In a common third-party BNPL model, the provider collects from the customer and the merchant tracks a provider clearing balance, but the signed contract determines the answer.
Are BNPL merchant fees refunded when an order is refunded?
Not always. Fee reversibility varies by provider, program, contract, and event, so use transaction detail and the signed fee schedule.
Why can a BNPL settlement be missing after a refund?
A refund or other adjustment can create a negative provider balance that is offset against later eligible transactions before a new settlement is generated.