What is ZIMRA fiscalisation?
Fiscalisation is the process of recording taxable transactions through an approved fiscal device and transmitting the relevant information to ZIMRA.
ZIMRA describes fiscal devices as electronic devices used to record transactional information before it is transmitted to ZIMRA's servers. These devices can be hardware-based or software-based. Virtual Fiscal Devices are one of the supported categories.
For a software-based business system, the important part is the connection between your application and ZIMRA's Fiscalisation Data Management System (FDMS).
Once your virtual fiscal device has been approved and activated in the live environment, your application can submit fiscal transactions to ZIMRA.
Before you start
You should have the following ready:
A registered business
Your ZIMRA TIN
Your VAT number, where applicable
Your business and branch information
Access to the ZIMRA FDMS test environment
A CompanyOp account
The CompanyOp ZIMRA Fiscalisation application
Internet access
The device information provided by the ZIMRA test environment
If you are already using CompanyOp Point of Sale & Inventory, the ZIMRA Fiscalisation application can also work as part of that workflow. CompanyOp currently lists ZIMRA Fiscalisation as an application for ZIMRA FDMS fiscal devices, receipts and day closing.
Step 1: Get your test fiscal device from ZIMRA
The first stage is performed in the ZIMRA FDMS test environment.
ZIMRA provides a test environment for fiscal device onboarding and testing. The test environment includes functionality for adding devices and working with device information.
The ZIMRA test portal's Add New Device page asks for information including:
Taxpayer TIN
Taxpayer name
VAT number
Taxpayer email
Trade or branch information
Telephone number
Address
Province
Region
Station
Device serial number
Device model
Integrator
You can access the ZIMRA FDMS test operations portal here:
The exact information available to you may depend on how your taxpayer and device have been configured in the ZIMRA environment.
Step 2: Record your ZIMRA test device details
After the test device has been created, you need to take note of the information associated with it.
Pay particular attention to information such as:
Device ID
Device serial number
Company/TIN information
Activation information
Device model
Branch or trade location
Any other configuration information supplied by the ZIMRA test environment
The Device ID is particularly important because it identifies the fiscal device to FDMS.
ZIMRA's API documentation describes device registration as a process involving the device ID, activation key and serial number. It also explains that a device must be registered before it can be used and that configuration information is subsequently obtained from FDMS.
The test environment also provides an activation-details function where a device serial number and company TIN can be used to retrieve activation information.
Keep these details somewhere safe.
Do not confuse your test device information with the live device information. The purpose of the test device is to allow you to prove that your integration works correctly before going live.
Step 3: Open CompanyOp
Once you have your ZIMRA test device information, log into your CompanyOp workspace.
Open the ZIMRA Fiscalisation application.
CompanyOp is designed around a company workspace where different business applications can operate together. This means you can use the fiscalisation functionality alongside applications such as Point of Sale & Inventory, Accounting and other business applications.
If you are using Point of Sale & Inventory, this makes the workflow particularly useful because your sales can be connected to the fiscalisation process rather than requiring you to manually enter every transaction into another system.
Step 4: Create the test device in CompanyOp
Inside the CompanyOp ZIMRA Fiscalisation application, create a new fiscal device.
At this stage, enter the details obtained from the ZIMRA test environment.
Depending on the fields presented by the CompanyOp application, these can include information such as:
Device ID
Serial number
Device name
TIN
VAT number
Branch
Device configuration information
Activation information
The important point is that you are creating the corresponding device in CompanyOp using the device information issued by ZIMRA's test environment.
You are not randomly generating a Device ID in CompanyOp.
The device must correspond to the device that exists in the ZIMRA FDMS test environment.
Step 5: Start testing
Once the test device has been created in CompanyOp, you can begin testing the fiscalisation workflow.
This is where the process becomes much easier.
Instead of manually constructing API requests or writing code to test the ZIMRA endpoints, CompanyOp provides the business interface for generating the test transactions.
You can create test receipts by using the available actions in the CompanyOp ZIMRA Fiscalisation application.
For example, you can generate test transactions representing normal sales.
The purpose of these transactions is not to make real sales.
They are test transactions used to demonstrate to ZIMRA that the integration is correctly generating and submitting fiscal documents.
ZIMRA's own onboarding guidance states that virtual fiscalisation applicants should conduct their API tests on the FDMS test platform and generate sample invoices, credit notes and debit notes for ZIMRA validation and approval.
Step 6: Generate your test fiscal documents
Generate the required test documents from CompanyOp.
Depending on what ZIMRA requires for your onboarding, this may include:
Fiscal Tax Invoices
Credit Notes
Debit Notes
Do not simply generate one random transaction and immediately assume the onboarding is complete.
The purpose of the test is to demonstrate that your system can correctly handle the fiscalisation process.
ZIMRA specifically states that sample invoices, credit notes and debit notes should be generated in the test environment and submitted for validation and approval.
Step 7: Close the fiscal day
After completing the required testing, close the fiscal day.
This is an important part of the testing process.
ZIMRA's published onboarding procedure specifically instructs taxpayers to close the fiscal day and check whether any errors were encountered.
The FDMS test environment also provides a dedicated Close Fiscal Day operation where a Device ID and day number can be supplied.
If the fiscal day cannot be closed successfully, do not rush to submit your documents for approval.
Resolve the problem first.
A successful test should give you confidence that the complete workflow works, rather than only proving that a receipt can be generated.
Step 8: Submit your test receipts to ZIMRA
Once your test transactions have been successfully generated, collect the required sample documents.
These are the documents you will send to ZIMRA for validation and approval.
ZIMRA's official onboarding guidance confirms that sample fiscal tax invoices, credit notes and debit notes should be submitted to ZIMRA for approval.
Your email should clearly identify the taxpayer and explain that the documents are being submitted for FDMS virtual fiscalisation testing and approval.
Include information such as:
Company name
TIN
VAT number, if applicable
Device ID
Device serial number
Branch
Company contact details
The CompanyOp system being tested
The sample fiscal documents
Any other information requested by your ZIMRA office
Step 9: Where should you email ZIMRA?
This is an important point because ZIMRA has updated its FDMS support contacts.
In Public Notice 37 of 2026, ZIMRA announced dedicated FDMS support email addresses for different regions. The notice specifically says these addresses can be used for FDMS issues including approval for onboarding or registration of ZIMRA Virtual Fiscal Devices for server-to-server integrations.
The currently published addresses are:
SCO
MCO
LCO
Region 2
Region2fdmssupport@zimra.co.zw
Region 3
Region3fdmssupport@zimra.co.zw
Use the address corresponding to the region responsible for your taxpayer.
Do not simply email every address at the same time. Use the appropriate ZIMRA FDMS support contact for your region.
Because ZIMRA can change support contacts, it is also worth checking the latest ZIMRA public notices before submitting your documents.
Step 10: Follow up with ZIMRA
After submitting your sample receipts, wait for ZIMRA to review them.
This is not the stage where you should immediately create a live fiscal device.
The approval from ZIMRA is important.
If you have not received a response after a reasonable period, follow up using the appropriate FDMS support email.
When following up, provide enough information for the ZIMRA team to identify your application quickly.
For example:
Subject: FDMS Virtual Fiscal Device Onboarding Follow-Up – [Company Name]
Include:
Company name
TIN
Device ID
Date the samples were submitted
Previous email subject
Your contact details
A short request for an update
Keep your original submission email and any responses from ZIMRA for your records.
Step 11: Wait for ZIMRA approval
Do not treat successful test receipts as automatic approval.
There are two separate stages:
Testing
Your CompanyOp device communicates with the ZIMRA test environment and generates the required sample documents.
Approval
ZIMRA reviews the submitted samples and confirms that the integration is acceptable.
ZIMRA's published virtual fiscalisation process explicitly states that after invoices are approved, registration is completed in the FDMS live environment and transactions can then begin.
This distinction is important.
A successful test does not mean that you are already authorised to start issuing live fiscal receipts.
Step 12: After approval, create the live device
Once ZIMRA has approved your onboarding and the device has been registered in the live FDMS environment, return to CompanyOp.
Open the ZIMRA Fiscalisation application and create/configure your live fiscal device.
At this point, you are no longer configuring the test device.
You are configuring the live device that corresponds to the device registered in ZIMRA's production environment.
Enter the live device details supplied by ZIMRA and complete the CompanyOp configuration.
The exact information required will depend on the live device configuration provided by ZIMRA.
Step 13: Start fiscalising
Once the live device has been successfully configured and connected, you can start using CompanyOp to fiscalise your transactions.
Your workflow can then look like this:
Customer buys → Sale is created → CompanyOp sends fiscal information to ZIMRA FDMS → ZIMRA processes the transaction → Fiscal receipt is generated
If you are using CompanyOp Point of Sale & Inventory, the fiscalisation process can be integrated into the sales workflow.
This means your business does not need to maintain a completely separate system simply for fiscalisation.
How the whole process works
The entire onboarding process can be simplified into the following sequence:
1. Create/get your test device from ZIMRA
↓
2. Record the Device ID, serial number and activation/configuration details
↓
3. Open CompanyOp
↓
4. Install/open ZIMRA Fiscalisation
↓
5. Create the corresponding test device in CompanyOp
↓
6. Generate test fiscal receipts
↓
7. Generate the required sample invoices/credit/debit documents
↓
8. Close the test fiscal day
↓
9. Submit the samples to ZIMRA
↓
10. Follow up with ZIMRA
↓
11. Receive ZIMRA approval
↓
12. ZIMRA registers the device in the live environment
↓
13. Create/configure the live device in CompanyOp
↓
14. Start fiscalising real transactions
How do you know your fiscalisation integration is working?
ZIMRA provides several ways to check whether a fiscal device is functioning correctly.
One important indicator is the fiscal document itself.
ZIMRA states that fiscal tax invoices and debit/credit notes should contain a verifiable QR code. When the QR code or invoice is validated through the ZIMRA FDMS portal, the system should indicate that the invoice is valid.
You can also verify that fiscal days can be opened and closed without errors.
These checks are useful because fiscalisation is not simply about producing a PDF or printing a receipt.
The transaction must actually be processed through the fiscalisation system.
Test environment vs live environment
One of the easiest mistakes to make is confusing the test environment with the live environment.
Test EnvironmentLive EnvironmentUsed for development and testingUsed for real business transactionsUses test device informationUses live device informationTransactions are test transactionsTransactions represent actual salesDocuments are submitted for approvalDocuments are part of normal fiscal operationsDoes not mean you are approved to transactUsed after ZIMRA approval
The safest approach is simple:
Test first. Get approval. Go live second.
Do not start fiscalising real business transactions through a test device.
What happens if something goes wrong?
If CompanyOp cannot communicate with FDMS, if a receipt is rejected, or if the fiscal day cannot be closed, do not simply continue generating transactions.
Check:
The Device ID
The device serial number
The TIN
The device configuration
The CompanyOp device configuration
The FDMS response/error
Your internet connection
Whether you are using the test or live environment
If the problem is on the ZIMRA side or requires FDMS intervention, contact the appropriate ZIMRA FDMS support address.
ZIMRA's 2026 public notice specifically directs taxpayers to the regional FDMS support addresses for onboarding, fiscal invoice issues, device problems and other FDMS matters.
You don't have to buy a physical fiscal machine
This is one of the biggest advantages of virtual fiscalisation.
ZIMRA recognises software-based Virtual Fiscal Devices and says virtual fiscalisation can be suitable for businesses processing transactions through connected servers, accounting systems or point-of-sale systems.
For a business already operating its sales through software, a virtual fiscal device can therefore be a much more natural solution than adding another physical device to the checkout.
CompanyOp's ZIMRA Fiscalisation application is designed around this software-based approach.
Instead of having your sales system and fiscalisation system completely disconnected, you can keep the process inside the same business software environment.
Final checklist
Before going live, make sure you have completed the following:
☐ Company has the required ZIMRA registration
☐ TIN and taxpayer information are correct
☐ Test device has been created in the ZIMRA FDMS test environment
☐ Device ID has been recorded
☐ Device serial number has been recorded
☐ Activation/configuration details have been recorded
☐ Test device has been created in CompanyOp
☐ Test receipts have been generated
☐ Required sample fiscal documents have been generated
☐ Fiscal day has been closed successfully
☐ Sample documents have been submitted to ZIMRA
☐ ZIMRA approval has been received
☐ Device has been registered in the ZIMRA live environment
☐ Live device has been configured in CompanyOp
☐ Live fiscalisation has been tested
☐ Real transactions are now being fiscalised
Start fiscalising with CompanyOp
Getting connected to ZIMRA FDMS does not have to mean buying complicated hardware or building an entire fiscalisation system from scratch.
With the virtual fiscalisation route, the process is essentially:
Get your ZIMRA test device → configure it in CompanyOp → test → submit samples → get ZIMRA approval → configure the live device → start fiscalising.
CompanyOp brings the fiscalisation functionality into the same business environment where you can manage your sales, inventory and other business operations.
For businesses looking for a software-based ZIMRA fiscalisation solution, CompanyOp provides a practical way to connect your business transactions to the ZIMRA FDMS workflow.