Home · Solutions · Other solutions
Solution · Other solutionsThe buyer decides in Teams on the day, not at the payment run three weeks later
Price and quantity mismatches resolved the day they appear
Blocked invoices are read hourly, settled by your tolerance rules where they can be, and put in front of the responsible buyer with order, receipt and invoice side by side.
Executive summary
A variance released under payment-run pressure becomes next quarter's price, and nobody negotiated it.
We keep the ERP match exactly as it is and change everything around it.
Overpayments fall because every variance above tolerance becomes a conscious decision with a recorded reason instead of a release under deadline…
SAP ECC (release, order price correction, invoice return); Power BI exception report
Business problem
Accounts payable
The three-way match is a good control implemented badly. When price or quantity fall outside tolerance the ERP blocks the invoice for payment, which is exactly right. What happens next is not. The block joins a list that accounts payable reviews once a week, the buyer hears about it by email, the goods receipt may simply be late, and the supplier calls before anyone inside the company does.
Under payment-run pressure blocked invoices are released in batches, so the variance is accepted rather than resolved. Procurement never sees the pattern by supplier, accounts payable has no authority to decide, and finance sees only the ageing. Each mismatch is small, each release is defensible, and nobody adds up the total.
The other half of the problem is the shape of the request. The buyer's task arrives as an invoice number and a question, not as the order line, the receipt line and the difference between them. Answering it means searching three systems, phoning a warehouse and emailing a supplier, which is why it waits until it cannot wait any longer.
How it works today
The sequence below is what a blocked invoice goes through today, whichever ERP raises the block.
- SystemThe invoice posts and is blocked for a price difference, a quantity difference or a missing goods receipt
- WaitingThe block waits in a list until the weekly review, which is usually a Friday
- PersonAccounts payable emails the buyer named on the order, quoting the invoice number
- PersonThe buyer searches for the order, the goods receipt and the supplier's last quotation, then asks the warehouse whether the receipt was posted
- WaitingDays pass while the supplier is asked for an explanation or a credit note; the dunning letter arrives first
- Risk of errorThe payment run approaches and a decision is requested today, so the block is released and the order price is left unchanged
- Risk of errorThe next invoice from the same supplier blocks for the same reason, and nobody records that this has happened before
Why the current process costs more than it appears
The budget shows headcount, not what it is spent on.
- Three people are paid to move one invoice: the clerk who chases, the buyer who investigates and the supervisor who confirms the receipt. None of that time is booked against the invoice, so the cost per block is invisible.
- A variance accepted at the payment run is an overpayment nobody negotiates back, and it resets the reference price, so the same difference is charged again on the next order without ever being agreed.
- Late payment costs twice: the discount is lost and the company moves down the supplier's priority list, which matters on the day stock is short.
- Auditors see releases without recorded reasons and ask about the effectiveness of the control, which turns a process problem into a finding.
- Every new range, currency or distribution centre adds mismatch types, so the weekly list grows while the number of reviewers does not.
Cost of inaction
Accepted variances compound quietly. A price released in March is the invoice price in April, and by the end of the year the order price in the ERP describes a commercial agreement that no longer exists. Suppliers learn that dunning works faster than answering questions, so they dun. Buyers spend more time on last quarter's invoices than on next quarter's prices.
The blocked list also grows in a way headcount does not. A new range, a new currency or an acquisition adds mismatch types and doubles the review without doubling the reviewers, and the auditors' point about release evidence comes back with the word repeat in front of it.
A plausible organisation with realistic proportions. The figures are there to be recalculated on your data; they are not a client result.
A food and beverage distributor serving France and Benelux from two distribution centres, with twelve buyers in procurement and five clerks in accounts payable, running SAP ECC.
About 2,000 purchase-order invoices a month, of which roughly 15% block for price, quantity or a missing goods receipt. Price variances come from promotional pricing and quarterly list changes, quantity variances from case-versus-unit confusion and short deliveries.
Blocked invoices are reviewed every Friday. The average block is cleared after sixteen days, mostly by release. Supplier statements show credit notes the company requested and never received, and nobody reconciles them.
Roughly 30 minutes per blocked invoice spread across the clerk, the buyer and the warehouse, almost all of it spent finding documents rather than deciding anything.
A robot reads newly blocked invoices from SAP every hour, applies your tolerance and matching rules, settles what the rules allow with a reason code, and turns everything else into a Teams task showing the order line, the receipt line and the invoice line with the difference highlighted. The buyer chooses an outcome and the robot executes it.
In the modelled case about half the blocks are settled without a person, the rest take twelve minutes instead of thirty, and the sixteen-day average becomes same-day for anything a buyer can decide. The figures are a model, not a measurement.
Proposed solution
We keep the ERP match exactly as it is and change everything around it. An unattended robot reads newly blocked invoices from SAP every hour with the block reason, the order line, the receipt line and the invoice line. A rule set we write with procurement and finance then does what a clerk does today, only in seconds: it clears price differences inside the agreed band, closes quantity blocks explained by a goods receipt posted since the block, converts cases to units where the unit of measure differs, and maps invoices covering several orders at line level. What the rules can settle, the robot settles in SAP with a reason code naming the rule.
Everything else becomes an Action Center task delivered in Microsoft Teams to the buyer named on the order, with the three lines side by side and the difference in euros and percent. The buyer picks one of four outcomes: accept the variance within their authority, request a credit note, correct the order price, or reject the invoice. The robot then executes it, releasing the block, drafting the credit-note request for sending from the accounts payable mailbox, updating the order after approval, or returning the invoice with a reason. Value thresholds route larger variances to the procurement director instead, and authority comes from Microsoft Entra ID groups that procurement maintains.
UiPath Maestro orchestrates the exception from the moment of the block to its closure, because the case may involve a robot, a buyer, a warehouse confirmation and a supplier over several days. UiPath Data Fabric holds the state, the reason and the outcome of every exception, which is what turns the Friday spreadsheet into a report: open blocked value by supplier, buyer, reason and age, and variances accepted per buyer and per supplier over twelve months.
The ERP three-way match and payment block; UiPath Orchestrator scheduling, queues, credential store and audit; UiPath Action Center tasks as actionable notifications in Microsoft Teams with service levels and escalation; UiPath Maestro for the long-running exception; UiPath Data Fabric entities with audit
The tolerance and resolution rule set with delegated authority levels; line-level mapping for invoices covering several orders and unit-of-measure conversion; the buyer task with the three lines side by side; the outcome execution workflows; the exception data model and the reporting on it
SAP ECC reads and writes through UiPath SAP automation (BAPI and OData) for blocks, receipts, order lines, releases and price corrections; supplier correspondence through the Microsoft Outlook 365 connector from a named mailbox
How the automated process works
- AutomationEvery hour the robot reads newly blocked invoices from SAP with the reason, the order line, the receipt line and the invoice line
- SystemThe rule set applies tolerances, checks for a goods receipt posted since the block, converts units of measure and maps multi-order invoices at line level
- AutomationWhat the rules allow is released or corrected in SAP with a reason code naming the rule that applied
- PersonEverything else reaches the buyer as a Teams task with the three lines side by side and the difference in euros and percent
- PersonThe buyer accepts the variance, requests a credit note, corrects the order price or rejects the invoice, within an authority level procurement owns
- AutomationThe robot executes the outcome in SAP, drafts any supplier correspondence for the accounts payable mailbox and records the decision
- AutomationThe exception closes in Data Fabric, and the report shows open blocked value by supplier, buyer, reason and age
Human-in-the-loop model
Automation handles
- Reading blocked invoices and their reasons from SAP every hour
- Applying tolerance, goods-receipt timing and unit-of-measure rules
- Mapping invoices that cover several orders at line level
- Executing the decided outcome in SAP and drafting supplier correspondence
People decide
- Whether a variance is acceptable, within a delegated authority level
- Whether the supplier owes a credit note or the order price was wrong
- Anything above the value threshold, which routes to the procurement director
- Which tolerances to change once the supplier patterns are visible
Before and after
Systems and integrations
Every entry can be checked in vendor documentation. The evidence class is stated next to each one.
Inputs
- SAP ECC blocked invoices
- purchase orders
- goods receipts
- supplier master and contract prices
Automation layer
- UiPath Orchestrator
- UiPath Robots
- UiPath Maestro
- UiPath Action Center
- UiPath Data Fabric
Target systems
- SAP ECC (release, order price correction, invoice return)
- Power BI exception report
Human touchpoints: buyer tasks in Microsoft Teams; escalation to the procurement director; the monthly tolerance review
Technologies used
reads blocks hourly, runs the rule set, executes outcomes in SAP, retries, logs and audits
Areads blocks, order and receipt lines; releases blocks, corrects order prices, returns invoices
Athe buyer task with three lines side by side, its service level and its escalation
Aorchestrates the exception across robot, buyer, warehouse and supplier until it closes
Aholds state, reason and outcome per exception with a full audit trail
Asends credit-note requests from the accounts payable mailbox using approved templates
Aopen blocked value by supplier, buyer, reason and age for finance and procurement
Awhat a rule may settle, what a buyer may accept and what must escalate
CIllustrative economic model
The arithmetic is open, so it can be argued with.
Half of the blocks disappear into rules and the other half still need twelve minutes each, so the hours in the box are 120 of today's 150 a month, and the volume that produces them is 240 rather than 300. Thirty minutes is the combined time of an accounts payable clerk, a buyer and a warehouse supervisor, which is why €41 is a blended fully loaded rate across those three roles rather than one salary. Nothing here was measured at a client.
Run the numbers on your data
An illustrative estimate from your own inputs. It models released capacity; it is not a promise of savings.
Business benefits
- Overpayments fall because every variance above tolerance becomes a conscious decision with a recorded reason instead of a release under deadline pressure
- Blocks clear in days because the buyer receives the case with everything needed rather than a question that starts a search
- Discounts and payment terms are kept because invoices no longer wait sixteen days for a Friday review
- Procurement sees which suppliers and which error types cause the blocks, so pricing and master-data problems get fixed at the source
- Accounts payable stops being the messenger between the buyer, the warehouse and the supplier
- The payment run stops being the deadline that forces decisions, because the list is worked every hour
The management view
- Blocked value by age and reason is a live number rather than a Friday spreadsheet, so payables can be forecast
- Procurement gets a list nobody has produced before: variances accepted per buyer, per supplier and per month, with the reasons attached
- Buyer response time becomes a measurable service level, which changes the conversation from finance is slow to this supplier's pricing is wrong
- Every release is evidenced as a decision by an authorised person, with what they saw attached to it
Board-level KPIs
Security and governance
Where the data sits and who can see it.
- A release or an order price correction is executed by the robot only after a person with the right authority level has decided, and the task record keeps who decided, when and on what evidence
- Authority levels come from Microsoft Entra ID groups maintained by procurement, not from the workflow, so changing a buyer's limit is an identity change and not a deployment
- The robot's SAP account is limited to the invoice and order transactions the process needs, with its secret in the Orchestrator credential store
- Supplier correspondence is drafted from approved templates and sent from a named accounts payable mailbox, so no robot writes to a supplier in its own name
- Processing runs in the EU region of UiPath Automation Cloud against your own SAP, and Orchestrator logs with Data Fabric audit give a complete trail per exception
Why now
Promotional and quarterly list pricing has become normal in food and beverage distribution, so the number of legitimate variances is far higher than the tolerances written years ago assumed, and the gap is paid for at every payment run
The three-way match is deterministic, which makes this a robot's job rather than a model's: the value is in the rules, the routing and the record, none of which needs AI
The buyer can now decide inside Teams with all three documents on one card, which removes the search that made buyers postpone the question in the first place
Relevant executive roles
Unchallenged variances and lost discounts are leakage that never appears as a line in the profit and loss account, and this makes both of them countable
Buyers see variances on the day they occur, and the supplier patterns behind them become an input to the next negotiation
Blocked value by age and reason becomes a report, and the payment run stops being the mechanism that forces decisions
Common questions and objections
It performs the match and raises the block. It does not chase the buyer, present the evidence, execute the decision or report the pattern, and that is where both the time and the money go.
A task with the three lines on one card takes about two minutes, an email takes twenty minutes of searching, and escalation after the service level makes ignoring it visible to a manager.
Those are the blocking tolerances. The resolution rules, the delegated authority and the multi-order mapping usually exist only in people's heads, and writing them down is half the value of the project.
When this is not the right solution
- Most invoices carry no purchase order, so there is nothing to match; purchasing discipline is the first project
- Blocks are rare because receipts and pricing are already disciplined, in which case a weekly review is proportionate
- Buyers are not assigned to orders in the ERP, so there is nobody to route the task to until the master data is corrected
A question for the next management meeting
Somebody accepted every price difference this company paid last quarter: can we produce their names, their reasons and the total?
Implementation approach
Delivery runs in stages, so it can be stopped at any point.
We deliver
- An analysis of one quarter of blocked invoices by reason, supplier, buyer and outcome, with the value behind each group
- The tolerance and authority matrix, agreed with procurement and finance and written down for the first time
- The rule set for reading, settling and executing, including unit-of-measure conversion and multi-order line mapping
- The buyer task in Teams, its service level, its escalation path and the outcome execution workflows
- SAP, Outlook and Teams integrations, the exception data model in Data Fabric and the reporting on it
- Testing on historical blocks, deployment, buyer training and support through the first tolerance reviews
We need from you
- One quarter of blocked invoices with reasons and outcomes
- The buyer-to-order assignment and the authority levels procurement wants to apply
- A SAP service account for the transactions the process needs, in test and production
- A procurement owner for the tolerances and a finance owner for the release policy
Stages
Replay
Last quarter's blocks run against draft rules to show what would have been settled and what would have reached a buyer
Design
Tolerances, authority levels, escalation thresholds, outcome workflows and the security model
Build
Robots, rule set, SAP execution, Teams tasks, Data Fabric entities and the report
Pilot
One supplier category or one distribution centre live, with the Friday review kept as a safety net
Scale
All categories, threshold escalations, supplier pattern reporting and the monthly tolerance review
Departmental. Effort follows the number of block reasons in scope, the state of the buyer-to-order assignment and how much of the resolution logic exists only in people's heads today.
Sixteen days from block to release, and the release is usually the answer.
Export last quarter's blocked-invoice list with its reasons and outcomes. We show which blocks a rule set would have settled within the hour, which would have reached a buyer the same day, and the value behind each group.
Replay last quarter's blocked listThe neighbouring process usually has the same problem
Stop chasing price and quantity differences by email while supplier payments wait for weeks.
View solution Other solutionsInvoices read, coded and routed; people see only exceptionsSomebody still types the PDF into the ERP, guesses the cost centre and chases the approver.
View solution Other solutionsThe same invoice by e‑mail, portal and post, paid onceA hyphen, a rescan or a reissued number is enough for the same invoice to be paid twice.
View solution Other solutionsRequests raised in Teams, approved and ordered the same dayThe compliant route is slower than a chat message, so people order first and paper it later.
View solution Case studyInvoice disputes without escalationA disputed invoice is not one task — it is an investigation: order, delivery, contract, correspondence.
View case study Case studyAutomated P2P query handlingInvoice copies, statuses and statements delivered instantly — around the clock.
View case studyIndustries we deliver this in most oftenManufacturing & industryRetail & e‑commerceServices & ITShared services