Subledger vs Reconciliation Account Balance Check Report (S/4HANA Migration Check)
Short answer: A custom ALV report that totals customer and vendor subledger balances by reconciliation account and compares them with the G/L account balance for the same period. Differing reconciliation accounts, reconciliation accounts changed later and inconsistencies before period close are found before the S/4HANA migration and before month-end.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 9
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
FAGLB03 shows the G/L balance, FD10N and FK10N the balance of one customer or vendor; none puts the subledger total next to the reconciliation account. Standard reconciliation programs produce a technical inconsistency list and no business-readable summary per account. Because consistent subledgers and G/L are a prerequisite for the S/4HANA conversion, projects usually run this check early with a custom report.
Who uses it? General ledger and month-end close teams, FI consultants on S/4HANA conversion projects and internal audit.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| KNC1Customer Master (Transaction Figures) | Customer period totals and balance carried forward (driving table) | — | ECC + S/4 |
| LFC1Vendor Master (Transaction Figures) | Vendor period totals and balance carried forward | LFC1-BUKRS = KNC1-BUKRS AND LFC1-GJAHR = KNC1-GJAHR | ECC + S/4 |
| KNC3Customer Master (Special G/L Transaction Figures) | Customer special G/L totals (subtracted) | KNC3-KUNNR = KNC1-KUNNR AND KNC3-BUKRS = KNC1-BUKRS AND KNC3-GJAHR = KNC1-GJAHR | ECC + S/4 |
| LFC3Vendor Master (Special G/L Transaction Figures) | Vendor special G/L totals (subtracted) | LFC3-LIFNR = LFC1-LIFNR AND LFC3-BUKRS = LFC1-BUKRS AND LFC3-GJAHR = LFC1-GJAHR | ECC + S/4 |
| KNB1Customer Master (Company Code) | Customer reconciliation account | KNB1-KUNNR = KNC1-KUNNR AND KNB1-BUKRS = KNC1-BUKRS | ECC + S/4 |
| LFB1Vendor Master (Company Code) | Vendor reconciliation account | LFB1-LIFNR = LFC1-LIFNR AND LFB1-BUKRS = LFC1-BUKRS | ECC + S/4 |
| FAGLFLEXTNew General Ledger: Totals | G/L balance of the reconciliation account (selected ledger) | FAGLFLEXT-RBUKRS = KNB1-BUKRS AND FAGLFLEXT-RACCT = KNB1-AKONT AND FAGLFLEXT-RYEAR = KNC1-GJAHR | ECC + S/4 |
| SKB1G/L Account Master (Company Code) | Reconciliation account type of the G/L account (customer/vendor) | SKB1-BUKRS = KNB1-BUKRS AND SKB1-SAKNR = KNB1-AKONT | ECC + S/4 |
| T001Company Codes | Company code currency | T001-BUKRS = KNC1-BUKRS | ECC + S/4 |
S/4HANA notes
- KNC1 → ACDOCA: In S/4HANA KNC1 is a view of the same name; totals are calculated from line items in ACDOCA.
- LFC1 → ACDOCA: In S/4HANA LFC1 is a view of the same name; totals are calculated from line items in ACDOCA.
- KNC3 → ACDOCA: In S/4HANA KNC3 is a view of the same name; totals are calculated from line items in ACDOCA.
- LFC3 → ACDOCA: In S/4HANA LFC3 is a view of the same name; totals are calculated from line items in ACDOCA.
- FAGLFLEXT → ACDOCA: In S/4HANA totals tables are no longer updated separately; FAGLFLEXT is read as a compatibility view that aggregates ACDOCA line items.
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | KNB1-BUKRS | Yes | 1000 |
| P_GJAHR | Fiscal year | Single value | KNC1-GJAHR | Yes | 2026 |
| P_PERIO | Balance up to period (inclusive) | Single value | — | Yes | 10 |
| S_AKONT | Reconciliation account | Range / multiple | KNB1-AKONT | No | 120000 |
| P_RLDNR | Ledger | Single value | FAGLFLEXT-RLDNR | No | 0L |
| R_CUST | Customers | Radio button | — | No | X |
| R_VEND | Vendors | Radio button | — | No | — |
| P_DIFF | Show only accounts with a difference | Checkbox | — | No | — |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Company code | KNB1-BUKRS |
| 2 | Subledger | Calculated Customer or Vendor by selection |
| 3 | Reconciliation account | KNB1-AKONT |
| 4 | Account type | SKB1-MITKZ |
| 5 | Fiscal year | KNC1-GJAHR |
| 6 | Number of accounts | Calculated Number of customers or vendors assigned to this reconciliation account |
| 7 | Subledger balance | Calculated KNC1/LFC1: UMSAV + period debits − period credits − KNC3/LFC3 special G/L totals |
| 8 | G/L balance | Calculated FAGLFLEXT-HSLVT + HSL01…HSLnn up to the selected period |
| 9 | Difference | Calculated Subledger balance − G/L balance |
| 10 | Accounts with changed reconciliation account | Calculated Number of accounts with a KNB1-AKONT/LFB1-AKONT change during the year (from change documents) |
| 11 | Currency | T001-WAERS |
| 12 | Status | Calculated Consistent when the difference is zero, otherwise Difference |
Sample output
| Company code | Subledger | Reconciliation account | Account type | Fiscal year | Number of accounts | Subledger balance | G/L balance | Difference | Accounts with changed reconciliation account | Currency | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1000 | Customer | 120000 | D | 2026 | 412 | 48,250,300 | 48,250,300 | 0 | 0 | TRY | Consistent |
| 1000 | Customer | 120100 | D | 2026 | 37 | 9,120,000 | 8,985,400 | 134,600 | 2 | TRY | Difference |
| 2000 | Customer | 120000 | D | 2026 | 156 | 15,402,750 | 15,402,750 | 0 | 0 | TRY | Consistent |
| 1000 | Customer | 121000 | D | 2026 | 9 | 1,250,000 | 1,310,000 | -60,000 | 1 | TRY | Difference |
How does the report work?
- For the selected company code and fiscal year, customer period totals are read from KNC1 and vendor period totals from LFC1; balance = balance carried forward (UMSAV) + debit totals − credit totals up to the selected period.
- Special G/L transactions are read from KNC3 and LFC3 and subtracted, because they are posted to the special G/L account rather than the reconciliation account.
- Each customer and vendor is grouped to its reconciliation account through KNB1-AKONT and LFB1-AKONT.
- The G/L balance for the same account and period is read from FAGLFLEXT (selected ledger, carry-forward HSLVT + period amounts); the reconciliation account type is confirmed through SKB1-MITKZ.
- Difference = subledger balance − G/L balance. Where there is a difference, accounts whose reconciliation account changed during the year are flagged from the change documents, which makes the cause easier to find.
Performance notes
Totals tables are far smaller than line-item tables, so the report runs in seconds. Line-item detail is read only on request for an account with a difference. On S/4HANA, G/L and subledger come from the same ACDOCA rows; the report can also be built on ACDOCA for post-migration validation.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking a row with a difference lists the customer or vendor balances on that reconciliation account.
- Export to Excel
- Runs as a background job Can run automatically before every month-end close.
Authorization objects
- F_BKPF_BUKAccounting data authorization by company code
- F_KNA1_BUKCustomer balance authorization by company code
- F_LFA1_BUKVendor balance authorization by company code
Frequently asked questions
How does a difference arise?
The most common cause is changing the reconciliation account of a customer or vendor that already has a balance: the old items stay on the old account, while the subledger is grouped to the new one. The report flags these accounts separately.
Does it work on systems with the classic general ledger?
Yes. If the new general ledger is not active, the G/L balance is read from GLT0 instead of FAGLFLEXT; this is set during installation.
When should it run during an S/4HANA migration?
Run it first at the start of the conversion project, then before every trial conversion and right before the final conversion, so differences are fixed well before the cut-over week.
Packages that include this solution
S/4HANA Conversion Readiness Pack
A five-component pack that finds the master data and finance inconsistencies to clean up before a system conversion from ECC to S/4HANA: business …
Currency Valuation and VAT Reconciliation Pack
A four-component pack that brings period-end valuation and tax checks together: daily automatic import of central bank exchange rates, an exchange …
Related reports
Cost Element vs G/L Account Consistency Check (S/4HANA Conversion Readiness)
A custom ALV report that compares the cost elements in an ECC system with the G/L accounts in the chart of accounts and lists inconsistencies that …
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.