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 IT Integrator
The books close inside this ERP: double-entry accounting on SKR03 and SKR04 with VAT pre-registration via ELSTER and the EU summary statement by XML, e-invoices in XRechnung and ZUGFeRD sent and received, SEPA payment files, configurable multi-level dunning and a DATEV hand-over for the accountant, plus fixed assets with automatic depreciation, cost accounting, budgeting and period and annual closings across up to 999 periods. The finance software is stated as audited to IDW PS 880, which is what my auditor will ask about. We found no public information on bank feed matching, intercompany consolidation or locked periods. 9 11 12 1 2