Iran's Moadian E-Invoicing System: Complete Business Guide (2026 Update)
English summary of the complete Persian guide to Iran's Moadian electronic invoicing mandate: legal basis (Article 169 bis), invoice types A/B/J, Karpoosheh, deadlines, the 1–4% penalty ladder, and how accounting software automates compliance.
ℹ️ This is an English summary of the full Persian guide. The complete guide — with Iranian price tables, penalty-rate tables, legal citations and step-by-step screenshots — is available in Persian: راهنمای کامل سامانه مودیان برای صاحبان کسبوکار (بهروز ۱۴۰۴).
One ordinary workday morning, an SMS arrives from the Iranian Tax Organization: "Dear taxpayer, please refer to your Karpoosheh (taxpayer inbox) in the Moadian System to receive an official notice." From that moment, most Iranian business owners face the same flood of questions: What exactly is Karpoosheh? Am I covered by the mandate or not? Are the invoices I have printed for years no longer valid? And the biggest fear: how large is the fine if I act late?
Moadian (سامانه مودیان) is the official electronic invoicing platform of Iran's tax authority (INTA). Under Article 169 Mokarrar ("bis") of the Direct Taxes Act — added by the 2021 amendment — every taxpayer with an active tax file must register in the system and submit sales and purchase invoices electronically through their dedicated Karpoosheh portal. Any transaction that is never submitted is subject to a 1%–4% penalty on the value of that same transaction, and the penalty doubles if the taxpayer still fails to act after the organization's formal two-month notice.
1. What the Moadian system actually is
Moadian is not a simple dashboard; it is a set of interconnected services. The ones you will actually touch as a taxpayer:
- Karpoosheh (کارپوشه) — your personal inbox for official notices, invoice-status tracking, responses to the tax organization's information requests, and tax-file follow-ups. Legal deadlines are counted from the date a notice is delivered here.
- Identity verification service — the secure entry gate where you (or your company's legal representative) authenticate with a national ID and password.
- Invoice reception service — the technical engine that receives invoices from licensed accounting software or intermediary panels and validates them.
- Inquiry system — validates the identity/economic codes of your counterparty before you issue an invoice.
The philosophy is simple: the tax authority wants to move from "declared estimates" to actual transaction data. For a healthy business this is ultimately good news — a fairer tax base, fewer blind presumptive assessments, and a documented tax file that banks and large partners trust.
2. Legal basis: Article 169 vs Article 169 Mokarrar
Article 169 of the Direct Taxes Act is the long-standing obligation to issue an invoice for every sale and hand a copy to the customer. Article 169 Mokarrar (2021 amendment) went a step further: it obliged the tax organization to build the Moadian system, and obliged taxpayers to submit their electronic invoices to it within statutory deadlines. The same article's notes form the basis of the cabinet-approved penalty directive. Always verify the latest rules through the official portal and your own Karpoosheh — implementing rules have been revised several times since the pilot phase began in late 2023.
3. Who must register?
Short answer: every taxpayer with an active file who issues invoices — individuals and legal entities alike. Enforcement has been phased by transaction volume: large taxpayers first (2023–2024), extending through 2024–2025 to smaller traders and retail. Two practical implications: if you are not covered yet, you very likely will be; and the only reliable source for your exact start date is the notice in your own Karpoosheh. Non-resident businesses operating in Iran must appoint a local legal representative. Businesses without a tax file must open one first — Moadian registration is not a substitute.
4. The three invoice types: A, B and J
Choosing the wrong type is one of the most common causes of invoice rejection:
- Type A — B2B sales to buyers who have a national ID / economic code. Recording the buyer's identifiers is mandatory.
- Type B — sales to final consumers without a national ID. Buyer identity is normally not required, but once cumulative purchases by one person exceed announced thresholds, identity details become mandatory.
- Type J — corrective invoices (returns, amount corrections, cancellations), always issued with an explicit reference to the original invoice's unique ID.
In mixed transactions (goods + services), every line item must carry its own correct commodity/service code. For the technical structure of economic codes and the invoice UUID, see the Persian guide.
5. From issuance to final acceptance
An invoice travels five steps: (1) issued in your sales tool; (2) packaged into the standard format — party identifiers, commodity codes, amounts, dates and a unique UUID; (3) transmitted to the reception service (instant if your software is directly connected); (4) validated across multiple layers; (5) finally registered, receiving a tax ID and entering both parties' tax files. Each invoice holds a live status — queued for validation, accepted, rejected-but-correctable, or finally rejected — and the rejection reason is stated in the system response. Experience shows most rejections happen in the first two weeks; after base-data cleanup, rejection rates typically fall below 2%.
6. Deadlines that matter
- Registration — before your mandate period begins, within the deadline stated in your Karpoosheh notice.
- Submission of each invoice — within the deadline set by the issued directives; this is the basis of the 1%–4% penalty calculation.
- Responses to information requests — counted per each notice; ignoring them triggers a separate penalty.
- Correcting a rejected invoice inside its window — legally treated as an on-time submission.
7. Penalties in one table
Based on the current directive, the penalty for an unsubmitted transaction is tiered by its amount: up to 50 million rials (5 million tomans) → 1%, doubled to 2% after the two-month notice; 5–20 million tomans → 2% / 4%; 20–100 million tomans → 3% / 6%; above 100 million tomans → 4% / 8%. Two further layers can stack on an undocumented transaction: a 2% penalty for not issuing an invoice at all, and a 30% performance-tax penalty if the transaction is absent from your legal books. A worked example from the Persian guide: forgetting just two 100-million-toman invoices in one month costs 16 million tomans after the notice period — roughly a year and a half of a full subscription to compliant accounting software. The complete penalty tables, examples and amnesty mechanisms are in the Persian original.
8. Threat or opportunity?
Hoosh's survey of 400 Iranian businesses found that 58% of taxpayers still check their Karpoosheh only weekly or less, and it takes an average of 11 days for a business to discover an unsent or rejected invoice — a delay that is itself a fine-generating event. Early compliers spend only about 7% of extra working time on Moadian tasks, versus 21% for those who delay. The upside for healthy businesses: a fairer tax base computed on real transactions, a credible tax history for loans, tenders and partnerships, faster B2B reconciliation, and forced digital discipline in daily bookkeeping.
9. How Hoosh automates Moadian compliance
Hoosh, the Iranian cloud accounting software, is officially and directly connected to the Moadian system: invoices are transmitted automatically the moment they are issued (no re-entry, no intermediary files), party identifiers and commodity codes are validated before sending, every invoice's acceptance/rejection status is visible inside the same workspace, rejected invoices raise an immediate alert with the stated reason, and Type J corrections are issued in a few clicks with automatic reference to the original invoice. Online sales channels (Digikala, Basalam, WooCommerce) convert automatically into compliant invoices, and photographing a purchase invoice lets the AI OCR (98% claimed accuracy) turn it into an accounting document.
10. A 90-day compliance roadmap
- Weeks 1–2: identity verification, Moadian registration, receive your identifiers.
- Weeks 3–4: commodity coding against the official list; complete organizational customer records — clean base data is the single biggest driver of fewer rejections.
- Weeks 5–6: connect your accounting software and complete a test submission.
- Weeks 7–8: issue real invoices, monitor statuses daily, fix errors.
- Weeks 9–12: turn monitoring into routine, train the sales team, document procedures.
Bottom line: Moadian is the new legal infrastructure of the Iranian economy. The penalty ladder is mechanical, not negotiable; the painless path is software that sends and monitors invoices for you. If you operate in Iran, start with the free 7-day Hoosh trial (no bank card required) — and for the full penalty tables, legal citations and registration walkthroughs, read the complete Persian guide. For the software-selection context around this mandate, see our English summaries of cloud vs desktop accounting in Iran and the 15-criteria buying framework; the Persian cloud-guide «نرمافزار حسابداری ابری چیست؟» covers the underlying concepts in depth.
Continue in Persian
The full guide — with Iranian price tables, penalty-rate tables and legal citations — is published in Persian: