Sourcing
Requisition, RFQ, Comparative Analysis, Purchase Order plus invitation tracking, line-level awards, and structured-or-free-form scoring criteria. The workflow engine of the suite.
- Frozen post-receipt
- Line-level awards
- Policy-gated
Loading
Ten canonical steps, five domains, one document trail — drawing against the budget above it. Every business rule is policy-gated per organization, so the same software serves a donor-funded NGO and a small business invoicing from a vendor's bill.
Each step is owned by a single domain. Document state propagates downstream, and constraints upstream. None of it is hardcoded; it's per-org policy reading the chain.
A line-level request for goods or services, each line bound to a budget allocation and routed up its signing ladder. Optional under relaxed policy; the line FK still tracks origin when present.
Request For Quotation. Skip if single-source. Each invitation is tracked individually; vendors may submit per-line quotes through the vendor portal.
One-shot anonymous magic link per invited vendor. Optional account ladder for self-service. Vendors never receive platform RBAC permissions.
Per-line quote submissions. Vendors may decline lines, offer partial quantity, propose alternates. Quote draft state until vendor explicitly submits.
Structured (criteria + scores) or free-form, gated by policy. Awards may split across vendors per-line. Approval atomically closes the RFQ and seeds one draft PO per awarded vendor.
Single-purchase or master agreement. Activation requires a signed-document attachment. Master-agreement utilization is computed at read time, never stored.
Header-typed as goods or service. Mixed POs not supported. Frozen once any receipt references it, with revisions only on a clean receipt slate.
GRN for goods POs (multi-line); Service Confirmation for service-line POs (one per line). Append-only reversals; over-receipt policy-gated. Confirmation emits budget consumption events.
Policy-gated matching: three-way against PO + receipt, two-way against PO, or no-match for fully manual invoices. Explicit human approval. Match overrides audited.
Many-to-many with invoices: one payment may settle multiple invoices, one invoice may receive multiple payments. Strict segregation of duties between approval and settlement.
Domains do not reach into one another's tables. Cross-domain contracts are explicit, audited, and policy-gated. Adding a domain to the suite extends the chain; it never reshapes it.
Requisition, RFQ, Comparative Analysis, Purchase Order plus invitation tracking, line-level awards, and structured-or-free-form scoring criteria. The workflow engine of the suite.
Vendor master, vendor portal, vendor responses. Vendor portal users are a third identity plane, separate from User and OrgMember, with hardcoded action sets scoped to their own vendor.
Single-purchase or master agreement, header-typed. Renewals are new contract rows linked to predecessors. Auto-expiry by date with a real-time read floor.
GRN for goods, Service Confirmation for services. Partial deliveries first-class. Confirmation atomically transitions budget committed → consumed and freezes the parent PO.
Vendor invoices, payments, match overrides. Closes the loop. Strict segregation of duties enforced through permission keys, not advisory.
Every REQUIRES X rule reads policy.X_required. Tighten or loosen for a given organization without forking the engine.
NGO · donor-funded
Commercial · mid-market
Small business
Whichever your organization picks at signup, every relaxed action writes the policy state at action time into the audit event. An auditor years later sees exactly why a rule was bypassed.
Pick a profile, pick your country, ship a budget in the same screen.
Request access