Skip to main content

Integrations / TRA VFD

TRA Virtual Fiscal Device integration for ERPNext

Tanzania's VFD makes fiscalisation a software problem: your ERP transmits sales to the EFDMS and prints the verification code and QR on every invoice. We build that connection.

TRAVFDDelivered as a service

Why this matters now

Businesses with annual turnover of TZS 11 million and above must issue fiscal receipts, and the 2025/26 budget moves toward pre-clearance and full inclusion of all remaining taxpayers. Receipts must pass EFDMS checks to support input VAT, and enforcement is continuous.

ERPNext and compliance in Tanzania

What the integration covers

VFD software fiscalisation

ERPNext registered as the invoicing system behind a VFD, transmitting to the EFDMS in near real time with the QR and verification code returned onto the printed document.

TRA schema compliance

TRA runs a bespoke XML schema, not Peppol. Field mapping, tax codes and document types are engineered against the national specification.

Pre-clearance readiness

The 2025/26 budget proposes token-based pre-clearance before issuance. The integration is architected for that flow so a regulation change is a configuration change.

Queue and retry resilience

Connectivity drops queue documents for automatic retry, the same zero-lost-receipts pattern from our KRA eTIMS module.

Multi-branch and POS coverage

Branch-scoped fiscalisation across back office and point of sale, including thermal receipt formats.

How we deliver

From discovery to verified go-live

01

Discovery and compliance mapping

We map your document flows, branches and item catalogue to TRA's VFD requirements, and confirm registration status and credentials with the authority.

02

Sandbox integration

ERPNext is connected to the VFD test environment. Sales invoices, credit notes and debit notes are generated and validated against the authority's schema before anything touches production.

03

Resilience engineering

Failed transmissions queue and retry automatically, with a circuit breaker for authority downtime. The pattern is proven in our KRA eTIMS module: zero lost receipts when the tax server is down.

04

Go-live and verification

Production credentials are registered, the first live documents are verified end to end, and your team is trained on exception handling and the VFD verification workflow.

05

Support and rate-change watch

We monitor authority notices and ship configuration updates when rules change, under a support agreement with defined response times.

Frequently asked questions

Is this a shipped module?

No. TRA VFD integration is delivered as an engineering service on ERPNext, applying the production-proven architecture of our Kenyan eTIMS module to TRA's EFDMS schema. We scope registration, schema mapping and go-live per project.

Who must fiscalise in Tanzania?

Any person supplying goods or services with assessed annual turnover of TZS 11 million and above must issue fiscal receipts through an electronic fiscal device, physical or virtual. The 2025/26 budget moves toward including all remaining taxpayers.

Does this cover Zanzibar?

No. Zanzibar operates a separate regime, the Virtual Fiscal Management System under the Zanzibar Revenue Authority. Island operations are scoped separately against that system.

What appears on a compliant invoice?

A verification code and QR code returned by the EFDMS, which customers and auditors can validate. E-invoices must be archived for five years, which the ERP handles as a byproduct of normal document storage.

Scope your VFD integration

A discovery call covers your document flows, registration status with TRA, and a delivery plan with verification criteria. We reply within one working day.

Book a Call