Client Modelling Examples

When integrating with Receive, the first design decision is how to map your business onto the platform's Account / Product / Claim model. These worked examples show that mapping for seven common business profiles. Each one describes a fictional company with a deliberately rich policy set, walks through a debtor scenario with real API payloads, and ends with the discovery questions whose answers tell you which parts of the example apply to you.

The guiding principle across all of them: model what is legally enforceable at placement time — a claim's amount is the collectible debt, not the contract value.

Example	Business profile	What it demonstrates
BNPL	Buy-now-pay-later	Claim per missed instalment, consolidation at acceleration with typed claim relations, instalment plans as a collections treatment
Personal Loan	Amortized consumer credit	Enforceable balance at acceleration, principal/fees decomposition, post-placement interest accrual, co-signers
Recurring Invoices	Telco / utility / subscriptions	Ledger-managed integration, invoice-derived claims, account-level payment matching, disputes and chargebacks
Debt Buyer	Purchased portfolios	Bulk import, portfolio and original-creditor references, pre-sale history, score-driven segmentation, settlements
Revolving Credit	Credit cards	One rolling claim per card maintained with debits/credits, fee buckets, fraud write-offs
B2B Invoices	Commercial receivables	Company debtors, disputes and credit notes, invoice splitting, promises to pay
Secured Auto Loan	Vehicle finance	Curative treatments (deferral via due-date shifts, restructuring via instalment plans), deficiency balance after repossession

A real client is almost always a subset of one of these examples — start with the closest profile and use its discovery questions to switch parts on or off.

The examples describe what to model; for the mechanics of each API call (authentication, creating and updating claims, registering payments, reversals, consolidation), see the generic Use Cases.