Armenia’s New Derivatives Reporting: CBA Trade Repository Obligations and Tax Implications

Armenia derivatives reporting is moving to the forefront as the Central Bank of Armenia (CBA) deepens market oversight and standardises contracts. For banks and corporates using derivatives for hedging in Armenia, early preparation for a trade-repository style regime will reduce regulatory exposure and support VAT and other tax positions.

Overview: CBA's Unified Registry — Scope

The CBA has been strengthening the legal and operational backbone of Armenia's derivatives market through multi-year reforms. In 2025, the CBA introduced Armenian-law master documentation for derivatives and repurchase transactions—an important standardisation step that complements supervisory oversight and facilitates future centralised reporting models (trade repositories) for systemic risk monitoring. Under Armenia's financial services regime, the CBA has the authority to regulate and supervise derivatives activity in the interest of financial stability, which can include detailed transaction reporting.

Timeline and Legal Basis Under Armenian Law

• 2016 foundation: Armenia—assisted by development partners—implemented legal reforms to strengthen close-out netting, collateral, and enforceability for derivatives, aligning with international standards and enabling safer market growth.
• 2022 market liberalisation: The CBA eased certain FX risk and derivatives-related requirements (e.g., FX position constraints), encouraging prudent use of hedging tools and broader participation.
• 2025 legal standardisation: Launch of Armenian-law master agreements for derivatives and repos to improve legal certainty and market trust, supporting scalability of oversight and potential central reporting regimes.

Together, these steps provide a clear legal basis for the CBA to require more granular reporting of derivative transactions, if and when necessary for prudential supervision.

Legal Standardisation: Armenian Standard Derivatives Agreement (ASDA) and ISDA Alignment for Enforceability

The CBA's 2025 initiative introduces Armenian law-governed master documentation, often referred to as the Armenian Standard Derivatives Agreement (ASDA), structured to align with ISDA-style provisions for netting, close-out, and collateral. This supports predictable enforcement in Armenian courts and reduces counterparty risk—key prerequisites for robust reporting and risk monitoring infrastructures. The alignment builds on the 2016 enforceability reforms that recognised and operationalised close-out netting in Armenia's legal system.

Why It Matters for Compliance Teams

• Standardised terms make trade attributes comparable and easier to report consistently.
• Netting and collateral clarity improve exposure metrics, a cornerstone of systemic risk oversight.
• Local-law governance reduces cross-border enforceability uncertainty for Armenian counterparties.

Reportable Instruments and Transactions: Which Derivatives

Although the CBA's supervisory powers cover the derivatives space generally, the 2025 standardisation focuses on Armenian-law master documentation for derivatives and repurchase transactions—capturing common hedging instruments such as rates, FX, and commodity derivatives, as well as repos used for financing and liquidity management.

Tax-wise, the Armenian Tax Code provides a broad VAT exemption for transactions involving financial instruments, including derivatives (sale, transfer, exchange, etc.), with carve-outs where fees relate to underlying goods or services—making hedging and repo operations more cost-effective when properly classified and documented.

Repos and FX Contracts Fall Within the Regime

The CBA's 2025 initiative explicitly extends to repurchase agreements, providing a local-law master framework for repo market activity that dovetails with prudential oversight and potential reporting needs. On the FX side, the CBA's earlier relaxation of foreign exchange risk rules helped normalise the use of FX derivatives for hedging, increasing the likelihood that FX forwards, swaps, and options will be within the scope of any detailed supervisory reporting the CBA may require to manage systemic risk.

Operational Mechanics: Trade-Repository Data Fields

Until the CBA publishes transaction-level specifications, compliance leaders should map internal data to the fields commonly used in trade repositories globally (good practice to ensure readiness). At a minimum, capture and validate:

• Counterparty identifiers (LEI or local equivalent), classification, and domicile.
• Trade economics: product type (e.g., IRS, FX forward), notional, currency, price/fixed rate, strike, maturity dates, underlying, day-count.
• Lifecycle events: new trades, amendments, novations, compressions, terminations.
• Collateral/margin: initial and variation margin, collateral type, segregation, netting set ID.
• Valuation and exposure: mark-to-market, valuation date, collateralised exposure.
• Unique trade/transaction identifiers (UTI) and master agreement references (ASDA/ISDA schedule/date).

These are implementation recommendations to support future CBA trade repository obligations that may be promulgated under the CBA's supervisory authority.

Reporting Timing

In preparation for potential same-day or next-day reporting cycles common in other jurisdictions, set internal service levels for:

• T+0 capture and enrichment of trade, counterparty, and collateral data.
• T+1 reconciliation and exception resolution, with evidence and audit trails.
• Lifecycle reporting for events (e.g., novations, collateral calls) within defined internal cut-offs.

This approach aligns operational readiness with the CBA's capacity to require granular, timely data under its risk-based supervisory mandate.

And Systems Integration Requirements

Ensure your front-, middle-, and back-office systems can produce complete, reconciled trade records that support both regulatory oversight and tax substantiation in Armenia. At a minimum:

• Integrate front-office trading with treasury, risk, and collateral systems to avoid breaks in notional, cash flows, and margin data.
• Connect your ERP and general ledger so accounting entries map to reported trades, enabling VAT-exempt treatment where applicable and evidenced by proper documentation.
• Implement LEI management, counterparty due diligence, and master agreement referencing (ASDA/ISDA).
• Build controls for data quality (completeness, accuracy, timeliness), with audit logs to demonstrate compliance readiness to the CBA.

Readiness Checklist (Quick View)

Workstream	Priority Actions
Contracts	Adopt ASDA/ISDA; maintain executed schedules; record governing law and netting sets.
Data model	Define trade, counterparty, collateral, valuation fields; create UTI generation and matching.
Operations	T+0 capture; T+1 reconciliation; lifecycle event controls aligned with supervisory expectations.
Tax	Map VAT-exempt derivatives; document any fees linked to underlying goods/services.
Governance	Assign reporting owner; implement data quality KPIs; preserve audit trails.

How to Apply a Compliant Reporting Workflow

1. Scope your universe: Create a complete inventory of derivatives, repos, and FX hedges, linking each to a master agreement and counterparty classification.
2. Standardise contracts: Transition legacy confirmations to ASDA/ISDA where feasible; record close-out netting sets to align exposures with legal enforceability.
3. Build the data pipeline: Define reportable attributes; implement controls for completeness, accuracy, and timeliness consistent with supervisory oversight practices.
4. Set timing SLAs: Adopt T+0/T+1 internal cut-offs; establish reconciliation and exception-handling playbooks.
5. Align tax records: Ensure ERP and tax files reflect VAT-exempt treatment for derivative transactions, with documentation for any exceptions.
6. Test and rehearse: Run mock submissions and regulatory-style audits to validate end-to-end readiness.

For broader structuring around financing, treasury, and cross-border ownership, see our resources on investment in Armenia, business registration, and Armenian taxes.

Tax Implications and Documentation

Under Armenia's Tax Code, transactions involving derivatives are generally VAT-exempt; this supports cost-efficient hedging and repo financing when correctly classified and evidenced. Where fees relate to underlying goods or services, the exemption may not apply, so careful documentation and invoicing are required. Accurate reporting and reconciled books help substantiate that a transaction is a qualifying financial instrument operation rather than a taxable supply.

If you need a readiness gap assessment or end-to-end implementation support for Armenia derivatives reporting and tax documentation, contact us.