NetSuite has a trial balance and a balance sheet, but no statutory German structure. The Fourangle balance sheet produces the complete assets and liabilities sides under § 266 HGB for corporations — directly from your posting periods, with a prior-year comparison and an audit-ready export.
The balances are right, the structure is not. German statutory accounts require specific positions in a specific order — and a result for the year that sits in equity without anybody calculating it there.
NetSuite groups by account type. Fixed assets, current assets, provisions and the equity positions only exist through a mapping somebody has to create.
Without a closing entry the net income does not appear in the balance sheet — and the totals drift apart. In Excel it then gets added by hand, every year again.
In home-grown reports an unmapped account simply drops out. That the total no longer matches the books shows up only when somebody recalculates.
German GAAP expects the prior year alongside. Pulling it from an older file means comparing two states that do not belong together.
HGB and IFRS side by side need the same report per book. Two tools mean two mappings — and eventually two results.
A position without a traceable account basis creates questions. And questions during the close cost more time than the report itself.
Accounts are pulled onto the statutory positions through the number ranges of SKR03 or SKR04; where no chart of accounts is assigned, the NetSuite account type applies as a fallback. If a position should differ, you override it on the account itself — once set, the override wins.
The complete assets and liabilities sides under § 266 HGB for large and medium-sized entities — as the full statutory layout or as a lean structure, switchable per deployment.
The reporting date is your posting period — month, quarter or fiscal year, with no calendar acrobatics on the side.
A fit for multi-subsidiary and multi-book structures: HGB and IFRS are reported separately, never mixed.
As soon as prior-year figures exist they sit alongside — from the same report, calculated in the same moment.
Read on screen, keep calculating in Excel, hand the PDF to auditors or your tax firm — reliable even with large data volumes.
No export, no intermediate state: the balance sheet is built from your ledger the moment you open it.
SuiteBundle 602256 is installed into your account like any other bundle. The mapping is derived automatically from the chart of accounts or the account type.
Accounts that belong elsewhere get their position on the account itself. Whatever stays open is shown in the report.
Pick period, subsidiary and accounting book, open the balance sheet, read it as HTML or pass it on as Excel or PDF.
Complete assets and liabilities sides for corporations — full or lean, switchable per deployment.
Via SKR03 or SKR04, with the NetSuite account type as fallback — no external mapping tables.
Assign individual accounts differently; the override wins over the automatic mapping.
Derived through double-entry bookkeeping and entered automatically as net income or net loss for the year.
By posting period, for a month, a quarter or a fiscal year.
Per entity and per accounting book — a fit for group structures.
Its own column as soon as prior-year figures are available.
Straight from NetSuite, reliable even with large data volumes.
Unassigned balances are shown instead of disappearing quietly.
The balance sheet is the sibling of the income statement under § 275 (3) HGB: same logic, same mapping, same data — the result for the year is identical on both sides. Together with the trial balance and the management report, the German reporting set is complete inside NetSuite.
The balance sheet is made for CFOs, accountants, controllers and tax advisors in companies that book in NetSuite and prepare statutory accounts for their German entity — particularly in groups whose NetSuite setup is geared towards US GAAP.
Native SuiteScript inside the account — the report reads the ledger directly.
SuiteBundle 602256 — installation and updates through NetSuite’s bundle mechanism.
SKR03 and SKR04 by number range, NetSuite account type as fallback, override per account.
Posting period, subsidiary and accounting book.
HTML on screen, Excel (XLSX) and PDF to pass on.
Everything stays in the account — no external service, no copy.
From the chart of accounts: SKR03 and SKR04 have fixed number ranges. Where none is assigned, the NetSuite account type applies as a fallback. Both can be overridden per account.
No. The result is derived through double-entry bookkeeping and entered automatically in position P.A.V (net income / net loss for the year) — without a closing entry in NetSuite.
They do not disappear. Unassigned balances are shown, so the total matches what was actually posted — and you see immediately where a mapping is missing.
Both. The report runs either with the full statutory layout under § 266 HGB or with a lean structure — switched by a setting on the deployment.
Yes. The report runs per accounting book. You produce it once for one book and once for the other, without the books mixing.
Yes — both work on the same postings and use the same logic for mapping and overrides. The result of the P&L is exactly the amount that sits in equity in the balance sheet.
As a PDF or Excel file from NetSuite. Anyone who wants to check its origin gets the report together with the positions it is composed of.
We produce the balance sheet for a reporting date of your choice — and you compare it with what your statutory accounts show today.