General Ledger Consistency and Trading Partner / Transaction Type Check Report
Short answer: 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.
- Estimated effort
- M · 8–12 working days
- System
- ECC and S/4HANA
- Tables
- 11
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? General ledger and closing teams, the consolidation team, finance managers and internal audit.
Closest standard alternatives
- FAGLF03 General Ledger Reconciliation. Compares new G/L totals with line items; does not check trading partner or transaction type.
- FAGLL03 G/L Account Line Items (New). Can list line items with trading partner and transaction type; does not flag missing values by rule.
- FS10N Balance Display. Shows the account balance; performs no consistency check.
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| ACDOCAUniversal Journal Entry Line Items | Universal Journal items: account, trading partner, transaction type, amount (S/4HANA driving table) | — | S/4HANA only |
| BKPFAccounting Document Header | Document header: document type, posting date, user | BKPF-BUKRS = ACDOCA-RBUKRS AND BKPF-BELNR = ACDOCA-BELNR AND BKPF-GJAHR = ACDOCA-GJAHR | ECC + S/4 |
| BSEGAccounting Document Segment | Document items, trading partner and transaction type (ECC) | BSEG-BUKRS = BKPF-BUKRS AND BSEG-BELNR = BKPF-BELNR AND BSEG-GJAHR = BKPF-GJAHR | ECC only |
| FAGLFLEXTNew General Ledger: Totals | New G/L period totals (ECC) | FAGLFLEXT-RBUKRS = BSEG-BUKRS AND FAGLFLEXT-RACCT = BSEG-HKONT | ECC only |
| GLT0G/L Account Transaction Figures | Classic G/L totals (ECC, when new G/L is not active) | GLT0-BUKRS = BSEG-BUKRS AND GLT0-RACCT = BSEG-HKONT | ECC only |
| BSISG/L Account Open Items (Secondary Index) | G/L open item index | BSIS-BUKRS = BKPF-BUKRS AND BSIS-BELNR = BKPF-BELNR AND BSIS-GJAHR = BKPF-GJAHR | ECC + S/4 |
| BSASG/L Account Cleared Items (Secondary Index) | G/L cleared item index | BSAS-BUKRS = BKPF-BUKRS AND BSAS-BELNR = BKPF-BELNR AND BSAS-GJAHR = BKPF-GJAHR | ECC + S/4 |
| SKB1G/L Account Master (Company Code) | Open item management and reconciliation account flag of the account | SKB1-BUKRS = ACDOCA-RBUKRS AND SKB1-SAKNR = ACDOCA-RACCT | ECC + S/4 |
| KNA1Customer Master (General Section) | Customer's trading partner in master data | KNA1-KUNNR = ACDOCA-KUNNR | ECC + S/4 |
| LFA1Vendor Master (General Section) | Supplier's trading partner in master data | LFA1-LIFNR = ACDOCA-LIFNR | ECC + S/4 |
| T001Company Codes | Company code, currency and chart of accounts | T001-BUKRS = ACDOCA-RBUKRS | ECC + S/4 |
S/4HANA notes
- FAGLFLEXT → ACDOCA: In S/4HANA totals tables are no longer updated separately; FAGLFLEXT is read as a compatibility view that aggregates ACDOCA line items.
- GLT0 → ACDOCA: In S/4HANA GLT0 is not updated; reads go through a compatibility view that aggregates ACDOCA line items.
- BSIS → ACDOCA: In S/4HANA BSIS is no longer filled as a separate index table; it is read through a compatibility view of the same name. New developments should use ACDOCA or the related CDS views.
- BSAS → ACDOCA: In S/4HANA BSAS is not filled as a separate table; it is read through a compatibility view of the same name. New developments should prefer ACDOCA or the related CDS views.
BAPIs and functions used
- BAPI_GL_GETGLACCPERIODBALANCESGet G/L Account Period Balances. Reads the period balances of a G/L account
- SO_NEW_DOCUMENT_ATT_SEND_API1SAPoffice: Send New Document with Attachments. Sends the summary to the people responsible for the close
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | ACDOCA-RBUKRS | Yes | 1000 |
| P_GJAHR | Fiscal year | Single value | ACDOCA-GJAHR | Yes | 2026 |
| S_POPER | Period | Range / multiple | ACDOCA-POPER | Yes | 010 – 011 |
| S_RACCT | G/L account | Range / multiple | ACDOCA-RACCT | No | 100000 – 899999 |
| P_CHK1 | Balance vs. line item check | Checkbox | — | No | X |
| P_CHK2 | Line item vs. open item check | Checkbox | — | No | X |
| P_CHK3 | Trading partner check | Checkbox | — | No | X |
| P_CHK4 | Transaction type check | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Check | Calculated Balance vs. item, item vs. open item, trading partner or transaction type |
| 2 | Company code | ACDOCA-RBUKRS |
| 3 | G/L account | ACDOCA-RACCT |
| 4 | Period | ACDOCA-POPER |
| 5 | Document | ACDOCA-BELNR |
| 6 | Amount (LC) | ACDOCA-HSL |
| 7 | Trading partner | ACDOCA-RASSC |
| 8 | Expected partner | Calculated VBUND from customer/supplier master data |
| 9 | Transaction type | ACDOCA-RMVCT |
| 10 | Difference | Calculated Difference between totals and item/index totals in the balance checks |
| 11 | Suggestion | Calculated Suggested correction |
Sample output
| Check | Company code | G/L account | Period | Document | Amount (LC) | Trading partner | Expected partner | Transaction type | Difference | Suggestion |
|---|---|---|---|---|---|---|---|---|---|---|
| Trading partner | 1000 | 120500 | 010 | 1400002345 | 185,000 | 2000 | Add trading partner 2000 to the document | |||
| Transaction type | 1000 | 500000 | 010 | 1700000112 | -2,500,000 | Enter the transaction type for the capital increase | ||||
| Item vs. open item | 1000 | 320900 | 011 | 5100004417 | 12,450 | 12,450 | Open item index missing; check with support | |||
| Trading partner | 2000 | 320100 | 011 | 5100000981 | -76,300 | 3000 | 1000 | Trading partner contradicts master data | ||
| Balance vs. item | 3000 | 153000 | 011 | 0 | 0 | No difference |
How does the report work?
- 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.
- 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.
- 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.
- 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.
- 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.
- Optionally the result is emailed as a summary to the people responsible for the close.
Performance notes
Restrict ACDOCA by company code, fiscal year and period; in the trading partner and transaction type checks read only the accounts flagged during installation. Compare balances on account and period totals, not at line item level. For large company codes run the report in the background overnight.
Features
- ALV list (sort, filter, subtotals)
- Double-click drill-down to the document Drill down from the document number to FB03.
- Runs as a background job Runs as an overnight job before the closing calendar.
- Send the result by email
- Export to Excel
Authorization objects
- F_BKPF_BUKDisplay of accounting documents by company code
- F_SKA1_BUKDisplay 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.
Related reports
Mass G/L Journal Entry Upload from Excel
A custom program that posts multi-line G/L documents (accruals, reclassifications, allocation entries) in bulk from Excel or CSV rows. It checks every …
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 …
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.