Nepal VAT and Tax Compliance for SaaS Businesses

By Kokil Thapa | Last reviewed: August 2026

Navigating Nepal VAT and tax compliance for SaaS businesses is the first real engineering constraint you face after validating a product idea. While building the application logic is straightforward, integrating Inland Revenue Department (IRD) requirements into your billing pipeline often causes more production incidents than the code itself. If you are launching a subscription platform or digital service in Nepal, understanding these fiscal obligations early prevents costly refactoring of your payment architecture later. For founders also managing their own technical careers or freelance income alongside a startup, aligning business taxes with personal filings is equally critical, as detailed in this Nepal income tax guide for freelancers.

How do you determine VAT registration thresholds for SaaS in Nepal?

The most common mistake I see with new SaaS founders is assuming they can delay registration until they are "big enough." Under the Value Added Tax Act 2052 and subsequent Finance Acts up to 2026, the threshold for mandatory VAT registration for service-oriented businesses, including software and digital services, is an annual turnover of NPR 5 million. However, for SaaS products intended for B2B clients who need to claim input VAT credits, voluntary registration before hitting this cap is often strategically necessary.

In practice, enterprise clients in Kathmandu will refuse to onboard a vendor who cannot provide a valid VAT bill because they cannot offset that expense against their own output tax. If you are building a B2B Laravel application or an API service, register immediately upon incorporation. The process involves submitting your company registration certificate, PAN certificate, and bank details to the local IRD office. Digital submission via the IRD portal has improved significantly by 2026, but physical verification of your registered address remains a standard step.

For SaaS businesses operating below the threshold with only B2C customers, PAN registration suffices. You still must file income tax returns, but you do not charge or remit VAT. Monitor your trailing twelve-month revenue continuously; crossing the 5 million NPR limit triggers immediate liability. I recommend implementing an automated revenue tracker in your admin dashboard that alerts you when cumulative sales approach NPR 4.5 million, giving you a buffer to complete registration paperwork without penalties.

What are the specific VAT rates and TDS rules for digital services?

Digital services, including SaaS subscriptions, cloud hosting, API access, and software licensing, attract the standard 13% VAT rate in Nepal as of 2026. There is no reduced rate for software exports unless specifically exempted under special economic zone provisions, which rarely apply to typical domestic SaaS startups. When pricing your product, decide whether to absorb this 13% or pass it through. Most B2B SaaS platforms list prices exclusive of VAT and add it at checkout, while B2C consumer apps often show VAT-inclusive pricing to avoid sticker shock.

Tax Deducted at Source (TDS) creates additional complexity for SaaS vendors receiving payments from corporate clients. When a Nepali company pays your SaaS invoice, they are legally required to deduct TDS before transferring funds. The rate varies: typically 1.5% for VAT-registered suppliers providing technical services, but potentially higher if your VAT status is unclear or if the payment is classified differently. This deducted amount is not lost; it becomes a tax credit you claim during your annual income tax assessment.

A critical operational detail: ensure your contracts explicitly state whether fees are inclusive or exclusive of VAT and clarify TDS responsibilities. I have seen disputes where clients deducted 15% TDS instead of 1.5% because the invoice lacked proper VAT registration details. Always display your PAN/VAT number prominently on every invoice and contract to secure the lower technical service rate.

How do you implement IRD-compliant billing in Laravel applications?

The IRD does not certify specific software frameworks, but it enforces strict invoice content requirements. Your Laravel-generated PDF or digital invoice must include: seller name, address, PAN/VAT; buyer name, address, PAN/VAT; unique sequential invoice number; date in BS (Bikram Sambat) format; itemized description; taxable amount; VAT amount; and total. Missing any field risks rejection during audit. For developers building custom billing systems, treating invoice generation as a regulated document rather than a simple receipt is essential.

When architecting this in Laravel 12, store both AD and BS dates. Use a dedicated package like nepali-date for accurate conversion rather than hardcoding offsets. Invoice numbers must be sequential without gaps per fiscal year. Implement database-level constraints or atomic counters to prevent race conditions in high-concurrency environments. Never allow manual editing of issued invoice numbers; if a correction is needed, issue a credit note with its own sequential reference.

<?php
// app/Services/NepalInvoiceGenerator.php
namespace App\Services;

use Carbon\Carbon;
use App\Models\Invoice;

class NepalInvoiceGenerator
{
    public function generate(array $data): Invoice
    {
        // Atomic lock prevents duplicate invoice numbers
        return \DB::transaction(function () use ($data) {
            $lastNum = Invoice::where('fiscal_year', '2082/83')
                ->lockForUpdate()
                ->max('sequential_number') ?? 0;
            
            $invoice = Invoice::create([
                'fiscal_year'     => '2082/83',
                'sequential_number' => $lastNum + 1,
                'buyer_pan'       => $data['buyer_pan'],
                'taxable_amount'  => $data['amount'],
                'vat_amount'      => round($data['amount'] * 0.13, 2),
                'total_amount'    => round($data['amount'] * 1.13, 2),
                'issued_at_bs'    => now()->toNepaliString(),
                'issued_at_ad'    => now(),
            ]);
            
            return $invoice;
        });
    }
}

Integrating local payment gateways like eSewa or Khalti adds another layer. These providers settle net of their merchant fees, but your VAT liability is calculated on the gross sale price, not the net settlement. Your reconciliation process must account for this discrepancy. Record the full invoice value as revenue and VAT payable, then record gateway fees separately as deductible expenses. Automating this split in your ledger prevents month-end reconciliation nightmares. For teams evaluating whether to build custom billing versus using existing tools, understanding the Laravel payment integration landscape helps balance compliance needs against development velocity.

How should SaaS companies handle cross-border transactions and export exemptions?

If your SaaS serves international clients, the tax treatment differs fundamentally from domestic sales. Services exported outside Nepal may qualify for zero-rated VAT, meaning you charge 0% VAT but retain the right to claim input VAT credits on your expenses. This is vastly superior to being VAT-exempt, where you cannot reclaim input tax. However, proving export status requires maintaining verifiable evidence: foreign currency receipts through banking channels, contracts showing overseas delivery, and client location documentation.

In my experience working on production Laravel applications serving mixed domestic and international users, segregating customer records by tax jurisdiction at the database level is non-negotiable. Do not rely on billing address alone; use IP geolocation at signup combined with payment method country validation as secondary checks. Create separate invoice templates for domestic (13% VAT) and export (0% VAT with export declaration note). Mixing these formats leads to audit exposure where IRD may disallow zero-rating due to insufficient documentation.

For imports, such as AWS infrastructure costs, GitHub Copilot licenses, or foreign contractor payments, understand that VAT reverse charge mechanisms may apply. When paying foreign vendors, you might be liable to self-assess VAT on imported digital services. Consult a chartered accountant specializing in IT sector taxation, as interpretations of digital import VAT continue evolving. Budget approximately NPR 30,000–50,000 annually (~USD 225–375) for specialized tax advisory; this investment prevents misclassification errors far exceeding the consultation cost.

What compliance automation strategies reduce audit risk for growing SaaS firms?

Manual VAT reconciliation fails predictably as transaction volume grows. By the time you reach 200+ monthly invoices, spreadsheet-based tracking becomes a liability. Implement automated compliance controls directly in your application stack. Schedule nightly jobs that validate all issued invoices contain mandatory IRD fields, flagging anomalies before month-end closing. Generate draft VAT return data automatically, requiring only human review rather than manual compilation.

• Sequential integrity checks: Run daily queries detecting gaps or duplicates in invoice numbering sequences across fiscal years.
• TDS reconciliation: Match incoming bank deposits against expected TDS deductions, creating automatic journal entries for tax credits receivable.
• Date validation: Ensure BS dates convert correctly to AD equivalents, especially around month boundaries where conversion errors frequently occur.
• Audit trail immutability: Store finalized invoices as immutable PDFs with cryptographic hashes; never regenerate historical documents from mutable database records.
• Gateway reconciliation: Auto-match eSewa/Khalti settlement reports against ledger entries, surfacing discrepancies within 24 hours.

Consider integrating with emerging Nepali accounting APIs or established ERP systems that support IRD reporting natively. While custom Laravel solutions offer flexibility, certified third-party tools shift compliance burden away from your engineering team. For startups choosing between building proprietary billing versus adopting existing platforms, evaluate long-term maintenance costs honestly. Building multi-tenant SaaS applications in Laravel is valuable engineering work, but tax compliance logic rarely provides competitive differentiation worth maintaining indefinitely.

Implementing Sustainable Tax Compliance Infrastructure

Building sustainable Nepal VAT and tax compliance for SaaS businesses requires treating fiscal obligations as first-class architectural concerns, not afterthoughts bolted onto finished products. Register proactively based on your target market, implement IRD-compliant billing with atomic safeguards, automate reconciliation before scale forces the issue, and maintain rigorous documentation for cross-border transactions. The engineering discipline applied here mirrors good software practices generally: validate inputs, enforce constraints atomically, maintain immutable audit trails, and automate repetitive verification tasks.

Tax compliance will never be your product's selling point, but failures here can shut down an otherwise viable business faster than any technical debt. Invest in proper setup early, engage qualified tax professionals for interpretation questions, and build systems that make correct behavior the default path. If you are architecting a SaaS platform in Nepal and need guidance on structuring compliant billing systems or integrating local payment infrastructure, reach out to discuss your project requirements.