# Subledger vs Reconciliation Account Balance Check Report (S/4HANA Migration Check)

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

- Type: Report, Custom development, ALV report
- Module: FI
- Estimated effort: M (4–6 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/subledger-reconciliation-account-balance-check-report/


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

### Closest standard alternatives

- FAGLB03: Shows the G/L balance; does not compare it with the subledger total.
- FD10N: Shows one customer's balance; does not total by reconciliation account.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| KNC1 | Customer period totals and balance carried forward (driving table) | Read | - | ECC + S/4 |
| LFC1 | Vendor period totals and balance carried forward | Read | LFC1-BUKRS = KNC1-BUKRS AND LFC1-GJAHR = KNC1-GJAHR | ECC + S/4 |
| KNC3 | Customer special G/L totals (subtracted) | Read | KNC3-KUNNR = KNC1-KUNNR AND KNC3-BUKRS = KNC1-BUKRS AND KNC3-GJAHR = KNC1-GJAHR | ECC + S/4 |
| LFC3 | Vendor special G/L totals (subtracted) | Read | LFC3-LIFNR = LFC1-LIFNR AND LFC3-BUKRS = LFC1-BUKRS AND LFC3-GJAHR = LFC1-GJAHR | ECC + S/4 |
| KNB1 | Customer reconciliation account | Read | KNB1-KUNNR = KNC1-KUNNR AND KNB1-BUKRS = KNC1-BUKRS | ECC + S/4 |
| LFB1 | Vendor reconciliation account | Read | LFB1-LIFNR = LFC1-LIFNR AND LFB1-BUKRS = LFC1-BUKRS | ECC + S/4 |
| FAGLFLEXT | G/L balance of the reconciliation account (selected ledger) | Read | FAGLFLEXT-RBUKRS = KNB1-BUKRS AND FAGLFLEXT-RACCT = KNB1-AKONT AND FAGLFLEXT-RYEAR = KNC1-GJAHR | ECC + S/4 |
| SKB1 | Reconciliation account type of the G/L account (customer/vendor) | Read | SKB1-BUKRS = KNB1-BUKRS AND SKB1-SAKNR = KNB1-AKONT | ECC + S/4 |
| T001 | Company code currency | Read | T001-BUKRS = KNC1-BUKRS | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | KNB1-BUKRS | Yes |
| P_GJAHR | Fiscal year | Single value | KNC1-GJAHR | Yes |
| P_PERIO | Balance up to period (inclusive) | Single value | - | Yes |
| S_AKONT | Reconciliation account | Range / multiple | KNB1-AKONT | No |
| P_RLDNR | Ledger | Single value | FAGLFLEXT-RLDNR | No |
| R_CUST | Customers | Radio button | - | No |
| R_VEND | Vendors | Radio button | - | No |
| P_DIFF | Show only accounts with a difference | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Company code | KNB1-BUKRS |
| Subledger | Calculated: Customer or Vendor by selection |
| Reconciliation account | KNB1-AKONT |
| Account type | SKB1-MITKZ |
| Fiscal year | KNC1-GJAHR |
| Number of accounts | Calculated: Number of customers or vendors assigned to this reconciliation account |
| Subledger balance | Calculated: KNC1/LFC1: UMSAV + period debits − period credits − KNC3/LFC3 special G/L totals |
| G/L balance | Calculated: FAGLFLEXT-HSLVT + HSL01…HSLnn up to the selected period |
| Difference | Calculated: Subledger balance − G/L balance |
| Accounts with changed reconciliation account | Calculated: Number of accounts with a KNB1-AKONT/LFB1-AKONT change during the year (from change documents) |
| Currency | T001-WAERS |
| Status | Calculated: Consistent when the difference is zero, otherwise Difference |

## How does the report work?

1. 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.
2. 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.
3. Each customer and vendor is grouped to its reconciliation account through KNB1-AKONT and LFB1-AKONT.
4. 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.
5. 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.

## Authorization objects

- F_BKPF_BUK: Accounting data authorization by company code
- F_KNA1_BUK: Customer balance authorization by company code
- F_LFA1_BUK: Vendor 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=fi-subledger-reconciliation-account-check
