Dynamics 365 Business Central Armenian Localization

What does the Business Central Armenian localization include?

Solzet delivers the Business Central Armenian localization: AMD as the local currency, Armenian tax and statutory reporting, an Armenian chart of accounts, Armenian-language documents, and e-invoicing integration with the State Revenue Committee where applicable. Solzet builds it as extensions on the international (W1) version of Dynamics 365 Business Central, which is available in Armenia.

Your accountants work in standard Business Central screens. The Armenian specifics sit in extensions and configuration on top of the base app, which is where they belong and where they can be maintained without touching Microsoft code.

• AMD as the local currency: the general ledger, bank accounts and statutory reports run in AMD, while customer, vendor and bank transactions in USD, EUR, RUB or any other currency are posted at the exchange rate and revalued against AMD.
• An Armenian chart of accounts: the account structure Armenian accountants expect, wired to posting groups and dimensions so every document lands on the right account without manual corrections at month end.
• Armenian tax and statutory reporting: VAT setup and VAT returns, statutory financial statements and the other reports your chief accountant files, produced from posted entries instead of being rebuilt in Excel.
• Armenian-language documents: invoices, acceptance acts, credit memos, orders and reconciliation statements laid out in Armenian, with the company details Armenian counterparties expect, such as taxpayer identification numbers and bank details.
• E-invoicing integration with the State Revenue Committee where applicable, so invoices issued in Business Central do not have to be retyped into a second system.

What must an Armenian localization of Business Central cover?

Before you compare offers, write down what the localization has to do. The list below is the checklist we use in the assessment. It is deliberately generic: the exact rules come from current Armenian legislation and from your own accounting policy, so we confirm each one with your chief accountant instead of hard-coding assumptions.

• Currency: AMD for the books, an agreed exchange rate source, and a revaluation policy for foreign currency receivables, payables and bank accounts.
• Chart of accounts and posting setup: the Armenian account structure, plus a documented mapping from your current chart, which is often a 1C chart, to the new one.
• VAT: correct VAT treatment on sales and purchases, and VAT returns built from posted entries.
• Statutory financial statements and tax reporting in the formats the authorities and your auditors expect.
• E-invoicing with the State Revenue Committee where your business is required, or chooses, to issue electronic invoices.
• Armenian print layouts for every document a counterparty, tax inspector or auditor will see.
• Master data: taxpayer identification numbers, legal addresses and bank details on customers, vendors and your own company.
• A maintenance path: who updates the extensions when Armenian requirements or Business Central itself change.

Why does Business Central in Armenia need a partner-built localization?

Business Central online is available in Armenia on the international (W1) base app, and Microsoft states that the localization for Armenia is provided by partners rather than by Microsoft itself. W1 gives you the full product: finance, sales, purchasing, inventory, projects, fixed assets, manufacturing, warehouse and service management. The Armenian layer on top is the part a partner has to build.

Solzet fills that role. We write the localization in AL, using the AL Language extension for Visual Studio Code, as extensions on top of W1. The Microsoft base app stays untouched, Microsoft updates keep arriving, and the Armenian features are maintained alongside each release. The same engineering practice runs through our Business Central AL development service.

How does Solzet run a localization project?

Accountants judge a localization by the first month close, so the project is organised around getting that close right. Every step below is done with your chief accountant in the room, not presented to them at the end.

• Assessment: your current accounting system, chart of accounts, the reports you file, the documents you print and the systems that feed the ledger.
• Chart of accounts mapping: old accounts to new ones, with posting groups, dimensions and opening balance rules agreed in writing.
• Setup: companies, currencies, VAT posting setup, number series, users and permissions.
• Document layouts in Armenian: each printout reviewed and approved by the people who sign it.
• Reporting extensions: VAT returns, statutory financial statements and the management reports your CFO needs.
• Data migration from 1C: master data, opening balances and open receivables and payables, rehearsed in a test company before cutover.
• Testing on your data: a full month posted and closed in a test company and reconciled to the old system.
• Training and go-live: accountants trained on their own processes, then support from the same team after go-live.

How do you move from 1C to Business Central with the Armenian localization?

Many Armenian companies keep their books in 1C today, and that is usually the starting point. We migrate you from 1C to Business Central: the 1C chart of accounts and its subconto analytics are mapped to the Armenian chart of accounts and dimensions in Business Central, customers, vendors, items and fixed assets are cleaned and loaded, opening balances and open items are brought across, and trial balances are reconciled between the two systems before you switch. History you need for audits can stay readable in an archive instead of being forced into the new ledger.

The method is set out in our guide to moving from 1C to Business Central, and our migration to Business Central service covers the same work for companies coming from Dynamics NAV, Dynamics GP and other systems.

Who is the Armenian localization for?

Companies registered in Armenia, and international groups with an Armenian subsidiary, that want finance, inventory, projects and light manufacturing in one cloud system with Armenian accounting done properly. It suits finance teams leaving 1C or spreadsheets, subsidiaries that report to a foreign parent, and companies that already run Dynamics 365 Customer Engagement and want the ERP on the same platform.

If your group has several legal entities across countries, deep supply chain or production needs, or retail operations on Commerce, compare Business Central with Finance and Operations first. The table is the short version; the Business Central implementation page has the long one.

How does the localized Business Central connect to CRM and other systems?

Solzet works on both sides of the Microsoft business stack, so the Armenian ledger can share data with the rest of your systems instead of becoming another island. Business Central connects to Dataverse through the Set up Dataverse connection assisted setup, which is also the route for integrating with Dynamics 365 Sales, so customers, orders and invoices mean the same thing in the CRM and in the books. Our Dynamics 365 consulting team designs the CRM side, and the same team builds the integration with Business Central.

Banks, online stores and other local systems connect through Business Central APIs and AL integrations, designed during the assessment rather than discovered after go-live.

What happens after go-live?

The first closes after go-live are where questions appear, so support starts on day one and stays with the team that built the localization. When Armenian requirements change, we update the extensions and tell your chief accountant what changed before the next filing. When Microsoft ships a Business Central update, we test the Armenian extensions against it before it reaches your production environment.

This page is also available in Armenian and Russian, so you can share it with colleagues who prefer to read in their own language.