How do you prevent duplicate vendor invoices in SAP ?
SAP FICO Interview Q&A
Topic: Duplicate Invoice Check
1. Basic Concept
Q1. What is a Duplicate Invoice in SAP?
Answer
A duplicate invoice occurs when the same vendor invoice is entered more than once in the system, which may lead to duplicate payment to the vendor.
Example:
Vendor: ABC Supplier
Invoice Number: INV-1001
Amount: 10,000
If this invoice is posted twice:
Document 1 → 1900000005
Document 2 → 1900000010
The vendor may get paid twice for the same invoice.
2. Why Duplicate Invoices Occur
Q2. What are the common reasons for duplicate invoice posting?
Answer
Duplicate invoices can occur due to several reasons:
1️⃣ Vendor sends the same invoice multiple times
2️⃣ Accounting staff posts the invoice twice by mistake
3️⃣ Invoice documents are misplaced or delayed
4️⃣ Intentional fraud between vendor and AP staff
SAP configuration helps prevent accidental duplicates, but fraud requires additional controls.
3. Controls to Prevent Duplicate Invoices
Q3. What is the holistic approach to prevent duplicate invoices?
Answer
Organizations must combine system configuration + internal controls.
Key controls include:
1️⃣ Restrict vendor master creation to authorized users
2️⃣ Prevent duplicate vendor master creation
3️⃣ Block inactive vendors
4️⃣ Make sensitive vendor fields (bank details) approval-controlled
5️⃣ Use Purchase Order process whenever possible
6️⃣ Implement 3-way match (PO + GR + Invoice)
7️⃣ Separate invoice parking and approval roles
8️⃣ Make Reference Document Number mandatory
These controls reduce duplicate invoice risk.
4. SAP Configuration for Duplicate Invoice Check
Q4. How does SAP automatically check duplicate invoices?
Answer
SAP performs duplicate invoice checks based on:
Vendor
Invoice reference number
Invoice amount
Invoice date
Company code
Currency
If the system finds the same combination, it generates a duplicate invoice warning or error.
5. Vendor Master Setting
Q5. How do you enable duplicate invoice check in Vendor Master?
Answer
In vendor master data:
Payment Data tab
Activate the field:
Check Flag for Double Invoices or Credit Memos
Field: LFB1-REPRF
This ensures SAP checks for duplicate invoices when posting.
Transaction codes:
FK01 / FK02
XK01 / XK02
6. Mandatory Reference Number
Q6. Why should the Reference Document Number be mandatory?
Answer
The Reference Document Number (XBLNR) usually stores the vendor invoice number.
If this field is mandatory:
Example:
Invoice Number: INV-123
If the same invoice number is entered again, SAP can detect the duplicate.
Configuration:
Transaction: OBA7
Define Document Types
Set Reference number field as mandatory.
7. Message Control
Q7. How do you stop duplicate invoices completely?
Answer
SAP can show duplicate messages as:
Information
Warning
Error
To prevent posting, set the message as Error.
Configuration:
Transaction: OBA5
Message example:
Check whether document has already been entered
If configured as Error, the system blocks the posting.
8. Logistics Invoice Verification (MIRO)
Q8. What fields are checked for duplicate invoices in MIRO?
For Logistics Invoice Verification, SAP checks these fields:
Company Code
Vendor
Currency
Gross Invoice Amount
Reference Document Number
Invoice Date
If these match an existing invoice, the system identifies it as a duplicate.
9. Configuration for Duplicate Check in Logistics
Q9. How can you control which fields are checked?
Configuration:
Transaction: OMRDC
Set Check for Duplicate Invoices
Fields that can be optionally ignored:
Company Code
Reference Number
Invoice Date
This provides flexibility for different business processes.
10. FI Invoice Duplicate Check
Q10. What fields are checked for duplicate invoices in FI posting (FB60)?
Two scenarios exist.
Case 1 – Reference number NOT entered
SAP checks:
Company Code
Vendor
Currency
Invoice Date
Invoice Amount
Case 2 – Reference number entered
SAP checks:
Company Code
Vendor
Currency
Invoice Date
Reference Document Number
The reference number becomes the key duplicate identifier.
11. Practical Example
Q11. How does SAP block duplicate invoice posting?
Example:
First invoice posted:
Company Code: 0001
Vendor: TESTVENDOR
Currency: EUR
Invoice Date: 19.12.2012
Reference Number: DUPL1
Document created:
1900000005
Second invoice attempt with same data:
Company Code: 0001
Vendor: TESTVENDOR
Currency: EUR
Invoice Date: 19.12.2012
Reference Number: DUPL1
SAP displays error:
Check whether document has already been entered
Document 1900000005
Posting is blocked.
12. Best Practice for AP Process
Q12. What best practices reduce duplicate invoices?
1️⃣ Use PO-based invoices whenever possible
2️⃣ Implement three-way matching
PO
GR
Invoice
3️⃣ Separate roles:
Invoice Entry
Invoice Approval
Payment Processing
4️⃣ Run duplicate payment detection reports
These steps strengthen the AP control framework.
Interview Tip (Important)
If an interviewer asks:
“How do you prevent duplicate vendor invoices in SAP?”
A strong answer structure is:
1️⃣ Vendor master duplicate check indicator
2️⃣ Mandatory invoice reference number
3️⃣ Message control configuration
4️⃣ Logistics duplicate check settings (OMRDC)
5️⃣ Three-way matching in procurement
This shows both configuration knowledge and process understanding.
If you want, I can also show you a real SAP interview scenario related to duplicate invoices that many candidates fail.
It involves MIRO vs FB60 duplicate invoice detection, which is a common trick question.
Comments
Post a Comment