Functional object map
An overview of business-model families and relationships structuring the main B2B flows. This map explains how concepts combine; it does not prescribe a mandatory process sequence.
Model families
Families organize documentation by business intent. An object keeps the same semantics when used in several journeys: classification indicates its documentation home, not a technical domain boundary.
Identify actors and qualify the journey
Companies and their contacts provide journey context. Checks and credit provide decision inputs.
Connect sales to payments
The sale is attached to a buyer. Journeys, checks, and credit may provide context; payments are then reconciled with the relevant documents.
Track purchasing and suppliers
The supplier is a Company. Its purchase orders, invoices, payables, and supplier payments belong to the Purchasing and suppliers family.
Structural relationships
| Source | Cible | Signification |
|---|---|---|
company | checkout_session / onboarding_case | The Company provides business identity to the journey; the journey case then keeps its own lifecycle. |
company | order / invoice / payment_term | The buyer is linked to sales documents and commercial terms applicable to it. |
order | invoice / return / dispute | The order may be invoiced, returned, and included in the scope of a dispute. |
return | return_item | A Return concerns exactly one Order and embeds the returned lines and quantities. |
approval_request | approval_assignment | The request aggregates assignments; an approved/rejected assignment constitutes the human decision. |
invoice | receivable | The receivable is a projection calculated from open documents, credit notes, and payment allocations. |
psp_payment / payment | payment_allocation | The allocation explains how a financial source is assigned to business targets. |
credit_limit | effective_credit_limit | The effective projection resolves applicable limits by date, strategy, currency, and calculation basis. |
effective_credit_limit / credit_exposure | credit_availability_check | The capacity check compares applicable limit and exposure with the requested amount. |
supplier_invoice | payable | The payable is the AP projection symmetrical to the sales-side receivable. |
company | purchase_order / supplier_invoice / supplier_payment | The supplier remains a qualified Company; AP objects each preserve their identity and lifecycle. |
Resources, projections, and embedded objects
Links on the map do not imply that all concepts have the same nature. A resource has durable identity; a projection is calculated on demand; an embedded object exists only in its parent context.
Resources
Exemples : company, invoice, return, approval_request, supplier_payment.
Projections
receivable, payable, effective_credit_limit et credit_availability_check have no autonomous identity.
Embedded objects
line_item, return_item et approval_assignment are documented in their parent context.