Workflow: Procure-to-Pay

Definition

Procure-to-pay is the inbound commercial and financial chain that answers: why did we buy, what did we commit to the supplier, what actually arrived, what did the supplier bill, and what did we pay. In Orbita, each hop has a named authority surface; hops must remain linkable rather than reconstructed from spreadsheets at month-end.

Demand signal → Purchase order → Receive (operational) → Supplier invoice review → AP posting → Payment

P2P is not “create PO and forget.” A healthy chain preserves references from demand through receipt so finance can explain AP exposure against real intake, partial receipts, short-closes, and quantity variances. When receipt truth and supplier billing diverge, the workflow must surface mismatch explicitly — not hide it behind a single posted total.

Orbita treats P2P as a cross-role workflow: Office and procurement modules own commitment and supplier master context; warehouse modules own physical receive evidence when WMS is enabled; finance modules own posting, period discipline, and payment closure. Atlas may observe and explain chain state but does not execute purchases, receipts, or ledger posts.

Purpose

Teams adopt structured P2P to reduce three recurring failures: paying against PO text without receipt alignment, recognizing supplier liability before intake is defensible, and losing audit lineage when partial deliveries and credit notes accumulate.

• Connect replenishment and order-driven demand to explicit PO lines.
• Preserve receive quantity and timing as the operational anchor for supplier billing.
• Separate goods received not invoiced style accrual logic from final AP recognition where configured.
• Make payment decisions traceable to reviewed supplier documents and posted liabilities.

P2P discipline also improves supplier relationship quality. When disputes arise, both sides benefit from a shared chain: PO line, receive history, supplier invoice lines, and payment status — rather than email threads and offline reconciliations.

For stock-to-books alignment, P2P is the inbound mirror of order-to-cash: physical inflow and AP consequence must remain explainable from the same operational references, especially when valuation, partial receive, or period close timing matters.

Workflow

1) Demand and procurement intent (Office authority)

Shortage signals, replenishment plans, or order-release bridges create purchasing intent. The intent should map to supplier scope, SKU identity, and quantity — not free-text requests that bypass product master discipline.

2) Purchase order creation and lifecycle

PO records express supplier commitment, expected lines, and status transitions (draft, sent, in-receive, closed variants). Profile completeness may be expressed on PO fields without blocking PO generation; export and invoice-adjacent outputs guard incomplete profile states at the output layer.

3) Receive bridge (WMS when enabled)

Receive desk monitors PO-driven intake; floor scan execution confirms physical lines. Receive history, inbound header lifecycle, and movement ledger entries provide evidence separate from commercial inventory views. Short-close and partial receive paths must remain visible rather than collapsed into “fully received.”

4) Supplier invoice review (Finance procurement bridge)

Supplier bills are reviewed against received context and PO linkage. Operators reconcile quantity, price, and tax shape before posting decisions. This step is a governance gate — not a cosmetic upload.

5) AP posting and liability recognition

Posted supplier invoices create AP exposure with ledger consequence governed by finance authority rules. Posting must respect open accrual and clearance semantics where configured, so legacy expense shortcuts do not bypass receive-backed liability shape.

6) Payment and closure

Payment records reduce open AP while preserving audit lineage to PO, receive evidence, and posted invoice. Period close and reconciliation workflows depend on this chain remaining intact across partial episodes.

Role boundaries stay strict: warehouse execution does not set supplier prices or post journals; finance does not replace receive scanning; procurement does not silently mutate posted ledger truth. Cross-links (for example variance views) are read paths, not parallel authorities.

Example

A trading company sees repeated SKU shortage on released customer orders. Replenishment creates a PO to a preferred supplier. WMS receive confirms two partial deliveries across a week; the third line is short-closed with documented reason. Supplier sends an invoice matching the first two deliveries plus freight. Finance reviews the bill against receive lines, posts AP for accepted amounts, and holds the disputed freight line pending clarification. Treasury pays the approved portion on terms; open AP for the dispute remains visible with references intact.

If the supplier invoice had been posted at PO quantity without receive alignment, month-end would show phantom liability or forced manual journals. The Orbita P2P pattern prevents that by forcing receive and review checkpoints before recognition.

If WMS is not enabled, P2P still exists at PO and finance layers, but physical evidence is weaker. Teams should treat that as a known risk boundary and avoid claiming floor-level certainty in disputes without scan-backed history.

FAQ

Is P2P only for manufacturers?

No. Any business with supplier purchase, receipt, and payable cycles benefits — distributors and importers included.

Can we pay suppliers without WMS?

Yes, but receive evidence quality is stronger when scan-led intake is enabled.

Who owns supplier invoice approval?

Finance review paths own posting readiness; operational modules supply receive and PO references.

What if supplier bill exceeds received quantity?

The workflow should block silent acceptance and require explicit review or adjustment handling.

Does Atlas post supplier invoices?

No. Atlas explains workflow state; finance authority modules execute posting.

How does P2P relate to order-to-cash?

O2C is customer outbound; P2P is supplier inbound. Both must align to inventory and books explainability.

Misconceptions

“PO sent equals goods received.” False. Commitment and physical intake are different authorities.

“AP posting can fix missing receive records.” False. Finance consequence does not recreate warehouse truth.

“Procurement and finance can share one vague ‘invoice done’ status.” False. Review, post, and pay are distinct transitions.

When It Matters

P2P discipline matters when supplier count, SKU breadth, partial delivery frequency, or audit scrutiny increases. It is essential during migration from spreadsheet AP and when implementing stock-to-books alignment programs.

It also matters for cash forecasting: AP aging backed by receive-linked invoices is materially more trustworthy than PO-only estimates or supplier statements without operational cross-check.