What an auditor asks forthat a report cannot show.
A report shows a figure. An audit asks for the entries behind it, and for the record of who could have changed them.
In short
- An audit reads the trail in both directions: from a document to the statements, and from a figure back to its document — for the whole retention period.
- German bookkeeping rules make that structural: postings must stay traceable in both directions, and a change must leave the original visible and the fact of the change recorded.
- A reporting tool holds an aggregated figure with a custodian PDF behind it. The postings, the reversal history and the log are what answer an audit sample.
The trail runs in both directions
The German principles for proper bookkeeping (GoBD, most recently the BMF letters of 11 March 2024 and 14 July 2025) describe two tests that an auditor may run at any point in the retention period. The progressive test starts at the document and follows it through the journals to the accounts, the balance sheet and the tax return. The retrograde test starts at a figure and works back to the document that supports it.
The same two directions appear in the international standards: ISA 500 requires sufficient appropriate audit evidence, and ISA 505 covers evidence obtained directly from third parties, which is how a bank balance is confirmed. Neither test can start without the entry.
What the auditor actually asks
Six questions cover most of an audit of a family office's books. Each has a record that answers it, and a framework that requires it to exist.
| The auditor asks | What answers it | Source of the requirement |
|---|---|---|
| Which entity holds this balance | That entity's own ledger and chart of accounts | GoBD Rz. 32–33 (traceability per booking) |
| Which postings make up the figure | The journal entry and the ledger lines it produced | ISA 500 (audit evidence) |
| Where the posting came from | The custodian statement or import file behind it | GoBD Rz. 30 (document principle); ISA 505 (external confirmation) |
| Who could have changed it | The audit trail, with user and timestamp on every change | GoBD Rz. 58–59, 110–112 |
| Whether anything was altered | An integrity check the office can run itself | GoBD Rz. 110 (immutability, logging) |
| How the process is controlled | The procedure documentation for the system | GoBD Rz. 145–150 (Verfahrensdokumentation) |
Why an aggregated figure fails the test
A reporting layer takes a figure from a custodian, places it against an account and adds it to a total. The total can be exactly right and still fail: the auditor asks which postings produced it, and there are none. What sits behind it is a PDF in a folder.
That is not a defect of reporting tools. It is the boundary of what they are for. The distinction matters most in a sample: an audit selects a balance, asks for the entries, then asks for the documents those entries came from. A system that holds only the aggregate replaces the sample with a walkthrough of how the number was produced — a weaker form of evidence for the same assertion.
Corrections must survive the correction
Books are corrected, and the correction is where a system is tested. A tool that allows an edit removes the evidence of what the figure was before the change. GoBD states the requirement plainly: a posting may not be altered in a way that the original content can no longer be established, and neither may changes be made whose nature leaves it unclear whether they were original or later (§ 146(4) AO, § 239(3) HGB).
A reversal followed by a corrected entry satisfies that without effort. The wrong posting stays, the reversal sits beside it, the correction follows, and the sequence reads in the order it happened. The same rule fixes the meaning of a reported date: a balance for February is the sum of the entries that existed in February, so a correction made in March appears in March.
A log you can test in the room
An audit trail is a record of changes, not a report about them. GoBD lists the ways immutability can be achieved — locking, versioning, automatic logging — and adds the requirement that later changes leave both the original content and the fact of the change visible (Rz. 110–112).
The practical test takes a minute: ask for a change to an entry, then ask the system to show the change, the original and who made it. If the answer is a screenshot from a colleague, the control is not in the system.
DACH specifics: GoBD and access
For a family office with German tax exposure, the audit has a second audience. § 147(6) AO gives the tax auditor three levels of data access — indirect (Z1), direct (Z2) and a handover of the data carrier (Z3) — and the GoBD expects a procedure documentation that a knowledgeable third party can follow (Rz. 145–150).
None of that requires a particular product. It requires that the entries, the documents behind them, the change history and the description of the process all exist and stay readable for the retention period.
The limit worth stating
INVARIO produces four fixed report types on request, in PDF, XLSX or CSV, and does not keep the file. There is no report archive and no stored pack to compare against the books, so an audit pack is run again from the ledger on the day it is needed.
For an audit that changes what a pack is. The document the auditor receives was produced from the books that morning, which is also why it cannot have drifted from them. The evidence stays where it belongs: in the entries, the statements and the log.
What to have ready
- Each entity's ledger, chart of accounts and trial balance at the period end.
- The postings behind any balance the auditor selects, with the statement or notice attached.
- Every reversal and its replacement, in sequence, with the person who posted both.
- An audit trail that cannot be edited, plus a way to run the integrity check in front of the auditor.
- Read-only access scoped to the entities in the engagement, rather than exports by email.
- The procedure documentation the GoBD asks for, kept current when the process changes.
Sources
- BMF, Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff (GoBD), letter of 28 November 2019 (BStBl I 2019, 1269), superseded by the letters of 11 March 2024 (BStBl I 2024, 374) and 14 July 2025 (BStBl I 2025, 1502). Paragraph references in the table follow the 2019 text.
- IAASB, ISA 500 Audit Evidence and ISA 505 External Confirmations, ISA 505 project page. Current editions.
- § 146(4) AO and § 239(3) HGB (immutability); § 147(6) AO (data access Z1/Z2/Z3). Read 13 November 2026.
This note describes requirements, not advice. Whether a given office falls under GoBD, and how a specific engagement is scoped, is a question for its auditor and tax adviser.
Bring your questionto a demo.
If this is the question your office is working on now, we can answer it in a demo built around your own entities and banks. You don't need to share any figures.