Origination, refinance and collections
Three verticals composing one shared capability library — what each adds, what it reuses, and where it meets SDUI and external systems.
Three businesses, one library. Each vertical is its own FabricModule with its own namespace, lifecycles and events. None of them copies another, and none of them re-answers who the borrower is or what the state permits.
The test to hold each to: what does this vertical add, and what does it merely depend on? A vertical that redefines a party or an agreement has forked the library in everything but name.
Origination
A new agreement comes into existence: who the customer is, which product they qualify for, whether policy allows it, and how funds move.
Adds: the application object and its lifecycle, decisioning verbs, stipulation handling, counter-offer, and the booking transition that brings an agreement into force.
Depends on: party for applicant and dealer, offering for the product and rate, agreement for the account it creates, settlement for funding, and compliance for adverse action and disclosure timing.
Meets SDUI at: the applicant card, the offer summary and the stipulation checklist, with submit and request_stip as action intents. Layout differs per brand and per surface; the permitted verbs do not.
Meets external systems at: the bureau pull during decisioning, e-signature at contract, and payment rails plus the servicing system at funding.
Refinance
An existing agreement is replaced or amended. Almost everything origination needed already exists — that is the point of the vertical.
Adds: replacement and amendment verbs over an existing agreement, and the payoff-and-rebook transition that has to be atomic — an account must never be both paid off and unbooked.
Depends on: agreement for the account being replaced, party for a customer already known, settlement for payoff and new funding, compliance for re-disclosure.
Meets SDUI at: the current-account panel, proposed terms, and an accept intent. The customer, the account and the compliance pack are already present, so the surface is mostly confirmation rather than collection.
Meets external systems at: a bureau pull and a collateral valuation when quoting, and the payment rails at payoff.
Collections and recovery
Work happens against a delinquent agreement and, eventually, a vehicle. This is the vertical where the platform's execution guarantees stop being infrastructure hygiene and become regulated business behaviour.
Adds: delinquency and cure states, agency assignment, field activity against a resource, condition evidence, and close-out.
Depends on: agreement for the account in default, party for borrower and collector, activity for the work, and compliance for cure windows and breach-of-peace rules.
Meets SDUI at: the assignment board, the order detail and the capture form, on a surface that must keep working with no signal.
Meets external systems at: skip-trace and location data, storage and auction platforms at disposition, and the servicing system throughout.
Why this vertical is the proof. Repossession authority is revocable right up to the moment of recovery. A collector captures a recovery offline; while the device is dark, the borrower pays and the order is cancelled. On reconnect the queued action replays through the same path, authority is re-checked at execution rather than at capture, and the action is refused into reconciliation with the collector's capture-time evidence attached — so the agency can see why, and the audit shows both moments.
That behaviour is not application code anyone wrote for collections. It is what the action's declared execution semantics already require, and it is available to every vertical that declares them.
What the third business costs
Origination builds most of the library. Refinance reuses nearly all of it and adds replacement verbs. Collections reuses the account, the parties and the compliance pack and adds field work.
| Origination | Refinance | Collections | |
|---|---|---|---|
| Party | reuse | reuse | reuse |
| Offering | reuse | — | — |
| Agreement | creates | replaces | acts against |
| Settlement | reuse | reuse | reuse |
| Activity | — | — | adds field work |
| Compliance | reuse | reuse | reuse |
That column of reuse is the return on the foundation. It is also the measurement to hold the design to: if a fourth business unit needs a fourth definition of an agreement, something above the capability library has leaked into it.
See also
Automotive finance
The industry as a composable framework — one shared capability library, the surfaces it drives through SDUI, and the external systems it integrates with.
The standard
What a team has to get right to build a composable application on Fabric Platform, and which of those things the build refuses to let them get wrong.