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 Head of Finance
The dedicated GoBD page gives me what my auditors ask for: GoBD conformity support stated with a procedure documentation, immutable data with full version history, complete logging of every processing step, plus incoming and outgoing e-invoices, bank transaction retrieval with open-item offsetting, automated dunning, and a DATEV export with automated pre-booking, posting-to-receipt linkage and free tax-advisor access. We found no public information on matching incoming e-invoices to purchase orders, OSS and reverse-charge VAT, or running several companies in one tenant, which keeps it below the top band. 1 4 9 10 11