ERP localization for Azerbaijan in 2026: what the system is required to do

SAP, Odoo, ERPNext are world platforms, and none of them arrives with a ready Azerbaijani layer. The chart of accounts, VAT/ÖDV, electronic documents, local payroll — all of this is a separate layer that someone has to build. 1C has this layer (a local partner built it); for the others, the integrator builds it. So the question is not "which ERP is the best in general," but "who localizes it for Azerbaijani law, and how." Let's break down point by point what exactly must be there.

Electronic waybills have been mandatory for VAT payers since 2017. Technically it works like this: the system produces a document in the prescribed XML format, it is signed with a strong electronic signature and uploaded to the State Tax Service portal. It's important to honestly understand the mechanics: this is not a "magic button with an official REST API," but producing correct XML + signature + submission. The ERP must be able to assemble this XML from the shipment data without manual entry. If you're promised "fully automatic integration via an official API" — clarify what exactly is meant.

Internal orders, contracts, and acts can be signed right inside the system. SİMA (cloud-based, biometric, by AzInTelecom) and Asan İmza (mobile, by B.EST Solutions) — both embed into business systems, but through an official agreement with the operator, not via an anonymous public key. The honest wording for any vendor: "we connect the signature through the operator for your project." If a vendor hints that an agreement with the operator isn't needed — that's a reason to be wary.

Since 2019, fiscalization of receipts has been mandatory: the register transmits data to the tax authority in real time and assigns the receipt a fiscal identifier. You can't make your own fiscalization — it goes only through a certified e-kassa operator and a registered device. The ERP/POS connects to this loop, it doesn't bypass it. So "integration with the cash register" is honest when it's integration through a certified operator.

This is the most underrated point. From January 1, 2026, the income-tax exemption for the private non-oil sector ended — a progressive scale was introduced. If your system still calculates by the old rules, the result is wrong. What must be set for 2026:

• Income tax (progressive): up to 2,500 ₼/month — 3%; 2,500–8,000 ₼ — 10%; above 8,000 ₼ — 14%. (3% is the lowest-band rate for 2026; by law it rises in stages in 2027–2028.)
• DSMF (social insurance): up to 8,000 ₼ — employee 3% on the first 200 ₼ + 10% on the rest, employer 22% on the first 200 ₼ + 15% on the rest.
• Mandatory medical insurance (İcbari Tibbi Sığorta): up to 2,500 ₼ — 4% (2%+2%); above — 1% (0.5%+0.5%) on the excess.
• Unemployment insurance: 0.5% + 0.5%.

The system must produce ready payment orders for the banks at these rates. Check yours — if it's on the old figures, that's a direct risk of errors and claims.

For the financial, telecom, and government sectors, personal data often has to be stored on servers inside Azerbaijan. For ordinary commerce the requirement is softer, but registration of the personal-data information system is still needed. So a localized ERP should have the option of hosting in the country (not only a foreign cloud) — otherwise, for regulated industries, a compliance gap appears.

Use these points to check any system before choosing:

1. e-qaimə — does it produce correct XML, sign it, submit it to the portal?
2. SİMA / Asan İmza — is connection through the operator provided for?
3. e-kassa — integration through a certified operator?
4. Payroll-2026 — are the new rates loaded (progressive tax, DSMF, medical insurance)?
5. Chart of accounts and ÖDV — in manats, by local rules?
6. Language — an Azerbaijani interface?
7. Hosting — is there an option to host inside the country?

If the answer to any point is "no" or "to be clarified" — that doesn't mean the system is bad; it means localization has to be built, and it matters who does it and how.

viasoft builds the Azerbaijani localization of ERPNext as a separate module (following the proven world pattern — the way it's done for India, the UAE, and other countries), and we connect the e-qaimə/SİMA/e-kassa integrations for the specific project through official operators. What's included and how much it costs — on the ERP implementation on ERPNext page.

• What must an ERP necessarily do in Azerbaijan? e-qaimə, support for SİMA/Asan İmza, connection to e-kassa, and correct payroll on the 2026 rates. Without this the system doesn't cover the local requirements.
• Did payroll taxes change in 2026? Yes — from January 1, a progressive income tax (3/10/14%) was introduced for the private non-oil sector instead of the former exemption; the DSMF and medical-insurance rates were updated too. Systems on the old figures calculate incorrectly.
• Can e-qaimə be fully automated? The system produces the XML, signs it, and submits it to the portal — that is the automation. But there's no "official public REST API" in the usual sense, so clarify the wording with the vendor.
• Is an operator agreement needed for SİMA and the cash register? Yes — the signature through an operator (AzInTelecom / B.EST), the register through a certified e-kassa operator. Without that it doesn't work legally.