FI Report Custom development ALV report

Intercompany Open Items Reconciliation Report

Short answer: A custom ALV report that matches receivable and payable open items between group companies by trading partner and reference number. Before the month-end consolidation it shows items that sit as a receivable in one company but have no payable in the partner company, or that differ in amount or currency.

Estimated effort
L · 5–8 working days
System
ECC and S/4HANA
Tables
5
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

FBL5N and FBL1N list each company code and account type separately; finding the partner's posting means matching two lists by hand in Excel. F.13 clears automatically within a company code and does not report unmatched items across company codes. Missing or different reciprocal postings are usually found through spreadsheet matching before consolidation.

Who uses it? Group accounting and consolidation teams, accounting teams that do intercompany billing and financial controllers.

Closest standard alternatives

  • FBL5N Customer Line Items. Lists intercompany customer items in one company code; does not match them with the partner company.
  • FBL1N Vendor Line Item Display. Lists the vendor items in the partner company separately; matching is done by hand.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
BSIDCustomer Open ItemsIntercompany customer open items (receivable side)—ECC + S/4
BSIKVendor Open ItemsVendor open items in the partner company (payable side)BSIK-BUKRS = ortak şirket kodu AND BSIK-XBLNR = BSID-XBLNRECC + S/4
KNA1Customer Master (General Section)Customer name and trading partnerKNA1-KUNNR = BSID-KUNNRECC + S/4
LFA1Vendor Master (General Section)Vendor name and trading partnerLFA1-LIFNR = BSIK-LIFNRECC + S/4
T001Company CodesCompany code to company (RCOMP) mapping and currencyT001-BUKRS = BSID-BUKRSECC + S/4

S/4HANA notes

  • BSID → I_OperationalAcctgDocItem: In S/4HANA BSID is no longer filled as a separate index table; reads work through a compatibility view of the same name. For new developments the I_OperationalAcctgDocItem CDS view is recommended.
  • 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.

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_BUKRSCompany codeRange / multipleBSID-BUKRSYes1000
S_VBUNDTrading partnerRange / multipleBSID-VBUNDNoGRP02
P_KEYDTKey dateSingle valueSY-DATUMYes31.10.2026
P_TOLAMTAmount difference toleranceSingle value—No10
P_MXBLNMatch by reference (XBLNR)Radio button—NoX
P_MZUONMatch by assignment (ZUONR)Radio button—No—
P_ONLYDFShow only differences and unmatched itemsCheckbox—No—

Output columns

#ColumnSource
1Company codeBSID-BUKRS
2Customer (partner)BSID-KUNNR
3Customer nameKNA1-NAME1
4Partner company codeCalculated Company code in T001 whose RCOMP = trading partner (BSID-VBUND or KNA1-VBUND)
5ReferenceBSID-XBLNR
6Receivable documentBSID-BELNR
7Receivable amountBSID-WRBTR
8Payable document (partner)BSIK-BELNR
9Payable amountBSIK-WRBTR
10Document currencyBSID-WAERS
11DifferenceCalculated Receivable amount − payable amount (at the key-date rate if currencies differ)
12StatusCalculated Matched, amount difference, currency difference or no reciprocal posting

Sample output

Company codeCustomer (partner)Customer namePartner company codeReferenceReceivable documentReceivable amountPayable document (partner)Payable amountDocument currencyDifferenceStatus
1000300010Doğa Lojistik A.Ş.20002026-04121800012501250,0005100007741250,000TRY0Matched
1000300010Doğa Lojistik A.Ş.20002026-0418180001264486,400510000780284,000TRY2,400Amount difference
1000300010Doğa Lojistik A.Ş.20002026-0425180001279037,8000TRY37,800No reciprocal posting
1000300022Ege Enerji Yatırım3000EXP-1107180001281112,000510000190412,000EUR0Matched
A view built with fictional sample data; not real system data.

How does the report work?

  1. For the selected company codes, the company (RCOMP) is read from T001.
  2. Receivable side: open items at the key date from BSID; the trading partner comes from BSID-VBUND, or from the customer’s KNA1-VBUND if empty.
  3. The partner company code is the company code in T001 whose RCOMP equals the trading partner.
  4. Payable side: vendor items in the partner company code are read from BSIK where the trading partner (BSIK-VBUND or LFA1-VBUND) is the reporting company.
  5. Items are matched by the chosen key (reference XBLNR or assignment ZUONR) in document currency. A difference above P_TOLAMT shows “Amount difference”; no counterpart shows “No reciprocal posting”. The opposite direction (our payables / partner’s receivables) is checked in the same run.
  6. If currencies differ, amounts are compared at the standard rate (rate type M) of the key date.

Performance notes

Read BSID and BSIK by company code and the set of trading partners; do the matching in memory with hashed tables. In groups with many companies, parallel background jobs per company pair can be used.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants
  • Double-click drill-down to the document FB03 opens from the document number on either side.
  • Export to Excel
  • Runs as a background job Can run in the month-end close calendar before consolidation.
  • Send the result by email The difference list can be sent to the accounting teams of the companies involved.

Authorization objects

  • F_BKPF_BUKAccounting document authorization for both company codes
  • F_KNA1_BUKCustomer master authorization by company code
  • F_LFA1_BUKVendor master authorization by company code

Frequently asked questions

What happens if the trading partner field is empty?

If the item has no trading partner, the one in the customer or vendor master is used. If both are empty the item is not treated as intercompany; this can be shown as missing master data in a separate warning list.

How are invoices in different currencies compared?

Document currencies are compared first. If the two sides posted in different currencies, amounts are converted at the standard key-date rate and the exchange difference is shown with its own status.

Does the report post the differences automatically?

No, the report only reads. The correction is posted in the relevant company with standard transactions; the detail list points directly to the document to correct.

Packages that include this solution

FI Package Custom

Month-End Close Control Pack

A pack that lists the five topics to clean up before the close with one company code and period selection: parked documents, unmatched bank items, …

5 components · v1.0

Related reports

FI Report Custom ALV report

Customer Receivables Aging Report

A custom ALV report that ages customer open items by net due date and shows down payments received and other special G/L items in the same list. …

BSID · BSAD · KNA1 · KNB1

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: Intercompany Open Items Reconciliation Report