NetSuite's native trial balance covers the basics. But as soon as a German subsidiary, a deviating fiscal year or a cross-year query is involved, the decisive parts are missing: fiscal year segmentation, the carry-forward into retained earnings, separate debit and credit columns — and an export that arrives even at millions of rows.
For a US setup, NetSuite's trial balance is coherent. In a German statutory close, what it does not do stands out — and it stands out to the very people you send the list to: accountants, auditors, group finance.
Query several years and the P&L accounts simply keep running. The list shows three years of revenue in one line — you cannot derive a balance sheet from that.
The result only reaches retained earnings once NetSuite has actually been closed. Until then it is missing — and the balance sheet does not balance.
A 4-4-5 calendar or a November-to-October fiscal year: if the fiscal year differs from the subsidiary's reporting year, the native report cuts in the wrong place.
A proper trial balance lives on both columns. Show the net balance only and you drop exactly the movement the auditor wants to see.
Large accounts, long periods, many subsidiaries: reports run into timeouts instead of finishing — and you cannot even be sure the result was complete.
If a period is not closed yet, later postings can change today's numbers. Without a note on the report nobody notices — until the figures drift apart.
The trial balance performs the statutory year end itself — in the report, not in the general ledger. Your NetSuite stays untouched: nothing is posted, nothing reconfigured, nothing back-dated.
For cross-year queries the P&L accounts are reset to zero at each fiscal year end and the annual result moves into retained earnings — separately for every year in the range.
The FY start date is a parameter — November 1 for a November-to-October fiscal year, for instance, no matter how the NetSuite calendar is configured.
Historical profits and losses are moved into retained earnings virtually. The balance sheet balances even if a closing entry was never made in NetSuite.
One Excel file, three sheets — the overview for the close, the line items for every follow-up question, and the control totals so nobody has to recalculate whether the list is complete.
Posting periods or a free date range, subsidiary, accounting book, debit/credit split or net — all on one screen.
Small queries return immediately. At high volume a background process takes over instead of letting you run into a timeout.
If the report runs in the background, an email arrives with a direct link to the result — you do not have to keep the page open.
The file sits in the NetSuite file cabinet and can be handed on unchanged — to accountants, auditors or group finance.
Balances come from direct SQL queries against the ledger — no saved search that quietly stops at 4,000 results.
Beyond a certain volume NetSuite splits the work into packages itself. Each package gets a fresh governance budget — the report finishes.
Either you get the complete file including control totals, or you get a clear message. There is no half result that looks like a whole one.
Filter by posting periods or set a free start and end date.
Either dedicated debit/credit columns per period or the compact net presentation.
Full support for multi-subsidiary structures — per entity or consolidated.
One report per accounting book — local GAAP and IFRS side by side, without mixing the books.
If a period is not closed yet, it says so on the report — not just in the back of your mind.
Every posting that makes up an account balance — the auditor's follow-up is answered in advance.
Large runs in the background, with an email and a direct link to the result.
Default subsidiary, accounting book, fiscal year override and target folder are script parameters.
The data never leaves NetSuite. No external service, no copy anywhere.
The trial balance is made for CFOs, controllers and accountants in NetSuite accounts with German, Austrian or Swiss entities — especially where the setup was originally geared towards US GAAP or a 4-4-5 calendar and the local close still has to be right.
SuiteScript 2.1 and SuiteQL — direct queries against the ledger, no saved searches.
Map/Reduce takes over automatically at high volume — no timeout, no partial result.
SuiteBundle 595828 — installation and updates through NetSuite's bundle mechanism.
Default subsidiary, accounting book, fiscal year override and export folder are set per deployment.
An Excel file in the file cabinet with trial balance, line items and totals sheet.
Everything stays in the account — no external service, no data replication.
Because in the native report the P&L accounts simply keep running. Under German GAAP they have to be reset to zero at fiscal year end and the result has to move into retained earnings. That is exactly what this report does — for every year in the range.
No. The carry-forward happens virtually inside the report. No posting is created in your ledger, nothing is closed and nothing is changed.
Then you set the FY start date as a parameter, for example November 1. Segmentation follows your statutory fiscal year regardless of how the NetSuite calendar is configured.
Large. Balances come from SuiteQL, and at high volume the calculation automatically runs as a Map/Reduce job in the background. You get an email with a direct link once the file is ready.
The report tells you. Open periods are flagged so it is clear that later postings can still change these numbers.
Yes. The report runs per accounting book. You produce the list once for one book and once for the other — the books are never mixed.
As an ordinary Excel file from the file cabinet — hand it over or link it. The line items are in the same document, so follow-up questions don't turn into another request to you.
We produce a trial balance for a range of your choice — ideally one that crosses a fiscal year end — and you check with your accountant whether it shows what they expect.