# Duplicate Vendor Invoice Check Report

> 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.

- Type: Report, Custom development, ALV report
- Module: FI
- Estimated effort: M (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/duplicate-vendor-invoice-check-report/


## 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.

### Closest standard alternatives

- FBL1N: Can sort vendor items by reference; does not group similar references or compare across vendors.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| BSIP | Vendor invoice duplicate check index (driving table) | Read | - | ECC + S/4 |
| BKPF | Document header: entering user, reversal data | Read | BKPF-BUKRS = BSIP-BUKRS AND BKPF-BELNR = BSIP-BELNR AND BKPF-GJAHR = BSIP-GJAHR | ECC + S/4 |
| LFA1 | Vendor name and tax number | Read | LFA1-LIFNR = BSIP-LIFNR | ECC + S/4 |
| BSIK | Whether the invoice is still open | Read | BSIK-BUKRS = BSIP-BUKRS AND BSIK-BELNR = BSIP-BELNR AND BSIK-GJAHR = BSIP-GJAHR | ECC + S/4 |
| BSAK | Cleared (paid) invoices and clearing document | Read | BSAK-BUKRS = BSIP-BUKRS AND BSAK-BELNR = BSIP-BELNR AND BSAK-GJAHR = BSIP-GJAHR | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | BSIP-BUKRS | Yes |
| S_LIFNR | Vendor | Range / multiple | BSIP-LIFNR | No |
| S_BLDAT | Document date | Range / multiple | BSIP-BLDAT | Yes |
| P_DAYS | Document date tolerance (days) | Single value | - | No |
| P_TOL | Amount tolerance (%) | Single value | - | No |
| P_XVEND | Also compare different vendors with the same tax number | Checkbox | - | No |
| P_NOREV | Exclude reversed documents | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Group | Calculated: Sequence number grouping possible duplicate invoices |
| Company code | BSIP-BUKRS |
| Vendor | BSIP-LIFNR |
| Vendor name | LFA1-NAME1 |
| Tax number | LFA1-STCD2 |
| Reference | BSIP-XBLNR |
| Document date | BSIP-BLDAT |
| Amount | BSIP-WRBTR |
| Currency | BSIP-WAERS |
| Document | BSIP-BELNR |
| Entered by | BKPF-USNAM |
| Payment status | Calculated: Open when found in BSIK, Paid when found in BSAK (with BSAK-AUGBL) |
| Match rule | Calculated: Rule that formed the group: reference + amount, amount + date or tax number |

## How does the report work?

1. The vendor invoice index BSIP is read for the selected company codes and document date range (vendor, currency, document date, reference, amount).
2. The reference is normalized: converted to upper case, with spaces, dashes, slashes and leading zeros removed.
3. 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.
4. Reversed documents (BKPF-STBLG filled) are removed by selection; the user who entered the document is added from BKPF.
5. Whether each document is open or cleared is found from BSIK and BSAK; duplicates that have already been paid are flagged separately.

## Authorization objects

- F_BKPF_BUK: Accounting document authorization by company code
- F_LFA1_BUK: Vendor 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=fi-duplicate-vendor-invoice-check
