How Maconomy's country packs, tax configuration, banking formats, e-invoicing, statutory reports and audit files translate into D365 country/region configuration, Electronic Reporting, Tax Calculation Service and Globalization Studio.
Localisation is the regulatory and statutory layer that sits atop the financial foundation. It encompasses tax determination and posting, withholding tax, banking and payment formats, e-invoicing mandates, statutory reports, audit files, declarations, document numbering, language and retention — everything a regulator, not a business…
The playbook mandates a per-country dossier that cannot be skipped or deferred. For each country where the firm operates:
Maconomy's tax configuration determines which tax applies to each transaction based on document type, customer/vendor tax status, item or service classification, and country of supply/receipt. D365 uses a comparable structure with different naming:
Tax Calculation Service is an optional microservice that externalises tax determination from the D365 engine. It provides:
Maconomy environments in countries with withholding obligations (Italy, India, Brazil, others) configure withholding rules on vendor payments. D365 provides:
Maconomy payment formats (SEPA, BACS, local clearinghouse standards) produce output files for bank submission. D365 replaces these with Electronic Reporting format configurations:
The Electronic Invoicing service (part of Globalization Studio) handles the transmission, digital signing, government-portal submission and response processing for countries that require real-time or near-real-time submission.
Countries mandating SAF-T (Norway, Portugal, Luxembourg, Poland, Lithuania, others) require periodic extraction of GL, customer, vendor and tax transaction data in a defined XML schema. D365 delivers SAF-T through ER configurations:
D365 supports data retention and archive policies at the database level. For long-term immutable retention beyond the transactional database, Azure Blob Storage with immutability policies or a qualified third-party archive solution provides the storage layer. The retention architecture must be defined per country before go-live.
Professional-services firms running Maconomy typically operate in 5–20 countries. The D365 migration must address:
D365's localisation estate is extensive but not universal. The boundary between first-party coverage and ISV/extension territory depends on the country and the requirement:
Localisation is not a late-stage configuration task — it is a parallel workstream that runs from discovery through go-live. The country dossier is the controlling document. Electronic Reporting is the delivery mechanism. Globalization Studio is the configuration interface.