FI Report Custom development ALV report

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.

TableRoleJoinSystem
BSIPIndex for Vendor Duplicate Document CheckVendor invoice duplicate check index (driving table)—ECC + S/4
BKPFAccounting Document HeaderDocument header: entering user, reversal dataBKPF-BUKRS = BSIP-BUKRS AND BKPF-BELNR = BSIP-BELNR AND BKPF-GJAHR = BSIP-GJAHRECC + S/4
LFA1Vendor Master (General Section)Vendor name and tax numberLFA1-LIFNR = BSIP-LIFNRECC + S/4
BSIKVendor Open ItemsWhether the invoice is still openBSIK-BUKRS = BSIP-BUKRS AND BSIK-BELNR = BSIP-BELNR AND BSIK-GJAHR = BSIP-GJAHRECC + S/4
BSAKVendor Cleared ItemsCleared (paid) invoices and clearing documentBSAK-BUKRS = BSIP-BUKRS AND BSAK-BELNR = BSIP-BELNR AND BSAK-GJAHR = BSIP-GJAHRECC + 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

ParameterDescriptionTypeReference fieldRequiredExample
S_BUKRSCompany codeRange / multipleBSIP-BUKRSYes1000
S_LIFNRVendorRange / multipleBSIP-LIFNRNo100245
S_BLDATDocument dateRange / multipleBSIP-BLDATYes01.01.2026 – 30.11.2026
P_DAYSDocument date tolerance (days)Single value—No5
P_TOLAmount tolerance (%)Single value—No1
P_XVENDAlso compare different vendors with the same tax numberCheckbox—NoX
P_NOREVExclude reversed documentsCheckbox—NoX

Output columns

#ColumnSource
1GroupCalculated Sequence number grouping possible duplicate invoices
2Company codeBSIP-BUKRS
3VendorBSIP-LIFNR
4Vendor nameLFA1-NAME1
5Tax numberLFA1-STCD2
6ReferenceBSIP-XBLNR
7Document dateBSIP-BLDAT
8AmountBSIP-WRBTR
9CurrencyBSIP-WAERS
10DocumentBSIP-BELNR
11Entered byBKPF-USNAM
12Payment statusCalculated Open when found in BSIK, Paid when found in BSAK (with BSAK-AUGBL)
13Match ruleCalculated Rule that formed the group: reference + amount, amount + date or tax number

Sample output

GroupCompany codeVendorVendor nameTax numberReferenceDocument dateAmountCurrencyDocumentEntered byPayment statusMatch rule
11000100245Atlas Ambalaj1234567890AA2026-00041810/02/202646,200TRY5100004120AYILMAZPaidReference + amount
11000100245Atlas Ambalaj1234567890AA2026 41810/02/202646,200TRY5100004388BKAYAOpenReference + amount
21000100387Delta Metal9876543210DM-778109/14/2026128,400TRY5100003955AYILMAZPaidTax number
21000100911Delta Metal Sanayi9876543210DM778109/15/2026128,400TRY5100004011CDEMIROpenTax number
A view built with fictional sample data; not real system data.

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.

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

BASIS Package Custom

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, …

6 components · v1.0

Related reports

FI Report Custom ALV report

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 …

REGUH · REGUP · BSIK · LFA1

FI Report Custom ALV report

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 …

BSIK · LFA1 · LFB1 · T001

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.

Related report: Duplicate Vendor Invoice Check Report