SAP catches blocked invoices. Nobody designed what happens next. This fills that gap — a Fiori-native resolution workspace built on top of what SAP already has.
Targets based on industry benchmarks
Every invoice that fails the three-way match lands in the same place: nowhere. There is no queue to work it from and no name attached to it. An AP clerk finds out by chasing a warehouse team for a goods-receipt confirmation. A buyer finds out when a vendor calls about a PO nobody logged. About one in five invoices travels this route, and the only record it leaves is in somebody's inbox.
The difference is ownership, context, and speed. None of which SAP's native tools provide.
The ??? is email chains, phone calls, and spreadsheets.
"I spend hours chasing warehouse teams for GR confirmations. There's no clear ownership."
AP Clerk"We get requests to change POs after the fact, but context is buried in email threads."
Buyer"Nobody tells us which invoices are urgent. We post GRs when we can get to them."
ReceiverSAP tells you an invoice is blocked.
It doesn't tell you who fixes it.
The gap isn't in the ERP. It's in the space between detection and resolution. Undesigned by SAP, owned by no one. SAP Central Invoice Management stops at viewing status. This workspace starts at resolution.
Three screens. One job: resolution.
Targets based on AP automation industry benchmarks. Parseur, Quadient, 2025. Concept prototype.