€14bn spend analysed
€819k recovered
85% found through supplier statements
A large retailer running SAP had built the kind of accounts payable controls most finance teams aim for.
Its three divisions run on a single SAP system and process millions of invoices from tens of thousands of suppliers. Every invoice passes through three-way match, a duplicate check and segregation of duties. With controls this strong, the question was what, if anything, still gets through.
To answer it, the retailer brought in Transparent with three goals:
- Recovery: find and recover overpayments, VAT and credits that had slipped through or were never processed.
- Control assurance: get an independent view of how well its control framework holds up.
- Process improvement: find where the purchase-to-pay process could be strengthened.
The most useful answer came from somewhere its own data could not reach.
Two views of the same payments
Transparent carried out an Accounts Payable Recovery Audit, looking at the retailer’s payments from both sides.
- Internal system analysis: payment data was run through sophisticated algorithms for duplicates, pricing, returns, bonuses, discounts and VAT, and every finding was checked against the archived invoice.
- External supplier statement reconciliation: the second stream moved outside the retailer’s ERP. Transparent contacted approved suppliers directly to collect and reconcile complete statements of account. That review brought up unapplied discounts or bonuses, and open credits sitting on vendor ledgers.
The two views told very different stories.
What the payment data showed
The internal analysis was reassuring. It found a relatively small number of duplicates, and invoices where a price difference stayed within the tolerance band. VAT came back clean.
On this evidence alone, the controls were doing their job.
What the supplier statements showed
This is where the picture changed. Around 85% of everything recovered came from credit notes and rebates that suppliers had issued and the retailer had never posted. The causes were ordinary:
- Returns that never reached AP: the return was booked in inventory management, and nobody told AP a credit was owed.
- Credits sent to the wrong person: the credit note went to the buyer on the original order, who had moved on.
- Rebates lost in a contract change: a bonus contract was replaced by a cheaper one, and the bonus terms didn’t carry over.
- Rebates lost in a merger: the supplier’s contacts changed, and the rebate statement went to someone who no longer dealt with it.
With nothing posted, there was no open item, and the next payment run paid the invoice in full.
“Services are excellent due to a strong customer service team, professional communication with us and our suppliers, and the recoveries are outstanding.”
– Global Sourcing Manager, Retail company
Why the controls couldn’t see it
Every control in the retailer’s purchase-to-pay process was built to judge an invoice. Three-way match compares it with the purchase order and the goods receipt. The duplicate check compares it with invoices already posted. Segregation of duties makes sure no one person can both create and approve a payment. Each of these acts once a document enters AP, and each did its job.
The money that got through sat in places those controls were never designed to look:
- Credits that never get posted on SAP: a credit note that never reaches AP, or reaches it and is never posted, creates no open item. With nothing on the ledger to offset, the next payment run pays the supplier’s invoice in full, and no control has anything to flag.
- Credits that arrive but can’t be matched: a credit with no open invoice to match against, or with a discrepancy in it, waits in an approval queue. Some suppliers also apply incoming payments to their oldest open invoice, whatever the remittance says, which leaves the credit sitting on their ledger.
- Rebates that live in the contract: the payment run reads invoices, and rebate terms sit in contracts. A rebate builds up across hundreds of invoices without any single one showing it, and when a contract is replaced or a supplier merges, the terms can drop out of view entirely.
- Price differences inside tolerance: the tolerance band sets how far an invoice price can drift before the invoice blocks. A price change that never reached the agreed price in SAP can sit inside that band and post without review.
- Duplicates that look new: SAP’s duplicate check compares vendor, reference and date, so one changed character or a retyped date is enough to pass it. The warning it raises can be clicked past, and it only compares invoices within one vendor account, so a supplier held under two vendor numbers is never compared with itself.
What these have in common is that documents are checked one at a time, and nobody owns the full balance with each supplier. A supplier who is owed money sends reminders until it gets paid. A credit owed to the buyer has nobody chasing it, and it shows up in one place first: the supplier’s own statement. That is why the statement is the one check internal data cannot replace.
“We see this pattern in a lot of audits. The AP controls are usually solid, because they’ve been built and tuned around the invoice for years. A credit note doesn’t travel that route. It lands with a buyer or in the warehouse, or it never leaves the supplier’s ledger at all, and nobody inside the company has a reason to go looking for it. The supplier statement is often the first place it shows up.”
– Sjoerd Gonggrijp, Sr. Delivery Manager, Transparent
From findings to process improvement
For each confirmed finding, Transparent traced where the payment error occurred. Each part of the retailer’s process worked well on its own: SAP, the warehouse, purchasing, the buyers and AP all did their job. The errors occurred at the points where information has to pass from one system or team to another, or between the retailer and its suppliers. In a business of this size, those points are hard to see from inside any one team. Five stood out, and each raised a question about how the retailer’s process was set up:
- No single route for documents into AP: suppliers sent credit notes, copies and reminders to whoever they had dealt with, often the buyer on the original order. Some never reached AP, and others reached it twice and were keyed as new invoices.
Our recommendation: set up a dedicated AP inbox for all invoices and credit notes, and define a clear process for documents that arrive anywhere else. - Information from other teams depends on someone passing it on: the warehouse knew goods had gone back, purchasing knew a price had been renegotiated, and procurement knew the rebate terms in the contract. AP only learned about any of it if someone passed it on.
Our recommendation: match return deliveries to credit memos, compare rebate terms in contracts with the rebate credits posted, and check invoice prices against agreed prices, line by line. - Supplier changes aren’t carried through: when a contract was replaced, a supplier merged or a contact moved on, the vendor record, the contacts and the rebate terms stayed as they were, and in some cases a second vendor record was created.
Our recommendation: screen vendor records for a shared tax ID, bank account or near-identical name. - Exceptions have no owner or deadline: a credit that couldn’t be matched waited in a queue, a duplicate warning could be clicked away, and price differences inside tolerance posted without a second look.
Our recommendation: limit who can dismiss a duplicate warning, review a sample of dismissed ones, and look at the price variances that post inside tolerance. - The full supplier position sits outside any one team’s view: AP checked invoices, credits and payments one at a time, as the process is designed to, and the overall balance with each supplier wasn’t part of anyone’s routine. Credits sitting on suppliers’ ledgers, and payments they had applied to the wrong invoice, went unnoticed.
Our recommendation: review vendors with a credit balance and credits older than 90 days with no clearing document, and reconcile supplier statements regularly.
Each of these points to a step the retailer can now build into its process, so it no longer depends on someone remembering.
Test what your controls can’t see
A clean result from your own data tells you the invoices you received were handled well. Speak with our specialists to find out what is sitting on your suppliers’ books.

Meet the Expert: Sjoerd Gonggrijp
Sjoerd Gonggrijp has spent more than 17 years at Transparent, helping global clients improve their purchase-to-pay processes from one audit to the next. Much of that work has been with mature organisations, where the remaining gaps are harder to spot and any change has to fit an established process. Clients and colleagues know him as the person to call for practical recommendations a team can act on straight away.
Sjoerd Gonggrijp, Sr. Delivery Manager at Transparent








