Skip to main content

Why Nepal

Built from the actual Rules, not a VAT-rate field

Most accounting software adds Nepal support by adding a 13% tax rate. This one was built the other way around: from the VAT Rules 2053 and the Income Tax Act provisions that actually govern how a Nepali business reports.

Generic Accounting Software

HISABI

Nepal support means a 13% tax rate typed into a settings field.

VAT Return form structure follows VAT Rules 2053, Rule 26(1) - generated from posted transactions, not re-typed.

Input VAT eligibility is tracked in a separate spreadsheet.

Rule 39-41 restrictions are captured at the purchase-bill line itself - only the creditable portion flows through.

Anusuchi 13 is assembled by hand from exported reports.

Aggregated automatically by counterparty against the statutory threshold, with a drill-down to source transactions.

Fiscal years are AD-only; BS dates are converted after the fact.

Fiscal years and periods carry both AD and BS dates - BS is entered directly, never derived by arithmetic.

Multi-tenant data isolation is "handled in the application code".

Tenant data is isolated at the database layer with row-level security, not only in application code.

VAT Return (Schedule 10 / अनुसूची १०)

The return form structure follows VAT Rules 2053, Rule 26(1). Every line is generated from posted Sales and Purchase transactions for the period.

Input VAT eligibility (Rule 39-41)

Where Rule 41 restricts what's creditable, that's captured at the purchase-bill line itself, and only the creditable portion flows through to the VAT Return.

Anusuchi 13

An Income Tax Act annual-return annex, not a VAT filing - aggregated by counterparty against the statutory threshold, with a drill-down to source transactions.

Bikram Sambat fiscal years

Fiscal years and periods carry both AD and BS dates. BS dates are entered directly, never derived by arithmetic.

Where things honestly stand

What's real today, and what's still provisional

VAT Return and Anusuchi 13 generate real, traceable figures

From your posted transactions - but every version is labeled DRAFT until you finalize it.

Anusuchi 13 currently models four transaction categories

The full statutory form uses more granular categories - a future update, not silently assumed complete today.

We don't claim certification we don't have

No government approval, no "100% compliant" claim - this page describes what the software does.

Trust

Every business's books, kept apart

Tenant data is isolated at the database layer with row-level security, not only in application code. A posted document is never silently edited - only reversed, or corrected with a new, linked document.

See the statutory depth for yourself