# General Ledger Consistency and Trading Partner / Transaction Type Check Report

> A check report run before period-end close. It compares G/L account balances with the line items and the line items with the open item indexes; it lists postings on intercompany accounts with a missing trading partner and items on accounts that need a transaction type (fixed assets, equity) with a missing or wrong transaction type. Every item to correct before consolidation is shown with its document number.

- Type: Report, Custom development, ALV report
- Module: FI
- Estimated effort: M (8–12 working days)
- Last updated: 2026-11-19
- URL: https://nekuhub.com/en/reports/general-ledger-consistency-and-trading-partner-check-report/


## Why is the standard not enough?

The standard has separate tools for balance-to-item consistency: FINS_RECON_RC1 in S/4HANA, SAPF190 and RFINDEX in ECC, FAGLF03 and TFC_COMPARE_VZ in new G/L. They find technical inconsistencies but do not flag intercompany postings with an empty trading partner or equity and fixed asset postings with a missing transaction type. These errors usually surface in consolidation as matching differences and require corrections after the fact.

### Closest standard alternatives

- FAGLF03: Compares new G/L totals with line items; does not check trading partner or transaction type.
- FAGLL03: Can list line items with trading partner and transaction type; does not flag missing values by rule.
- FS10N: Shows the account balance; performs no consistency check.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| ACDOCA | Universal Journal items: account, trading partner, transaction type, amount (S/4HANA driving table) | Read | - | S/4HANA only |
| BKPF | Document header: document type, posting date, user | Read | BKPF-BUKRS = ACDOCA-RBUKRS AND BKPF-BELNR = ACDOCA-BELNR AND BKPF-GJAHR = ACDOCA-GJAHR | ECC + S/4 |
| BSEG | Document items, trading partner and transaction type (ECC) | Read | BSEG-BUKRS = BKPF-BUKRS AND BSEG-BELNR = BKPF-BELNR AND BSEG-GJAHR = BKPF-GJAHR | ECC only |
| FAGLFLEXT | New G/L period totals (ECC) | Read | FAGLFLEXT-RBUKRS = BSEG-BUKRS AND FAGLFLEXT-RACCT = BSEG-HKONT | ECC only |
| GLT0 | Classic G/L totals (ECC, when new G/L is not active) | Read | GLT0-BUKRS = BSEG-BUKRS AND GLT0-RACCT = BSEG-HKONT | ECC only |
| BSIS | G/L open item index | Read | BSIS-BUKRS = BKPF-BUKRS AND BSIS-BELNR = BKPF-BELNR AND BSIS-GJAHR = BKPF-GJAHR | ECC + S/4 |
| BSAS | G/L cleared item index | Read | BSAS-BUKRS = BKPF-BUKRS AND BSAS-BELNR = BKPF-BELNR AND BSAS-GJAHR = BKPF-GJAHR | ECC + S/4 |
| SKB1 | Open item management and reconciliation account flag of the account | Read | SKB1-BUKRS = ACDOCA-RBUKRS AND SKB1-SAKNR = ACDOCA-RACCT | ECC + S/4 |
| KNA1 | Customer's trading partner in master data | Read | KNA1-KUNNR = ACDOCA-KUNNR | ECC + S/4 |
| LFA1 | Supplier's trading partner in master data | Read | LFA1-LIFNR = ACDOCA-LIFNR | ECC + S/4 |
| T001 | Company code, currency and chart of accounts | Read | T001-BUKRS = ACDOCA-RBUKRS | ECC + S/4 |

## BAPIs and functions used

- BAPI_GL_GETGLACCPERIODBALANCES: Reads the period balances of a G/L account
- SO_NEW_DOCUMENT_ATT_SEND_API1: Sends the summary to the people responsible for the close

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | ACDOCA-RBUKRS | Yes |
| P_GJAHR | Fiscal year | Single value | ACDOCA-GJAHR | Yes |
| S_POPER | Period | Range / multiple | ACDOCA-POPER | Yes |
| S_RACCT | G/L account | Range / multiple | ACDOCA-RACCT | No |
| P_CHK1 | Balance vs. line item check | Checkbox | - | No |
| P_CHK2 | Line item vs. open item check | Checkbox | - | No |
| P_CHK3 | Trading partner check | Checkbox | - | No |
| P_CHK4 | Transaction type check | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Check | Calculated: Balance vs. item, item vs. open item, trading partner or transaction type |
| Company code | ACDOCA-RBUKRS |
| G/L account | ACDOCA-RACCT |
| Period | ACDOCA-POPER |
| Document | ACDOCA-BELNR |
| Amount (LC) | ACDOCA-HSL |
| Trading partner | ACDOCA-RASSC |
| Expected partner | Calculated: VBUND from customer/supplier master data |
| Transaction type | ACDOCA-RMVCT |
| Difference | Calculated: Difference between totals and item/index totals in the balance checks |
| Suggestion | Calculated: Suggested correction |

## How does the report work?

1. Check 1 – balance vs. line items: in S/4HANA, ACDOCA period totals per account and period are compared with the result of the G/L balance query (BAPI_GL_GETGLACCPERIODBALANCES). In ECC, FAGLFLEXT (or GLT0 in classic G/L) totals are compared with BSEG/BSIS/BSAS item totals.
2. Check 2 – line items vs. open items: on open-item-managed accounts (SKB1-XOPVW) the BSIS and BSAS index amounts are compared with the line item amounts; items missing from or surplus in the index are listed.
3. Check 3 – trading partner: on accounts flagged as intercompany during installation, or on postings to customers/suppliers that carry a trading partner in master data (KNA1/LFA1-VBUND), the item is flagged when ACDOCA-RASSC (BSEG-VBUND in ECC) is empty or contradicts the master data.
4. Check 4 – transaction type: on accounts that feed the equity and fixed asset movement schedules, the item is flagged when ACDOCA-RMVCT (BSEG-BEWAR in ECC) is empty or not in the list of transaction types allowed for the account. Transaction types are validated against T856 and intercompany companies against T880.
5. The result is grouped by check type; every line shows company code, account, document, amount and the suggested correction. Clicking the document number opens FB03.
6. Optionally the result is emailed as a summary to the people responsible for the close.

## Authorization objects

- F_BKPF_BUK: Display of accounting documents by company code
- F_SKA1_BUK: Display of G/L accounts by company code

## Frequently asked questions

### Does this report replace the standard consistency programs?

No. If a technical inconsistency is found, the standard programs (FINS_RECON_RC1 in S/4HANA, SAPF190 and RFINDEX in ECC) and, if needed, SAP support are used for the correction. The report brings their result together with the trading partner and transaction type checks in one list.

### How do we correct a posting with a missing trading partner?

It depends on the posting: for items not yet cleared, a document change or a reversal and new posting is made. For a lasting fix, the trading partner field should be filled in customer and supplier master data and made mandatory on intercompany accounts.

### How is it decided which accounts need a transaction type?

During installation a mapping table defines account ranges and the transaction types allowed for them (equity, fixed asset, provision accounts and so on). The report uses this table; the consolidation team can maintain the list itself.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=fi-gl-consistency-trading-partner-checks
