FICO General Ledger Part 5: Financial Statement Versions and GL Troubleshooting

📌 KEY POINTS
✅ Financial statement versions (FSV) arrange GL accounts into balance sheet and P&L nodes.
✅ Every account must be assigned; unassigned accounts show up separately and distort statements.
✅ Debit/credit shift lets one account appear on different sides depending on its balance (e.g. bank overdraft).
✅ Balance carryforward (FAGLGVTR) moves balance sheet accounts and P&L result to retained earnings each year.
⚠️ A balance sheet that doesn't balance usually means a missing carryforward or unassigned accounts, not a posting error.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
This final GL part turns accounts into statements and covers common GL issues.

━━━━━━━━━━━━━━━━━━━━
▶ 1. FINANCIAL STATEMENT VERSIONS
An FSV is a hierarchy of nodes — assets, liabilities, equity, revenue, expenses — with GL accounts or ranges assigned. Different versions can serve statutory statements, management reports or group reporting. In S/4HANA, FSVs are also used by Fiori apps and analytics to present statements.

━━━━━━━━━━━━━━━━━━━━
▶ 2. COMPLETENESS CHECKS
New accounts are often created without assignment to the FSV. Statements then show an 'accounts not assigned' node, which is easy to miss. A periodic check of unassigned accounts, or a rule that account creation includes FSV assignment, keeps statements complete.

━━━━━━━━━━━━━━━━━━━━
▶ 3. DEBIT/CREDIT SHIFT
Some accounts belong on different sides depending on their balance, for example a bank account that can be in overdraft. The FSV can show such an account under assets when debit and under liabilities when credit. Without it, an overdraft reduces assets instead of appearing as a liability.

━━━━━━━━━━━━━━━━━━━━
▶ 4. BALANCE CARRYFORWARD
At year end, FAGLGVTR carries forward balance sheet account balances and transfers P&L balances to retained earnings according to the retained earnings account assignment. If it is not run, or new postings are made to the old year after it ran without rerunning, opening balances are wrong and the balance sheet does not balance.

━━━━━━━━━━━━━━━━━━━━
▶ 5. COMMON TROUBLESHOOTING
Unbalanced statements: check carryforward and unassigned accounts. Missing amounts: check ledgers and currencies selected in the report. Posting errors: read the message — often missing cost object due to field status, closed period, or missing tax code — and fix the setting or the entry, not the symptom.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Display your company's FSV and find the unassigned-accounts node.
2. Assign a missing account and rerun the balance sheet.
3. Check debit/credit shift for bank accounts.
4. Run balance carryforward in test and compare opening balances.

✅ CHECKPOINT: statements are complete, balance, and opening balances match prior closing.

The first balance sheet of a new year did not balance. Audit adjustments had been posted to the previous year after balance carryforward had run, and carryforward was not repeated. Rerunning FAGLGVTR updated opening balances, and the close checklist now reruns carryforward after any prior-year posting.

• New accounts not assigned to the FSV.
• No debit/credit shift for overdraft accounts.
• Prior-year postings after carryforward without rerun.
• Fixing report symptoms instead of causes.

• FSV assignment part of account creation.
• Periodic unassigned-account check.
• Rerun carryforward after prior-year postings.
• Structured troubleshooting by message.

Interviewers ask what a financial statement version is, why a balance sheet may not balance after year end, and what balance carryforward does in S/4HANA.