A finance manager finishes the day in Sage Pastel with a clean sales report. The critical question is whether the business also issued each applicable invoice through a ZRA-approved Smart Invoice process and can reconcile it to the ledger.

Sage Pastel does not become ZRA Smart Invoice compliant merely because an add-on is installed. The business must verify the specific Certified Invoicing System, VSDC connector, vendor and production deployment against ZRA’s current published requirements and Approved Vendor List.

## The short answer: Pastel alone does not meet the requirement

Sage Pastel is an accounting package. It does not, by itself, demonstrate compliance with the Zambia Revenue Authority, ZRA, Smart Invoice requirement.

Where Pastel is the invoicing system, the business generally needs a Certified Invoicing System integration with ZRA Smart Invoice through the Virtual Sales Data Controller (VSDC). A Sage licence, PACRA registration or NAPSA registration does not establish Smart Invoice compliance, because those documents cover different obligations.

VAT taxpayers were required to register and use Smart Invoice by 30 September 2024, with standard penalties applying from 1 October 2024. ZRA’s programme also serves specified non-VAT taxpayer categories. Confirm the taxpayer’s exact registration and invoicing obligations rather than assuming a product or user group is exempt.

### What directors should verify

Ask the provider four direct questions before relying on a Pastel deployment:

- Does ZRA’s current Approved Vendor List identify the actual provider and invoicing solution proposed for this deployment?

- Does the accounting package use the certified VSDC integration route, with supported exceptions and recovery procedures?

- Has the taxpayer completed the required application, integration testing and production confirmation?

- Can the provider show a real sales and credit-note trail from Pastel to Smart Invoice and back to the ledger?

ZRA’s official Approved Vendor List page was updated on 7 August 2026. Check the live list again immediately before contracting and go-live; neither an older screenshot nor a provider’s marketing claim is enough to validate the proposed solution.

## Sage Pastel integration options compared

For businesses retaining Pastel, the main decision is often between a supported third-party VSDC connector and a properly maintained in-house integration. ZRA’s own Desktop, Online and Mobile solutions serve different taxpayer needs and should not be treated as interchangeable substitutes.

| Approach | Appropriate use | Control to prove |

| --- | --- | --- |

| Certified third-party VSDC connector | An established Pastel deployment with partner support | Current ZRA listing, deployment and live tests |

| Maintained in-house VSDC integration | A business with qualified development and compliance capacity | Latest specification, test and incident evidence |

| ZRA Desktop / tablet | Taxpayers without accounting packages | Eligibility and approved operating route |

| ZRA Online or Mobile | Eligible low-volume or specified taxpayer categories | Confirm suitability before replacing workflows |

ZRA publishes its own Smart Invoice applications without a software charge, while an enterprise retaining its accounting package remains responsible for any required integration and support. Evaluate implementation scope, exception handling, continuity and supplier accountability rather than publishing illustrative prices.

### Option 1: Third-party VSDC integration

A third-party connector links the Pastel sales workflow to ZRA Smart Invoice through VSDC. It can preserve familiar invoicing and stock processes while transmitting the required transaction data through the approved route.

The taxpayer must use the official Smart Invoice Taxpayer Portal to apply for its selected invoicing route, including VSDC where appropriate. ZRA’s published steps include downloading and attaching the Commitment Form, sending the application and completing the subsequent technical and operational activation requirements.

ZRA guidance distinguishes portal application from technical certification and live use. Require documented testing, configuration evidence, user procedures and production confirmation; portal registration alone is not proof that transactions are compliant.

### Option 2: In-house integration

An enterprise can develop and maintain its own VSDC connection if it has adequate integration, security, testing and release-management capability. Use ZRA’s latest available VSDC API specification and developer checklist; do not rely on a version number copied from an old implementation note.

This route suits a business that already controls its development, information security and release-management functions. It does not suit an enterprise that expects its finance team to manage API errors, software releases and audit evidence without technical ownership.

An in-house integration still needs ongoing maintenance, response to ZRA specification changes, tax control ownership and recovery procedures. The decision should depend on capability and long-term support, not on an assumed saving from avoiding a third-party connector.

### Option 3: Separate ZRA tools

A common error is to keep Pastel as the operating invoicing system while separately issuing invoices through ZRA Desktop. ZRA states that Desktop is intended for taxpayers without accounting packages, so it should not be treated as a routine substitute for certified VSDC integration.

Separate systems also create a control risk. Staff can post a sale in one system, omit it from the other, or correct an invoice in Pastel without making the corresponding correction in the Smart Invoice process.

## The route from Pastel to live Smart Invoice use

A compliance project should begin with the sales process, not with the software quotation. Map where a sale starts, who raises the invoice, which branch or till produces it and how a credit note moves through the system.

### 1. Confirm the taxpayer’s position

Identify the legal taxpayer and the invoices it issues, then confirm which Smart Invoice registration category applies. For a VAT-registered business using Pastel, confirm that the certified integration and production controls are complete rather than treating an unresolved connector as a future project.

Do not assume a group-level setup covers every company, branch or billing process. The form, invoice sequence and system configuration must align with the taxpayer that actually makes the sale.

### 2. Check the approved solution, not the brand name

Check the current ZRA Approved Vendor List for the exact solution and provider. The official listing available during this editorial review was updated on 7 August 2026, but it should be rechecked at contract signature and production approval.

The phrase “ZRA-approved accounting software” can mislead procurement teams. The meaningful question is whether the specific invoicing-system integration that will process your sales has the required ZRA status.

### 3. Register through the Smart Invoice Taxpayer Portal

The taxpayer signs up on the Smart Invoice Taxpayer Portal and selects VSDC as the Smart Invoice type. The process calls for the Commitment Form to be downloaded, attached and submitted with the application.

Keep copies of the application, approval communications, form and responsible officers. Those documents form part of the enterprise’s tax compliance record and help when a CFO changes, a vendor contract ends or ZRA requests an explanation.

### 4. Test before production approval

The integration must be tested according to ZRA’s current technical requirements. Before production sign-off, rehearse taxable sales, returns, credit notes, cancelled transactions, branch-specific sequences, connectivity loss and controlled recovery.

Ask the implementation team to process these cases from the counter or sales desk through to the final accounting record. A successful test invoice proves very little if the business cannot handle the transactions that create reconciliation differences at month-end.

### 5. Create a daily control

Finance should reconcile Pastel sales, issued Smart Invoice records and daily cash or receivables totals. A branch manager needs a simple escalation route when the connector stops transmitting, rather than an informal instruction to invoice later.

For a business with low transaction volumes, a manual daily reconciliation may be enough. For multi-branch retail, distribution or hospitality operations, we would expect an exception report and a named owner because invoice omissions can accumulate quickly.

## Two practical scenarios

### A Lusaka wholesaler with an existing Pastel setup

Consider a Lusaka electrical wholesaler using Pastel across several sales locations. Management is offered an add-on described as approved, but no one checks whether the offered connector is the same solution and provider shown on ZRA’s current list.

The stronger approach is to verify the actual listing, complete the taxpayer’s VSDC application and test sample invoices, credit notes and exception handling from each location. Assign finance responsibility for fiscal records and IT responsibility for transmission and recoverability; keep both accountable for reconciliation.

The operational lesson is simple. The wholesaler should assign ownership jointly to finance and technology, because finance owns tax evidence while technology owns the connection that creates it.

### A retailer considering ZRA Desktop beside Pastel

Consider a retailer using Pastel for stock, invoicing and customer balances. Its owner proposes adding ZRA Desktop as a separate invoicing tool simply because it is available without a software charge.

That design can create two competing sales records and inconsistent credit notes. Because ZRA’s Desktop offering is intended for taxpayers without accounting packages, the retailer should instead assess a certified integration or redesign its invoicing process with professional guidance. Test the chosen process during normal trading volume, not only a quiet demonstration.

The relevant decision is whether staff can operate one compliant transaction chain, resolve failed transmissions and demonstrate a daily reconciliation—not which software option appears cheapest.

## Enforcement risk and governance oversight

ZRA has publicised enforcement action against Smart Invoice non-use, including an August 2026 conviction. This illustrates the need for a valid approval trail and consistent fiscal invoicing, but one court outcome should not be presented as a standard penalty applicable to every taxpayer.

The legal consequences depend on the offence, facts and applicable legislation. Ask a qualified tax adviser to verify current statutory penalties rather than using a penalty illustration as an ERP purchasing argument.

Boards should ask for a short Smart Invoice compliance pack at least quarterly. It should show the approved solution, portal and production status, test evidence, daily reconciliation exceptions and the person accountable for resolving failures.

A PACRA annual return, a NAPSA registration or a valid Sage licence may all remain necessary in their own areas. None answers ZRA’s question about whether the taxpayer uses Smart Invoice for live sales.

## Frequently asked questions

### Is Sage Pastel approved by ZRA for Smart Invoice?

Not necessarily. Pastel is not itself a blanket Smart Invoice approval. Check the exact connector, vendor and production deployment against ZRA’s current Approved Vendor List and taxpayer requirements.

### Can we use ZRA Desktop Smart Invoice while retaining Pastel?

ZRA states that Desktop is for taxpayers without accounting packages. A business that uses Pastel should not assume Desktop provides a substitute for VSDC integration.

### What is the first step for a Pastel user?

Start by mapping the actual invoicing workflow and checking the proposed connector against the current Approved Vendor List. Then register on the Smart Invoice Taxpayer Portal, select VSDC and submit the Commitment Form as part of the application process.

### What changed in 2026?

In 2026, ZRA continued to maintain its Approved Vendor List and developer documentation, and publicised enforcement of Smart Invoice requirements. The appropriate response is to check the live approval and specification records—not to rely on a version number or expired provider presentation.

Speak with M&J Consultants to review your Sage Pastel sales workflow, approved VSDC integration options, exception controls and Smart Invoice evidence before committing to a solution.