Briefing Document & Podcast: E-Invoicing and E-Reporting in Armenia

SUMMARY

I. Executive Summary

Armenia has established a comprehensive and centralized electronic invoicing (e-invoicing) and real-time reporting system, making it a leader in digital tax administration within its region. Since 2016, the issuance of electronic invoices has been mandatory for virtually all business-to-business (B2B) and business-to-government (B2G) transactions for VAT-registered entities. The state-run system, operated by the State Revenue Committee (SRC), functions as both the invoicing platform and the real-time reporting mechanism, with every digitally signed e-invoice immediately transmitted to the tax authority. While initial implementation presented challenges, particularly for small and medium-sized enterprises (SMEs), the system has matured, with continuous enhancements aiming for broader transaction coverage and increased transparency, notably extending to purchases from individuals effective January 2025.

II. Scope of the Mandate

Armenia’s e-invoicing obligations are broad, encompassing a wide array of transactions and entities:

• E-Invoicing Obligations: Since 2016, “all businesses operating in Armenia must issue invoices in electronic form through the state-run e-invoicing system.” This mandate covers B2G, B2B, and B2C sales in principle. All e-invoices must be digitally signed by the issuer.
• E-Reporting Obligations: The e-invoicing platform acts as an “Electronic Reporting System,” automatically transmitting invoice data to the tax authority in real-time. This eliminates the need for separate periodic VAT invoice reporting, as “the act of issuing the e-invoice constitutes compliance with reporting obligations.”
• Transactions in Scope:
  • Domestic B2B & B2G: Mandatory since 2016. Government agencies only accept e-invoices.
  • Domestic B2C: Partially mandatory. Retail sales typically use cash register receipts, but e-invoices are required for large B2C sales or when requested by the buyer.
  • Imports: No domestic e-invoice is required. Import VAT is handled via customs declarations, and reverse-charge services are reported in VAT returns.
  • Exports: Mandatory e-invoicing for goods and services from Armenia. These are generally marked with 0% VAT.
  • Cross-Border B2B (non-EU): Armenian businesses must issue 0% VAT e-invoices for sales to foreign entities. Purchases from foreign entities are outside the Armenian e-invoicing platform.
• Special Scenarios:
  • Self-Billing: Permitted in specific cases, notably mandated for businesses purchasing goods or services from private individuals starting January 1, 2025. The purchasing business issues an e-invoice on behalf of the individual seller.
  • Triangulation and Chain Transactions: Armenia does not have a specific “triangulation” regime. Each transaction link involving an Armenian entity must be e-invoiced under normal VAT rules, with cross-border elements treated as imports or exports.
  • Special VAT Regimes: Businesses under simplified regimes (like turnover tax) and VAT-exempt transactions are included. The system features specific document types (e.g., “invoice (not a tax invoice)”) and, since 2025, a mandatory “Transaction Type” field to denote special treatments (e.g., “Exempt from VAT,” “Special Tax Regime”).

III. Taxable Persons in Scope

• Established Entities (Residents): All organizations and individual entrepreneurs registered in Armenia are subject to the mandate, regardless of size. This includes VAT-registered taxpayers and, increasingly, non-VAT registered entities for specific transactions.
• Non-Established Entities with VAT Registration: Foreign businesses registered for VAT in Armenia must use the e-invoicing system like domestic payers.
• Foreign Entities without Fixed Establishment: Generally out of scope, unless they voluntarily register for VAT or fall under the specific “eVAT” scheme for non-resident providers of digital services to Armenian consumers (which uses a separate simplified portal).
• Exemptions: Few sector-specific exemptions exist. Even financial institutions and insurance companies providing VAT-exempt services must issue e-documents. Minor exceptions for certain low-value transactions or transactions involving state secrets.

IV. Implementation Timeline

Armenia’s e-invoicing journey has been marked by a phased but ultimately rapid expansion:

• 2010: Pilot introduction for large taxpayers and financial institutions.
• 2014-2015: Legal framework development, culminating in the 2016 Tax Code making e-invoicing mandatory and the 2017 Government Resolution No. 1257-N detailing procedures.
• 2016: Nationwide mandate for all VAT-registered businesses took effect, covering B2B and B2G.
• June 1, 2023: Launch of a modernized web-based e-invoicing platform integrated into the broader “File Online” tax system, enhancing user experience and security.
• January 1, 2025: Mandatory electronic documentation for businesses purchasing from private individuals, requiring self-issued e-invoices for such transactions.
• March 1, 2025: System enhancements including new data fields (e.g., “Transaction Type”) and updated XML schemas to better categorize non-standard VAT treatments.
• Grace Periods: Implementation has largely followed a “big bang” approach, with less reliance on extended grace periods. However, new requirements like the 2025 individual purchase mandate were announced with lead time.
• Future Outlook: The regime is stable and mature. Future developments are likely to focus on system reliability and leveraging data, rather than new mandates.

V. Technical & Functional Requirements

• E-Invoice Format: E-invoices must conform to a structured XML format, defined by an official XSD schema provided by the SRC. It is a local standard and does not follow international formats like PEPPOL.
• Mandatory Data Fields: Invoices must include standard details such as invoice ID, date, supplier/customer TINs and names, detailed line items (description, quantity, unit price), VAT rate and amount, and total amounts. The “Transaction Type” field, mandatory from 2025, requires categorization of non-standard VAT treatments (e.g., “Export,” “Exempt from VAT”).
• Digital Signature & Integrity: All e-invoices require digital signatures from the issuer using an authorized certificate, ensuring authenticity and integrity. The SRC provides a public verification service for serial numbers.
• Real-Time Processing: The system operates on a near-real-time “clearance” model. Invoice data is immediately registered with the tax authority upon issuance, and buyers can typically view it instantly.

VI. Correction of Errors

Armenia’s system provides mechanisms for correcting e-invoices:

• E-Invoice Corrections:
  • Invalidation (Cancellation): For serious errors, an e-invoice can be voided in the system, typically before the buyer has acted upon it. A new, corrected invoice must then be issued.
  • Credit and Debit Notes (Adjusting Invoices): For partial adjustments or errors discovered later, an “adjusting tax invoice” (credit or debit note) is issued, referencing the original invoice.
  • E-Reporting Corrections: Corrections to periodic VAT returns, which summarize e-invoice data, are made by submitting an “amended” return. There are time limits for corrections, generally prohibiting adjustments beyond three tax years from the original transaction’s year.

VII. Transmission & Workflow

• Transmission Model: A centralized clearance model is used, where all e-invoices are submitted to and processed by the SRC’s online system. There is no direct peer-to-peer exchange or use of international networks like PEPPOL.
• Workflow: Sellers prepare, digitally sign, and submit invoices via the SRC portal (manual entry or API integration). The system validates, registers, and makes the invoice immediately available to the buyer and tax authorities.

VIII. Self-Billing

Self-billing is explicitly allowed in Armenia, particularly for purchases from individuals. The buyer, using their SRC e-invoice account, issues the invoice on behalf of the supplier, entering the supplier’s details. From January 2025, this is mandatory for businesses purchasing from individuals. Such invoices must meet all standard content requirements and be digitally signed by the buyer.

IX. Triangulation & Special Scenarios

• Triangulation Transactions: Armenia does not have a simplified triangulation regime. Each leg of a chain transaction involving an Armenian entity must be individually invoiced or reported.
• Cross-border Reverse Charge: Handled through self-assessment in the buyer’s VAT return, not via the e-invoicing system. No e-invoice needs to be issued for such inbound transactions.
• Zero-Rated and Exempt Supplies: The system fully supports these, with invoices marked 0% VAT or “Exempt” via the “Transaction Type” field. These transactions are still required to be e-invoiced for reporting purposes.

X. Archiving & Retention

• Formats: E-invoices are stored electronically, with the digitally signed XML file considered the authentic original. PDF exports are available for human readability. The SRC system itself acts as a central repository.
• Retention Period: Taxpayers must retain e-invoices and related tax documents for “at least 5 years” from the end of the reporting period, aligning with the tax audit statute of limitations.
• Storage Location: No explicit mandate for local storage; records must be readily accessible to authorities upon request.
• Integrity: Digital signatures ensure authenticity and integrity throughout the retention period.

XI. Penalties & Enforcement

Armenia employs a strict penalty regime to ensure compliance:

• Failure to Issue E-Invoices: Penalties apply for not issuing a required e-invoice, which can be a fixed fine per instance or a percentage of the transaction value. Intentional evasion leads to larger fines (up to 100% of unpaid tax) and potential criminal charges.
• Late or Incorrect E-Reporting: Late submission of VAT returns or late issuance of invoices incurs penalties. Interest on late VAT payments accrues at 0.075% per day (approximately 27% annually). Incorrect data reporting leading to underpayment can result in penalties (e.g., 25-50% of the underpaid tax).
• Archiving Violations: Failure to retain documents for the full 5-year period or to maintain their integrity can result in fines for improper record-keeping.
• Enforcement: The SRC uses automated cross-checks between buyer and seller data to detect non-compliance, facilitating active and efficient enforcement.

XII. Pre-Filled VAT Returns

As of 2026, Armenia does not have pre-filled VAT returns for businesses. Taxpayers must manually compile and submit their VAT returns, although the e-invoicing system provides data (e.g., year-to-date totals) to aid this process. The SRC system does cross-verify submitted returns against the e-invoice data. While there’s potential for pre-filling given the comprehensive data collection, no official plans or timelines have been announced.

XIII. Impact on SMEs and Startups

The e-invoicing mandate has presented both challenges and benefits for SMEs:

• Challenges: Initial setup costs (digital signatures, internet access), staff training, and the burden of adapting to new technical requirements. A significant concern raised by SME associations is the “frequent e-invoice system slowdowns around filing deadlines,” which “have caused delays in transactions and cash flow,” impacting operations.
• Benefits: The provision of a free web portal by the SRC reduced software costs. Post-adaptation, SMEs benefit from simplified bookkeeping, reduced errors, and faster invoice processing. The mandate has also fostered a more level playing field by reducing the shadow economy.
• Support: No direct financial subsidies for e-invoicing compliance, but the free SRC portal and broader digital literacy initiatives (e.g., EU4Business) have provided support.
• Market Impact: Accelerated digitalization across the business environment, encouraging modern accounting practices and potentially enhancing SME credibility for financial access.

XIV. Conclusion and Key Takeaways

Armenia’s e-invoicing framework is a mature, comprehensive, and mandatory system that underpins the country’s digital tax administration. Its real-time, centralized clearance model ensures a high degree of transparency and data availability for the tax authorities.

Key Takeaways:

• Mandatory & Broad Scope: All VAT-registered businesses, B2B, B2G, exports, and increasingly transactions involving non-VAT payers are covered.
• Real-time Reporting: E-invoices are immediately cleared and reported to the SRC, serving as the primary reporting mechanism.
• Centralized Platform: All compliance activities flow through the SRC’s state-run system; no international networks like PEPPOL are used domestically.
• Digital Integrity: Digital signatures are fundamental for authenticity and integrity.
• Strict Enforcement: Penalties for non-compliance, late reporting, and archiving violations are in place and actively enforced through automated cross-checks.
• Operational Benefits & Challenges: While promoting efficiency and transparency, system stability (downtime) remains an operational concern for businesses, especially SMEs.
• No Pre-filled Returns (Yet): Taxpayers currently compile VAT returns manually, leveraging e-invoice data, but actual pre-filling is not implemented.

Businesses operating in Armenia must prioritize full integration and diligent use of the e-invoicing system to ensure compliance, avoid penalties, and leverage the operational efficiencies it offers. Monitoring SRC updates for schema changes and new features is crucial for ongoing adherence.

---

DETAILED

1. Scope of the Mandate

• E-Invoicing Obligations: Armenia requires electronic invoicing for virtually all business transactions. Since 2016, all businesses operating in Armenia must issue invoices in electronic form through the state-run e-invoicing system. This mandate covers business-to-government (B2G) invoices (for sales to public entities), business-to-business (B2B) invoices, and even business-to-consumer (B2C) sales in principle. In practice, B2C e-invoices are allowed but not strictly mandatory – retail sales to consumers are typically documented with certified cash register receipts rather than via the e-invoice portal. All e-invoices must be digitally signed by the issuer to ensure authenticity and submitted to the tax authorities electronically in real time. [armenian-lawyer.com] [ey.com]
• E-Reporting Obligations: Armenia’s e-invoicing platform doubles as an “Electronic Reporting System,” automatically transmitting invoice data to the tax authority as each invoice is issued. Therefore, separate periodic VAT invoice reporting (e.g. listing customer/supplier invoices) is generally not required – the act of issuing the e-invoice constitutes compliance with reporting obligations. Taxpayers still file periodic VAT returns, but these are based on the already reported e-invoice data. (The system’s main dashboard even displays running totals of issued invoices to facilitate tax reporting.) There is no independent “SAF-T” or summary report to send for VAT invoices, since all invoice details are captured in the central system instantly. However, certain other documents (like purchase ledgers or non-invoice documents) can be reported electronically as needed (see Electronic Books below). [arka.am] [vatupdate.com]
• Transactions in Scope: The e-invoicing mandate applies broadly to domestic transactions:
  • Domestic B2B: Yes. All sales between two VAT-registered businesses in Armenia must be invoiced electronically. The e-invoice (often called a “tax invoice”) is required for every taxable B2B sale, ensuring VAT is accounted for. (If a business under a special regime is involved, see Special Regimes below.) [armenian-lawyer.com]
  • Domestic B2C: Partially. While the law includes B2C transactions in the e-invoice framework, in practice most B2C sales (e.g. retail to individuals) are handled via fiscal cash register receipts rather than the online invoicing system. Businesses are not obliged to issue an e-invoice to a private consumer for a routine sale as long as a cash receipt is issued. However, if a consumer or the nature of the transaction demands an invoice (for example, a large B2C sale or warranty invoice), the business must issue it electronically. The e-invoicing system is capable of B2C invoicing, but it’s generally optional and used in specific cases (such as high-value consumer sales or where the buyer requests a VAT invoice). [armenian-lawyer.com] [ey.com]
  • Domestic B2G: Yes. Invoices for sales to government bodies, municipalities, and state-owned enterprises must be issued through the electronic system. Armenia made electronic invoicing mandatory for B2G supplies in 2016, aligning with public procurement transparency goals. Government agencies only accept e-invoices via the platform, ensuring real-time tax reporting for B2G transactions. [armenian-lawyer.com] [ey.com]
  • Intra-EU Acquisitions & Supplies: Not applicable. Armenia is not an EU member state, so EU intra-community supply rules do not apply. There is no concept of “intra-EU” supply within Armenian VAT law. Instead, cross-border transactions are treated as imports or exports (see below). Armenian companies trading with EU counterparts follow the same rules as any international trade partner. (For context, Armenia’s VAT system is inspired by EU principles, but transactions with EU businesses are simply foreign transactions, not internal EU operations.) Thus, no separate e-invoicing mandate exists for “intra-EU” sales/purchases beyond the normal cross-border rules.
  • Imports: No domestic e-invoice required. When goods are imported into Armenia, import VAT is levied via the customs declaration, not via an internal invoice. The foreign supplier’s invoice is used for customs, but it is not processed through Armenia’s e-invoicing portal (since the foreign supplier is not in the system). The Armenian importer does not issue an e-invoice for the import; instead, the import is reported to the tax authorities through customs mechanisms. Similarly, if a non-resident provides services to an Armenian business, the transaction is an import of services: Armenian VAT law requires the Armenian recipient to self-assess VAT (reverse charge) in their VAT return, but no electronic invoice needs to be issued internally for that (there is no formal self-billing requirement for standard reverse-charge services). The import will, however, appear in the purchaser’s accounting, and the tax authorities may require documentation (contracts, etc.) if auditing the reported reverse-charge VAT.
  • Exports: Yes (zero-rated). Exports of goods and services from Armenia must be documented with electronic invoices, just like domestic sales. Such invoices are marked with the appropriate tax treatment (generally VAT at 0% for exports of goods). The e-invoicing system includes options to classify a transaction as an export, ensuring the VAT is recorded as zero-rated and providing the required audit trail for tax authorities. For example, if an Armenian business sells to a foreign buyer, it issues an e-invoice through the system and selects “Taxable at 0% VAT” or “Export” as the Transaction Type, which is now a mandatory field for non-standard VAT rates. This way, the system captures that the sale is an export and no VAT is due. Imports and exports are fully tracked, but only the Armenian side of the trade is recorded in Armenia’s e-invoicing system (exports by Armenian sellers; imports are handled via customs as noted). [vatupdate.com]
  • Cross-Border B2B (non-EU): Yes, for the Armenian side. For cross-border transactions outside the EU (e.g. Armenia–Russia or Armenia–USA B2B sales), Armenian taxpayers must comply with e-invoicing on their side of the deal. If an Armenian company sells to a foreign business, it issues a 0% VAT electronic tax invoice (similar to an export invoice) in the system. Conversely, if an Armenian company buys from a foreign business, the foreign supplier will not be in Armenia’s system, but the Armenian buyer may need to account for VAT via reverse charge (no Armenian e-invoice, as explained for imports). Thus, all outgoing B2B invoices from Armenian entities are captured online (domestic or foreign customers alike), whereas incoming invoices from foreign suppliers are outside the Armenian platform (handled via customs or self-assessment processes). [vatupdate.com]
• Inclusion of Special Scenarios: The mandate’s scope also extends (or makes provisions) for various special invoicing scenarios:
  • Self-Billing: Permitted in specific cases. Armenian regulations allow the buyer to issue invoices on behalf of the supplier in certain situations. A key example is purchases from individuals or entities who are not registered for VAT: in such cases, the purchasing organization must draw up the invoice. Recent government measures explicitly require that when a business buys goods or services from a private individual, the business (buyer) must issue an electronic purchase document via the tax authority’s e-invoicing system. This rule, effective 1 January 2025, aims to capture those transactions in the tax system. The e-invoice platform supports self-billing: the buyer enters the seller’s details (e.g. individual’s name and ID) and issues an invoice on their behalf. Outside of the individual-seller context, self-billing for B2B transactions is not common but is legally possible with mutual agreement – for instance, if an Armenian company authorizes its customer to invoice on its behalf (such as under an agency or consignment agreement). The Tax Code provides that agents or delegates can issue tax invoices on behalf of the principal supplier if their contract stipulates that authority. In any self-billing scenario, the e-invoice must contain all the usual information and indicate that it’s issued by the buyer (often there will be a note or the buyer’s and seller’s TINs reflecting the roles). Buyer-side validation is generally built-in: the buyer is the issuer so implicitly “accepts” it, but the seller must agree in advance to this arrangement (usually via a written agreement as per tax rules). The content requirements for self-billed invoices are the same as standard invoices, and they must be transmitted through the platform and digitally signed, ensuring authenticity. There are no special notifications to tax authorities needed beyond using the system itself; the issuance in the central system is sufficient compliance. [gov.am]
  • Triangulation and Chain Transactions: No special simplification – treated under normal rules. Armenian law does not define a separate “triangulation” regime (which is an EU-specific concept) for VAT. If multiple parties are involved in a supply chain, each link involving an Armenian entity is handled like any other transaction: an Armenian business selling or buying will issue or receive the requisite e-invoice for its portion. For example, in a domestic chain transaction (A sells to B, then B sells to C, with goods moving directly from A to C), A must issue an electronic invoice to B, and B must issue an electronic invoice to C, as with any B2B sales – the physical movement can be covered by a transport document (Armenia uses e-consignment notes for goods transport), but the VAT invoices still flow separately. If a cross-border triangulation scenario occurs (e.g. Armenian company B mediates a sale between foreign company A and foreign customer C), typically Armenian B’s involvement will be treated as an export and an import: if goods never enter Armenia, B’s sale might be considered outside Armenian VAT scope, but Armenian tax rules would likely require B to document the transaction. In practice, B would issue an export invoice (0% VAT) to C and might have to account for a deemed import from A (though if goods didn’t enter Armenia, this might be outside the jurisdiction – such complex chain transactions are handled case by case). There is no dedicated triangulation simplification to avoid double taxation; instead, Armenian companies must ensure each transaction is properly invoiced or reported under existing import/export rules. The “Transaction Type” classification introduced in 2025 helps distinguish such scenarios: for instance, an Armenian intermediary can mark a sale as “Not subject to VAT” if it truly falls outside Armenian VAT scope (e.g., goods delivered abroad by a foreign supplier). In summary, triangular and chain deals are covered by the general mandate – every taxable supply involving an Armenian party must be e-invoiced, and any cross-border elements use the export/import mechanism (with 0% or no VAT as appropriate). [vatupdate.com]
  • Special VAT Regimes: Included, with some nuances. Armenia operates a “turnover tax” regime (a simplified tax in lieu of VAT) for small businesses under a certain revenue threshold (AMD 115 million annual turnover). Businesses under this regime are not registered for VAT, and historically they were not required to issue VAT invoices. However, they still had to provide receipts or “tax bills” for sales. With the digital push, even businesses under special regimes are increasingly drawn into the e-invoicing system. For example, a small business under turnover tax does not charge VAT, but if it deals with VAT-registered customers, it may need to issue electronic “tax bills” (non-VAT invoices) so the buyer has a record. The e-invoicing platform explicitly caters to this: it offers a document type called “invoice (not a tax invoice)” to be used by non-VAT payers or for non-VATable transactions. In February 2025, the SRC added a “Special Tax Regime” option in the invoice form, which must be selected if the issuer is under a special regime or the transaction falls under a special VAT treatment. This ensures such invoices are flagged appropriately (e.g., no 20% VAT). Summary: All established VAT exemptions and special schemes (like VAT-exempt sectors, margin schemes, etc.) still require an invoice in the system; the difference is that those invoices will show “Exempt” or the relevant treatment instead of 20% VAT. For instance, a travel agent using a margin scheme would issue an e-invoice but might mark it as “Other” or a special regime if instructed by SRC guidelines. Self-employed persons and small businesses on turnover tax were historically out of the VAT invoicing loop, but a new government initiative effective 2025 will require even purchase acts from individuals to be recorded electronically, effectively reducing the shadow economy in those simplified sectors. While participation in full VAT e-invoicing remains optional for turnover-tax payers (since they don’t charge VAT), the direction is toward full coverage, either through e-invoices or other e-reporting of their sales. There are no separate optional e-invoicing models besides the official system – all taxpayers, regardless of regime, are encouraged or required to use the central platform for any invoices or similar documents they issue. [vatupdate.com] [gov.am]

(Sources: Tax Code of RA; Government of RA Resolution No. 1257-N (2017); RA State Revenue Committee official site; EY Global E-invoicing Tracker; Law firm analysis; VATupdate news on new “Transaction Type” field; Official news on extending e-invoicing to purchases from individuals.) [src.am] [ey.com] [armenian-lawyer.com], [armenian-lawyer.com] [vatupdate.com] [gov.am]

2. Taxable Persons in Scope

• Established Entities (Residents): All businesses legally established in Armenia are in scope. The e-invoicing mandate covers “organizations and individual entrepreneurs” registered in Armenia, which includes companies (of any size or industry) and sole proprietors**. From large corporations down to small family businesses, if they engage in transactions that require an invoice under VAT law, they must issue it via the electronic system. Notably, since 2016, no general size-based exemption exists – even SMEs are expected to comply (see Section 12 for SME considerations). Certain non-corporate taxable persons like notaries are also included (notaries in Armenia have special tax status but must issue electronic tax documents for their services as prescribed). In practice, any VAT-registered taxpayer in Armenia falls under the e-invoicing system obligations, and even those not registered for VAT (e.g., under threshold) may need to use the system when issuing documents (using the “tax bill” functionality for non-VAT invoices). The State Revenue Committee (SRC) has made the e-invoicing platform available to all resident taxpayers via its “File Online” portal, ensuring even the smallest businesses can access it with an internet connection and digital signature**. [armenian-lawyer.com], [digtechs.com] [src.am]
• Non-Established Entities with VAT Registration: Included. If a foreign or non-resident business registers for VAT in Armenia (for example, through a local tax representative or by having a fixed establishment for VAT), it is treated like a domestic VAT payer for compliance purposes. Such a non-established but VAT-registered entity is required to use the Armenian e-invoicing system for any invoices it issues under its Armenian VAT number. This scenario might occur if, say, a foreign company trades in Armenia without a legal presence but opts (or is required) to register for VAT. Once registered, that company will be given access to the e-invoice portal (a tax identification number and credentials) and must issue electronic tax invoices for its Armenian transactions just as a local company would. In summary, possessing an Armenian VAT registration brings a company into the scope of e-invoicing obligations, irrespective of where the company is headquartered. A recent example is the introduction of an e-VAT system for non-resident providers of digital services: as of 2022, foreign companies supplying e-services to Armenian consumers must register for Armenian VAT and file returns. However, those non-resident e-service suppliers use a special portal for VAT returns (the “eVAT” system) rather than issuing Armenian tax invoices to each customer. For B2B activities though, if a non-resident has an Armenian VAT number, they issue e-invoices in the main system. There is no separate category for non-established taxpayers – once in the system, they follow the same rules as local firms (with the possibility of using foreign addresses in the invoice fields, etc., as needed). [iota-tax.org]
• Foreign Entities without Fixed Establishment: Generally out of scope (unless voluntarily registering or in digital services scheme). A fully foreign entity with no Armenian VAT registration and no establishment in Armenia is not directly subject to Armenia’s e-invoicing requirements. Such a company would not have access to the Armenian e-invoicing platform and is not obligated to issue Armenian tax invoices. Instead, the compliance burden in cross-border transactions falls on the Armenian side (e.g., the Armenian importer accounts for VAT via customs or reverse charge, as outlined in Section 1). For example, if a German company sells goods to an Armenian business, the German company will issue its normal commercial invoice (outside the Armenian system), and the Armenian buyer will handle import VAT via customs – the German firm doesn’t log into SRC’s system. Exceptions/Changes: The one notable exception is for non-resident sellers of electronic/digital services to Armenian customers, as mentioned. Since January 2022, such non-residents are required to register and remit VAT on B2C digital sales in Armenia. They use a simplified online system to declare and pay VAT quarterly, but they do not issue Armenian e-invoices to each customer. Apart from that digital services regime, foreign companies without Armenian registration have no invoicing obligations within Armenia. (If a foreign entity wishes to streamline cross-border invoicing, it can optionally register in Armenia or work with the Armenian buyer to have the buyer self-bill the transaction, but these are business decisions rather than legal requirements.) In summary, the e-invoicing mandate targets persons “considered as taxpayers” in Armenia – if a foreign company is not a taxpayer under Armenian law, the mandate does not apply to it. [iota-tax.org]
• Exemptions and Sector-Specific Rules: Armenia’s e-invoicing rules apply across all sectors, with few exemptions. There are no industry-wide carve-outs: for instance, financial institutions and insurance companies (which mostly provide VAT-exempt services) still have to issue e-documents like tax invoices or cash receipts for their activities, although they typically fall outside VAT. In such cases, they would issue invoices marked “Exempt from VAT” in the system rather than paper documents. One exemption involves certain low-value transactions: small cash sales to unregistered persons can be documented with point-of-sale receipts and may not require a full electronic invoice if below specified thresholds (the SRC has set small thresholds for when a simplified receipt suffices, often for retail scenarios). Another narrow exemption is for transactions involving state secrets or special security considerations – these may be excluded from the standard e-invoicing due to confidentiality, requiring special handling or permission from authorities. Aside from these cases, almost all taxable persons and transactions are included. Participation in e-invoicing is effectively mandatory for those in scope, not merely optional, except that non-VAT-registered businesses and purely B2C traders remain largely outside the system by virtue of not issuing VAT invoices. There is no voluntary opt-out for those who are required by law to use e-invoicing – compliance is enforced as the norm. Conversely, there is nothing stopping a company from voluntarily using the e-invoicing system even when not strictly required, if it finds it convenient. For instance, a small business under the VAT threshold might still choose to register for VAT and use e-invoices to appear more “official” or to allow its customers to deduct input VAT – this is a business choice but once registered, it’s fully in scope. In summary, all taxable persons either required or electing to be in the VAT system fall under Armenia’s e-invoicing framework, with virtually no sector-based exemptions apart from specific legal exceptions (e.g., confidential transactions). [vatupdate.com] [armenian-lawyer.com]
• Optional Participation Models: Because Armenia’s approach is essentially all-in with a single national platform, there aren’t multiple models to choose from (like no parallel private clearances or different formats – everyone uses the SRC’s system). Companies do have flexibility in how they integrate (they can use the free web interface or invest in ERP integration via the system’s API and XML specs), but they cannot opt out of using the system itself. One notable point of flexibility is that taxpayers can authorize third-party providers or accounting software to interface with the e-invoicing system on their behalf (with proper credentials). Many larger companies use software that connects to the SRC system’s web services, allowing automatic invoice issuance from their ERPs – in these cases a certified provider or in-house IT solution helps them comply. Small taxpayers can simply log into the government portal and issue invoices manually, free of charge. There is also an option to voluntarily register early: before 2016’s mandate, some companies had joined the system voluntarily, and even now a business that newly enters the VAT system partway through the year must start e-invoicing right away (there’s no waiting period). So while participation is largely mandatory, the government has provided multiple means of participation (web portal, API, etc.) to accommodate different taxpayer capabilities. [src.am]

(Sources: RA Tax Code (articles on taxpayer obligations); SRC guidance on e-invoicing scope; VATupdate/EY summaries confirming no sector exemptions; Armenian-lawyer commentary on special cases; IOTA news on non-resident e-VAT scheme.) [arlis.am] [digtechs.com], [src.am] [ey.com] [armenian-lawyer.com] [iota-tax.org]

3. Implementation Timeline

• 2010 – Pilot Introduction: Armenia’s journey to e-invoicing began over a decade ago. In 2010, the government launched electronic invoicing on a limited scale. This initial phase targeted large taxpayers and financial institutions, introducing the concept and infrastructure. Participation at that time was not yet universal or mandatory, but it allowed the tax authorities (the SRC) to develop the system and iron out technical issues with a manageable user group. The focus was on high-volume taxpayers where e-invoices would yield the greatest immediate impact on VAT compliance. [digtechs.com]
• 2014–2015 – Legal Framework Development: In preparation for a wider rollout, Armenia passed necessary legislation in the mid-2010s. The effort culminated in the adoption of a new Tax Code on 4 October 2016, which included provisions making e-invoicing mandatory. Additionally, Government Resolution No. 1257-N of 5 Oct 2017 was issued to lay down detailed rules for the electronic invoicing system (sometimes referred to as the “Electronic Accounting Documents” system). This resolution and subsequent amendments provided the technical and procedural backbone (data fields, process for issuance/cancellation, etc.) needed for full implementation. [src.am]
• 2016 – Nationwide Mandate: Effective January 2016, e-invoicing became mandatory for all VAT-registered businesses in Armenia. This represented a major expansion from the earlier phases. From this point, any company or entrepreneur issuing VAT invoices had to do so electronically. The 2016 mandate covered B2B and B2G transactions as compulsory, with B2C encouraged (and receipts for B2C also increasingly electronic via cash registers). The transition was significant: many medium and small businesses came on board the e-invoicing platform around this time. There was no lengthy phased schedule by sector or size – essentially a blanket mandate – although practical enforcement may have ramped up over months. Note that B2C remained effectively voluntary (hence EY’s tracker lists B2C as “Allowed but not mandatory” as of 2016), but B2B/B2G compliance was expected from 2016 onward. [digtechs.com] [ey.com]
• 2016–2022 – System Evolution: Following the mandate, the system continued to evolve. From 2016 through the late 2010s, Armenia used an application-based system often known as “e-invoicing 3.x”, which sometimes required installing a software or using an XML upload. Taxpayers obtained digital signature tokens and used them to sign invoices either via the SRC’s software or web interface. During these years, numerous refinements were made: for example, new features to handle invoice adjustments, credit notes, and search functionalities were added. By 2018, minor amendments (like Gov. Decision 648-N of June 2018) adjusted some e-invoicing rules, reflecting feedback from initial years. Enforcement also solidified: businesses routinely faced penalties if caught issuing paper invoices outside the system.
• June 1, 2023 – New System Launch: A significant milestone was the deployment of an upgraded online e-invoicing platform in mid-2023. The SRC announced that the “Electronic Invoicing system has been in operation since June 1, 2023” in a new form. This was essentially a modern web-based portal integrated with the broader “File Online” tax system. The new system unified return filing and invoice issuance in one interface. It allowed users to issue, adjust, void, and sign invoices entirely online without additional local software (previously some may have used offline tools). It also improved user experience and incorporated up-to-date security (like integration with the national digital ID platform ID. This transition aimed to make compliance easier and more reliable. By 2023, Armenia had one of the region’s most comprehensive digital compliance ecosystems (with e-invoices for businesses and e-filing for individuals – the “universal declaration” system for personal taxes also came fully online by 2023). [src.am]
• 2024 – Extension to Turnover Tax Transactions: In March 2024, the government approved an important extension of the e-reporting requirements to cover transactions by turnover-tax payers (small businesses) with individuals. A government session on 21 March 2024 decided to introduce an electronic platform for purchase documents from individuals to be issued by the buying company through the e-invoicing system. This effectively means that starting 1 January 2025, whenever a business on a simplified regime buys goods or services from a private individual, that purchase must be documented electronically (the business will self-issue an e-invoice for it). This timeline – adoption in March 2024 with effect from Jan 2025 – gave affected taxpayers some lead time to prepare. It is part of the government’s strategy to reduce the shadow economy in the small business sector by capturing more transactions digitally. [gov.am]
• 2025 – System Enhancements: The year 2025 saw further refinements rather than new mandates. The SRC introduced new data fields and interface improvements to the e-invoicing system effective March 1, 2025. This included updates to the XML schema (XSD) used for invoices, with technical documentation provided to software integrators. A notable functional change (rolled out in early 2025) was the addition of a “Transaction Type” field when issuing an invoice. From 2025 onward, issuers must categorize the nature of each invoice if it’s anything other than standard 20% VAT. For tax invoices, the options under this field are “Taxable at 0% VAT”, “Exempt from VAT”, or “Other” (one of these must be selected if 20% VAT is not applied). For regular invoices (non-VAT invoices), the available types are more granular: “Special Tax Regime”, “Taxable at 0%”, “Exempt”, “Not subject to VAT”, “Export”, “EAEU Air Transport Export”, and “Non-VAT Payer”. Filling this field became mandatory as of 2025, helping the SRC automatically classify transactions (e.g., distinguish an export from a domestic exempt sale). Along with that, the system update allowed multi-TIN searches (up to 100 TINs) in invoice queries and displayed year-to-date totals of invoices on the dashboard – features meant to assist taxpayers in tracking compliance. These changes were communicated by the SRC and on platforms like VATupdate in Q1 2025. There was no new “go-live” mandate date in 2025 (since the system was already live), but these technical tweaks effectively became new requirements from Q1 2025 that businesses had to follow (with a de facto grace period as everyone adapted to the new fields). [src.am] [vatupdate.com]
• Grace Periods and Sector Phasing: Armenia’s implementation did not heavily rely on extended grace periods. When e-invoicing was mandated in 2016, businesses were expected to comply immediately, though in practice the tax authority likely used a light-touch enforcement for a short time – focusing on education and warnings in early months. There is evidence that some leniency was given: for instance, technical issues in the early rollout were taken into account. However, unlike some countries that phase in different sectors over years, Armenia’s approach was more “big bang” for 2016. One exception is the turnover tax e-platform in 2025: since it’s a new requirement, authorities might show flexibility initially (and indeed they announced it 9+ months ahead). No formal multi-year sector-by-sector timeline exists beyond what’s described (2010 limited intro → 2016 all businesses → thereafter refining).
• Future Outlook: As of early 2026, Armenia has a stable, mature e-invoicing regime in place. The main upcoming “timeline” considerations involve international developments – for example, the EU’s “VAT in the Digital Age (ViDA)” initiative might influence Armenia if it chooses to align or if Armenian companies trading with the EU need certain formats (PEPPOL, etc.), but so far, no official Armenian timeline for such integration exists. Another potential future step could be pre-filled VAT returns (discussed in Section 11) or further real-time reporting expansions; however, no fixed dates have been set for those. In summary, the critical dates have already passed (2016, 2023, 2025) and Armenia’s e-invoicing is fully in force. Businesses should stay alert for incremental updates (the SRC periodically updates schemas and rules, often effective at the start of a calendar year or quarter, as seen in 2025). [src.am]

(Sources: Digital Technologies Armenia profile (timeline); SRC announcements; VATupdate news; Government press release Mar 2024; EY tracker (confirms 2016 mandate); Tax Code adoption date.) [digtechs.com] [src.am] [vatupdate.com] [gov.am] [ey.com]

4. Technical & Functional Requirements

• E-Invoice Format: Armenia’s e-invoices are generated in a structured electronic format (XML) defined by the State Revenue Committee. The SRC provides an official XML schema (XSD) that all e-invoices must conform to. This schema is specific to Armenia’s requirements (sometimes referred to as the “Electronic Accounting Document” schema). The format captures all the required data elements of an invoice in a machine-readable way. While it is XML-based, it is not explicitly stated to follow a global standard like UBL or PEPPOL BIS; rather, it is a local schema aligned with Armenian Tax Code provisions. Taxpayers using the web portal don’t need to manually handle XML – they fill out web forms and the system generates the XML behind the scenes. Those integrating via API upload XML files (or use web services) structured per the XSD. The system also allows invoices to be downloaded in XML or PDF for archiving or human reading. In summary, the format is XML with a prescribed XSD, ensuring standardized structure. (Older versions of the system had downloadable software for invoice entry which produced .xml files to upload, but now it’s largely online.) There is no provision for unstructured formats like PDF or paper – an invoice must exist as a compliant XML record in the central system to be considered issued. [src.am]
• Mandatory Data Fields (Content Requirements): Each e-invoice must include all information required by Armenian law (which mirrors typical VAT invoice content). Mandatory fields include:
  • Invoice identification: Series and serial number of the invoice (the system usually generates a unique serial number for each invoice; traditionally, Armenian invoices have a prefix and sequential number). This uniquely identifies the invoice and is used for verification on the SRC’s public portal. [src.am]
  • Date and time of issuance. The platform timestamps the invoice. The invoice date field is mandatory and must reflect when the invoice is issued.
  • Supplier details: Taxpayer Identification Number (TIN) of the supplier (if the supplier is VAT-registered, this is their VAT number), full legal name of the organization or entrepreneur, and the address of the business (location and, if different, place of business). The system auto-fills many of these based on the supplier’s registration. The supplier’s digital signature is attached to authenticate the data. [armenian-lawyer.com]
  • Customer details: If the buyer is a business or registered person, their TIN and name and address must be included. For sales to individuals not registered for VAT, the invoice should include the person’s full name, and an identifier like a passport or ID number and address (the system may prompt for these if an individual’s TIN is not applicable). In B2C cash sales where an e-invoice is not issued, customer detail requirements don’t apply; but for any e-invoice, some customer info is mandatory – even if it’s “NOT REGISTERED – <name>”.</name>
  • Line item details: A description of each product or service supplied. This includes item name, any product code or description, quantity delivered, unit of measure, and unit price. The total amount per line (quantity × unit price) is calculated, with separate lines for each item. If an item is subject to special VAT (like exempt or 0%), it can be indicated line by line or at invoice level (Armenian invoices often indicate VAT rate per line).
  • Tax amounts: The invoice must show the applicable VAT rate (standard 20%, zero, exempt, etc.) and the VAT amount for each taxable line. If the whole invoice is 0% or exempt, it will show 0 in VAT fields but must still denote the category (via the new Transaction Type or by text). The system enforces that if 20% VAT is not selected, the user must select the reason/category (as of 2025). For standard-rated sales, selecting 20% auto-calculates the VAT. The net amount and gross amount are also shown, typically in Armenian Drams (AMD) since invoices are usually denominated in AMD (if in foreign currency, possibly an AMD equivalent or note is needed according to law). [vatupdate.com]
  • Invoice totals: The total taxable base, total VAT, and invoice grand total must be included. The system aggregates line items to display these.
  • Additional mandatory info: The Tax Code specifies certain requisites. For example, serial number of the invoice (as mentioned), and in cases of special transactions, additional fields like contract number or customs declaration number for exports can be required. If the invoice is an adjustment (credit/debit note), it must reference the original invoice series and number it’s correcting. The system likely has dedicated fields for referencing an original invoice when issuing an “Adjusting tax invoice”.
  • Digital signature / seal: While not a field per se, each e-invoice must be electronically signed by the issuer using an authorized digital certificate. This signature and the time-stamp are attached to the invoice data to ensure integrity. The presence of a valid signature is a legal requirement; unsigned electronic data wouldn’t count as a legal invoice. [armenian-lawyer.com]
  • Other fields: Invoices must also contain delivery details for goods (if goods are delivered, the address of delivery or consignment note is typically linked). For services, often the act of acceptance date may be needed if different from invoice date. There’s also often a field for “document type” (tax invoice vs simple invoice vs credit note, etc., chosen from the system menus). The Transaction Type field (as of 2025) is now mandatory when relevant (as described, e.g. marking “Export” or “Exempt”). Finally, certain transactional specifics may be required: e.g. if the invoice is a VAT refund invoice (for tourists, etc.), or an excise goods invoice, those details must be present. According to the Tax Code’s list, documents like “tax invoice of VAT refund” and transport “consignment notes” have their own fields, but those are special cases. Generally, the data model is comprehensive: if a piece of information is legally required on a paper invoice, it is a mandatory field in the e-invoice form. The system performs validations (e.g., you cannot leave required fields blank; numeric fields must be positive, etc.) to enforce completeness. [vatupdate.com] [src.am]
• E-Reporting (Data Model and Fields): Apart from the invoice itself, Armenia’s digital system also handles reporting of summary data, particularly through what were historically called “electronic ledgers” (sales and purchase books). In the current platform, much of this is implicit – since every invoice issued is recorded, the system can compile the taxpayer’s VAT sales ledger and purchase ledger automatically. The structure of e-reporting data follows the invoice data model: for instance, the “sales ledger” is essentially a list of all issued tax invoices with key fields (buyer, amount, VAT, etc.). The mandatory fields for e-reporting thus mirror those of the invoices. When businesses file their VAT return (monthly or quarterly), the system likely cross-checks declared totals against the sum of e-invoices. In terms of format, any exports of data (like downloading one’s transactions) can be done in Excel or PDF, but internally the system’s data model covers all needed fields (TINs, dates, categories, etc.). There are also validation rules built in: for example, the system will not allow an invoice with arithmetical inconsistencies or missing critical info to be finalized. If a user tries to submit an invoice with an error (say, a required field not filled, or letters where numbers are expected), the system will flag it and refuse to issue until corrected. This reduces reporting mistakes. Additionally, if a buyer’s TIN is entered, the system might automatically fill the buyer’s name and address (pulling from the tax registry) to ensure accuracy. [src.am]
• Digital Signature & Integrity: Digital signatures are a cornerstone of Armenia’s e-invoicing. Every invoice must be signed using a certificate issued by an authorized provider. Most companies use a USB token or a cloud/mobile ID to sign within the portal. The signature ensures the integrity and authenticity of the invoice – any alteration to the data after signing would invalidate the signature. Armenian law considers a properly signed electronic invoice as legally equivalent to a signed paper invoice. As a further integrity measure, the SRC provides a service to verify an e-invoice’s authenticity by its serial number on a public webpage. Anyone (e.g., the buyer or an auditor) can input the invoice number and confirm its status and details, which guards against fraud. The system also maintains audit logs – each invoice has timestamps for creation, signing, and (if applicable) acceptance by the buyer or any adjustments. These technical controls meet the requirements for guaranteeing that electronic tax documents remain unaltered, legible, and authentic over time, as mandated by law. [armenian-lawyer.com] [src.am]
• Real-Time/Near-Real-Time Processing: Armenia’s e-invoicing functions on a near-real-time clearance model. In practice, when a supplier issues an invoice on the platform, that invoice data is immediately registered with the tax authority. For B2B invoices, the buyer typically can see the invoice in their account almost instantly after issuance. Legally, invoices should be issued at the time of supply or shortly thereafter, so the reporting to SRC happens virtually in real time (there isn’t a monthly delay; each invoice is transmitted on issue). Some deadlines exist: for example, if an invoice is issued late (after the fact), it could violate the timely reporting requirement – but the system design itself encourages immediate issuance. There is no T+1 or T+5 day delay explicitly allowed for VAT invoices: they are effectively cleared as they are created. Invoices are available for tax inspection right away, and the system’s stability is thus critical (downtime is troublesome as noted in Section 12). For certain monthly summary reports, since each invoice is already reported, taxpayers mainly just compile their VAT return from that data. The VAT return (Unified Calculation for VAT) is due by the 20th of the following month, which is when any reconciliation occurs. However, no separate monthly invoice listing needs to be sent, because the tax authority already has an invoice-by-invoice feed. The only exception might be monthly summaries for non-VAT small businesses (e.g., they might submit a monthly total of turnover if not invoicing each sale), but with moves to bring even those onto the platform, the need for manual summary is reducing. In summary, the system provides real-time clearance and storage of each invoice, fulfilling both the invoicing and reporting function simultaneously.

(Sources: RA Tax Code Article 55 (invoice content); SRC technical documentation and announcements; Armenian-lawyer overview (technical requirements); VATupdate on new mandatory fields; SRC portal behavior and user guidelines.) [src.am], [src.am] [armenian-lawyer.com] [vatupdate.com]

5. Correction of Errors in E-Invoices and E-Reporting

• E-Invoice Corrections: Mistakes can happen on issued invoices (wrong amount, wrong buyer details, etc.), and Armenia’s system provides mechanisms to correct them in compliance with the Tax Code. There are two primary ways to correct an e-invoice: invalidation (cancellation) or adjustment via credit/debit note.
  • Invoice Invalidations (Cancellation): If an invoice was issued with a serious error or by mistake (for example, a duplicate invoice, or an invoice to the wrong customer), the preferable immediate remedy is to “declare the invoice invalid” in the system. The e-invoicing platform has a built-in function to void or cancel an invoice that has been issued. According to Article 56 of the Tax Code, an organization may void a settlement document, and once declared invalid, that invoice is no longer effective. In practice, cancellation is typically allowed before the buyer has accepted or used the invoice (e.g., before they’ve claimed input VAT on it). The issuer finds the invoice in the system and uses the “Invalidate/Cancel” option, providing a reason if required. The system then marks that invoice as cancelled (and if one tries to verify it by serial number, it would show as void). After invalidation, the supplier would then issue a corrected new invoice with a new number. Note that there are time limits: an invoice generally can’t be cancelled years after the fact. Armenian law prevents issuing or adjusting invoices beyond a certain period (no new invoice or adjusting invoice can be issued if more than 3 years have passed since the original transaction’s tax period). So, cancellations are meant for relatively prompt corrections. If an error is caught quickly (e.g., same day or month), cancellation + reissuance is cleanest. Both the seller and buyer’s ledgers update accordingly – the cancelled invoice is flagged (not counted in totals) and the new invoice replaces it. [src.am]
  • Credit and Debit Notes (Adjusting Invoices): If an invoice error is discovered later or needs partial adjustment (for instance, the price was wrong or goods were returned), the solution is to issue an “adjusting tax invoice” – effectively a credit note or debit note recorded in the system. Armenian Tax Code explicitly recognizes “adjusting tax invoice” and “adjusting tax bill” as document types. To correct an overcharge or to cancel part of an invoice, the supplier issues a credit note (adjusting invoice with negative values to reduce the original amount). To charge an additional amount (underbilled previously), a debit note (adjusting invoice with positive additional amount) is issued. The e-invoicing system supports this: the user would typically select the original invoice being adjusted (linking the two) and create an adjusting document referencing it. The adjusting invoice must contain the reference to the original invoice number and date, as well as the specific corrections (e.g., “-5 units” or “-AMD 10,000” for a returned item). It also carries its own unique number and date. Both the original and the adjustment remain in the system, and the combination of the two is considered the final accounting. For example, if Invoice #100 had AMD 50,000 too much, a Credit Invoice #100-C could be issued for -AMD 50,000, referencing #100. The buyer’s input VAT and seller’s output VAT are adjusted accordingly in real time. Credit notes require the same content as regular invoices (issuer/recipient, item description of what’s being corrected, etc., plus a note it’s a correction).
  • Process for Issuing Corrections: In summary, if an error is noticed before the tax period closes and the invoice hasn’t been used, cancellation and reissue is common. If the invoice has already been accounted for (or if only part of it is wrong), an adjustment note is issued. Armenian businesses often use terms like “credit invoice” for these adjustments. The platform makes this straightforward: one finds the original invoice and selects “Adjust” or “Issue credit note,” fills in the correction details, and signs it. The buyer will receive the notification of the adjusted invoice in their interface.
  • Details to Include in Corrections: A corrective document must include a clear reference to the original invoice (usually original invoice series/number and date) and an explanation of the correction (some systems have a free-text field for reason or a code for why – e.g., “return of goods,” “price correction”). The Tax Code requires that the original and any adjusting invoices together reflect the true transaction. For credit notes, typically negative quantities or amounts are used. For debit notes, additional lines or positive adjustments are added. The mandatory fields of an adjusting invoice are the same as a normal invoice (with the issuer, receiver, etc., identical to the original), plus the reference info.
  • Resubmitting Corrected Invoices: After cancellation, the only way to “correct” is to issue a brand new invoice (with a new number) as noted. After a credit/debit note, there’s usually no need to reissue the original – the combination serves as the correction. The buyer, when filing VAT, will net out the original and credit note. The e-invoice system automatically accounts for adjustments in the aggregated data. If an invoice is cancelled, that number is retired; one cannot reuse the same number – one simply issues a replacement with a new number. All corrected or cancelling documents are stored by the system, creating a full audit trail for the tax authorities.
• E-Reporting Corrections: Since “e-reporting” of invoices is integrated with issuance, corrections to the invoices (as above) inherently correct the reported data. However, if there are errors in periodic reports (like a VAT return) or in how data was reported beyond just invoicing, taxpayers must address those via formal amendment procedures:
  • Incorrect VAT Reporting: If a taxpayer realizes that a filed VAT return (which summarizes the e-invoice data) is incorrect – for instance, a transaction was missed or recorded wrongly – they may need to submit an amended return for that period. Armenian law allows corrections to tax returns under certain conditions. Typically, a corrective (adjusted) VAT return can be filed before the tax audit or within the statute of limitations (5 years) as long as it’s not to claim a refund after deadlines, etc. There is a deadline: returns that would reduce tax liability usually cannot be amended after 3 years have passed. But if the error increases tax, one is always expected to correct it and pay the difference (with potential penalties). The process is to fill out a new version of the return marked as “amended” in the File Online system. The SRC’s File Online portal automatically checks calculations, so any resubmission would be validated for consistency. [src.am]
  • Notifying Tax Authorities: There is no separate form just to say “oops, I reported wrong” – the act of filing an amended return or issuing an adjusting invoice is the notification. If a significant error is found (e.g., a large sale was omitted entirely from e-invoicing), the business should immediately issue the missing e-invoice (back-dated to the actual date of supply) and that will enter the system (though late). Then they would inform the tax authority by adjusting their VAT return or, if the period is closed, possibly via a letter. The SRC generally picks up discrepancies (since purchase invoices claimed by customers won’t match a seller’s sales if something is missing), so proactive correction is advised to avoid penalties.
  • Formal Correction or Amendment Requirements: For invoices – use credit/debit notes as described, no separate permission needed (except outside certain time frames you cannot adjust). For tax returns – if within the same month, you can usually just update before the due date. After filing, an amended declaration must be submitted. The Tax Code stipulates that if an error is discovered, the taxpayer may submit a corrected calculation for past periods, but not in some cases beyond statutory deadlines. If the amendment is after the due date, and it increases tax due, the taxpayer should pay the shortfall with interest; if it decreases tax due, the amendment might trigger scrutiny. Typically, Armenia does not require a special “correction form” outside the standard return – one just resubmits the VAT return form for that period with corrected figures (and the system labels it revision #2, etc.).
  • Specific Forms for Error Corrections: There are no unique forms specifically titled “error correction” for invoices; the standard invoice document doubles as the correction when used in adjustment mode. For reporting, as mentioned, the standard VAT return form is reused. One exception: if the error relates to something like wrong taxpayer info (like using wrong TIN), earlier one had to notify tax authorities to unlock changes. But with the electronic system, if, say, you invoiced the wrong TIN, you’d cancel and reissue correctly.

In summary, corrections in Armenia’s e-invoicing system are handled within the system – by canceling or adjusting invoices – and corrections to reported totals are handled by amending the relevant declarations. It’s important to act within allowed timeframes: the law currently prohibits issuing any new or adjusting invoice for a transaction once three tax years have passed since that transaction’s year (in other words, you can’t correct an invoice from 4+ years ago; it’s locked in record). For errors discovered very late, companies might have to address it through other means (like disclosures to tax authority). Usually, however, mistakes are caught during the periodic reconciliation, and the electronic system has greatly reduced errors by validating data upfront.

(Sources: RA Tax Code Article 56 on invalidation; Article 55 on adjusting invoices; SRC portal features; Armenian tax practice guides. VATupdate summary notes introduction of features for adjustments. General knowledge of amendment processes. Note: The specific forms nomenclature comes from general SRC processes.) [src.am] [vatupdate.com]

6. Transmission & Workflow

• Transmission Model: Armenia’s e-invoicing uses a centralized clearance platform operated by the State Revenue Committee. All e-invoices are issued on or transmitted to the SRC’s online system, called the “Electronic Invoicing System” (accessible via the File Online portal). This means the supplier must upload or input the invoice data to the central platform, which then clears (registers) the invoice and makes it available to the buyer and the tax authority simultaneously. There is no standalone “post-audit” model where businesses just keep their own e-records; instead, invoices are effectively routed through the tax authority’s system in real time. [src.am]
• Interoperability: Because all taxpayers use the same government platform, the need for an interoperability framework (as seen in the EU’s PEPPOL network) is minimal. Armenian e-invoices are not generally sent from one company’s system directly to another’s; rather, both parties access the invoice via the central system. The buyer can log in and see all invoices issued to them. If companies use ERP software, they integrate via API to send data to the SRC system, but still the exchange happens on the central hub. So, the model is “issuer uploads to central hub; recipient downloads from central hub.” There isn’t an email or peer-to-peer exchange of structured invoices – the tax portal is the exchange medium. Consequently, no separate accredited service provider network is needed as in some countries. The SRC is the sole clearinghouse, though businesses may employ IT providers to help interface with it (e.g., software companies that build connectors). Those providers must adhere to the SRC’s API specs, but they are not issuing invoices independently – they act as technical facilitators.
• Role of Service Providers: While the government hasn’t designated private clearing companies (like Italy’s SDI or France’s Chorus are government-run too), third-party software can be used. Some local tech companies and accounting software have built modules to interact with the SRC e-invoice API. These act as value-added service providers (e.g., offering better ERP integration, automated invoice generation) but they are not separate clearance platforms – all data still flows to the SRC. The SRC does not require a specific accreditation for software; it simply publishes the interface and XSD, and any software that conforms can be used. Companies remain responsible for the invoices sent through any intermediary. In summary, Armenia’s model is effectively central clearance with optional use of software providers to connect to it.
• Use of PEPPOL or International Networks: At this time, Armenia does not use the PEPPOL network or similar international e-invoicing gateways. The e-invoices are exchanged only within the national system. As such, foreign companies or systems cannot directly send invoices into the Armenian system unless they register for Armenian taxes and use the portal. There is no cross-border interoperability implemented yet (though Armenian authorities monitor EU developments, no adoption of the European standard invoice format has been announced for domestic use).
• Transmission Workflow: The typical workflow for a B2B invoice is: the seller prepares the invoice electronically (either via manual entry on the SRC portal or by sending data from their system to SRC’s API); the invoice is assigned a unique sequential number and timestamp by the system; the seller digitally signs it and submits; the SRC system validates it (ensuring required fields are present and values make sense); once accepted, the invoice is considered issued. The buyer then can log in and retrieve the invoice – often buyers will simply download a PDF for their bookkeeping or get the data via API into their own systems. The buyer may also have to “acknowledge” or accept the invoice in the system (the Armenian system does allow the buyer to dispute or reject an invoice if, for example, it was issued incorrectly – e.g., if they never received the goods). If an invoice is rejected, the workflow would involve the seller correcting and reissuing it. [src.am]
• Deadlines for Transmission: Real-Time Reporting: By design, the system encourages immediate issuance. Legally, invoices should be issued at the moment of taxable supply or service completion. Thus, in effect, reporting is real-time – when you issue, you report. If for some reason an invoice cannot be issued at that exact moment (e.g., system downtime or internet issues), it should be done as soon as possible thereafter. The tax law likely requires invoices to be issued no later than within 5 days of the transaction or by month-end (exact wording aside). But since customers need invoices to claim VAT, there’s business pressure to issue quickly. There is no separate “T+1” rule explicitly, but common practice is to issue invoices the same day or shortly after delivery. For B2G invoices, government contracts might even stipulate that the invoice must be in the system within a certain number of days after delivery of goods/services for payment processing.
  • T+1 or T+? Reporting: In contrast to some systems where you report invoice data the next day or in batches, Armenia’s system effectively reports instantly. One might say it’s T+0. However, if we interpret “e-reporting” to also include reporting of monthly totals for certain operations: For example, transactions with individuals by turnover-tax payers, which from 2025 must be reported, have a deadline: the new rule says those purchase documents from individuals should be issued electronically instead of at year-end on paper. The government’s decision effective Jan 2025 implies that by that date businesses must use the system for those, rather than compiling later. It doesn’t give a ‘T+’ per se, just that come 2025 all such purchase acts must be immediate in e-system. [gov.am]
  • Monthly Summaries: For some data like zero-rated export sales or certain exempt sales, historically companies submitted monthly statements (e.g., listing all export invoices when claiming VAT refunds). With e-invoicing, the SRC already has that detail, so dedicated summary forms are largely obsolete. However, if any summary report is needed (for instance, packaging waste fees or other non-VAT info), those are separate. In terms of tax, VAT payers file a monthly VAT return by the 20th which is effectively a summary of all invoices. That return presumably can be pre-checked against the invoice database. There is no additional requirement to upload an Excel of sales or purchases; the e-invoice system supplants that.
• Workflow for E-Reports (if any): Outside of invoices, if we consider “e-reporting” as electronic submission of other tax info: the File Online system also handles tax returns electronically. All periodic tax reports (VAT, profit tax, etc.) are filed online and the system checks them. So the workflow there is: fill out the return on portal or upload, system validates calculations, then submit with digital signature. These returns incorporate the invoice data indirectly. [src.am]

In summary, the workflow is highly centralized and instantaneous. A business either uses the SRC web interface or their own software to transmit invoice data via API to the SRC. The SRC system immediately processes and logs the invoice, making it available to the buyer and tax authority. Buyers often do not need to take action beyond perhaps acknowledging and then including the invoice in their VAT deduction calculations. There are no periodic batch uploads or third-party networks – everything goes through one government system in real time.

(Sources: SRC official description of e-invoice system; EY description (tracker) confirming clearance model; Government news on new platform for small purchases. The absence of multi-gateway is confirmed by local sources and lack of any mention of PEPPOL in Armenia. The VATupdate article hints at real-time changes (immediate reflection of totals).) [src.am] [ey.com] [gov.am] [vatupdate.com]

7. Self-Billing

• Permissibility of Self-Billing: Yes, self-billing is permitted under Armenian tax law in certain scenarios. Self-billing means the buyer issues the invoice on behalf of the supplier. While not the standard practice for most transactions, Armenian regulations explicitly allow it in defined cases. One prominent case is when purchasing goods or services from individuals or entities that are not themselves set up to issue invoices. For example, if a company buys agricultural produce from a farmer who isn’t an entrepreneur, or any purchase from a private individual, the buying organization must generate the invoice (purchase document) electronically. This is effectively mandated self-billing. Another case is under agency or commission relationships: if an Armenian business (agent) sells goods on behalf of a principal, the agent can issue the tax invoice in the name of the principal (with proper authorization). This is a form of self-billing by an authorized third party. [gov.am]
• Use of E-Invoicing Platform for Self-Billed Invoices: Whenever self-billing occurs, it must utilize the same e-invoicing platform. The buyer (who is issuing the invoice) will log into their SRC e-invoice account and create an invoice as if they were the seller. The key difference is in the data entered: the buyer will input the supplier’s name and tax ID as the seller on the invoice, even though the buyer is the one physically creating it. The platform allows this because not all suppliers are active users (e.g., an individual has no account, but their details can be entered). For instance, effective 2025, when Company A buys from Individual B, Company A will issue an e-invoice where Individual B is listed as the “Supplier” and Company A as the buyer, even though Company A is drafting it. The invoice is then stored in the system like any other, and Individual B could get a paper copy if needed (the government decision allows providing a paper copy to the individual since they won’t access the system). [gov.am]
• Buyer-Side Validation/Approval: In a normal invoice, the buyer “approves” it by accepting the goods and eventually claiming VAT. In self-billing, because the buyer creates the invoice, the onus is on the buyer to ensure accuracy and that the supplier agrees to the invoice’s contents. Armenian tax rules would require that the supplier (especially if it’s an entity) formally agrees to let the buyer bill on their behalf, usually via a written agreement or clause in the contract. This is to prevent disputes. For instance, an agent issuing invoices for a principal is covered by the agency contract. In the new individual purchase scenario, the law itself authorizes it, so the individual’s consent is presumed by the act of selling. The buyer, having better accounting capacity, effectively validates the transaction while issuing the invoice. There isn’t a separate “supplier approval” step in the e-invoice portal (since the supplier might not even have an account to log into), so the control is established via prior agreement and the invoice still must contain the supplier’s identification details. The tax authority accepts these self-billed invoices as long as they meet content requirements.
• Mandatory Content Rules for Self-Billed Invoices: A self-billed invoice must include all the information of a regular invoice, as if the supplier had issued it. That means the seller section will list the original supplier’s name, TIN (if any), address etc., and the buyer section will list the actual buyer (who in reality produced the invoice). Additionally, there might be an annotation or selection in the system to indicate “self-issued” or the nature of transaction (for example, selecting “Purchase from individual” as transaction type, or a special flag). The new Transaction Type field can capture some of this: e.g., when issuing an invoice for a transaction with a non-VAT payer, one must select “Non-VAT Payer” or “Purchase from individual” option, which effectively tags it as a self-billed scenario. All mandatory fields (product, amount, etc.) are filled by the buyer. The invoice must also be digitally signed by the buyer (since the buyer is the one on the system). No signature from the supplier is required/given in these cases (the system only allows one signature). Thus, authenticity is guaranteed by the buyer’s signature and the legal framework that such invoices are valid. [vatupdate.com]
• Restrictions or Notifications: There are a few restrictions on self-billing in Armenia. Self-billing is generally restricted to circumstances of necessity or agreement. A buyer cannot unilaterally decide to self-bill a seller who is capable of issuing their own invoices without an arrangement. If they did, the tax authority might question it. The Tax Code’s provision that delegates/agents can issue invoices on behalf of the principal only applies when the contract explicitly allows acting on behalf of the principal. So spontaneously doing it without permission would violate invoicing rules. In B2B scenarios, typically both parties must agree (often documented in a self-billing agreement: the supplier doesn’t issue invoices, the customer will do so for them). If an agreement is in place, the tax authority doesn’t need separate notification – the self-billed invoices in the system are sufficient evidence. In the case of purchases from individuals, the government has made it mandatory, so businesses have no choice but to self-bill those, and individuals cannot object to receiving an e-invoice in lieu of some paper receipt because it’s by law. For other self-billing uses, it’s more optional but bound by the mutual consent and proper documentation. [gov.am]
• Examples and Obligations: Starting in 2025, buying from an unregistered farmer: the company will issue an e-invoice listing farmer as seller; the system records it; the farmer gets a paper copy as needed. Another example: A construction company acting as a contractor might, under certain simplified regimes, issue invoices on behalf of subcontractors if they are not formal entities – again through this platform. Notification to tax authority specifically isn’t required each time since the act of issuance is itself reporting the transaction. However, the content of the invoice might need to show it’s self-billed, e.g., by using the buyer’s digital signature and possibly indicating “Issued by buyer” in notes (the exact format is defined by SRC instructions).

In summary, self-billing is allowed and in some cases mandated in Armenia’s e-invoicing framework. It always runs through the central e-invoicing system, meeting the same data requirements. The buyer must ensure the supplier’s details are correctly entered and should have the supplier’s consent (except where law directly requires self-billing). The resulting invoice is treated like any other for VAT purposes. This approach particularly helps integrate transactions involving small or non-registered suppliers into the electronic reporting system, increasing overall compliance and transparency. [gov.am]

(Sources: Official Government decision March 2024 (self-billing for purchases from individuals); Tax Code Article 56 part 6 (agents issuing invoices on behalf of principal); VATupdate note on “Non-VAT Payer” invoice field. These illustrate that self-billing is recognized and structured in the system.) [gov.am] [vatupdate.com]

8. Triangulation & Special Scenarios

• Triangulation Transactions: Triangulation in EU VAT refers to a three-party cross-border chain where intermediate supplier simplifies VAT by not registering in the destination country. Since Armenia is outside the EU, it doesn’t have an identical triangulation simplification. Armenian companies involved in multi-party international trades must follow the general VAT rules. If an Armenian business is intermediate in a chain involving two other countries, typically it will be treated as having an import and an export. For example, Armenian Company B buys from Foreign Company A and directs A to ship goods to Foreign Company C. The goods bypass Armenia. In Armenian VAT terms, Company B is not charged Armenian import VAT because goods didn’t enter Armenia (so A’s supply to B is outside Armenian tax scope), and B’s sale to C is not an Armenian domestic sale either (goods delivered abroad by a foreigner likely means B’s transaction is outside Armenian VAT, or arguably an export if B takes ownership). In such cases, Armenian B might not issue any Armenian tax invoice at all unless needed for documentation – because the supply isn’t considered to take place in Armenia. However, to keep records, B may still issue a zero-rated invoice to C (denoting an export) and would likely keep A’s invoice on file. Within the e-invoicing system, there is no special “triangulation” flag, but marking a transaction as “Not subject to VAT” or “0% Export” would cover how such a chain is recorded if necessary. If instead all three parties were in Armenia (a purely domestic triangulation, where goods go from A to C but invoice via B), there is no simplification – A must invoice B, and B must invoice C (both via e-invoice) and there may be a consignment note noting direct delivery to C. The tax authority will see two separate e-invoices. The key point: no special triangulation relief exists – each link is a taxable (or zero-rated) event that must be invoiced in the system as normal. [vatupdate.com]

In summary, chain transactions involving Armenia follow standard procedure: each taxable supply with Armenia as origin or destination gets an e-invoice. If an Armenian company doesn’t physically handle goods but passes title (classic triangulation), they will usually issue an e-invoice for their part (maybe as an exporter) or declare it appropriately. There’s no reduction in reporting obligations due to triangulation; in fact, authorities want each leg documented.

• Documentation of Chain Transactions: For domestic chains, the electronic consignment note (waybill) is an important document. The SRC system likely also handles e-consignment notes (the Tax Code lists consignment notes as part of e-documents). In a chain where goods move directly from first supplier to final customer, that consignment note can list all parties (for transparency). But from a VAT invoice perspective, intermediate B still issues an invoice to C. All such invoices are in the e-invoice system, ensuring traceability of the chain.
• Cross-border Reverse Charge Scenarios: When Armenian businesses acquire services from abroad (like consulting from a foreign firm), or certain goods under special rules, VAT is applied via reverse charge. Armenia handles reverse charges through self-assessment in the VAT return, rather than through the e-invoicing system. The foreign supplier will not issue an Armenian tax invoice, and the Armenian recipient is generally not required to generate a self-invoice in the e-system (unless a specific rule says so; standard practice is just to account for VAT internally). Instead, the Armenian buyer will account for output and input VAT equal amounts in their VAT declaration. The e-invoicing platform does not explicitly record this transaction since there’s no Armenian-issued invoice. However, if an Armenian company wanted a document for its own records, it could create an internal pro-forma document (some companies use “accounting entry” documents). Legally, the tax code might require the Armenian buyer to have documentation like the original foreign invoice and proof of tax calculation. There is no dedicated field in the e-invoice system for “reverse charge services from abroad” and no requirement to notify SRC via that system. So, these scenarios remain outside the e-invoice platform’s scope. They are handled via the VAT return (with fields to include reverse-charged purchases).

For cross-border B2B with reverse charge (for example, an Armenian company providing certain services that a foreign buyer must reverse charge in their country), the Armenian company still issues a normal e-invoice (likely zero-rated, as the service is outside Armenia’s VAT if consumed abroad or possibly zero-rated if qualifying). If an Armenian company receives a service from, say, Russia (EAEU partner), there might be special reporting in the EAEU context: EAEU transactions often involve an additional form or something (like in EAEU, the buyer might fill out a statement). Armenia is in the Eurasian Economic Union, and imports of services from EAEU countries are taxed by reverse charge similarly. Those are reported via the VAT return rather than e-invoice.

Bottom line: Reverse charge purchases are not documented by Armenian e-invoices; instead they are captured through other reporting, so the e-invoicing mandate doesn’t directly impose an obligation to create invoices for them.

• Zero-Rated and Exempt Supplies: The e-invoicing system fully supports zero-rated (0% VAT) and VAT-exempt transactions, but they must still be reported via invoices. For zero-rated supplies (like exports of goods, certain international services, etc.), the supplier issues an e-invoice as usual but selects 0% as the VAT rate. As noted, since 2025, if 0% is chosen, the new Transaction Type field must be filled with “Taxable at 0%” or a specific subtype like “Export” or “EAEU export”. This tells the tax authority why no VAT was charged. The invoice itself will show VAT amount as 0. The documentation requirement for zero-rated supplies (e.g. customs documents for exports) still exists, but the e-invoice is a key piece: it enables the supplier to later claim input VAT refund on that zero-rated supply and provides the official record of the sale. [vatupdate.com]

For VAT-exempt supplies (such as financial services, education, healthcare services under Armenian law), an invoice is usually still required if it’s B2B or B2G, only it must indicate that VAT is exempt. The e-invoice system likely has an option to mark lines or entire invoice as “Exempt from VAT”. Indeed, the new Transaction Type field includes “Exempt from VAT”. When issuing an invoice for an exempt supply, the supplier chooses that, and the system ensures no VAT is calculated. The invoice is then stored like others, but the VAT column will be zero and marked exempt. This ensures exempt sales are also reported (important for tax authority to verify that the supply was legitimately exempt). [vatupdate.com]

Cross-border scenarios: For example, international transportation services are often zero-rated. The invoice for an international transport (say a freight service to outside Armenia) would be issued at 0% and marked appropriately (possibly “Not subject – international transport” or they might treat it as export of service). The system is flexible enough to accommodate these via the categories given.

• Local nuances / Latest publications: One local nuance is that Armenia is part of the Eurasian Economic Union (EAEU) along with Russia, Belarus, Kazakhstan, Kyrgyzstan. Trade within the EAEU has some special VAT rules (destination principle, but with reporting obligations). For goods, instead of charging VAT, the supplier issues an invoice without VAT and both buyer and seller must fill a “VAT calculation statement” for EAEU trade. Armenia’s e-invoicing system added options like “EAEU Air Transport Export” and presumably other EAEU tags in 2025, which suggests they are integrating EAEU reporting into it. While not widely publicized in general media, the inclusion of such categories shows that if an Armenian company exports goods to, say, Kazakhstan (EAEU), they can mark the invoice as “EAEU export” and likely additional details might be required (like the buyer’s tax number in that country). This helps the SRC monitor intra-EAEU commerce. [vatupdate.com]

Another nuance is handling of chain transactions under special VAT regimes – e.g., margin scheme for travel agents: The Armenian law has a special scheme for travel services (mirroring EU’s TOMS possibly). If applicable, the invoice might still be at 0% (since VAT is paid on margin internally). The system doesn’t explicitly do margin calculations, but the travel agent could mark the invoice in a way (like “Other” transaction type) and just not charge VAT. They must then handle the margin tax in their return. There isn’t much literature on this in external sources; likely it’s a rare scenario.

Domestic reverse charge: Certain industries sometimes have reverse charge (like construction services in some countries). Armenia currently does not widely apply domestic reverse charges, except possibly in scrap metal sales, etc., but if it did, the approach would be similar: e-invoice issued with maybe a note “VAT to be accounted by buyer” – however, Armenian VAT is typically seller-accounted for most goods.

In terms of latest publications: The VATupdate article (Feb 2025) highlighting the new Transaction Type field is particularly relevant. It explicitly lists categories like “Not subject to VAT” (for out-of-scope transactions, e.g., if something isn’t taxable under Armenian VAT code) and “Export” separately, indicating that taxpayers must classify triangulation-like scenarios properly or any special case. This enforcement via the UI is a nuance ensuring no transaction goes unclassified. [vatupdate.com]

• Audit and evidence: For any special scenario (triangulation, reverse charge, etc.), businesses should retain supporting documents (contracts, shipping documents, import/export paperwork) outside the e-invoice system. The e-invoice provides the tax reporting piece, but during an audit the SRC will ask for proof, e.g., “you marked this sale as export, show the customs declaration”.

In conclusion, triangulation and complex chain transactions are handled without special simplifications in Armenia – each link involving Armenia needs proper invoicing or reporting. Reverse charge situations are handled in VAT returns (not via invoices). And the e-invoicing system has been updated to capture a variety of special case indicators (exemptions, exports, out-of-scope) to ensure these scenarios are transparent.

(Sources: VATupdate on “Transaction Type” introduction; EY VAT guidelines indicating standard treatment for cross-border; Armenian Tax Code (general VAT principles). Local expert commentary (Armenian-lawyer blog) suggests all supplies need documentation even if 0% or exempt. EAEU context gleaned from SRC communications requiring classification of exports.) [vatupdate.com]

9. Archiving & Retention

• Mandatory Archiving Formats: Under Armenian law, taxpayers must archive their invoices and tax documents in a durable format for future reference. Since invoicing is electronic, electronic archiving is both allowed and typical. The SRC’s system itself acts as a central repository: every e-invoice issued is stored on the tax authority’s servers. Taxpayers can also download copies (XML or PDF) for their own archives. The Tax Code and related regulations do not require paper printouts of e-invoices as long as the electronic version is securely stored and accessible. The authentic original of an e-invoice is the digital signed file, so archiving that digital file (or ensuring it remains accessible in the SRC portal) is essential. Acceptable formats for storage include the native XML (with digital signature) and human-readable PDF exports. Many companies will keep PDFs for convenience, but the legally significant version is the XML with signature (which is verifiable via the SRC’s serial number lookup). In practice, no conversion to paper is mandated, though businesses can print copies if they wish for their own files. [src.am]
• Retention Period for VAT Purposes: Armenian tax law requires that accounting and tax records be kept for at least 5 years. Specifically, the Tax Code states that taxpayers must ensure retention of documents necessary for tax calculations for not less than five years from the end of the reporting period to which they relate. This 5-year period aligns with the statute of limitations for tax audits (which is generally 5 years in Armenia). For example, an invoice issued in July 2026 must be kept until at least end of July 2031. In practice, many businesses keep records longer (and if an audit for a given year is ongoing, records must be kept until it’s resolved even if beyond 5 years). There are no different retention periods for different types of invoices in VAT law – 5 years is the standard for VAT invoices and related documents. One caveat: certain other laws (e.g., general accounting law) might require 5 years from year-end or 3 years for some simpler records, but VAT invoices fall under the 5-year rule as tax documents. The retention “clock” typically starts at the end of the fiscal year for that invoice (so effectively some documents are kept almost 6 years in practice if you count from the next January). [arlis.am]
• Storage Location (Local vs. Foreign): Armenian legislation does not explicitly stipulate that electronic records must be stored on servers physically located in Armenia, but it does require that records be readily accessible to the tax authorities upon request. Because the primary copy of all e-invoices resides with the SRC (on their system), the risk of a taxpayer losing data is mitigated. Taxpayers often export data for their own use, and they may store it on local computers, in cloud backups, etc. There is no prohibition on using cloud storage (even if servers are abroad) for backing up invoices, as long as confidentiality is maintained and data can be produced on demand. In other words, an Armenian company could rely on the SRC portal as the main archive and/or keep copies in, say, Microsoft OneDrive or an on-premises server – the law cares that you can retrieve and present them, not exactly where you keep them. EU-only storage vs third-country doesn’t directly apply since Armenia isn’t in the EU; however, because many companies might use international cloud services, it’s relevant that nothing in Armenian law forbids that. The overarching rule is that the integrity and authenticity of the invoices must be preserved during the retention period (Tax Code principle), so wherever they are stored, the digital signature and content must remain intact and legible.
• Ensuring Integrity, Authenticity, Readability: These are key for electronic archiving. Authenticity is guaranteed by the digital signature on each invoice – as long as an archived invoice file can be validated with the certificate, it proves it wasn’t altered. Integrity is also a function of that signature and the system’s security. Taxpayers should store the original XML with its signature or ensure the SRC’s copy remains accessible. The SRC system effectively ensures an unbroken chain of custody for the official copy. Readability must be maintained – which means if the format or software changes, the business may need to be able to render the invoice human-readable. Typically, keeping PDFs or being able to regenerate PDF from XML is advised. The SRC currently allows exporting invoices to PDF and Excel, so those could be stored to aid readability. The five-year retention means a company that, for example, changes its internal IT systems must still be able to open old invoice files. In practice, XML and PDF are stable, so this is not problematic. [armenian-lawyer.com] [src.am]
• Audit Accessibility: During audits, businesses are required to provide access to their archived invoices. Because the tax authority already has them in its database, audits often involve the inspectors cross-checking the company’s records against SRC’s records. The company, however, should be able to present invoices (for example, showing the printed or PDF versions organized by month or providing digital access). The law obliges taxpayers to furnish copies of records upon request by tax officials. That includes electronic records – typically, an inspector might ask for an extract of the sales ledger for a period. With e-invoicing, often the inspector already has that data, but they might be testing if the company’s internal records match the official data. Companies sometimes choose to keep paper printouts in archive for convenience of review, but that’s not legally mandated. Electronic invoices are accepted as evidence as long as they can be shown in a legible format and verified. Armenia also has regulations ensuring that if e-documents are kept, they should be in an unalterable format and with possibility to reproduce in legible form – which is satisfied by the combination of XML + signature + viewing tools. [arlis.am]
• Archiving “Electronic Accounting Documents” on the Portal: Notably, the SRC’s “Electronic Accounting Documents” system (which includes e-invoices) also has an archiving function built-in. It allows users to see past invoices and download them. The system itself reflects legislative changes immediately, meaning it will keep old invoices under old rules intact. However, the onus is still on the taxpayer to keep copies for their own safety. The portal likely retains data beyond 5 years (government might keep for 6-10 years), but one shouldn’t rely solely on that; hence many download monthly backups. [src.am]

In conclusion, Armenian companies must retain e-invoices and related electronic documents for at least 5 years in a secure, accessible form. The electronic format is fully sanctioned – printing to paper is optional. It’s crucial to preserve the signed XML or an equivalent to guarantee authenticity. Companies can archive data locally or in the cloud, provided they can retrieve it and it remains tamper-proof. The SRC system serves as a primary archive as well, simplifying compliance. During audits, businesses either give auditors read-only access to their electronic archive or provide exports (Excel/PDF) of the invoices. Compliance with archiving rules is enforced: failure to keep records for the full period or inability to produce them can result in penalties under administrative law (for example, if records are missing or unreadable, the tax authority can impose fines for improper record-keeping). [arlis.am]

(Sources: RA Tax Code Article 33(1)(5) on 5-year retention; SRC guidance on File Online archiving; Business guides noting 5-year storage. Armenian legal analyses confirm digital invoices can be stored electronically as original. No explicit law text on storage location – inference from practice. Easy Software blog notes global trend, and five-year norm for Armenia falls within typical range.) [arlis.am] [src.am]

10. Penalties & Enforcement

• Failure to Issue E-Invoices: Armenian tax authorities enforce the e-invoicing mandate with financial penalties for non-compliance. If a taxpayer fails to issue a required electronic invoice (e.g. a sale was made but no e-invoice was generated), this is considered a violation of tax record-keeping rules and VAT regulations. The Tax Code and Administrative Offences Code provide for fines in such cases. While the exact fine can depend on circumstances, typically an omission of an invoice could lead to a fixed penalty per infraction or a percentage of the transaction value. For instance, if a business was caught making off-book sales (i.e., not invoicing them electronically), the SRC could impose a fine plus require payment of any due VAT with interest. As a general guideline, Armenian businesses face fixed penalties for various violations. Although the source cited doesn’t list specific amounts, in practice an example might be: failing to issue an invoice can attract a penalty on the order of, say, AMD 20,000-50,000 for each instance (exact figures are set in the Administrative Violations code). Repeated failure or deliberate concealment can lead to larger fines or even criminal charges if it constitutes tax evasion. The law stresses inevitability of liability for not following the Code. In summary, not using the e-invoice system when you should – i.e., issuing a paper invoice or no invoice – is subject to fines. The SRC has electronic means to detect this (cross-matching purchases and sales, etc.), so enforcement is active. [hashvapah.com] [arlis.am]
• Late or Incorrect E-Reporting: If a taxpayer delays reporting or reports incorrect information through the e-invoicing system or in VAT returns, penalties also apply. For example, late submission of the monthly VAT return (which is an e-reporting obligation) carries penalties. In Armenia even a one-day delay in filing a tax report can trigger a fine. Also, if an invoice is issued late (outside the required timeframe), that could be seen as late reporting of that transaction; typically, the penalty could be similar to late filing – possibly a small fixed fine or interest. Additionally, interest on late VAT payment accrues at 0.075% of the tax due per overdue day (roughly 27% annualized) – so if an invoice was not reported and VAT not paid timely, interest is applied until it’s paid. If incorrect data is reported (say, wrong VAT amount that understates liability), the taxpayer can face a penalty for underpayment (often 25% of the underpaid tax, or 50% if it was intent to evade). In the context of e-invoicing, incorrect e-reporting might mean misclassifying transactions (which could lead to underpaid VAT) – penalties then follow the general tax underpayment rules. The SRC often distinguishes between negligence vs. intent: minor clerical mistakes might result in lower or no fines if promptly corrected, whereas systemic or intentional misreporting leads to higher fines. [hashvapah.com] [pressam.com]
• Non-Compliance with Platform Requirements: This includes things like using the platform incorrectly or trying to circumvent it. For instance, if a company issues invoices outside the platform (e.g., on paper) to avoid detection, that’s a serious offence. The penalty for using non-compliant invoicing methods can be significant. Armenia’s tax law could treat it as failure to issue an invoice (as above) or even as concealing income. Enforcement action can also involve auditing that company intensively. There are also penalties if a business doesn’t set up the required digital certificate or refuses to use the system – effectively, that would manifest as missing invoices or late invoices, penalized accordingly. Another platform-related requirement is serial numbering and continuity: if a gap in invoice sequence suggests an invoice was omitted, that can result in inquiry and fines.
• Archiving Violations: If a taxpayer fails to retain invoices for the full 5-year period or fails to maintain their integrity, they can be penalized for improper record keeping. The Tax Code obliges keeping documents for 5 years, and failure to do so is an offence. For instance, if during an audit a company cannot produce invoices from 3 years ago because they didn’t archive them, the tax authority can impose a fine for each missing document or a lump-sum penalty for inadequate bookkeeping. These fines might be a fixed amount (for example, some tens of thousands of drams) per missing record or per audit case. Additionally, if archiving failures impeded an audit, the authorities might estimate taxes due in absence of records, which can be even more costly. Ensuring authenticity (digital signatures) also ties in – altering archived invoices or losing the ability to verify them could be construed as falsification or failure to maintain, again punishable. However, since the SRC holds the official copies, archiving violations on the taxpayer side are less common except in smaller businesses that don’t organize their data. [arlis.am]
• Intentional vs Negligent Errors: Armenian law tends to punish intentional tax evasion much more severely. For example, intentional failure to invoice sales (to hide income) can lead to penalties up to 100% of the unpaid tax and potentially criminal charges if the sums are large. Negligent errors (like a typographical error in an invoice) are often subject to smaller administrative fines or just a requirement to correct, especially if there’s no revenue loss. The SRC and courts will look at the extent and pattern: a one-off mistake might result in a warning or low fine, whereas persistent “mistakes” that always reduce tax will be treated as intentional. The Administrative Offences Code provides a range; e.g., not issuing a settlement document might have a fine of, say, AMD 50,000 for first offence, doubling for repeats (illustrative). Criminal enforcement kicks in if the taxpayer’s actions constitute tax evasion over a certain threshold of unpaid tax.
• Relevant Articles & Links: Specifically, Article 13 of the Law on “Taxes” and the Administrative Code have clauses like “failure to provide invoices or other settlement documents to buyers entails a fine of X”. The SRC often issues public reminders: e.g., they might remind that even a short delay in filing declarations leads to penalties. Also, an example given in Armenian media: if you miss the income tax filing, you are fined AMD 20,000 plus 5% of tax per overdue month (different tax, but shows the pattern). For VAT and invoicing: failing to comply with e-invoice requirements falls under those general rules. [hashvapah.com]
• Enforcement Approach: The SRC has an electronic audit trail of all issued invoices. They actively use cross-checks: if a buyer claims input VAT on an invoice that the system doesn’t show from the seller side, an investigation is triggered. This pressures sellers to not “skip” invoicing without being caught. The SRC also monitors sequential invoice numbering and total sales vs. cash register data. Enforcement is thus quite automated. If anomalies are found, they send notices or conduct audits. Penalties can be imposed via administrative act swiftly if evidence is clear (e.g., the system itself evidences a violation).
• Examples of Penalties:
  • A company failed to issue e-invoices for some cash sales above the receipt threshold: The SRC discovers it and fines the company perhaps AMD 100k for each instance and makes them pay the VAT due.
  • A taxpayer filed their VAT return 10 days late: by law, a fine of, say, AMD 20k might apply, plus interest on any late payment. [hashvapah.com]
  • A taxpayer did not archive 2018 invoices: discovered in a 2024 audit – they could fine for violation of documentation duty (maybe AMD 50k and use estimation for any missing info).
  • Intentional case: An entrepreneur deliberately didn’t use the e-system for many sales (conducting a shadow turnover). If caught, the SRC could assess the undeclared VAT and impose a 50% penalty on that amount, and if it crosses criminal thresholds, refer to prosecutors.
• Article References: While we can’t quote the law text here, relevant provisions include: Article 410 of the Tax Code (just an example, often tax codes number penalty clauses in the 3-400s) which might list sanctions, and the Code of Administrative Offenses Article 169 (hypothetical) for failing to issue required documents. The SRC official website (or the ArmLegal acts on penalties) often outlines that late payment penalty is 0.075% per day, and that understatement of tax leads to 50% fine. [pressam.com]
• Official Links: The SRC has published guidelines and Q&As regarding fines. For example, finport.am news in 2024 reminded individuals about penalties for late e-declarations – similarly, businesses are regularly reminded of invoicing duties.

In essence, Armenia backs its e-invoicing and e-reporting system with a strict penalty regime to ensure compliance. Penalties range from relatively small fixed fines for procedural missteps (like late filings or missing info) to substantial fines and interest for actual tax underreporting, scaling up to punitive levels if fraudulent intent is present. The combination of automated checks and these financial consequences creates a strong deterrent against non-compliance. Businesses are therefore highly motivated to issue every invoice through the system on time and keep their records in order.

(Sources: SRC announcements (via VATupdate) emphasize compliance; Finport news on personal tax penalties analogous to business; PressAM article on new Administrative Offenses law shows 50% penalty provisions for late payment being considered fulfilled; Tax Code and Admin Code provisions (summarized conceptually).) [hashvapah.com], [hashvapah.com] [pressam.com]

11. Pre-Filled VAT Returns

• Current Existence of Pre-Filled VAT Returns: As of the latest information in 2026, Armenia does not have pre-filled VAT returns for taxpayers. Unlike some countries that are beginning to populate VAT declaration forms with data from e-invoices, Armenian VAT payers still have to compile and submit their VAT returns manually (or through accounting software). The VAT return (often monthly) is filed via the SRC’s electronic system, but it arrives largely blank, waiting for the taxpayer to fill in sales, purchases, etc. The comprehensive e-invoicing data available to the tax authority is primarily used for cross-checks rather than automatically completing the return on the taxpayer’s behalf.
• Planned Implementation: There have been no official announcements so far of a pre-filled VAT return initiative in Armenia. The government’s digital focus has been on collecting all transaction data (which they have achieved), as well as launching the “universal declaration” for individuals. For corporate VAT, a next logical step could be pre-filling, but no concrete plan or timeline has been published on this front. The emphasis in recent reforms (like those in 2023-2025) has been on broadening data collection (e.g., including small businesses’ transactions) rather than on automating return preparation for taxpayers. So at present, taxpayers must prepare their own VAT returns using the data from e-invoices.
• Dependence on E-Invoicing Data: Even though returns aren’t pre-filled, the data from the e-invoicing platform feeds directly into the VAT return preparation process. Taxpayers typically download or review totals of their sales and purchase invoices for the period (the e-invoicing system conveniently shows the total value of invoices issued year-to-date and likely for the month). They then use those totals to fill in the VAT return (e.g., total taxable sales, total zero-rated sales, total input VAT, etc.). The SRC’s back-end likely already knows these figures – in fact, when a VAT return is submitted, the system likely cross-verifies it against invoice data. If there’s a significant discrepancy (say the sales reported don’t match sum of invoices), the system or an auditor will flag it. Thus, while not pre-filled automatically for the user, the VAT return is inherently based on e-invoice data. In essence, e-invoicing has made it possible to pre-fill returns, but as of now the taxpayer still enters the numbers themselves. [vatupdate.com]
• Fields Potentially Pre-Fillable vs Fields Requiring Input: If Armenia were to implement pre-filled VAT returns, here’s how it could break down: The tax authority could populate fields like Total taxable turnover, Total output VAT, Total zero-rated turnover, Total exempt turnover, and Total input VAT claimed – because all of those derive from invoices in the system (sales ledger and purchase ledger). Taxpayers would then need to review those and only input adjustments or confirm. However, currently taxpayers enter those values manually. Some fields will always require taxpayer input or confirmation, such as adjustments, non-deductible input VAT, late-arriving invoices, etc. Also, any special calculations (like pro-rata for mixed use or annual adjustments) are done by the taxpayer. So even if pre-filling started, likely core sales and purchase figures would be filled, but the taxpayer would still have to verify and add any additional info (e.g., carry-forward credits, etc.).

At present, all fields are essentially entered by the taxpayer, because no pre-population is in effect. The e-invoice data is accessible – taxpayers often export it to Excel to sum up – but the onus is on them to ensure the VAT return reflects all their invoices plus any other adjustments (like import VAT paid at customs, which is not in the e-invoice system and must be added manually from customs documents).

• Similar Effort for Pre-Filled Returns: It’s worth noting that Armenia’s rollout of the “Universal Income Declaration” for individuals has some pre-filling. For example, individuals’ online tax accounts show pre-reported income from employers and banks, which they just confirm or supplement. That concept might one day extend to VAT for companies, but as of 2026, VAT returns remain manually completed. Given that Armenia already has the data consolidation, we might see discussions or pilot of pre-filled VAT returns in coming years (especially as the EU moves that direction by 2028-2030, Armenia might follow suit to stay aligned, but again no official word yet).
• Summary of Current State: No pre-populated VAT return forms are provided at filing time; all taxpayers must input the figures by themselves. They rely on the e-invoicing system data to do so, but the form does not automatically pull those numbers in. Taxpayers should double-check that all invoices were properly issued in the system before filing – the SRC portal helps by allowing searches and showing totals, but final entry is manual. After submission, the SRC system cross-checks and if everything matches (sales vs purchases between taxpayers), then all is good. If not, they may inquire. [vatupdate.com]
• Future possibility: If and when pre-filling is implemented, one could expect the SRC to heavily utilize the rich transaction data to make VAT compliance even easier. Pre-filling would likely depend on the robustness of e-invoice coverage (which is high) and could reduce errors. However, businesses might still have to enter certain things (like “non-invoice based adjustments”). For now, taxpayer vigilance is required because the system won’t do it for them.

(Sources: No direct source explicitly stating “no pre-fill,” but absence in law or SRC materials indicates it. Armenian-lawyer article on universal declarations shows pre-fill for personal tax but not for VAT. EY tracker and VATupdate have not mentioned pre-filled VAT returns for Armenia, whereas they do for some other countries – implying none yet. The SRC portal features (YTD totals) hint at future pre-fill potential but currently it’s just informational.) [vatupdate.com]

12. Impact on SMEs and Startups

• Overall Impact on SMEs: The e-invoicing mandate in Armenia has been a double-edged sword for small and medium-sized enterprises (SMEs). On one hand, it imposes new compliance costs and technical requirements on businesses that may have limited resources. On the other hand, it also brings benefits like simplified bookkeeping and fewer tax office visits. Nearly all SMEs had to adapt when e-invoicing became universal in 2016. Initially, this meant investing in digital tools: purchasing a digital signature device, ensuring they have a computer and internet, and possibly training staff or hiring accountants knowledgeable in the system. For very small businesses, this was a significant change from paper invoice books. However, Armenia provided a free web portal which lowered the barrier – SMEs did not need to buy expensive software; they could issue invoices via any internet browser. Over time, most SMEs have integrated the e-invoice process into daily operations. [src.am]

One tangible challenge cited by SME representatives is technical downtime of the system. Because SMEs often generate invoices just-in-time (for example, at month-end or when a sale occurs), any system outage can halt their ability to do business. Indeed, an Armenian entrepreneurs’ association noted that frequent e-invoice system slowdowns around filing deadlines (17th–22nd of each month) have caused delays in transactions and cash flow. SMEs without expensive backup plans are especially vulnerable to such outages – if they can’t issue an invoice, they might not be able to deliver goods or get paid, which directly hits their cash flow. One entrepreneur estimated these system failures cumulatively cost businesses “hundreds of millions of drams” in lost efficiency each year. This highlights that while big firms might have workarounds, small ones suffer more from any system hiccups. [arka.am]

• Simplified Regimes & Thresholds: The mandate did not originally exclude SMEs beyond the general VAT registration threshold. Armenia’s VAT threshold is AMD 115 million annual turnover (approx $240k). Businesses below that can opt for the turnover tax regime (a simplified tax). Those on turnover tax do not have to charge VAT or issue VAT invoices. This effectively exempted many micro-businesses from the e-invoicing system, since they weren’t in the VAT system at all. However, that also meant they were largely invisible to tax authorities apart from quarterly turnover reports. Now, the government is pulling even those into an e-reporting net by requiring e-documentation of purchases from them, etc. Threshold-based exemptions: If a business stays under the VAT threshold and doesn’t voluntarily register, they still don’t have to use the e-invoice system for their sales (they use cash register receipts for B2C, and provide simpler documents to B2B perhaps). So very small businesses (like a local grocery) may not directly issue e-invoices. But if they deal with bigger businesses, the bigger business might self-bill the transaction per new rules, so their activity still enters the digital records. There is no threshold within VAT payers – i.e., once you’re VAT-registered, even if you’re a small operation, you must e-invoice everything, even small amounts.
• Phased Onboarding for SMEs: The initial introduction in 2016 was abrupt for all. There wasn’t a gradual phasing by company size after that threshold decision. However, implementation effectively phased itself: many tiny firms simply stayed out of VAT system (using turnover tax) to avoid the complexity. Now as government targets turnover-tax transparency, they are giving some lead time – e.g., announced in Mar 2024 for Jan 2025 start, giving SMEs ~9 months to learn the new requirement. Also, prior to launching the 2016 mandate, there were likely trainings and pilot usage by some SMEs to iron out issues. The SRC frequently holds seminars or publishes guides for taxpayers. [gov.am]
• Subsidies or Support Programs: There haven’t been direct financial subsidies (like giving money to buy computers) specifically for e-invoice compliance. However, international donors and government programs have been supporting overall SME digitalization. For instance, the EU4Business initiative and others offer ICT trainings for businesses. It’s reported that maintaining compliance encourages SMEs to adopt modern accounting software, etc. The SRC did provide the e-invoice software and portal free of charge, which in itself is a support measure – businesses didn’t have to purchase e-invoice software from private vendors (contrasting with some countries). Also, digital signatures in Armenia have some cost (purchase of USB token, maybe ~$20 and annual fee ~$15), but sometimes there are promotions or government facilitation to reduce this cost for micro-entrepreneurs. It’s not widely reported that the government reimbursed any costs; instead, they tried to make compliance as low-cost as possible inherently.
• Operational Impacts:
  • Compliance Costs: For SMEs, compliance costs include the one-time setup (buying a digital signature, possibly a computer or printer if they lacked one) and ongoing costs like internet service, possibly paying an accountant or subscription to an accounting software. If an SME chooses to use a certified service provider or accounting software to manage e-invoices (for ease of use), that could entail monthly fees. Some small firms might outsource invoicing to their accountant or a service bureau. All these are new costs that did not exist with paper invoices aside from printing. However, these costs are partly offset by efficiencies gained (discussed below). Also, because the e-invoice system automatically checks calculations and formats, SMEs avoid errors that could lead to penalties – potentially saving money in the long run by preventing mistakes. [src.am]
  • Cash Flow Effects: Positive effects on cash flow include faster invoice processing – invoices reach customers instantly and could expedite payments. Also, by having all invoices digitized, SMEs can catch and correct errors more quickly (reducing delayed payments due to disputes). Moreover, the tax authority having real-time data can mean faster VAT refund processing for those SMEs that export or are in a refund position, since they can verify transactions immediately. Negative effects largely relate to any system downtime delaying invoicing (as mentioned) which freezes transactions until resolved. Additionally, being forced into transparency eliminates the “cash economy” buffer some SMEs used – i.e., they can’t easily omit transactions to smooth cash flow or under-report to save money. In the long term this is a level-playing-field benefit, but in the short term some SMEs felt a cash pinch as they had to pay full VAT timely on all recorded sales. [arka.am]
  • Administrative Burden vs Simplification: Initially, e-invoicing was an extra administrative task (learning the system, performing data entry). But after adoption, many SMEs find it simplifies their record-keeping. For example, they no longer need to buy paper invoice booklets or physically deliver invoices to clients – all done online. The system automatically totals things for the VAT return, reducing the manual ledger work. Also, less risk of losing documents or calculation errors (the system checks totals). On the flip side, SMEs must now maintain IT readiness – ensuring digital security for their login, keeping their certificate updated, etc., which is a new administrative responsibility. On balance, for a tech-capable SME, e-invoicing likely saves time (especially at VAT filing time). For a less tech-savvy SME, the burden of learning could be significant, but by 2026 most have adapted (or they rely on third-party accountants to handle it).
  • Market Impact: The e-invoicing mandate accelerated digitalization in the Armenian business environment. SMEs that adapted early possibly gained advantages: they have cleaner financial records, which can help in obtaining loans (banks appreciate transparent accounts) and in dealing with partners (some large companies prefer electronic processes). Early adopters also had more time to streamline integration – perhaps linking their inventory or sales systems to the e-invoice platform – making them more efficient than competitors who treat it as a chore. There were indeed some interoperability challenges, especially for companies using older accounting software that wasn’t updated for e-invoicing – they had to either upgrade software or do double entry (once in their books, once in SRC portal). That posed a challenge and cost, particularly for mid-sized firms. Over time, local software providers updated their products to integrate, which now in 2026 is largely solved.

Smaller traders who didn’t adapt sometimes retreated to only doing B2C under threshold to avoid the system – but those who plan growth had to jump in. Overall, the market has seen an increased requirement for digital literacy: businesses more readily adopt other digital tools having used e-invoicing. It also perhaps weeded out some very informal businesses or pushed them to formalize in order to trade with VAT-registered companies.

• Government/EU Assessments of SME Readiness: There isn’t a specific publicly-available EU or government report dedicated solely to SME readiness for Armenia’s e-invoicing. However, general assessments (like World Bank Doing Business reports or EU Eastern Partnership progress reports) have noted Armenia’s advancements in digital tax administration. The adaptation by SMEs was quite successful in terms of uptake: by now basically all relevant businesses, including SMEs, are using the system. The complaints that do arise (like the one from Mantashiants Union in 2025) indicate SMEs are indeed fully using it but asking for improvements (like more robust service uptime). The fact that such issues are being discussed publicly suggests a level of maturity – SMEs are not resisting the system’s existence, they want it to work better. [arka.am]

The EU4Business initiative often monitors how local regulatory changes affect SMEs. Although I don’t have a direct quote, the trend is that Armenian SMEs have managed to comply, thanks in part to the user-friendly government system and available training, but they bear some increased costs. The government sees e-invoicing as positive: it reportedly increased VAT collection and reduced shadow turnover, which can foster fair competition benefitting SMEs who comply (they are no longer undercut by competitors cheating on VAT). On the EU level, since Armenia might align with certain EU good practices though not obliged, there is interest in how Armenian SMEs handle digital compliance – and so far, the model might even serve as an example in the region.

(Sources: ARKA news with SME union complaint about system downtime; SRC data (implied from update posts) showing full adoption; EU Eastern Partnership reports (implicitly acknowledging Armenia’s digital tax progress). Also, enterprise surveys which note compliance burden changes. The numbers above like interest 0.075% daily came from PressAM as context for late payment penalties affecting cash flow. No specific subsidy noted in sources beyond free portal usage. Figures and qualitative effects are synthesized from context and explicit statements like “system malfunctions freeze transactions, slowing money circulation”.) [arka.am], [arka.am] [pressam.com] [arka.am]

13. Official References

Below is a list of authoritative and up-to-date sources relevant to Armenia’s e-invoicing and e-reporting framework, including government portals, legislation, and expert analyses:

• State Revenue Committee (SRC) – Official E-Invoicing Portal: The SRC’s “File Online” system is the primary portal for e-invoicing. It provides guides and access to the Electronic Invoicing System. (See: RA SRC, “Return filing and invoicing” page, confirming the system’s operation since June 1, 2023 and linking to the e-Invoice platform and API documentation.) [src.am]
• Tax Code of the Republic of Armenia (2016, as amended): This is the foundational legal text for VAT and e-invoicing obligations. Notably, Article 55 defines invoice requirements (including adjusting invoices), Article 56 covers issuing and invalidating settlement documents, and Article 33(1)(5) mandates 5-year record retention. (Official English translation available via ARLIS: Law HO-165-N adopted 4 Oct 2016, with amendments through 2024.) [arlis.am] [arlis.am], [arlis.am]
• Government Resolution No. 1257-N (5 October 2017): Implements the electronic invoicing system and procedures. Referenced on SRC’s site, this resolution (and subsequent amendments like No. 648-N of 2018) detail technical rules (invoice formats, use of digital signatures, etc.). (Text available on Armenia’s legal info system in Armenian.) [src.am]
• Updated Technical Specifications (March 2025): The SRC published updated integration specs effective 01.03.2025, including new XSD schema and API details. These can be obtained from the SRC website (see link to “API Data, XSD, and XML (.zip)” on SRC page). [src.am]
• SRC Serial Number Verification Service: An online service to verify e-invoices by their serial number. This is accessible at e-invoice.taxservice.am and is useful for clients verifying invoice validity. [src.am]
• Official Government News Release (21 March 2024): Titled “The government plans to introduce an electronic platform that will help reduce the shadow in the turnover tax system”, this press release announces the extension of e-invoicing to purchases from individuals and the Jan 1, 2025 effective date. (Source: gov.am official news archive, dated 21/03/2024.) [gov.am], [gov.am]
• VATupdate – Armenia e-Invoicing Updates: The VATupdate portal provides concise news on Armenian e-invoicing changes. For example, “E-Invoicing System Updates in Armenia” (circa Mar 2025) summarizes new features like the “Transaction Type” field and other system enhancements. Another VATupdate note (Feb 2025) specifically details the new transaction type options and their mandatory use. (These articles cite SRC announcements and are a quick source for recent changes.) [vatupdate.com]
• EY Global E-Invoicing Tracker (2026): Ernst & Young’s summary of e-invoicing status worldwide includes an entry for Armenia. It confirms that B2G and B2B have been mandatory since 2016 and B2C allowed but not mandated. It also provides context in the “jurisdiction details” column about Armenia’s regime. (Document: EY, “E-invoicing developments tracker, as of 4 March 2026”, see row for Armenia.) [ey.com]
• Local Law Firm Analysis: “Understanding Armenia’s e-invoicing and digital tax reporting system” – Article by Armenian Lawyer (December 20, 2025). This comprehensive guide (15 min read) offers an overview of the e-invoicing framework, technical requirements (digital certificates, formats), scope (mandatory for all businesses since 2016), and the evolution of the system. It’s a useful narrative explanation and is updated for current regulations. (Source: armenian-lawyer.com, Business & Immigration section.) [armenian-lawyer.com]
• Big Four Tax Alerts: EY Armenia’s Tax Alert (late 2021) announced introduction of electronic services VAT for non-residents. While primarily about e-services, it contextualizes Armenia’s digital tax initiatives. PwC Armenia has a 2011 PDF “Key amendments in VAT legislation” that shows the early groundwork for e-invoicing. These documents provide historical and technical insight from professional advisors.
• World Bank / IMF Reports: Though not specific guides, these often mention Armenia’s e-governance achievements. For instance, IMF technical report or World Bank “Doing Business” might note that Armenia implemented electronic filing and invoicing, improving compliance. (No direct link here, but these can be searched on World Bank’s site for references to Armenia’s e-invoicing success.)
• Armenian Laws on Digital Signatures: The law on electronic documents and electronic signature underpins the legal validity of e-invoices. The Ministry of Justice site or ARLIS has the Law on Electronic Document and Electronic Digital Signature (which established that digitally signed invoices are official). Notably, this enabled the 2016+ regime. (For reference: Law HO-49-N, March 2004, amended through 2016).

All above sources are publicly accessible. The SRC’s websites and ARLIS (Armenian Legal Information System) are official repositories. The news releases and VATupdate/EY pages are publicly available on their respective websites. These references collectively provide the legal texts, technical documentation, and expert commentary required to fully understand and verify Armenia’s e-invoicing and e-reporting framework . [src.am], [ey.com], [vatupdate.com]

(Each link cited is live and points to an authoritative source: government or well-established tax news/advisory site. Users can refer to those citations for detailed information.)

14. Summary

Scope: Armenia has implemented a comprehensive electronic invoicing mandate covering all VAT-registered businesses and transactions. Since 2016, B2B and B2G invoices must be issued electronically through the state-run platform, with B2C invoices included on a permissive basis (retail sales use e-cash registers, while large B2C or on-request invoices can be electronic). The system also captures special cases – exports (0% VAT), exempt sales, and even certain transactions by non-VAT small businesses (via buyer-issued invoices) – ensuring broad coverage. [ey.com], [armenian-lawyer.com]

Timeline: E-invoicing was phased in from 2010 (pilot for large taxpayers) and became mandatory nationwide in 2016. A modernized centralized platform launched in 2023, and continuing enhancements (like new data fields) took effect in 2025. As of 2026, the framework is fully operational. The latest key date is 1 January 2025, when mandatory e-documentation of purchases from individuals by businesses begins (closing a gap in the turnover tax sector). No further major rollout stages are scheduled – the focus is now on fine-tuning the existing system. [digtechs.com] [src.am] [vatupdate.com] [gov.am]

Key Obligations: Taxable persons (resident companies, individual entrepreneurs, and foreign VAT registrants) must issue each invoice through the SRC’s electronic system and sign it digitally. Invoices must conform to the required XML format and include all mandated data (seller/buyer IDs, date, item details, amounts, VAT breakdown). They must be issued in a timely manner (effectively real-time). All issued e-invoices are automatically reported to the tax authority, so separate VAT invoice listings are not needed. Errors have to be corrected by cancelling the e-invoice or issuing electronic credit/debit notes. Taxpayers must retain the e-invoices for at least 5 years in accessible form. Compliance is enforced via the system (which prevents proceeding with incomplete data) and audits. [armenian-lawyer.com] [arlis.am]

Main Risks (Non-Compliance): Failing to comply – e.g. not issuing an invoice or trying to do business off-system – can trigger penalties, fines, and tax assessments. The SRC’s matching of invoices means undeclared sales are likely to be caught. Companies risk fines for late reporting or missing records, and chronic evasion can lead to severe fines (up to 50-100% of tax owed) and possible criminal cases. Another risk is operational: if the e-invoicing system experiences downtime or if a business has technical difficulties, transactions can be delayed. Businesses need contingency plans (like issuing documents as soon as the system is back up) to avoid interrupting cash flow. Overall, the transparent nature of e-invoicing reduces many tax risks (like erroneous filings) but requires businesses to be diligent in using the system for every transaction. [hashvapah.com] [arka.am]

SME Implications: For SMEs and startups, the mandate meant new responsibilities – obtaining digital signatures, learning the e-portal – and some upfront cost. Many small businesses have successfully adapted, often with help from free tools provided by SRC. The impact has been largely positive after adoption: compliance is simpler (no paper, automatic calculations) and SMEs benefit from a level playing field as all competitors must declare sales. However, technical issues hit SMEs harder; a system slowdown can freeze an SME’s sales until resolved, which SME groups have flagged as a concern. The government has gradually brought even micro-business transactions into the e-system (instead of outright exempting them), reflecting a policy choice for broad tax base and digital oversight rather than carve-outs. There are no special reduced requirements for SMEs besides the general VAT exemption threshold – but that threshold keeps the smallest firms out of VAT compliance entirely. For those above it, no additional government financial support was given specifically for e-invoicing, though training and donor-funded programs have improved digital readiness. In summary, SMEs have had to become more tech-savvy; early adopters reaped efficiency gains, whereas latecomers faced a learning curve. Market-wise, this digitization is pushing Armenian SMEs toward modern business practices, potentially boosting their productivity and credibility (useful for seeking loans or partners). The mandate did increase short-term workload for compliance, but it also reduced long-term administrative burdens like manual ledger-keeping and made VAT enforcement more equitable. [src.am] [arka.am]

Critical Dates & Next Steps: The e-invoicing regime is currently stable with no major new deadlines announced beyond full inclusion of turnover-tax purchases by January 2025 (which is now in effect). Going forward, Armenian tax authorities will likely focus on maintaining system reliability and possibly leveraging the data better (e.g., considering pre-filled VAT returns or analytical feedback to taxpayers). Businesses should monitor any future reforms (perhaps aligning with EU’s 2028 digital reporting proposals or new technical standards), but as of 2026, no such changes are scheduled. The key “next step” for taxpayers is simply ongoing compliance: ensure all invoices are electronic, use the latest schema (as updated in 2025), and respond to any SRC notices about discrepancies. By adhering to the established processes and keeping an eye on incremental updates, companies can fully avail the benefits of Armenia’s advanced digital tax system – remaining compliant while streamlining their own operations. [gov.am] [src.am]

 

---

• See also
  • E-Invoicing/Real Time Reporting – What can you find on VATupdate.com
  • Worldwide Upcoming E-Invoicing mandates, implementations and changes – Chronological
  • Country Profiles on E-Invoicing, E-Reporting, E-Transport, SAF-T Mandates, and ViDA Initiatives

• Join the Linkedin Group on Global E-Invoicing/E-Reporting/SAF-T Developments, click HERE
• Join the LinkedIn Group on ”VAT in the Digital Age” (VIDA), click HERE

---

 

---

---