Quick answer
Smart Invoice readiness is primarily a data and process exercise. Clean product and customer records, define tax treatment, control document numbering, assign responsible users, test every document type and design a procedure for failed or delayed submissions.
What matters most
- Start with clean master data before integration.
- Test invoices, credit notes, refunds and offline exceptions.
- Do not mark a transaction fiscally complete until the authoritative response is recorded.
- Reconcile local sales to submitted fiscal documents every day.
Names, codes, units, prices and TPIN details.
Rates and exemptions mapped to each item.
Invoice, credit note, refund and cancellation.
Least privilege and clear responsibility.
Local sales matched to fiscal responses.
Clean master data before connecting
Standardise product descriptions, stock units, prices, tax categories and item codes. Duplicate or vague products create tax errors at the point of sale.
For business customers, define when a TPIN is required and how it is validated. Keep the customer’s legal name and TPIN separate from free-text delivery information.
Map the complete document lifecycle
A working invoice is not a complete implementation. Test sales invoices, credit notes, debit adjustments where applicable, cancellations, refunds and corrections.
Define what the cashier or finance user sees while a submission is pending, rejected or unavailable. The user needs a safe next action, not a technical error code.
Protect numbering and credentials
Document numbers must be unique and traceable. Avoid multiple devices producing overlapping sequences or staff editing numbers manually.
Restrict fiscal credentials and tokens to the server-side integration. Never place them in browser code, screenshots or support messages. Log access and rotate credentials through an authorised process.
Reconcile every trading day
Compare the point-of-sale or invoicing total with accepted fiscal documents, pending submissions, rejected documents, credit notes and refunds. Investigate every gap while staff still remember the transaction.
Preserve the request reference, authoritative response and final document together. A local “success” message is not enough evidence on its own.
Follow official onboarding instructions
Use ZRA’s Smart Invoice registration guide and solution information for the current onboarding path. Choose the solution that matches transaction volume, number of devices, connectivity and integration capability.
Run controlled tests before production and define who can contact ZRA or your implementation provider when a fiscal transaction is blocked.
Working checklist
Products and tax categories cleaned
Customer TPIN workflow defined
Invoice and credit-note flows tested
Unique numbering protected
Credentials kept server-side
Pending and rejected states visible
Daily reconciliation owner assigned
Official ZRA onboarding steps completed
Common mistakes to avoid
- Treating one successful test invoice as production readiness
- Allowing manual invoice-number edits
- Hiding failed submissions from cashiers
- Storing fiscal credentials in frontend code
Common questions
What should a business prepare before Smart Invoice integration?
Prepare clean products and customers, tax mappings, document flows, authorised users, numbering controls, credentials and a daily reconciliation process.
What happens if a Smart Invoice submission fails?
The system should preserve the transaction, show a clear pending or failed state, prevent duplicate finalisation and support an authorised retry or correction process. Follow current ZRA guidance for outages.
Where should API credentials be stored?
Only in protected server-side configuration with restricted access. They should never be exposed in browser code or public documentation.
Official sources
Rules and online processes can change. Use these primary sources to confirm the current position before acting.
