NetSuite GoBD compliance –
a matter of configuration, not of the system
Is NetSuite GoBD-compliant? The question can’t be answered that way. No system is compliant in itself – what matters is configuration, lived processes and solid process documentation. We review your NetSuite setup from a tax perspective and support the tax audit.

What the GoBD require – and what that means in NetSuite
The GoBD (Germany’s principles for the proper keeping of books in electronic form) set clear requirements for orderliness. Translated to the system level, this means:
Traceability
Every entry is traceable back to the source document.
Completeness
No business transactions are missing or recorded twice.
Accuracy
Accounts and tax codes reflect the transaction correctly.
Timely recording
Documents are posted promptly, not back-dated.
Immutability
Posted records cannot be changed without a log.
Retention
Data stays legible and analysable throughout the retention periods.
Process documentation
The entire process is documented in a traceable, written form.
Where international NetSuite setups typically break
Four points come up again and again in group setups – not out of negligence, but because the German specifics were not in focus at roll-out.
- Closed periods can be reopened afterwards: who holds the permission, and how is the reopening logged?
- Immutability and journalling: what the audit trail delivers – and where its limits are.
- Document and entry not linked: documents outside the system with no clear allocation.
- Where the data sits: servers outside Germany and access in the event of an audit.
Tip: two clicks, the most common finding. Permissions are often taken over from the group template at roll-out. In day-to-day operations this never shows. In an audit it is one of the first points where the orderliness of the books is questioned.
What happens in a tax audit?
In an audit, what counts is whether the data from NetSuite can be provided properly.
- Data access and data-carrier provision: direct (Z1), indirect (Z2) and data-carrier access (Z3).
- Process and preparation: the audit order, data provision, point of contact.
- Typical objections and how to avoid them: open periods, missing document links, unclear permissions.
Our services – tax advisors, not ERP implementers
We review and own the tax side of GoBD; the technical configuration sits with the implementation partner.
- GoBD review of your NetSuite setup from a tax perspective
- Process documentation – created or reviewed
- Support during the tax audit from the order through to closure

Awarded Top Tax Advisor 2026
In the renowned FOCUS-MONEY tax advisor test, TAUBE Steuerberatung was recognised as a Top Tax Advisor 2026. This independent award reflects proven advisory quality, reliable support and the trust of our clients – a standard we deliver on in every engagement.
Your added value in NetSuite GoBD compliance
FAQ: NetSuite GoBD compliance
The same questions come up again and again around GoBD compliance in NetSuite and the tax audit. We answer the key ones here.
Is NetSuite GoBD-compliant?
NetSuite is not GoBD-compliant across the board. No system is compliant in itself – GoBD compliance depends on configuration, lived processes and the process documentation. That is exactly what we review from a tax perspective.
Do we need process documentation?
Yes, process documentation is part of the GoBD requirements. It describes, in a traceable way, how data is created, processed and retained in NetSuite. We create or review this documentation for your setup.
What do Z1, Z2 and Z3 mean for data access?
Z1, Z2 and Z3 describe the tax authority’s access types: direct access (Z1), indirect access via analyses (Z2) and data-carrier provision (Z3). We prepare the data from NetSuite so that all three can be served.
May the NetSuite data sit on servers outside Germany?
NetSuite data may sit on servers outside Germany, provided data access is ensured in the event of an audit and the retention obligations are met. We clarify whether your setup meets these requirements.
What are typical GoBD objections with NetSuite?
Typical GoBD objections with NetSuite are periods reopened after the fact, missing document links and overly broad permissions taken from the group template. We work through these points in advance in the GoBD review. Request a GoBD review.
Have NetSuite GoBD compliance reviewed – enquiry
Briefly outline your setup. You’ll receive a first assessment of GoBD compliance and of preparing for a tax audit.

David Taube
Certified Tax Advisor (Master of Arts), Managing Director
Taube Steuerberatungsgesellschaft mbH

Note: Oracle NetSuite is a registered trademark of Oracle Corporation. Taube Steuerberatung has no business relationship with Oracle Corporation and is not an official partner or provider of Oracle NetSuite.






