.svg)
Inside a live NetSuite account, the trial balance, the balance sheet and the income statement are a few clicks away. Those reports run inside the account. When the account is retired, the finance team keeps the need for them and loses the place they ran. CSV exports of invoices and journal entries help, but files on their own do not produce a trial balance, and a PDF of last year's statements cannot show the transactions behind a figure.
Which financial reports will we still need after NetSuite is retired?
In our archival work the same requests come back year after year: a trial balance for a closed period, a balance sheet or income statement at a past year-end, the general ledger activity behind one account, the detail of a specific transaction, and profit and loss by subsidiary, department, class or location for a comparison. Auditors, tax authorities, acquirers and the finance team's own reviews all ask for them, often years after the migration. Each of these is built from accounting entries, which is where the archive has to start.
Why does the GL impact of each transaction matter?
An invoice record tells you a sale happened. Its GL impact tells you how it moved the books: which accounts were debited and credited, in which subsidiary, period and accounting book. Financial statements are sums of those entries. An archive that keeps the transactions but not their GL impact can show that an invoice existed and still cannot produce the trial balance it contributed to without someone reconstructing the postings by hand.
That is why the extraction keeps more than transaction headers. AcroXtract extracts the transactions with their lines, the accounts, entities, subsidiaries and accounting periods, and the GL impact of each transaction, into a relational archive where those records stay related. The statements are then produced from the archived ledger itself, and each figure leads back to the transactions behind it.
The reports DBVault produces from the archived ledger
On DBVault for NetSuite, the financial reports run inside the platform against the archived data. Which ones apply depends on what the account held and what the extraction scope included.
- Financial statements: cumulative and consolidated trial balance, period activity balance, balance sheet, income statement, general ledger, account activity, chart of accounts and transaction detail.
- Management and multi-currency: profit and loss by department, class, location and subsidiary; revenue by customer and expenses by vendor; trial balance by currency and FX analysis.
- Audit: transaction journal, period comparison, account type summary and the reversals report.
Multi-Book accounting is supported, and the consolidated trial balance covers several subsidiaries where the archived data supports consolidation. A custom report someone built in NetSuite is not reproduced automatically: the reports your team relies on are confirmed during scoping and tested during your validation period, before the account closes.
From a figure back to the transactions
The point of producing reports from the archive, rather than keeping static copies, is the path back. A reviewer looking at an account balance opens the account activity, then the transaction, then its lines and GL impact, and the attachments linked to it where the File Cabinet was archived too. That is the difference between telling an auditor what a number was and showing how it was made.
Access follows the archive's roles. A read-only reviewer, an external auditor for example, can be given the statements and the subsidiaries their engagement covers without the ability to see anything else, and every login and download is logged.
Plan the reporting during the archive project
Keeping a NetSuite account open only so that finance can run historical reports is one choice. Extracting the history and producing the reports from an archive is another, and it works best when the reporting requirement is part of the extraction scope from the start. Before the account closes, have finance run the reports it will be asked for, for a few closed periods, and compare them with the figures it already signed off. If they agree, the history is usable. If they do not, the account is still there to find out why.
If your team is planning a retirement and wants to see the statements run on archived data, bring the subsidiaries, books and periods that matter to you and see how DBVault for NetSuite produces them. For the wider question of reaching the records themselves after the account ends, see access to NetSuite data after you cancel.
.svg)
