Purchase order, receipt, price and documentation differences handled as a case with a named owner, the applicable authorization and a verifiable outcome — from detection to the confirmation recorded in the authorized financial system.
01 · The problem
An invoice stops because of a specific difference: the quantity received does not match the quantity invoiced, the price differs from the agreed one, the purchase order is missing, or the document arrived incomplete. Resolving it takes procurement, the receiving team, quality, accounts payable — or the supplier.
The work is coordinated with whatever is at hand: Microsoft Excel spreadsheets holding the pending list, email asking for the explanation, and Power BI reporting on the accumulated volume. Each piece serves a useful purpose, and none of them records who was supposed to act, what was answered, and under which authorization the difference was closed.
Delay rarely comes from missing systems: it comes from a difference with no assigned owner and no verifiable outcome.
02 · The solution
Every difference is handled as a case with a declared path: detection or intake of the exception, classification of the difference type, assignment to the owner who can resolve it, query and answer, the authorization that applies by rule and amount, and confirmation from the authorized financial system.
The path comes from the approved definitions of the Operational Graph: each invoice is connected to its purchase order, its goods receipt, its contract where one exists, the legal entity and the owner who can resolve it. BPMflow carries it — cases, assignment, deadlines, authorizations and evidence: the process comes from the graph rather than from an isolated diagram.
Supplier Service Desk for Shared Services is the supplier's front door; this path resolves the next step. When the difference is settled against contractual truth, the context comes from Vendor, SLA & Contract Intelligence. Once the difference is resolved and approved, the payment follows a route of its own — instruction, posting, execution, rejection or return, reconciliation — in Corporate Payments and Reconciliation.
03 · Capabilities
Differences sit in a single queue, with type, owner, aging and pending authorization in plain view. Max answers about the case within the authorized context: it explains what is missing, shows the evidence on record and proposes the next owner.
Opens the case from invoice posting, a periodic review or the supplier's request.
Separates quantity, price, missing purchase order, incomplete documentation, disputed tax or unexpected charge: each type carries its own owner and rule.
Routes the case to procurement, the receiving team, quality, accounts payable or the supplier, based on type, legal entity and amount, with a committed deadline.
Records the question, the answer, the attachment and the agreed correction. The supplier takes part with scoped access to its own case.
Applies the rule in force by difference type and amount band, and keeps the signed approval with its author and timestamp.
Takes in the confirmation from the authorized financial system and keeps what was detected, who resolved it and what was authorized.
04 · Roles
Detects the difference and carries the case.
What they see
The held invoices by type, aging, legal entity and owner, with their documentation.
What they do
Open or confirm the exception, classify it, assign it and record the agreed outcome.
Explains or corrects the difference.
What they see
The cases in their area with the order, the receipt, the supplier document and the deadline.
What they do
Provide the explanation, correct the source data or request the correction from the supplier.
Approves the resolution within their scope.
What they see
The exceptions pending at their level, with the supporting evidence and the amount at stake.
What they do
Approve, reject or return with a query, according to the rule in force and the amount band.
Provides the missing document or correction.
What they see
The status of the exception involving them and what information is missing, in their own case.
What they do
Answer the query, send the credit note or the corrected document, and follow progress.
05 · Implementation
Implementation starts from the current process: the minimum context of the first path is enough, with no prior architecture project.
1 · Agree on the outcome
Which differences are in scope, who resolves each type, which authorization applies by amount, and what counts as the agreed outcome.
2 · Recover context and connect sources
Takes the purchase order, the goods receipt and the invoice from the ERP and the procurement platform, and integrates with the organization's document repository — Microsoft SharePoint, for example — when that is the authorized source.
3 · Test the path and adopt it
Tested with cases from the current period, rules and deadlines are tuned, and daily operation stays under the client team's control.
06 · Typical scenarios
Several legal entities, high invoice volume, distributed procurement and receipt teams: situations that repeat daily.
An invoice exception is resolved when someone can explain it, someone can authorize it and the outcome is confirmed. Starting from one specific difference type is the practical way in.
Invoice Exception Resolution is an EAFlow cross-industry solution on the Operational Graph, carried by the BPMflow automation capabilities. Supplier Service Desk for Shared Services organizes the supplier's front door, and Vendor, SLA & Contract Intelligence provides contractual truth. When the difference turns into a commercial negotiation, that is a separate path: commercial claims and deductions, on the same base.
