Dynamics 365 Bulgaria Localization Checklist

This guide examines the operating choices behind the technology: where value is created, which risks require deliberate control, and how leaders can move from isolated improvement to a sustainable business capability.
Begin with the Bulgarian operating footprint
Localization scope should follow the activity of the Bulgarian legal entity, not a generic country checklist. A sales office, distributor, manufacturer, shared-service centre, and holding entity create different transaction patterns, documents, integrations, and reporting needs.
Map what the entity sells and buys, where goods move, which parties are VAT registered, how imports and intra-EU transactions occur, what assets are held, which banks are used, and which intercompany flows exist. Include likely future activities.
Confirm requirements with qualified Bulgarian tax and accounting stakeholders. The implementation team translates validated requirements into the system; it should not invent the legal position.
Scope discovery should identify.
Legal entities, registrations, and reporting responsibilities. Domestic, EU, and non-EU sales and purchases. Goods movements, warehouses, imports, exports, and Intrastat relevance. Services, advances, credit notes, corrections, and self-assessment. Fixed assets, banking, expenses, and local documents. Statutory, group, and audit reporting needs.
Assess VAT, VIES, and evidence
VAT configuration connects tax groups, item or service treatment, counterparty status, geography, dates, amounts, exemptions, reverse-charge logic, and posting. Review scenarios end to end, including the accounting entry, source document, ledger, declaration position, and correction process.
VIES-related processes depend on valid counterparty information and correct treatment of qualifying cross-border transactions. Reliable validation and ownership of registration data are therefore essential.
Do not test only normal invoices. Include advances, credit notes, cancellations, partial transactions, foreign currency, late documents, corrections, and special scenarios relevant to the entity.
Readiness evidence.
Approved tax decision matrix. Ownership for VAT and counterparty master data. Expected declaration, ledger, and VIES outputs. Reconciliation and exception procedure. Scenarios approved by local finance or tax owners.
Prepare Intrastat and statutory outputs
Organizations trading goods with other EU member states may have Intrastat obligations when applicable conditions are met. Readiness can depend on commodity classification, partner country, origin, weight, quantity, value, delivery terms, transport, and nature of transaction.
Identify where every data element originates and who maintains it. Product and logistics teams may own information that finance ultimately reports. Late spreadsheet enrichment is difficult to control at scale.
List every local output, interface, printed form, electronic file, register, reconciliation, and archive requirement. Record its purpose, frequency, owner, source data, review, submission, and retention.
Resolve before configuration.
Current or expected Intrastat obligations. Availability of classifications and units in product data. Traceability of corrections to original transactions. Which outputs standard or localized functionality delivers. Which submissions remain outside the ERP and their controls.
Test real Bulgarian scenarios and govern change
Localization testing should prove more than whether a report runs. Trace transactions from master data and document creation through posting, settlement, correction, declaration, general-ledger reconciliation, and retained evidence.
Use realistic volumes and period-end sequences. Include permissions, integrations, exchange rates, document printing, exports, migration balances, and group processes such as centralized purchasing or intercompany invoicing.
After go-live, regulatory monitoring, Microsoft updates, localization releases, and business change need one controlled assessment process. Define who identifies a change, validates interpretation, analyzes impact, approves the response, tests it, and confirms deployment.
Proceed when.
Requirements are validated and owners are named. Critical data is available and controlled. Outputs and reconciliations are mapped. Local stakeholders can execute and approve testing. Maintenance, documentation, and support are funded. Accepted limitations have owners and resolution dates.
Move from insight to action
The practical next step is to test these principles against your own processes, data, controls, and operating constraints.
