Procure-to-Pay: Design for a Dependable Outcome

Define completion before changing the work

Consider a requester arranging one fixed-price service visit under an existing agreement with an approved supplier. One purchase order covers the visit and one invoice. Supplier payment details are already verified and unchanged. Supplier selection and onboarding precede this boundary; partial delivery, milestone billing, disputed work, changed bank details and specialist tax or cross-border cases follow their established routes outside the initial eligible scope.

The Outcome owner defines accepted completion for this design: the agreed service has been verified and accepted, the correct obligation has been paid once to the intended supplier, beneficiary credit is confirmed, and the bank and accounts-payable records are reconciled. No unresolved discrepancy remains through the agreed follow-up. The selected payment route is assumed to provide confirmation sufficient to establish that credit. Where it does not, a submitted instruction leaves the outcome unconfirmed.

Timeliness is a separate service commitment. A late purchase can meet the completion criteria and count once as an accepted outcome, but its missed payment date remains visible. Its additional handling, recovery and applicable late-payment charges remain within the declared recurring cost boundary. Reporting must distinguish accepted on-time outcomes from accepted late outcomes, alongside pending and failed cases. A lower Cost per accepted outcome cannot by itself establish a dependable service.

This definition gives each participant a result to recognize. The business receives the agreed service. The supplier receives the correct payment and useful information when a problem delays it. Operating teams can resolve the case without repeatedly reconstructing its history. An approved invoice, a payment instruction and an accepted evidence handoff are intermediate states within that result.

The starting constraint is also hypothetical. Before funding the intervention, trace ordinary and delayed cases to see whether acceptance gaps account for consequential waiting and rework. If dependable evidence is already available and approval queues dominate elapsed time, the priority may be reviewer capacity or a different authorized workflow. The Redesigning Work Around Outcomes method begins with that diagnosis.

Carry the purchase across the whole operation

The requester describes the required service and its intended result. An authorized budget holder approves the need within the applicable policy and purchasing limits. Procurement then issues the order against the agreement. At that point, the order names the service acceptor and qualified backup, identifies the evidence needed to confirm delivery, and records the relevant terms and dates. The receiving manager confirms that these responsibilities fit the team's workload.

After the visit, the supplier submits its service report. In the ordinary case, the designated acceptor checks the delivered work against the agreed requirement and records acceptance in the authoritative receiving or service system. Accounts payable receives that evidence with the order reference and can accept the handoff. Sending a notification does not establish that AP has received usable information or can process it within the required window.

When the invoice arrives, extraction makes its contents available for checking. AP establishes the invoice's relationship to the applicable order, service acceptance, agreement, prior invoices and adjustments. It also checks for duplication and whether the conditions for payment have been met. Microsoft's invoice-matching documentation describes comparisons among invoice, purchase-order and receipt information, with configured tolerances. Those comparisons support controls; they cannot supply a business acceptance that was never recorded.

The authorized Finance approver then authorizes the specific payment. The payment function initiates that instruction through the controlled route, using the governed supplier record. The operation records authorization, initiation and confirmed outcome separately. Even a successful technical response can acknowledge processing that remains incomplete: HTTP's 202 Accepted status explicitly has that meaning. The payment provider's actual status contract must determine what its response establishes.

The reconciliation team checks confirmation of beneficiary credit and matches the payment to bank and AP records. A return, unexplained difference or uncertain outcome remains an owned case. Only when the completion criteria and follow-up are satisfied is the purchase accepted. A shared case record connects the source references, versions, decisions, responsible people and current state; the supplier master, order, acceptance record and payment systems remain authoritative for their own facts.

Keep the exception owned through recovery

Now change one condition. The invoice still matches the order, but the business acceptance is absent or cannot be trusted. The supplier's report establishes what the supplier reported. The system must preserve the unresolved question of whether the business has accepted the service, rather than convert that report into an approval.

Invoice intake, checks of other fields and evidence assembly can continue. Payable clearance and payment release that require acceptance remain held. Finance separately determines accounting recognition; a payment hold does not by itself establish that no liability exists. AP sends the designated acceptor the applicable order, service report, missing evidence and decision required, with a response window that leaves time to protect the payment commitment.

The acceptor needs relevant expertise and decision authority as well as availability. A qualified backup must have the same permissions for the assigned decision. If neither can respond, the Operating owner retains the case and escalates before the response window expires to the designated duty decision maker, with the necessary Finance or commercial authority. That person arranges qualified verification or addresses the commitment under existing policy; unavailable staff cannot be replaced by assumed evidence. AP communicates the known status and next step to the supplier. This is a coverage failure to resolve, not a conclusion about an employee's capability.

The authorized receiving/source owner verifies the work and corrects the governing acceptance record. If unclear instructions caused the gap, the Knowledge owner works with procurement and Finance to correct the applicable guidance. As the Enterprise Knowledge Backbone explains, source applicability matters at the decision: a newer document is useful only if it governs this service and commitment.

Correction must reach relevant derived information. The Technology owner ensures that stale summaries or cached context cannot continue to support the case, while required decision history is preserved. The information-rights treatment also matters here: access, reuse and disclosure need a permitted purpose. An assistant summarizing service evidence has no reason to receive supplier bank details, and retaining that evidence as persistent model memory is not an automatic entitlement.

Before resumption, AP and the controlled workflow recheck the current order, acceptance, invoice history, permissions, approvals and payment state. The systems-of-record treatment explains why stable operation references and supported duplicate and concurrency controls matter. A timeout must not open a second payment route while the first might have succeeded. The payment function resolves the original attempt's state before deciding whether another instruction is warranted.

Once those conditions are satisfied, the purchase returns to the ordinary validation, authorization, payment and reconciliation route. The hold concerns this affected case. Repeated gaps become evidence for changing order requirements, guidance or coverage through approved changes; they do not authorize a system to rewrite its own rules.

Choose the first intervention from the constraint

The first commitment covers a defined cohort of standard service orders handled by a participating receiving team. It changes how acceptance responsibility is assigned at the order stage, how evidence is recorded and how AP accepts that evidence. The full purchase remains the unit for judging eventual value. Decisions about the commercial commitment, service acceptance and payment retain their established human authority.

Start by making the acceptance requirement workable. Procurement and the receiving manager agree who can verify the service, what evidence is sufficient, who provides cover and how long a case can wait before escalation. A structured confirmation and deterministic workflow can check required fields, track deadlines, route tasks and enforce a hold. This is a credible first response to the assumed constraint.

AI assistance remains conditional. A source-linked summary could help a person review a narrative service report, but it must earn its place against the structured workflow after human checking, correction and recurring cost. Workflow, Agent, or Both? helps distinguish that assistance from an agent choosing its next investigative step.

Consider a possible subsequent capability when an invoice arrives without dependable acceptance evidence. Within an authorized investigation, an agent checks permitted order, service and acceptance records. What it finds determines the next permitted step: checking the applicable service report, locating the designated acceptor or identifying the qualified backup. Choosing among these steps as the case develops is the agent contribution. That flexibility might help with variable exceptions; a predefined workflow remains sufficient where the useful sequence is predictable.

The agent assembles a source-linked explanation of the evidence, unresolved questions and proposed next step. It routes the unresolved decision to the qualified person only through explicitly authorized recipients, channels and message purposes. The person verifies the service and records the decision in the authoritative system. Before resuming, the controlled workflow rechecks current evidence, permissions, approvals and payment state. The agent's summary remains supporting material, never the authoritative acceptance record.

The agent cannot infer business acceptance from a supplier's report, manufacture missing evidence, attest service or approve payment. It cannot override controls, change supplier bank details or initiate an alternative payment route. Unresolved conflicts, unavailable qualified coverage, tool failures or exhausted investigation limits trigger escalation, with the dependent action held. Information access and retention remain limited to the permitted purpose.

This is a possible later capability requiring separate evidence and authorization, not an implemented feature or a prerequisite for the first intervention. Compare its incremental value with the deterministic workflow using exception-resolution time, evidence quality, human review effort, errors and recurring cost. No result or saving is established by this example.

The authority arrangements below distinguish the first intervention from any separately authorized later investigation. They coexist; they are not a progression toward greater autonomy. Access to information does not confer authority to approve a payment, as Before an AI Agent Acts makes explicit.

These arrangements need funded owners. The Outcome owner accepts the end-to-end criteria and resourcing commitment. The Operating owner runs the queue, response coverage and recovery route. The Knowledge owner maintains applicable guidance, while transactional source owners retain correction duties. The Technology owner maintains the integrations, access and enforceable checks. The Control lead coordinates control evidence, and the Sponsor resolves commitments beyond the operating team's authority. Procurement, Finance, legal or privacy specialists and independent assurance keep their distinct mandates.

The intervention could demonstrate that acceptance evidence reaches AP with less delay and rework, and that this improvement survives the remaining payment journey. It would not establish readiness for changed bank details, broader purchasing categories or delegated payment authority. Those would require separate evidence and decisions.

Use released capacity without weakening service

Evaluate the cohort from the purchase need through accepted completion. Report accepted on-time and accepted late outcomes separately, with pending, failed and reopened cases visible. Pair total elapsed time with waiting at each handoff. Track repeated acceptance gaps, rejected handoffs, corrections and recovery, together with supplier contacts and repeated requests for evidence. Include additional receiving-team effort: moving work from AP to a service team is not itself a saving.

Cost per accepted outcome divides the cohort's total recurring operating cost by its accepted completed purchases, using the same scope, accounting window and agreed follow-up. Include technology and usage, work across procurement, receiving, AP and payments, human review, correction, failed or repeated attempts, support and recovery. Record attributable late-payment charges consistently within the declared boundary. The supplier's underlying service price is tracked separately from this process operating-cost measure. One-time design and build investment is also separate.

A correctly completed late purchase enters the denominator once after acceptance; its late status and costs remain. Pending or unresolved purchases do not enter it. Count each purchase once even if several attempts were needed. Reopened cases keep their identity, with acceptance and cost reporting corrected consistently. Match the cohort and its accumulated costs through the stated follow-up rather than dividing this month's costs by unrelated earlier completions. Report unfinished work and the reporting lag. With zero accepted outcomes, report “not calculable.”

Compare like-for-like scope and case mix with the starting operation. Separate improvement from the process and workflow changes from any incremental AI contribution. Finance validates the cost allocations and any savings claim. Unchanged payroll is not a cash saving, and released hours remain potential capacity until someone can use them for accepted work. This follows the realized-value reasoning in From Idea to Operating Case.

Suppose AP spends less time chasing acceptance. Before any analyst time is reassigned, the Operating owner must confirm residual coverage for normal demand, exceptions, absences and recovery. The review includes representative workload and an absence scenario, with qualified backup capacity available. An improvement in average handling time alone cannot justify reduced service cover.

The Procurement operations manager could then accept a finite assignment to review already-approved, upcoming service orders that lack named acceptance coverage. That receiving manager explicitly accepts the scope, available analyst time, access, preparation, supervisory effort and completion criteria. Service managers must also commit time to validate qualified acceptors and backups. The analyst prepares gaps and proposed corrections; the authorized managers make the assignments. Record this additional receiving and specialist effort when evaluating the benefit.

The assignment ends when the defined order queue is accepted as corrected, or reaches its pre-agreed end date. At the scheduled review before that endpoint, the receiving manager accepts completed work and identifies any residual queue. The Outcome owner decides the next allocation with the Operating owner and receiving manager, using verified coverage, corrected orders and subsequent acceptance-gap evidence. The decision can close the assignment and select its next use, fund a defined extension, or return capacity to AP if coverage has weakened. This preserves the distinction developed in The Human Side of Autonomous Operations between reassigning capacity and reducing the coverage that keeps the operation dependable.

At the intervention review, the Outcome owner can Expand the eligible volume when completed outcomes, recurring cost and capacity justify it; expanded authority remains a separate decision. Continue keeps the bounded scope while sufficient follow-up evidence accumulates and controls remain workable. Narrow removes a source, service category or team that cannot sustain the requirements. Redesign changes the operation when another constraint dominates or assistance adds work without enough benefit. Stop ends the specified trial or assisted component when it cannot sustain its benefit or controls, with the Operating owner retaining a staffed route for outstanding purchases. None of these decisions can be inferred from a single faster task.