Finance, tax & compliance
How this is scored
Whether the ERP keeps books a tax adviser and an auditor accept: general and subledgers, VAT per country, GoBD-compliant posting and archiving, e-invoices sent and received (XRechnung, ZUGFeRD), payments and dunning, and a DATEV export or a documented hand-over to the accountant.
0 — No accounting at all; invoices leave as PDFs and the books are kept somewhere else by hand.
3 — Invoices and credit notes are created in the system, but there is no ledger, no stated GoBD compliance and no export the accountant can import.
5 — Invoices, open items and payments in the system with a DATEV or accounting export, VAT rates per item, dunning, and e-invoices in XRechnung or ZUGFeRD format sent to customers.
8 — Full financial accounting or a live-synchronised one: general, receivables and payables ledgers, incoming e-invoices read and matched to purchase orders, bank feeds with payment matching, OSS and reverse-charge VAT, GoBD compliance stated with a procedure documentation, and several companies in one tenant.
10 — The money side closes inside the system: an auditor's GoBD or IDW PS 880 attestation published, consolidation and intercompany postings across entities, fixed assets and cost accounting, every posting traceable to the order, goods movement and user behind it, and period close with locked periods documented.
The Skeptic
Invoicing, dunning and tax administration are in the system even in the free edition, with a DATEV booking-data export to the accountant, real-time matching of bank and payment-provider receipts, OSS, ELSTER transmission and GoBD-conform, audit-proof archiving of tax-relevant documents. The GoBD claim is 'out-of-the-box' with no procedure documentation behind it, e-invoices are documented only as received and processed in ZUGFeRD and XRechnung, and we found no public information on a general ledger or several companies in one tenant — the ledger side is handed over to DATEV, Lexware or SAP. 7 8 2