A&O: own ERP at a client
A&O uses my own ERP for invoices, e-invoicing and DMS. XRechnung and ZUGFeRD are implemented in-house and checked against the official validator.
A gas and water installation business: writing invoices, issuing e-invoices in the correct format, filing documents. Three tasks that come together in daily work and should fit into one system.
A&O is a paying client and uses the ERP for invoices, e-invoicing and filing in the DMS. What the system can do beyond that is listed separately under “What the system can do”.
Starting point
The requirements are unspectacular and still demanding: e-invoices must be formally correct, documents should not be captured twice, and the path into accounting must be right. Small systems rarely fail on the interface; they fail on formats and edge cases.
Solution
So I built an ERP of my own.
A&O uses it for invoices, e-invoicing and filing in the DMS.
What the system can do beyond that: quote, order, document processing. E-invoicing is implemented in-house, XRechnung in the CII variant and ZUGFeRD as a PDF/A-3 container, plus import and validation against the KoSIT validator, running as a sidecar. The DATEV export creates a posting batch in EXTF format. Posting assignment comes from a booking matrix; accounting reviews the suggestions and approves them.
The connections needed in daily work come on top: mail sync with a queue, filing into the DMS including migration with a dry run, bank statement import and payment matching. The AI in the system runs locally; if the model is missing, a rule-based fallback without a model takes over.
What this shows
The formats and interfaces are not bought; I implemented and checked them. Anyone introducing e-invoicing sees the work behind it: validation, rounding, tax rates, retention. Anyone connecting DATEV sees the posting batch and the assignment logic with approval by accounting.
What this page does not show: how much work the deployment removed. That confirmation from the client is missing, and I do not invent it.
Neutrality
I advise on ERP selection and ERP replacement. My own ERP on the same website could look like a conflict of interest. That is why it stands here as technical evidence, not as a product I recommend in selection projects. In selection projects I recommend vendor-neutrally.
Limit
Whether the system fits another business depends on that business’s processes, not on this page. The system is not certified. It is checked against the KoSIT validator and takes GoBD requirements into account; GoBD compliance depends on the procedure documentation and the client’s use.
More
The technical side is under E-invoicing & DATEV. How custom software is built here is under Custom software & apps.