VATupdate
Nepal

Share this post on

Nepal — E-Invoicing & E-Reporting Country Booklet


Executive Summary

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

  1. 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].
  2. 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].
  3. 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].

advert


EXTENDED ARTICLE

CTC / Continuous Transaction Controls Analysis for Senior Leadership

Information cut-off date: 2 July 2026. All statements reflect sources available on or before this date. Every substantive statement carries an inline citation [n] resolving to the numbered source list in Chapter 20. Where information is unavailable, not yet legislated, or not applicable, this is stated explicitly rather than omitted. Sources older than 12 months or apparently superseded are flagged inline. Local-language terms are given in Dutch with an English gloss on first mention.

One-line orientation: Nepal is not a Continuous Transaction Controls (CTC) or clearance country. It has no mandatory domestic B2B or B2G e-invoicing clearance regime and no mandatory continuous transaction reporting (CTR) system in force. Nepal has introduced tax digitalisation measures through the Inland Revenue Department (IRD), including electronic tax services and electronic billing requirements for certain categories of taxpayers, but it does not operate a nationwide real-time invoice clearance model comparable to CTC jurisdictions. As of 2 July 2026, no general domestic B2B e-invoicing or digital-reporting mandate requires all businesses to transmit invoice data to the tax authority in real time or near real time. [1][2][4]

Chapter 0 — Executive Summary “At-a-Glance”

Country: Federal Democratic Republic of Nepal. Tax authority: Inland Revenue Department (IRD). Information cut-off date: 9 July 2026. (Nepal uses the Bikram Sambat (BS) calendar; BS years are given alongside Gregorian throughout — e.g. 2074 BS ≈ 2017, 2080/81 BS ≈ 2023/24, 2082/83 BS ≈ 2025/26.)

  • Status: Phased mandatory (threshold-based e-billing). Electronic billing linked to the IRD’s Central Billing Monitoring System (CBMS) is mandatory for in-scope taxpayers; it is not (yet) a universal, all-taxpayer mandate. Notably, Nepal does not appear in the EY E-invoicing Developments Tracker as of 17 June 2026 [20], so this booklet is sourced from the IRD, Nepali law and specialist advisors rather than that tracker.
  • Model: Near-real-time reporting (CTC-style), generally non-blocking. In-scope taxpayers must issue invoices through IRD-certified billing software that transmits each invoice’s data to the CBMS at the moment of issuance; the CBMS records and monitors transactions but is generally described as not blocking invoice issuance [24][16]. (Some advisor sources describe it as “pre-clearance” — the characterisation is inconsistent and is flagged in Chapter 6 [23].)
  • Mandatory format(s): Invoices are produced by IRD-certified computerised billing software in the prescribed tax-invoice format; advisors describe the CBMS payload as JSON/XML per the CBMS schema [24][25], though a practitioner notes the IRD publishes no public API and the schema is not openly documented [17]. There is no adoption of EN 16931 / Peppol / UBL [29].
  • Key go-live dates: CBMS pilot launched 17 November 2017, operational in FY 2018/19 with ~600 large taxpayers [30][33]; governing rule is the Electronic Billing Procedure, 2074 (2017), amended repeatedly (4th amendment 5 October 2021) [5]; mandatory e-billing extended to firms with annual turnover above Rs 250 million (Rs 25 crore) from the FY 2080/81 (2023/24) budget [11][34]; threshold lowered to Rs 200 million (Rs 20 crore) by IRD notice dated 4 Baishakh 2083 (≈ April 2026) [6].
  • Taxpayers in scope: VAT/PAN-registered businesses above the turnover threshold (now Rs 20 crore), plus earlier-phase large taxpayers; banks and financial institutions that do not directly invoice consumers are exempt [6]. Standard VAT rate is 13% [21].
  • Central platform / operator: the CBMS, operated by the IRD, with the taxpayer portal at ird.gov.np / taxpayerportal.ird.gov.np [7][10].
  • Penalty exposure (headline): VAT Act 2052 Section 29(1)(c) — failure to issue an invoice: “the amount of tax payable plus Two Thousand Rupees”; Section 29(2) — false/fabricated invoices: “a fine not exceeding twice the amount of tax or an imprisonment up to Six months, or … both” [1]. Specialist commentary reports current administrative fines up to Rs 20,000 per incident (non-issuance) and up to Rs 100,000 plus 100% of tax for fraud [14].
  • ViDA alignment: N/A. Nepal is not an EU Member State; the EU VAT in the Digital Age package (adopted March 2025) does not apply. Nepal is not an OECD member, not a member of the OECD/G20 BEPS Inclusive Framework [28], and not a Peppol Authority [29].
  • Top 3 open risks / uncertainties: (1) Documentation opacity — the CBMS schema/API, QR/digital-signature status and even the “clearance vs reporting” nature are not settled in public sources and are contested by a practitioner [17][16]; (2) Moving thresholds — the mandatory-turnover trigger dropped from Rs 25 crore to Rs 20 crore within ~2 years, and a state-owned free e-billing tool is planned for 2026, so scope is expanding [6][38]; (3) Retention/penalty specifics — VAT (6-year) vs income-tax (5-year) retention and current Section 29 penalty amounts require primary confirmation [13][4][14].
  • Information cut-off date: 9 July 2026.

Chapter 1 — Introduction & Country Context

1.1 Tax digitalisation journey leading to the mandate

Nepal’s e-billing regime is built on the Value Added Tax Act, 2052 (1996) (VAT implemented from FY 1998/99) and its invoicing rules [1][3]. A statutory hook for computerised billing was added as Section 14(5) by the Financial Ordinance 2060 (2003), empowering the Department to “order taxpayers to issue invoices by using a cash machine or computer” [1]. The IRD operationalised this through the Electronic Billing Procedure, 2074 (2017) and launched the Central Billing Monitoring System (CBMS) as a pilot on 17 November 2017, linking large taxpayers’ billing software directly to IRD servers [5][30][31].

1.2 Rationale (VAT gap, fraud prevention, modernisation)

The driving rationale is fake-VAT-bill fraud and revenue leakage. In 2021 the Department of Revenue Investigation exposed a racket in which scores of firms issued fake VAT bills; the IRD later framed the CBMS as targeting “tax evasion practices, such as using fake VAT bills, concealing genuine transaction details, employing duplicate excise duty stickers” [35][33]. Nepal’s informal economy is large — estimated at 38.6% of GDP for 2020–21 (with some studies as high as ~51%) — and VAT is heavily import-based, indicating weak internal-VAT mobilisation [36][37].

1.3 Positioning: early mover / follower

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. It sits between India’s blocking IRP/IRN clearance model (mandatory since 2020) and jurisdictions with no live system; unlike Mongolia (mandatory since 2016) it covers only in-scope taxpayers [24][23].

1.4 Supranational authorisation / derogation

Not applicable. As a non-EU state, Nepal needs no EU derogation, and Directive 2014/55/EU (B2G) does not apply. Nepal is not an OECD member and is not in the OECD/G20 BEPS Inclusive Framework [28]. IMF engagement (e.g. under the Extended Credit Facility) has emphasised domestic revenue mobilisation and automation generally, though the June 2026 IMF country report does not name the CBMS specifically [27].

Chapter 2 — Regulatory Framework

2.1 Primary legislation

The core statute is the Value Added Tax Act, 2052 (1996) [1][2]. Section 14(1) requires that “Every registered person is required to issue an invoice to the recipient, in supplying any goods and services save the circumstances as prescribed,” with the format “as prescribed” (Section 14(2)) and computerised billing enabled by Section 14(5) [1]. The standard VAT rate is 13% (raised from 10% in 2005; the rate is set annually by the Finance Act under Section 7) [21][37]. Record-keeping and penalties sit in Sections 16 and 29 [1]. The Income Tax Act, 2058 (2002) governs income-tax records and retention [4].

2.2 Implementing regulations, decrees, orders

The Value Added Tax Rules, 2053 (1997) prescribe invoice formats, the abbreviated (retail) invoice (permitted up to a NPR 10,000 per-transaction ceiling) and record retention [13][18]. The e-billing regime is governed by the Electronic Billing Procedure, 2074 (2017) and its amendments (4th amendment published 5 October 2021), covering “Listing of Billing Equipment and Software,” “Approval for Electronic Billing,” and the requirements for billing software and cloud computing [5]. The mandatory-turnover thresholds were set by successive Finance Acts and IRD notices — Rs 25 crore (FY 2080/81 budget) [11], reduced to Rs 20 crore by IRD notice 4 Baishakh 2083 (≈ April 2026) [6].

2.3 Circulars, administrative rulings, FAQs

The IRD publishes CBMS notices and the certified-software registry, plus the Digital Service Tax Procedure, 2079 (2022) [6][7][9]. An IRD notice of 3 Asaar 2079 (June 2022) reinforced mandatory issuance of invoices by electronic means for prescribed taxpayers [8].

2.4 Supranational / international legal basis

Not applicable for EU instruments. Nepal’s international footprint is limited: it is not in the BEPS Inclusive Framework [28] and is not a Peppol Authority [29].

Chapter 3 — Scope of the Mandate

3.1 Transactions in scope

CBMS e-billing applies to in-scope resident taxpayers’ supplies — covering B2B, B2C and B2G invoicing — where the taxpayer meets the turnover threshold (now Rs 20 crore) or falls within an earlier phase (large taxpayers; fraud-prone sectors such as hotels, restaurants and furniture) [24][26][33]. The general VAT invoice obligation under Section 14 applies to all VAT-registered persons regardless of CBMS status [1].

3.2 Special transactions

Non-resident digital-service supplies to Nepali consumers are subject to 13% VAT and a 2% Digital Service Tax, effective 29 May 2022, above an NPR 2 million transaction threshold [19][9]. These are reported by the non-resident directly to the IRD (not via CBMS billing software) [19]. Abbreviated (retail) invoices are permitted for small-value B2C sales but do not confer input-VAT credit [18][13].

3.3 Excluded / exempt transactions

VAT-exempt and zero-rated supplies are listed in the Schedules to the VAT Act [1]. Within the e-billing mandate, banks and financial institutions that do not directly issue invoices to consumers are exempt from CBMS e-billing per the 2026 IRD notice [6]. Taxpayers below the turnover threshold and outside prescribed sectors are not yet subject to mandatory CBMS e-billing [6][24].

Chapter 4 — Taxable Persons in Scope

4.1 Established domestic entities

VAT registration is compulsory for a goods business once 12-month turnover exceeds Rs 5 million (Rs 50 lakh), and for services/mixed business at a lower threshold — reported as Rs 2 million by one advisor and Rs 3 million (per the Finance Act 2081) by another; the current-year figure should be confirmed against the operative Finance Act [21][40]. CBMS e-billing then applies to those above the Rs 20 crore turnover trigger or in an earlier phase [6][33].

4.2 Non-established entities

Non-residents supplying digital services must obtain a PAN, register, and file VAT monthly (and DST) where transactions exceed NPR 2 million in 12 months; this is a direct-reporting obligation, distinct from CBMS billing-software integration [19][9].

4.3 Voluntary participation models

Businesses below the threshold may adopt IRD-certified e-billing voluntarily, and many do to obtain compliant tax invoices [24][15]. Voluntary VAT registration is also available [21].

4.4 Sector-specific rules and exemptions

Earlier CBMS phases targeted fraud-prone sectors (e.g. hotels, restaurants, furniture/flooring) and large taxpayers [26][33]. Certain sectors face compulsory VAT registration from first sale regardless of turnover (advisor-reported list includes liquor, tobacco, hotels, software, telecom and professional services); this list is advisor-sourced and should be confirmed against the underlying IRD notification [40].

Chapter 5 — Implementation Timeline

5.1 Legislative history and milestones

  • 1996 (2052 BS): VAT Act enacted; VAT implemented FY 1998/99 [1][37].
  • 2003 (2060 BS): Section 14(5) added, enabling cash-machine/computer billing [1].
  • 2005: standard VAT rate raised from 10% to 13% [37].
  • 17 November 2017 (2074 BS): CBMS pilot launched (~600 large firms; 140 licensed software developers) [30][32].
  • FY 2018/19: CBMS operational [33].
  • June 2022 (3 Asaar 2079): IRD notice reinforcing mandatory electronic invoicing [8].
  • 29 May 2022: 13% VAT + 2% DST on non-resident digital services [19].
  • 5 October 2021: Electronic Billing Procedure 2074, 4th amendment [5].
  • FY 2080/81 (2023/24): mandatory e-billing for turnover above Rs 25 crore [11][34].
  • 4 Baishakh 2083 (≈ April 2026): threshold lowered to Rs 20 crore [6].

5.2 Voluntary / pilot phases and incentives

The 2017 pilot (first participant reported as Sipradi Trading) preceded phased mandatory rollout; adoption has been driven by the certified-software requirement rather than consumer incentives [30][32].

5.3 Mandatory go-live dates (issuance vs receipt)

For in-scope taxpayers, issuance and real-time CBMS registration are simultaneous; there is no separate buyer-side receipt obligation [24][6].

5.4 Grace periods and transitional provisions

Rollout has been phased by turnover and sector, with the IRD issuing directives giving taxpayers time to upgrade software [32][33]. The 2026 threshold reduction expands the mandatory population [6].

5.5 Pre-mandate technical milestones

The IRD maintains a certified-software registry (several hundred approved applications) as the standing prerequisite for CBMS integration [7][39].

5.6 Known or anticipated postponements

No formal postponement of the core mandate is indicated. The principal forward item is the planned state-owned free e-billing software (reported May 2026), for which no firm launch date has been published [38].

Chapter 6 — Operating Model (How It Really Works)

6.1 Model type and role of the tax authority

Nepal operates a near-real-time transaction-reporting (CTC-style) model: certified billing software transmits each invoice’s data to the IRD’s CBMS “the moment it is printed,” enabling the IRD to “monitor and retrieve all transaction data” [16][31]. Whether the CBMS is strictly non-blocking reporting (e-invoice.app: “The CBMS does not block invoice issuance” [24]) or a pre-clearance step (vatcalc [23]) is characterised inconsistently across secondary sources; the weight of evidence favours near-real-time reporting rather than blocking clearance, and this ambiguity is flagged for the reader.

6.2 Step-by-step invoice lifecycle

  • Creation: the seller issues a tax invoice from IRD-certified software in the prescribed format [1][5].
  • Transmission: the software sends the invoice data to the CBMS at issuance; if the connection drops, a compliant system “records the bill locally and queues it for the IRD” [16][12].
  • Immutability: once issued, an invoice cannot be edited or deleted; data must be non-editable and logged/archived [12][16].
  • Correction: via a credit note that references the original bill and records the reason (Chapter 9) [16].
  • Verification: invoices may carry a QR/verification code, though the existence and cryptographic basis of this are disputed (see 6.6) [16][17].

6.3 Authentication and access methods

Taxpayers use IRD-certified software registered under the Electronic Billing Procedure 2074; software approval reportedly requires source-code submission and CBMS-integration testing [5][17][15]. Access to filing services is via the IRD taxpayer portal [10].

6.4 Offline / contingency mode

Compliant software must buffer invoices locally and forward them to the CBMS when connectivity is restored, rather than failing the sale [16][12]. A formally published national contingency specification was not located in primary sources [17].

6.5 Buyer-side workflow

There is no mandated buyer accept/reject workflow; input-VAT credit depends on holding a valid tax invoice (abbreviated invoices do not confer credit) [18][13].

6.6 QR / verification code requirements

Evidence is conflicting: one vendor guide states invoices “carry a QR code signed with an Ed25519 cryptographic key,” while a practitioner states that “even approved electronic software have not adopted digital signature modules” and that the IRD “hasn’t worked on any such digital verification” [16][17]. The QR/digital-signature position should therefore be treated as unverified pending a primary IRD specification [17].

Chapter 7 — Acceptable E-Invoice Formats

7.1 Mandatory format(s)

The mandatory instrument is the prescribed tax invoice produced by IRD-certified billing software, transmitted to the CBMS [5][1]. Advisors describe the CBMS payload as JSON/XML per the CBMS schema [24][25]; however, no openly published IRD schema/API was located, and a practitioner states the IRD provides “no public API” [17].

7.2 Relationship to international standards

Nepal has no adoption of EN 16931, Peppol BIS 3.0, UBL 2.1 or UN/CEFACT CII, and is not a Peppol Authority [29][24].

7.3 Voluntary / legacy / transitional formats

Paper and abbreviated (retail) invoices remain in use for out-of-scope taxpayers and small B2C sales [18][13]. Hybrid formats (Factur-X/ZUGFeRD) are not part of the Nepali framework [24].

7.4 Attachments

No specific national rule on invoice attachments was identified; treat as “no official guidance located” [17].

Chapter 8 — Technical & Functional Requirements

8.1 E-invoice specifications

Certified billing software must use a relational database (e.g. MySQL, PostgreSQL, SQL Server), issue immutable, timestamped, sequentially numbered invoices, enforce single-print with “Copy of Original” reprints, log/archive every transaction, and transmit real-time data to the CBMS [12]. Mandatory invoice content follows the VAT Rules’ prescribed format (supplier/buyer details, PAN, invoice number, description, value, 13% VAT) [1][13].

8.2 E-reporting specifications

VAT returns are monthly, due within 25 days of the month-end (by the 25th of the following month) [23]. CBMS data is used to reconcile against the return line by line; there is no evidence of pre-filled/auto-populated VAT returns (see Chapter 15) [16][24].

8.3 Digital signature and integrity

Integrity rests on software immutability plus real-time CBMS transmission and central logging rather than a confirmed per-invoice digital signature; the digital-signature/QR position is disputed (see 6.6) [12][17].

8.4 Real-time / near-real-time / batch processing

Processing is near-real-time at issuance, with local queuing on connectivity loss [16][12]. No published performance target was located [17].

Chapter 9 — Correction of Errors

9.1 E-invoice corrections

Because issued invoices are immutable, corrections are made by a credit note that “references the original bill and records the reason,” re-transmitted through the CBMS-connected software [16]. The VAT Act provides for credit/debit adjustments; specific rule references were not primary-verified [1][13].

9.2 E-reporting corrections

Amended VAT returns follow IRD procedure; late returns and late payment attract interest and fees (Chapter 14) [14]. Specific corrective-return deadlines were not separately verified [14].

Chapter 10 — Transmission & Workflow

10.1 Central platform

The central platform is the Central Billing Monitoring System (CBMS), operated by the IRD, with the taxpayer portal at ird.gov.np / taxpayerportal.ird.gov.np [7][10].

10.2 Transmission channels

The channel is IRD-certified billing software integrated to the CBMS; there is no Peppol network and (per a practitioner) no openly published public API [17][29]. A planned government-owned mobile e-billing tool would add a free channel [38].

10.3 Accredited service providers / certified intermediaries

Software must be certified/registered by the IRD under the Electronic Invoice/Billing Procedure 2074; the IRD publishes a registry of several hundred approved applications, and many local vendors (e.g. BUSY, Swastik, Tigg, OneFlow, BizPro) market IRD-certified products [7][39][24]. No global CTC provider was found offering an IRD-certified Nepal product [24].

10.4 Interoperability

CBMS is a closed national system with no Peppol or cross-border interoperability and no cross-border digital-reporting exchange [29][24].

10.5 Deadlines and timing

Invoice data transmits at issuance (near-real-time); the monthly VAT return is due by the 25th of the following month [16][23].

Chapter 11 — Self-Billing

  • 1 Legality: No distinct national self-billing (recipient-created tax invoice) regime was identified; invoicing is seller-issued [1][17].
  • 2–11.6: No dedicated self-billing routing, authorisation, content, flag or foreign-buyer rules were located; treat as “no official self-billing guidance located” [17].
  • 7 Buyer-side approval: Buyer participation is limited to holding a valid tax invoice for input-VAT credit [18][13].

Chapter 12 — Triangulation & Special Scenarios

  • 1 Triangulation / 12.2 Chain transactions: No dedicated CBMS rules were located; each supply generates its own invoice [17].
  • 3 Cross-border / non-resident: Non-resident digital services are taxed via 13% VAT + 2% DST with direct IRD reporting [19][9]; imports are taxed under the VAT Act [1].
  • 4 Zero-rated and exempt supplies: Exports are zero-rated and exemptions are scheduled in the VAT Act; annotated on the standard invoice [1].
  • 5 Local nuances: The abbreviated (retail) invoice (up to NPR 10,000, no input credit) and the fraud-prevention focus (fake-bill enforcement) are the defining local features [18][35].

Chapter 13 — Archiving & Retention

13.1 Central archiving by the platform

The CBMS centrally records transmitted invoice data, giving the IRD retrieval access; taxpayers must also archive locally [24][12].

13.2 Mandatory archiving format(s)

Data is retained in the certified software’s database (non-editable, logged) and centrally in the CBMS [12][24].

13.3 Retention period

Retention periods differ by statute: VAT records must be kept 6 years (VAT Act Section 16 / VAT Rules, per specialist commentary) [13], while income-tax records must be kept at least 5 years from the end of the income year under Income Tax Act Section 81(2) [4]. (One advisor profile cites 5 years generally [25]; the VAT-specific 6-year figure and its rule cite should be confirmed against the primary VAT Rules [13].)

13.4 Storage location

For cloud-based systems, the Electronic Billing Procedure requires the central server to be located in Nepal, with IRD access [12].

13.5 Integrity, authenticity, readability

Integrity rests on immutable, timestamped, logged records plus central CBMS transmission [12][16].

13.6 Audit accessibility

The IRD has retrieval access to CBMS-recorded transactions, supporting real-time monitoring and audit [31][33].

Chapter 14 — Penalties & Enforcement

14.1 Grace period / graduated enforcement

Enforcement is graduated and phased, with directives allowing software upgrades; sealing/blacklisting are used for persistent non-compliance [32][14].

14.2 Penalties by category

Under the VAT Act 2052: failure to issue an invoice (Section 29(1)(c)) attracts “the amount of tax payable plus Two Thousand Rupees,” and false/fabricated invoices (Section 29(2)) attract “a fine not exceeding twice the amount of tax or an imprisonment up to Six months, or … both” [1]. Specialist commentary reports current administrative fines of up to Rs 20,000 per incident for invoice breaches, up to Rs 100,000 plus 100% of tax for fraud, 100% of tax for under-reporting, and up to Rs 10,000 for failure to register [14].

14.3 Penalty amounts and escalation

Late VAT payment reportedly attracts 15% annual interest plus 1% per month, and late returns Rs 1,000–5,000 [14]. No discrete monetary penalty labelled “failure to connect to the CBMS” was located; non-compliance is enforced through the Section 14/29 invoice penalties and administrative measures (sealing, blacklisting) [1][14].

14.4 Article references and links

Primary references: VAT Act 2052 Sections 14, 16, 29 [1]; Electronic Billing Procedure 2074 [5]; IRD CBMS notices [6][8].

Chapter 15 — Pre-Filled VAT Returns

  • 1 Available today? No evidence of pre-filled returns. CBMS captures invoice data in near-real-time, but returns are prepared by the taxpayer; only reconciliation against CBMS data is described [16][24].
  • 2 Fields pre-filled vs input required: All return fields are taxpayer-input today [24].
  • 3 Announced plans and timeline: No pre-filled-return roadmap was located [24].
  • 4 Dependency on e-invoicing/e-reporting data: Any future pre-filling would rely on CBMS data, which exists for in-scope taxpayers [24].
  • 5 Alignment with ViDA pre-filled return provisions: N/A (non-EU) [20].

Chapter 16 — ViDA / International Digital Reporting Readiness

16.1 Country position

N/A to ViDA (non-EU). Against CTC benchmarks, Nepal is a phased, threshold-limited real-time-reporting regime — ahead of jurisdictions with no live system but behind universal-mandate peers [24][23].

16.2 Alignment of national format and model

CBMS is a proprietary national system with no EN 16931/Peppol/UN-CEFACT alignment and no Peppol Authority status [29][24]. Gaps relative to international CTC norms include the absence of an openly published schema/API and unresolved digital-signature standards [17].

16.3 Cross-border digital reporting

Nepal has no cross-border B2B digital-reporting framework and does not participate in the EU’s planned 2030 cross-border DRR or any equivalent exchange [29][24]. It is not in the BEPS Inclusive Framework [28].

16.4 Business implications

For multinationals, Nepal is a compliance-now jurisdiction for in-scope entities: use IRD-certified CBMS-integrated software, retain records per the VAT/income-tax rules, and monitor the falling turnover threshold and the planned state-owned e-billing tool [6][38][7].

Chapter 17 — Impact on SMEs and Startups

  • 1 Phased onboarding: The turnover threshold (now Rs 20 crore) keeps most micro/small businesses outside the mandatory CBMS net for now, while larger firms and fraud-prone sectors are in scope [6][33].
  • 2 Free government tools, education, helpdesks: No government-provided free e-billing tool exists yet; a state-owned free mobile e-billing platform was reported as planned in May 2026, aimed at small B2C taxpayers [38]. Private “free, IRD-certified” options are marketed by vendors [24].
  • 3 Simplified regimes and threshold exemptions: Small taxpayers below the VAT-registration and CBMS thresholds remain outside the mandate; abbreviated invoices simplify low-value retail [18][6].
  • 4 Subsidies, tax credits, grants: None identified; the planned state tool would cut software cost (reported at Rs 20,000–50,000 plus renewals today) [38].
  • 5 Compliance costs: Buying and maintaining IRD-certified software is the principal SME cost, which the state tool aims to remove [38][16].
  • 6 Cash-flow and operational benefits: Central recording reduces disputes and supports cleaner audits [33][16].
  • 7 Net administrative burden vs simplification: Weak active compliance (a large share of nil/credit VAT returns) suggests real capacity constraints among smaller filers [37].
  • 8 Market and competitive impact: CBMS narrows the space for fake-bill operators, helping compliant businesses compete [35][33].
  • 9 Official assessments of SME readiness: VAT registrations reached ~314,076 by mid-2022; no primary quantified SME-readiness assessment was located [37].

Chapter 18 — Practical Implementation Considerations

  • 1 ERP/finance-system impacts: ERP/POS systems must use or integrate an IRD-certified billing module that transmits to the CBMS; the IRD registry lists the approved stacks [7][39].
  • 2 Master-data prerequisites: Accurate PAN, invoice numbering, item and VAT (13%) data, and — for cloud systems — Nepal-based server hosting are prerequisites [12][1].
  • 3 Common pitfalls: Editable/deletable records or missing real-time transmission fail certification; connectivity handling (local queue) is essential; QR/digital-signature expectations are unsettled [12][16][17].
  • 4 Vendor/service-provider landscape: Predominantly local vendors (e.g. BUSY, Swastik, Tigg, OneFlow, BizPro) certified under Procedure 2074; no global CTC provider found offering a certified Nepal product [39][24].
  • 5 Governance and internal control: Controls should ensure every in-scope sale is issued through certified software and transmitted, records are immutable and logged, and returns reconcile line-by-line to CBMS data [12][16].

Chapter 19 — Summary & Key Takeaways

  • 1 Scope: Phased mandatory CBMS e-billing for in-scope taxpayers (turnover above Rs 20 crore, plus earlier large-taxpayer/sector phases); banks/FIs not directly invoicing consumers are exempt [6][33].
  • 2 Format: Prescribed tax invoice via IRD-certified software transmitted to CBMS; advisor-described JSON/XML schema, no open public API; no EN 16931/Peppol [24][17][29].
  • 3 Timeline: CBMS since 2017; Rs 25 crore threshold from FY 2080/81; lowered to Rs 20 crore in ~April 2026; state-owned tool planned 2026 [30][11][6][38].
  • 4 How it works: Near-real-time, generally non-blocking transaction reporting to the IRD (clearance characterisation disputed) [24][23].
  • 5 Key obligations: Use certified software; issue/transmit every in-scope invoice; file the monthly VAT return by the 25th; retain VAT records ~6 years / income-tax records ~5 years [1][23][13][4].
  • 6 Main risks: Documentation opacity (schema/API, QR/signature), falling thresholds, and unresolved retention/penalty specifics [17][6][13].
  • 7 SME implications: Threshold shields most SMEs today; a free state tool is planned to cut software cost [6][38].
  • 8 ViDA / international readiness: ViDA N/A; not OECD; not BEPS Inclusive Framework; not a Peppol Authority [28][29].
  • 9 Critical dates & next steps (actionable): Confirm whether your entity now exceeds the Rs 20 crore trigger and integrate IRD-certified CBMS software if so [6]; verify current VAT-registration thresholds and Section 29 penalty amounts against the latest Finance Act [21][40][1]; confirm the applicable retention period (VAT vs income tax) [13][4]; monitor the state-owned e-billing rollout [38].

Chapter 20 — Official References & Sources

20.1 Government portals

Inland Revenue Department — ird.gov.np [2]; IRD taxpayer portal [10]; IRD certified-software registry [7]; IRD CBMS notice (Rs 20 crore) [6].

20.2 Legislative texts

VAT Act 2052 (ICAN translation) [1]; VAT Act bilingual text [3]; Income Tax Act 2058, Section 81 [4]; Electronic Billing Procedure 2074 (4th amendment) [5]; Digital Service Tax Procedure 2079 [9].

20.3 Technical specifications

IRD certified-software registry [7]; Electronic Billing Procedure requirements [12]; practitioner note on the absence of a public API [17]. No openly published CBMS schema/API located [24][17].

20.4 Tax authority publications

IRD CBMS notices [6][8]; ICAN Federal Budget 2080/81 highlights (Rs 25 crore) [11].

20.5 Advisor and technology publications

EY (DST alert; E-invoicing Tracker) [19][20]; Baker Tilly (VAT portal; Tax Fact 2024/25) [21][22]; vatcalc [23]; e-Invoice.app [24]; Voxel Group [25]; specialist guides [12][13][14][15][16][17][18].

20.6 VATupdate.com and recent briefings

VATupdate Nepal budget briefing (30 May 2024) [26]; media coverage of the CBMS expansion and state tool [33][34][38].

20.7 Numbered source list

[1] Value Added Tax Act, 2052 (1996) — authoritative English translation hosted by the Institute of Chartered Accountants of Nepal (ICAN). https://en.ican.org.np/_browsable/file/career/23Value-Added-Tax-Act-2052.pdf

[2] Inland Revenue Department (IRD) — Value Added Tax Act 1996/2052 landing page. https://ird.gov.np/content/7798/thevalueaddedtaxact19962052/

[3] Value Added Tax Act, 2052 (1996) — bilingual section text (actnepal). https://actnepal.com/en/act/3/27/value-added-tax-act-2052-1996

[4] Income Tax Act, 2058 (2002), Section 81 (record retention) — actnepal. https://actnepal.com/en/section/269/0/section-81-to-maintain-records-or-documents-of-income-tax-act-2058-2002

[5] IRD — Electronic Billing Procedure, 2074 (4th amendment, published 5 October 2021), via Baker Tilly Nepal tax portal. https://bakertilly.com.np/tax-portal/notices-and-circulars/electronic-billing-procedure-2074-4th-amendment

[6] IRD — CBMS notice lowering mandatory e-billing threshold to Rs 20 crore (notice 4 Baishakh 2083; decision 27 Poush 2082). https://ird.gov.np/content/13488/cbms-notice-01-04/

[7] IRD — registry of certified electronic billing software (under the Electronic Invoice Procedure, 2074). https://www.ird.gov.np/public/pdf/834857563.pdf

[8] IRD — notice on mandatory issuance of invoices by electronic means (3 Asaar 2079 / June 2022). https://ird.gov.np/content/8070/notice-16542603731/

[9] IRD — Digital Service Tax Procedure, 2079 (2022). https://ird.gov.np/public/pdf/1935769683.pdf

[10] IRD — Taxpayer Portal. https://taxpayerportal.ird.gov.np

[11] ICAN — Highlights of the Federal Budget 2080/81 (CBMS Rs 25 crore threshold, Highlight 453). https://en.ican.org.np/_browsable/file/downloads/Highlights_of_Federal_Budget_2080_81.pdf

[12] ebillingnepal.com — ‘Legal Provision for E-Billing in Nepal’ (Electronic Billing Procedure requirements). https://ebillingnepal.com/en/articles/legal-provision-for-e-billing-nepal

[13] notarynepal.com — ‘VAT Rules in Nepal’ (retention, abbreviated invoice). https://notarynepal.com/blog/vat-rules-in-nepal

[14] commonlaw.com.np — ‘VAT Invoice Rules & Penalties in Nepal 2026’. https://commonlaw.com.np/publications/vat-invoice-rules-and-penalties-in-nepal

[15] estartupnepal.com — ‘E-Billing in Nepal: Process, Benefits & Legal Guidelines’. https://estartupnepal.com/article/e-billing-in-nepal

[16] mis.ac — ‘Electronic Billing in Nepal: The IRD CBMS Compliance Guide’. https://mis.ac/articles/blog/electronic-billing-cbms-nepal.php

[17] Sushil Parajuli — ‘Electronic Invoicing in Nepal: User’s Perspective’. https://sushilparajuli.com/electronic-invoicing-in-nepal-users-perspective/

[18] nepaltaxes.com — ‘Provisions relating to Invoices / Abbreviated Tax Invoice’. https://nepaltaxes.com/provisions-relating-to-invoices-guide-to-invoice-abbreviated-tax-invoice/

[19] EY — ‘Nepal Inland Revenue Department amends VAT and DST procedures’ (Global Tax Alert, 28 August 2023). https://www.ey.com/en_gl/technical/tax-alerts/nepal-inland-revenue-department-amends-vat-and-dst-procedures-re

[20] EY — E-invoicing Developments Tracker (as of 17 June 2026; Nepal not listed). https://www.ey.com/content/dam/ey-unified-site/ey-com/en-gl/technical/tax-guides/documents/en-gl-einvoicing-developments-tracker.pdf

[21] Baker Tilly Nepal — VAT tax portal (13% rate; registration thresholds). https://bakertilly.com.np/tax-portal/vat

[22] Baker Tilly Nepal — Tax Fact 2024/25. https://bakertilly.com.np/storage/download/1718620336_Tax_Fact_2024-25.pdf

[23] vatcalc — Nepal e-invoicing. https://www.vatcalc.com/nepal/nepal-e-invoicing/

[24] e-Invoice.app — Nepal e-invoicing country profile. https://www.e-invoice.app/country/NP

[25] Voxel Group — Electronic Invoicing Guide in Nepal. https://www.voxelgroup.net/compliance/guides/nepal/

[26] VATupdate — ‘Nepal’s 2024-25 Budget Introduces Mandatory E-Invoicing to Combat Fraud’ (30 May 2024). https://www.vatupdate.com/2024/05/30/nepals-2024-25-budget-introduces-mandatory-e-invoicing-for-businesses-to-combat-fraud/

[27] IMF — Nepal, Country Report No. 26/127 (June 2026). https://www.imf.org/-/media/files/publications/cr/2026/english/1nplea2026002.pdf

[28] OECD — Members of the OECD/G20 Inclusive Framework on BEPS (Nepal not listed). https://www.oecd.org/tax/beps/inclusive-framework-on-beps-composition.pdf

[29] OpenPeppol — Peppol Authorities list. https://peppol.org/members/peppol-authorities/

[30] The Kathmandu Post — ‘600 firms to be linked to central billing system’ (7 December 2017). https://kathmandupost.com/money/2017/12/07/600-firms-to-be-linked-to-central-billing-system

[31] myRepublica / Nagarik Network — ‘Govt brings central billing monitoring system’ (November 2017). https://myrepublica.nagariknetwork.com/news/govt-brings-central-billing-monitoring-system/

[32] TechLekh — ‘Central Billing Monitoring System To Be Implemented By The End of Fiscal Year’ (8 December 2017). https://techlekh.com/central-billing-monitoring-system-implemented/

[33] Fiscal Nepal — ‘IRD expands central billing monitoring system mandate for high-turnover businesses’ (21 December 2023). https://www.fiscalnepal.com/2023/12/21/14830/ird-expands-central-billing-monitoring-system-mandate-for-high-turnover-businesses/

[34] myRepublica — ‘IRD makes it mandatory for firms with transaction of Rs 250 million per annum to issue electronic billing’ (December 2023). https://www.myrepublica.nagariknetwork.com/news/ird-makes-it-mandatory-for-firms-with-transaction-of-rs-250-million-per-annum-to-issue-electronic-billing

[35] The Kathmandu Post — ‘Tax authorities bust fake VAT bill racket’ (14 April 2021). https://kathmandupost.com/money/2021/04/14/tax-authorities-bust-fake-vat-bill-racket

[36] The Kathmandu Post — ‘Nepal’s informal economy is 38.6 percent of GDP’ (26 January 2024). https://kathmandupost.com/money/2024/01/26/nepal-s-informal-economy-is-38-6-percent-of-gdp

[37] Farsight Nepal — ‘Assessing 25 years of VAT implementation in Nepal’ (12 July 2023). https://farsightnepal.com/news/185

[38] clickmandu — ‘Government to launch state-owned e-billing software to curb tax leakage’ (28 May 2026). https://english.clickmandu.com/2026/05/8966/

[39] Nepalese Express — ‘List of IRD verified Softwares (as per Electronic Invoice Procedure 2074)’. https://nepalesexpress.com/@bhojrajbhatt/list-of-ird-verified-softwares-as-per-electronic-invoice-procedure-2074

[40] lawalpine.com — ‘VAT in Nepal: Rates and Thresholds 2082/83’. https://lawalpine.com/blog/vat-in-nepal-rates-and-thresholds-2082-83



Sponsors:

Fiscal Solutions Bottom
Pincvision

Advertisements:

  • iopole
  • Zampa
  • Pincvision