🌍 Localizations

A country package is a model in the Customization layer: the law, the statutory fields, the contributions and the connectors to the country's services. Not a branch in Core. Tax is a frequent first scope, not the package's boundary.

How it fits into the platform — Global Core. The network and the secrets — outbound integrations: the same host that serves Fatoora will go to a bank and to a government portal. UI translations and RTL — Arabic localization, which is not a country package.

← Developer wiki

Countries#

• Ukraine
  • VAT (ПДВ) and the regimes — the first event, the TaxMapping exemption driven by the legal entity's regime, the payroll withholdings.
  • Unified Register of Tax Invoices (ЄРПН) — the TaxDocument envelope, the operator's queue, Issued ≠ Cleared. M.E.Doc is REST on a PC; there is no cloud sandbox.
  • PrivatBank statement — Autoclient GET, register UaBankStatement. There is no Autoclient sandbox.
  • Diia — login is not in the package; no channel without the Ministry of Digital Transformation.
• Saudi Arabia
  • ZATCA / Fatoora — the contours, the PDF, the host because a script gets no HTTPS. The other KSA services (GOSI as a report to the fund, Mudad, Qiwa, Nafath, SADAD) are not in the package.

A country page is not a table of contents for its own sake: it holds what applies to the whole package and does not fit into any one of the topics. The comparison of two packages — who builds the XML, who signs, when the answer comes — lives exactly there.

A new country or a new country service means a country folder next to the Localization… model, not one more entry in a shared list. A channel is an object of a model, not an if (country) in the kernel.

Same topic for other readers: Analyst