SAP's standard duplicate invoice check works well when the reference is typed the same way. It is silent when it isn't.
SAP's standard duplicate invoice check only runs for suppliers flagged for it, and it needs the reference to match exactly. Export supplier line items for at least 12 months and test for references typed differently, same amount and date, repeats within 30 days and duplicate supplier records.
SAP checks for duplicate supplier invoices, but only for suppliers whose master record has the Chk double inv. indicator set (company code data, payment transactions).
List supplier line items for at least the last 12 months, including cleared items: in SAP GUI that is transaction FBL1N, and in S/4HANA the Manage Supplier Line Items app. Show the supplier, reference, document date and amount, then export to a spreadsheet. Keep invoices and filter out payments and credit memos before you test.
Your system's own check compares fields exactly. Real duplicates usually differ in one small way, so test the export four ways:
The free Online Duplicate Invoice Checker runs all four on up to 1,000 lines in your browser, shows the value at risk and lists each flagged line next to the line it matches. Nothing is uploaded. If you prefer formulas, How to find duplicate invoices in Excel shows how to build the same tests yourself.
Make sure every active supplier has Chk double inv. set. On premise, consider making F5117 an error rather than a warning, and review which fields OMRDC compares for MIRO. Agree one way of keying the reference, exactly as printed on the invoice. Then keep the four tests as a regular check for the variants the standard check can't see.
Hold every HIGH flag that is still unpaid until someone has compared the two documents. For REVIEW flags, confirm whether it is a genuine repeat charge and note why. If a duplicate has already been paid, ask the supplier for a refund or a credit note straight away and track it until the money is back: the duplicate payment audit guide covers the recovery steps.
Run the check before every payment run, not once a year. Duplicates are usually keyed weeks apart, so always include at least the previous 12 months of bills, not just the invoices in this run.
SAP uses "vendor" in older releases and "supplier" in S/4HANA; both mean the same record. UK and US teams run the same check.
Supplier statement to AP ledger. Finds invoices you haven't posted, credit notes still to come, price differences, duplicate postings and payments in transit, and builds the supplier reconciliation. Runs in your browser on your own computer: nothing is uploaded.
Paste or upload your invoice list and see likely duplicates in seconds. Runs in your browser; nothing is uploaded.
The Accounts Payable Control System runs four duplicate-invoice tests, supplier master fraud checks and a three-way match on every invoice, with a payment run release gate that blocks release while exceptions are open. Excel, no macros, one-time price.
Common reasons: the supplier didn't have Chk double inv. set, the reference was typed differently, the document date differed, or the warning was accepted.
By default it is a warning. On premise the FI message can be changed to an error; check what your system uses.
FBL1N in SAP GUI, or the Manage Supplier Line Items app in S/4HANA. Include cleared items so paid invoices are tested too.
Last updated 03 November 2026. General guidance for finance teams; check it against your own policies, systems and local rules.