Duplicate Vendor Invoice Check Report
Short answer: A custom ALV report that compares posted vendor invoices by reference number, amount and document date and lists possible duplicates in groups. Invoices whose reference was typed differently (spaces, dashes, leading zeros) and invoices posted to different vendors with the same tax number are caught too, which reduces the risk of paying twice.
- Estimated effort
- M · 3–5 working days
- System
- ECC and S/4HANA
- Tables
- 5
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
The standard duplicate invoice check only warns at posting time and only when reference, amount and date match exactly; it misses an invoice whose reference was typed differently or posted to another vendor number, and it does not scan past postings in bulk. FBL1N can be sorted by reference, but it does not group similar references. Audits usually do this scan by downloading data into Excel.
Who uses it? Accounts payable teams, internal audit and finance managers who approve payments.
Closest standard alternatives
- FBL1N Vendor Line Item Display. Can sort vendor items by reference; does not group similar references or compare across vendors.
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| BSIPIndex for Vendor Duplicate Document Check | Vendor invoice duplicate check index (driving table) | — | ECC + S/4 |
| BKPFAccounting Document Header | Document header: entering user, reversal data | BKPF-BUKRS = BSIP-BUKRS AND BKPF-BELNR = BSIP-BELNR AND BKPF-GJAHR = BSIP-GJAHR | ECC + S/4 |
| LFA1Vendor Master (General Section) | Vendor name and tax number | LFA1-LIFNR = BSIP-LIFNR | ECC + S/4 |
| BSIKVendor Open Items | Whether the invoice is still open | BSIK-BUKRS = BSIP-BUKRS AND BSIK-BELNR = BSIP-BELNR AND BSIK-GJAHR = BSIP-GJAHR | ECC + S/4 |
| BSAKVendor Cleared Items | Cleared (paid) invoices and clearing document | BSAK-BUKRS = BSIP-BUKRS AND BSAK-BELNR = BSIP-BELNR AND BSAK-GJAHR = BSIP-GJAHR | ECC + S/4 |
S/4HANA notes
- BSIK: In S/4HANA BSIK is no longer filled as a separate index table; reads work through a compatibility view. For new developments the I_OperationalAcctgDocItem CDS view is recommended.
- BSAK → I_OperationalAcctgDocItem: In S/4HANA BSAK is not filled as a separate table; it is read through a compatibility view of the same name. For new developments the I_OperationalAcctgDocItem CDS view is recommended.
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | BSIP-BUKRS | Yes | 1000 |
| S_LIFNR | Vendor | Range / multiple | BSIP-LIFNR | No | 100245 |
| S_BLDAT | Document date | Range / multiple | BSIP-BLDAT | Yes | 01.01.2026 – 30.11.2026 |
| P_DAYS | Document date tolerance (days) | Single value | — | No | 5 |
| P_TOL | Amount tolerance (%) | Single value | — | No | 1 |
| P_XVEND | Also compare different vendors with the same tax number | Checkbox | — | No | X |
| P_NOREV | Exclude reversed documents | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Group | Calculated Sequence number grouping possible duplicate invoices |
| 2 | Company code | BSIP-BUKRS |
| 3 | Vendor | BSIP-LIFNR |
| 4 | Vendor name | LFA1-NAME1 |
| 5 | Tax number | LFA1-STCD2 |
| 6 | Reference | BSIP-XBLNR |
| 7 | Document date | BSIP-BLDAT |
| 8 | Amount | BSIP-WRBTR |
| 9 | Currency | BSIP-WAERS |
| 10 | Document | BSIP-BELNR |
| 11 | Entered by | BKPF-USNAM |
| 12 | Payment status | Calculated Open when found in BSIK, Paid when found in BSAK (with BSAK-AUGBL) |
| 13 | Match rule | Calculated Rule that formed the group: reference + amount, amount + date or tax number |
Sample output
| Group | Company code | Vendor | Vendor name | Tax number | Reference | Document date | Amount | Currency | Document | Entered by | Payment status | Match rule |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 1000 | 100245 | Atlas Ambalaj | 1234567890 | AA2026-000418 | 10/02/2026 | 46,200 | TRY | 5100004120 | AYILMAZ | Paid | Reference + amount |
| 1 | 1000 | 100245 | Atlas Ambalaj | 1234567890 | AA2026 418 | 10/02/2026 | 46,200 | TRY | 5100004388 | BKAYA | Open | Reference + amount |
| 2 | 1000 | 100387 | Delta Metal | 9876543210 | DM-7781 | 09/14/2026 | 128,400 | TRY | 5100003955 | AYILMAZ | Paid | Tax number |
| 2 | 1000 | 100911 | Delta Metal Sanayi | 9876543210 | DM7781 | 09/15/2026 | 128,400 | TRY | 5100004011 | CDEMIR | Open | Tax number |
How does the report work?
- The vendor invoice index BSIP is read for the selected company codes and document date range (vendor, currency, document date, reference, amount).
- The reference is normalized: converted to upper case, with spaces, dashes, slashes and leading zeros removed.
- Rules are applied in order: (a) same vendor + normalized reference + amount; (b) same vendor + amount + document dates within P_DAYS; (c) if selected, rule (a) across different vendors with the same tax number (LFA1-STCD2). The amount tolerance is applied with the P_TOL percentage.
- Reversed documents (BKPF-STBLG filled) are removed by selection; the user who entered the document is added from BKPF.
- Whether each document is open or cleared is found from BSIK and BSAK; duplicates that have already been paid are flagged separately.
Performance notes
BSIP is a narrow index table designed for the duplicate check, so even a one-year scan is fast. Grouping is done in memory by sorting on the normalized key. BSIP is still used on S/4HANA.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the document number opens FB03.
- Export to Excel
- Runs as a background job Can run automatically every day before the payment run and email open duplicates.
- Send the result by email
Authorization objects
- F_BKPF_BUKAccounting document authorization by company code
- F_LFA1_BUKVendor master authorization by company code
Frequently asked questions
Does the report block payment?
In the standard scope it only lists. If needed, an approval step that sets a payment block on open duplicates can be added; it runs with a separate authorization and a log.
Are invoices entered through MM invoice verification (MIRO) checked too?
Yes. MIRO invoices also create an accounting document, so they are written to BSIP and compared with the same rules.
How are false alarms reduced?
Date and amount tolerances are kept narrow, and groups that were reviewed and confirmed as not duplicate go to an exception list, so later runs no longer show them.
Packages that include this solution
SAP Access and Payment Risk Audit Pack
A six-component pack that brings together the controls asked most often in the yearly IT and finance audit: users with critical authorizations, …
Related reports
Payment Proposal Exceptions and Blocked Items Report
A custom report that collects, in one ALV list, the items in an automatic payment program (F110) proposal that will not be paid and the vendor items …
Vendor Open Items Aging Report
A custom ALV report that ages vendor open items by net due date and spreads the amounts into not-due, 0–30, 31–60, 61–90 and 90+ day buckets. The …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.