Picks up every supplier invoice blocked for a price or quantity variance, gets the buyer's or receiver's answer, and releases the block or requests the credit note.
Today an accounts payable (AP) clerk works a list of blocked invoices and emails buyers and receivers for answers, and each answer arrives with the invoice number retyped. The supplier calls about payment before the block is understood.
The app reads every supplier invoice carrying a price or quantity block, puts the invoice line beside the order line and the goods receipts, and computes the variance. A price variance goes to the buyer, who accepts the invoiced price and changes the order, or keeps the order price and requests a credit note; a quantity variance goes to the receiver, who posts the receipt that is still open or records a short delivery from a handheld. The supplier uploads the credit note on the portal screen, and the app matches it to the invoice. When order, receipt and invoice agree, the block is released through the invoice release interface and the payment run picks the invoice up.
| Lane | Does |
|---|---|
| Accounts payable | reviews the variance, asks the buyer or receiver, releases the block |
| Buyer | decides on a price variance: change the order or request a credit |
| Receiver | confirms the goods on site and posts the receipt from a handheld |
| Supplier | uploads the credit note or confirms the price on the portal screen |
| AP lead | releases invoices above the tolerance and watches due dates |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Blocked invoices | grid of invoices with supplier, amount, block reason, variance amount, due date, days blocked, owner; filter by plant and reason; open button |
| S02 Invoice detail | invoice line beside the order line and the receipts: price ordered and invoiced, quantity ordered, received and invoiced; variance computed; ask-buyer and ask-receiver buttons |
| S03 Buyer decision | options: accept the invoiced price and change the order, keep the order price and request a credit, split; note; decide button |
| S04 Receiver check | mobile screen: delivery note number, receipt to post with quantity field and scan; post receipt or record short delivery |
| S05 Supplier credit | portal screen: the difference and its reason; upload of the credit note or confirmation of the price; submit |
| S06 Board | blocked value by reason and age, invoices due within 7 days still blocked, cash discount at risk, releases per day |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Supplier invoice | supplier invoices with block reason, amount and due date | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Purchase order line | order lines with price and quantity | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Goods receipt | receipts posted against the order line | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Supplier master | supplier contacts and payment terms | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Supplier invoice | payment block released; credit note reference recorded |
| Purchase order line | price changed on the order line when the buyer accepts the invoiced price |
| Goods receipt | goods receipt posted by the receiver for the delivered quantity |
Start: A supplier invoice whose block is set for a price or quantity variance.
# start criterion, in canonical fields; each system page shows it in that system's fields
{invoice.block} in (price, quantity)| Step | Moves when |
|---|---|
| Block detected | invoice with a price or quantity block read from the ERP; variance computed; owner set by reason: price to the buyer, quantity to the receiver |
| Facts checked | buyer or receiver answers within 2 working days on their own screen |
| Decision | order price changed, credit requested, receipt posted or short delivery recorded |
| Supplier credit | credit note uploaded on the portal and matched to the invoice; or price confirmed |
| Released | block removed through the invoice release interface; payment run picks the invoice up; case closed |
| Component | Trigger → action → outcome |
|---|---|
| btn_ask_buyer | on click → send the line to the buyer with the price difference and the last price paid → start the 2-day clock |
| btn_accept_price | on click → change the price on the order line through the ERP order interface → release the block, close the case |
| btn_post_receipt | on tap → post the goods receipt for the delivery note quantity through the ERP goods movement interface → rerun the match, release the block when the quantities agree |
| btn_request_credit | on click → create the portal request with the difference → hold the invoice until the credit note is matched, remind the supplier after 5 days |
| Step | Time limit and escalation |
|---|---|
| Buyer or receiver answer | 2 working days, then the AP lead is copied and the owner's lead reminded |
| Supplier credit note | 5 working days, then the supplier's account manager is copied |
| Due date | an invoice still blocked 5 days before its due date moves to the top of S01 and the AP lead sees it |
Names, places and figures are illustrative; the pattern is the catalogue's.
At 07:45 the queue for the Manchester shared service centre held 128 blocked invoices worth 2.3 million, 41 of them due within a week. Claire in accounts payable opened a 46,000 invoice with a 4 percent price difference, sent it to the buyer at 08:10 and had his decision by 09:30: the increase matched a new price list, so he updated the order line and the block released at once. A quantity block on a pallet of filters went to the receiver, who found the delivery note in the goods-in office and posted the receipt from his handheld at 11:20. The board showed the AP lead 74 releases that day and 380,000 of cash discount kept.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Supplier invoice read from RBKP · RSEG (supplier invoices); also on SAP ECC.
Open the S/4HANA page →Supplier invoice read from Payables REST: invoices; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Supplier invoice read from CONFORMED.SUPPLIER_INVOICE; lakehouse.
Open the Snowflake page →Supplier invoice read from silver.supplier_invoice; lakehouse.
Open the Databricks page →Other systems connect through the same handlers; see how SmartApps connect.
About 30 minutes to a first running screen on your live rows, and 4 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.
Any of SAP S/4HANA, Oracle Fusion Cloud, Snowflake, Databricks, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.
Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.