ERPClaw EU Regional Compliance

Problem

Cross-border ERPs often fail at EU tax details rather than core ledgers: 27 member-state VAT rates, reverse charge, OSS, Intrastat, EN 16931 e-invoicing, SAF-T exports, and validation of VAT numbers, IBANs, and EORI codes are easy to get wrong when maintained manually. This skill treats EU compliance as a pure overlay: it does not modify ERPClaw core tables, reads business data, and only writes default accounts or templates for EU setup.

How It Works

It runs 26 actions through one entry point, db_query.py --action, against a local SQLite database. The workflow is offline and does not call external VIES or cloud services. Key steps include seed-eu-defaults to create VAT accounts and templates, setup-eu-vat to store the company VAT number and member state, compute-vat for standard or reduced rates, compute-reverse-charge for seller-side 0% and buyer-side self-assessment, and compute-oss-vat for B2C digital services at the buyer-country rate. Compliance outputs include generate-vat-return, generate-ec-sales-list, generate-saft-export, generate-intrastat-dispatches and generate-intrastat-arrivals, generate-einvoice-en16931, and generate-oss-return. Financial amounts are stored as TEXT and computed with Python Decimal; VAT, IBAN, and EORI values are checked against country-specific formats and checksums.

Boundaries

It is intended for companies whose country is an EU member-state code. If the company is not set to an EU code, actions fail. OSS mainly targets B2C digital services, and the distance-selling threshold is checked against the EUR 10,000 EU-wide rule. Treat generated returns, lists, invoices, and SAF-T exports as drafts or validation materials; final filing still requires local rules, contractual terms, and professional tax advice.