# Intercompany Open Items Reconciliation Report

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

- Type: Report, Custom development, ALV report
- Module: FI
- Estimated effort: L (5–8 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/intercompany-open-items-reconciliation-report/


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

### Closest standard alternatives

- FBL5N: Lists intercompany customer items in one company code; does not match them with the partner company.
- FBL1N: Lists the vendor items in the partner company separately; matching is done by hand.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| BSID | Intercompany customer open items (receivable side) | Read | - | ECC + S/4 |
| BSIK | Vendor open items in the partner company (payable side) | Read | BSIK-BUKRS = ortak şirket kodu AND BSIK-XBLNR = BSID-XBLNR | ECC + S/4 |
| KNA1 | Customer name and trading partner | Read | KNA1-KUNNR = BSID-KUNNR | ECC + S/4 |
| LFA1 | Vendor name and trading partner | Read | LFA1-LIFNR = BSIK-LIFNR | ECC + S/4 |
| T001 | Company code to company (RCOMP) mapping and currency | Read | T001-BUKRS = BSID-BUKRS | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | BSID-BUKRS | Yes |
| S_VBUND | Trading partner | Range / multiple | BSID-VBUND | No |
| P_KEYDT | Key date | Single value | SY-DATUM | Yes |
| P_TOLAMT | Amount difference tolerance | Single value | - | No |
| P_MXBLN | Match by reference (XBLNR) | Radio button | - | No |
| P_MZUON | Match by assignment (ZUONR) | Radio button | - | No |
| P_ONLYDF | Show only differences and unmatched items | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Company code | BSID-BUKRS |
| Customer (partner) | BSID-KUNNR |
| Customer name | KNA1-NAME1 |
| Partner company code | Calculated: Company code in T001 whose RCOMP = trading partner (BSID-VBUND or KNA1-VBUND) |
| Reference | BSID-XBLNR |
| Receivable document | BSID-BELNR |
| Receivable amount | BSID-WRBTR |
| Payable document (partner) | BSIK-BELNR |
| Payable amount | BSIK-WRBTR |
| Document currency | BSID-WAERS |
| Difference | Calculated: Receivable amount − payable amount (at the key-date rate if currencies differ) |
| Status | Calculated: Matched, amount difference, currency difference or no reciprocal posting |

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

## Authorization objects

- F_BKPF_BUK: Accounting document authorization for both company codes
- F_KNA1_BUK: Customer master authorization by company code
- F_LFA1_BUK: Vendor 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=fi-intercompany-open-items-reconciliation
