App catalogue Procurement

Invoice exception resolution

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.

SCREENSDATA HANDLERSSOURCE OBJECTS, READ IN PLACES01 Blocked invoicesscreenS02 Invoice detailscreenS03 Buyer decisionscreenS04 Receiver checkscreenS05 Supplier creditscreendh_invoiceSupplier invoicedh_poPurchase order linedh_grGoods receiptdh_vendorSupplier masterS/4HANARBKP · RSEGS/4HANAEKKO · EKPO · EKET · EKBES/4HANAMATDOCS/4HANALFA1 · LFB1 · LFM1rows stay in the source · access rules apply at read time · writes go through the source's released interface and are confirmed
The screens, the data handlers behind them and the objects each handler reads in place on S/4HANA. Other systems have their own page.
4 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
4
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
3
clocks with escalation
catalogue
What it does

Today, and with the app

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.

Who takes part

Data-driven app: starts from the records a criterion selects; each record launches its own flow

LaneDoes
Accounts payablereviews the variance, asks the buyer or receiver, releases the block
Buyerdecides on a price variance: change the order or request a credit
Receiverconfirms the goods on site and posts the receipt from a handheld
Supplieruploads the credit note or confirms the price on the portal screen
AP leadreleases invoices above the tolerance and watches due dates
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 Blocked invoicesgrid of invoices with supplier, amount, block reason, variance amount, due date, days blocked, owner; filter by plant and reason; open button
S02 Invoice detailinvoice 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 decisionoptions: accept the invoiced price and change the order, keep the order price and request a credit, split; note; decide button
S04 Receiver checkmobile screen: delivery note number, receipt to post with quantity field and scan; post receipt or record short delivery
S05 Supplier creditportal screen: the difference and its reason; upload of the credit note or confirmation of the price; submit
S06 Boardblocked value by reason and age, invoices due within 7 days still blocked, cash discount at risk, releases per day
Data handlers

4 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Supplier invoicesupplier invoices with block reason, amount and due dateS/4HANA · Oracle Fusion · Snowflake · Databricks
Purchase order lineorder lines with price and quantityS/4HANA · Oracle Fusion · Snowflake · Databricks
Goods receiptreceipts posted against the order lineS/4HANA · Oracle Fusion · Snowflake · Databricks
Supplier mastersupplier contacts and payment termsS/4HANA · Oracle Fusion · Snowflake · Databricks

Written back

ObjectWhat changes
Supplier invoicepayment block released; credit note reference recorded
Purchase order lineprice changed on the order line when the buyer accepts the invoiced price
Goods receiptgoods receipt posted by the receiver for the delivered quantity
The flow

From the trigger to the last write

THE FLOW · INVOICE EXCEPTION RESOLUTION1Block detectedinvoice with a price orquantity block read fromthe ERP; variance computed;owner set by reason: priceto the buyer, quantity tothe receiver2Facts checkedbuyer or receiver answerswithin 2 working days ontheir own screen3Decisionorder price changed, creditrequested, receipt postedor short delivery recorded4Supplier creditcredit note uploaded on theportal and matched to theinvoice; or price confirmed5Releasedblock removed through theinvoice release interface;payment run picks theinvoice up; case closed
Each step and the criterion that moves it.

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)

StepMoves when
Block detectedinvoice 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 checkedbuyer or receiver answers within 2 working days on their own screen
Decisionorder price changed, credit requested, receipt posted or short delivery recorded
Supplier creditcredit note uploaded on the portal and matched to the invoice; or price confirmed
Releasedblock removed through the invoice release interface; payment run picks the invoice up; case closed
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
btn_ask_buyeron click → send the line to the buyer with the price difference and the last price paid → start the 2-day clock
btn_accept_priceon click → change the price on the order line through the ERP order interface → release the block, close the case
btn_post_receipton 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_crediton click → create the portal request with the difference → hold the invoice until the credit note is matched, remind the supplier after 5 days

Clocks

StepTime limit and escalation
Buyer or receiver answer2 working days, then the AP lead is copied and the owner's lead reminded
Supplier credit note5 working days, then the supplier's account manager is copied
Due datean invoice still blocked 5 days before its due date moves to the top of S01 and the AP lead sees it

Measures

blocked value by reasoninvoices released within 3 dayscash discount keptcredit notes received within 5 daysblocks per 1,000 invoices
A day with the app

Illustrative

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.

illustrative scenario · Invoice exception resolution
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

Terms on this page

Payment blockThe mark on a supplier invoice that keeps it out of the payment run until someone removes it.
Price varianceThe difference between the price on the purchase order and the price on the invoice.
Three-way matchThe check that order, goods receipt and invoice agree on price and quantity.
Questions

How long does it take to have this running?

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.

Which system does it run on?

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.

Who takes part from outside the company?

Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

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.