“Technology works best when it provides security and efficiency invisibly in the background.” Over the course of my career, I have scaled many software projects from zero to one hundred and learned one thing: good ideas rarely fail because of the concept. They fail in practical implementation.
Even the most attractive SaaS interface is of little use to a car dealer if the tax advisor arrives at year-end with a stack of error reports. At Autaxo, we therefore do not build quick-and-dirty tools. We build digital processes that reduce work. This article looks at our technology stack and engineering principles.
Quick definition: the Autaxo architecture at a glance
In brief: Autaxo combines specialist tax logic with efficient IT. Shift-left validation during data imports, a security-by-design architecture using reversing entries rather than deletion, and intelligent DATEV transfers without a hard locking indicator support a traceable workflow designed around GoBD requirements between the dealership and its tax advisor.
Key facts
- Shift-left principle: Data from upstream systems is validated immediately during import, not at the end of the month.
- Error prevention: We use high-precision libraries such as
decimal.jsto prevent financial rounding errors in the cloud. - API mapping: Inconsistent data from external platforms such as mobile.de is translated into sound accounting logic before entering the system, including VAT flags.
- Security by design: There are no
DELETEcommands for accounting transactions in the database. Corrections use reversing entries and cancellation documents. - DATEV transfer: We deliberately omit a hard locking indicator so the tax advisor retains the professional latitude required for final accounting adjustments.
Why do we validate data during import?
We validate data from upstream systems, such as an existing DMS or mobile.de, immediately during import to prevent administrative errors and legacy issues before the annual accounts are prepared.
When data enters our cloud infrastructure, we apply the shift-left principle. We check and correct it as early as possible, at the far left of the process timeline.
- GoBD from the first second: As soon as an administrative transaction takes place in Autaxo, it must be completed fully and correctly.
- Precision: Standard data types inevitably create financial rounding errors in some situations. Under the hood, we therefore rely on precise libraries such as
decimal.js. - Open source: As a SaaS-first company, using open technology is natural to us. We also support the projects we depend on as sponsors.
How does Autaxo deal with inconsistent API data?
Missing or ambiguous API data from external platforms is translated automatically into correct accounting records through intelligent mapping before it can contaminate the system.
Theory is useful, but real architecture has to work in practice. Anyone who integrates marketplace APIs knows that data quality can be open to interpretation.
- The VAT problem: A classic example, highlighted by our expert Paul Bogdan, is the VAT flag attached to imported vehicles. Whether standard VAT or the margin scheme under Section 25a of the German VAT Act (UStG) applies is essential for the dealer.
- The solution: Autaxo contains specific safeguards that turn incomplete data packages into consistent logic. The complexity is reduced before it reaches the user.
Why does Autaxo use reversing entries instead of database deletion?
To support traceability and the technical requirements of the GoBD, we block DELETE commands for accounting transactions and correct them through cancellation invoices instead.
As CTO, I am responsible for a strict security-by-design approach at Autaxo. A common developer reflex when encountering an incorrect entry is a simple DELETE statement in the database. That does not exist in our accounting workflow.
- We mirror reality: A dealership cannot simply tear up an incorrectly issued invoice. It issues a cancellation invoice.
- DATEV standards: By embedding the principle of a Generalumkehr, or reversing entry, deep in the code, every change remains fully traceable. This supports documentation that can be reviewed by auditors and the German tax authorities.
Why do we transfer DATEV exports without a locking indicator?
We deliberately transfer posting records without a hard locking indicator so the tax advisor has the professional latitude needed for final accounting adjustments.
Despite our end-to-end responsibility and consistent alignment with GoBD requirements, we deliberately chose this approach for the DATEV interface. At first glance, a missing lock may seem counterintuitive, but it is a matter of respect and efficiency.
- Clear roles: We are the technology experts. The tax advisor is the accounting professional.
- A frictionless workflow: We do not force tax firms into a rigid IT framework. Trusting the advisor’s expertise reduces friction between the software provider, client and tax firm.
FAQ about Autaxo architecture and compliance
What does the shift-left principle mean at Autaxo?
Data from upstream systems such as a DMS or mobile.de is validated immediately during import. Errors are resolved before they enter the accounting workflow, preventing administrative debt at year-end.
How does Autaxo support GoBD-compliant processes?
Through security by design and the principle of reversing entries. The database contains no DELETE commands for accounting transactions. Corrections are made through cancellation invoices with a complete audit trail.
Why does Autaxo omit the DATEV locking indicator?
So the tax advisor retains the professional latitude required for final accounting adjustments. Autaxo supplies a traceable foundation designed around GoBD requirements without imposing a rigid IT framework on the tax firm.
About the author
Leonard Niehaus, Co-Founder and CTO at Autaxo
As CTO, Leonard has end-to-end responsibility for Autaxo technology, architecture and security. An experienced SaaS and cloud architect, he specializes in scaling platforms from zero to one hundred and translating complex requirements into simple digital processes. His focus is on modern web technology, cloud infrastructure and security by design.
🔗 Connect with Leonard Niehaus on LinkedIn