Application family
5 recognisable systems, connected by the work between them.
Operational and financial work shares commitments, constraints and exceptions. These examples keep the consequence visible before allocation, scheduling, payment or contact changes.
Choose the operating system closest to the work.
Every example is an illustrative application pattern, not a customer outcome or a limit on what can be defined.
Order management
O2C: capture to fulfillment to invoice trigger with no re-keying.
- Relevant state
- Promise risk surfaced
- Prepared work
- Recovery option prepared
- Decision owner
- Order owner decides
Procure-to-pay
PR → PO → GRN → 3-way match; payment on a clean match.
- Relevant state
- Match exception surfaced
- Prepared work
- Resolution prepared
- Decision owner
- Finance owner decides
Inventory & warehouse
One stock picture across locations, with batch, serial and expiry control.
- Relevant state
- Shortage surfaced
- Prepared work
- Replenishment prepared
- Decision owner
- Inventory owner decides
Production & planning
BOMs, work orders and material runs that flag shortages early.
- Relevant state
- Shortage flagged
- Prepared work
- Schedule option prepared
- Decision owner
- Planner decides
Collections & dunning
Bucket strategies, PTP tracking, settlement gates with authority.
- Relevant state
- Promise risk surfaced
- Prepared work
- Contact strategy prepared
- Decision owner
- Collections owner decides
Bring the process that does not fit a standard system.
Start with the records, roles, decisions and exceptions that make the work specific to your enterprise.
The named pages are examples. The application specification starts from your process and keeps human authority explicit.