Nepal has implemented a phased, mandatory e-billing regime through its Inland Revenue Department (IRD) and the Central Billing Monitoring System (CBMS). While not a full Continuous Transaction Controls (CTC) or clearance country, it operates a “near-real-time reporting (CTC-style)” model for in-scope taxpayers [1][24]. The system requires businesses meeting specific turnover thresholds to issue invoices via IRD-certified software that transmits data to the CBMS at the moment of issuance [16]. This initiative is primarily driven by the need to combat VAT fraud, address revenue leakage, and modernize tax administration within Nepal’s significant informal economy [35][33][36]. The mandate has been progressively expanded, with the turnover threshold recently lowered to NPR 200 million (Rs 20 crore) in April 2026 [6].
Main Themes and Important Ideas/Facts
1. Nature of the E-Billing System: Near-Real-Time Reporting (CTC-Style)
- No Universal Clearance: Nepal is explicitly stated as “not a Continuous Transaction Controls (CTC) or clearance country” and has “no mandatory domestic B2B or B2G e-invoicing clearance regime and no mandatory continuous transaction reporting (CTR) system in force” [1].
- Phased, Threshold-Based Mandate: Instead, it employs a “phased mandatory (threshold-based e-billing)” model, meaning it’s “not (yet) a universal, all-taxpayer mandate” [Executive Summary].
- Non-Blocking Reporting: The model is generally described as “near-real-time reporting (CTC-style), generally non-blocking” [Executive Summary]. In-scope taxpayers’ certified billing software transmits invoice data to the CBMS upon issuance, and while the CBMS monitors transactions, it is “generally described as not blocking invoice issuance” [24][16]. However, some sources inconsistently characterize it as “pre-clearance,” an ambiguity noted in the documentation [23][Executive Summary].
- Rationale: The primary driver is to tackle “fake-VAT-bill fraud and revenue leakage,” as highlighted by past exposeés of fraudulent schemes and the large informal economy in Nepal [35][33][36].
2. Scope and Evolution of the Mandate
- Initial Rollout: The CBMS pilot launched on November 17, 2017, becoming operational in FY 2018/19 with approximately 600 large taxpayers [30][33]. The governing rule is the “Electronic Billing Procedure, 2074 (2017), amended repeatedly” [5].
- Expanding Scope (Lowering Thresholds): The mandatory e-billing was extended to firms with annual turnover above Rs 250 million (Rs 25 crore) from the FY 2080/81 (2023/24) budget [11][34]. This threshold was subsequently lowered to Rs 200 million (Rs 20 crore) by an IRD notice dated April 2026 [6]. This “moving threshold” is identified as a key open risk [Executive Summary].
- In-Scope Taxpayers: Applies to “VAT/PAN-registered businesses above the turnover threshold (now Rs 20 crore), plus earlier-phase large taxpayers” [Executive Summary]. It also covers “fraud-prone sectors such as hotels, restaurants and furniture” targeted in earlier phases [24][26][33].
- Exemptions: Banks and financial institutions that do not directly invoice consumers are exempt from CBMS e-billing [6]. Taxpayers below the turnover threshold and outside prescribed sectors are not yet subject to mandatory CBMS e-billing [6][24].
- Transactions Covered: CBMS e-billing applies to in-scope resident taxpayers’ supplies, covering B2B, B2C, and B2G invoicing [24]. The general VAT invoice obligation under Section 14 applies to all VAT-registered persons regardless of CBMS status [1].
- Non-Resident Digital Services: Non-residents supplying digital services to Nepali consumers are subject to 13% VAT and a 2% Digital Service Tax (DST) above an NPR 2 million transaction threshold, effective May 29, 2022. This is a direct reporting obligation to the IRD, distinct from CBMS billing software integration [19][9].
3. Operational Model and Technical Requirements
- Certified Software: Taxpayers must use IRD-certified billing software. This software must transmit each invoice’s data to the CBMS “the moment it is printed” [16][31]. Approval for software reportedly requires source-code submission and CBMS-integration testing [17][15].
- Invoice Lifecycle:Creation: Seller issues a tax invoice from IRD-certified software in the prescribed format [1][5].
- Transmission: Data is sent to CBMS at issuance. In case of connection drops, the system “records the bill locally and queues it for the IRD” for later transmission [16][12].
- Immutability: Once issued, an invoice “cannot be edited or deleted”; data must be non-editable and logged/archived [12][16].
- Correction: Achieved via a credit note that “references the original bill and records the reason” [16].
- Format: Invoices are produced in the prescribed tax-invoice format. Advisors describe the CBMS payload as “JSON/XML per the CBMS schema” [24][25], but a practitioner notes the IRD publishes “no public API and the schema is not openly documented” [17]. Nepal has “no adoption of EN 16931 / Peppol / UBL” [29].
- Digital Signature/QR Code Ambiguity: Evidence regarding QR codes and digital signatures on invoices is conflicting. One source suggests invoices “carry a QR code signed with an Ed25519 cryptographic key,” while a practitioner states that the IRD “hasn’t worked on any such digital verification” [16][17]. This is an “open risk” requiring primary confirmation [Executive Summary].
- Central Platform: The CBMS, operated by the IRD, with the taxpayer portal at ird.gov.np / taxpayerportal.ird.gov.np [7][10].
- Archiving and Retention: The CBMS centrally records transmitted invoice data. Taxpayers must also archive locally. VAT records must be kept for 6 years, while income tax records require 5 years [13][4]. For cloud-based systems, the central server must be located in Nepal [12].
4. Penalties and Enforcement
- VAT Act Penalties: Failure to issue an invoice (VAT Act Section 29(1)(c)) incurs “the amount of tax payable plus Two Thousand Rupees.” False/fabricated invoices (Section 29(2)) can lead to “a fine not exceeding twice the amount of tax or an imprisonment up to Six months, or … both” [1].
- Administrative Fines: Specialist commentary reports administrative fines up to Rs 20,000 per incident for non-issuance and up to Rs 100,000 plus 100% of tax for fraud [14].
- Enforcement: Enforcement is graduated and phased, with measures like sealing/blacklisting for persistent non-compliance [32][14].
5. Impact on SMEs and Future Developments
- Threshold Protection: The turnover threshold (currently Rs 20 crore) shields most micro/small businesses from the mandatory CBMS requirement for now [6].
- Planned Free State Tool: A “state-owned free e-billing tool” is planned for 2026, aimed at small B2C taxpayers to reduce compliance costs (currently Rs 20,000–50,000 for software) [38][Executive Summary].
- Market Landscape: The vendor landscape is predominantly local, with many IRD-certified products available [39][24]. No global CTC provider offers a certified Nepal product [24].
- No Pre-filled Returns: Currently, there is “no evidence of pre-filled returns.” VAT returns are prepared by the taxpayer, with CBMS data used for reconciliation [16][24].
6. International Context
- No International Alignment: Nepal is not an EU Member State, an OECD member, or part of the OECD/G20 BEPS Inclusive Framework [28]. It is not a Peppol Authority and has “no adoption of EN 16931 / Peppol / UBL” [29][Executive Summary]. The CBMS is a “closed national system” [29][24].
- Regional Position: Nepal is an “early regional adopter of transaction-level monitoring” (CBMS live since 2017) but remains “a threshold-limited, phased regime rather than a universal clearance mandate” [1.3].
Key Open Risks / Uncertainties
- Documentation Opacity: The specific CBMS schema/API, the definitive status of QR codes and digital signatures, and the precise “clearance vs. reporting” nature are not settled in public sources and are contested by practitioners [17][16][Executive Summary].
- Moving Thresholds: The mandatory turnover trigger has significantly dropped (from Rs 25 crore to Rs 20 crore within two years), indicating a continued expansion of scope. Businesses need to monitor these changes closely [6][Executive Summary].
- Retention and Penalty Specifics: There are differing statutory retention periods for VAT (6 years) versus income tax (5 years), and current Section 29 penalty amounts require primary confirmation against the latest legal texts [13][4][14][Executive Summary].
Actionable Next Steps for Businesses
- Threshold Confirmation: Confirm whether your entity currently exceeds the Rs 20 crore turnover threshold. If so, prepare to integrate IRD-certified CBMS software [6].
- Regulatory Verification: Verify current VAT-registration thresholds and the precise Section 29 penalty amounts against the latest Finance Act and IRD notifications [21][40][1].
- Retention Period Clarity: Confirm the applicable record retention period for your specific records (VAT vs. income tax) [13][4].
- Monitor State Tool: Keep track of the planned rollout of the state-owned free e-billing software, as this could impact compliance costs and options [38].
- Compliance Review: Ensure internal controls are in place to issue every in-scope sale through certified software, transmit data, maintain immutable records, and reconcile VAT returns line-by-line with CBMS data [12][16].

EXTENDED ARTICLE
Latest Posts in "Nepal"
- Nepal Tax Agency Releases 2026 Finance Act Information Booklet
- Nepal Introduces VAT Directive for Electricity Services with Household and Commercial Rates
- Nepal Imposes 5% VAT on Ride-Sharing Platforms Under Finance Act 2083
- Nepal Clarifies VAT on Electricity Applies Only from July 1, 2026
- NEA Seeks Higher VAT Threshold to Ease Domestic Electricity Bills













