Recorded sales
Store the business, location, service time, receipt reference, items, taxes, and payment status needed for normal operational records.
GOVERNMENT & TAX COMPLIANCE
E-POS AI is designed to help businesses maintain clear records for sales, receipts, corrections, and operational decisions. Accurate records can support lawful tax compliance while preserving each business’s privacy, ownership, and separate access controls.
COMPLIANCE-READY RECORDS
The platform’s operational controls help a business review its records before reporting. A government authority should never need unrestricted access to every business dashboard simply because a country later adopts an approved reporting process.
Store the business, location, service time, receipt reference, items, taxes, and payment status needed for normal operational records.
Keep voids, refunds, discounts, and credit notes connected to their original record with an authorized actor, time, amount, and stated reason.
Use append-only operational events so corrections are visible rather than silently disappearing from a business record.
Keep businesses and locations separate, and design any future authority reporting to transmit only the legally authorized scope of information.
CURRENT STATUS — TEST READINESS ONLY
E-POS AI is not currently connected to a tax office, ministry, revenue service, taxpayer database, fiscal device, e-invoice gateway, or government API. It does not transmit live sales, taxpayer information, voids, refunds, or tax data to any authority.
E-POS AI will not accept a real taxpayer key, TIN credential, government login, or live endpoint in its public test foundation. An approved country integration must be separately designed, verified, certified, and activated only after the required authority process is complete.
COUNTRY-BY-COUNTRY ACTIVATION
Tax and fiscal rules are country-specific. A lawful connection must follow the relevant authority’s process—not a generic software switch.
01
Review the applicable tax, fiscal-device, invoice, privacy, retention, and reporting requirements with the relevant authority and qualified local advisers.
02
Use the authority’s required taxpayer registration, business enrollment, and any approved fiscal-device or e-invoice process. E-POS AI will not guess a taxpayer identity.
03
Obtain an official API, certified fiscal-device path, authorized gateway, or integration specification—plus sandbox access and non-production credentials where available.
04
Complete authority-required test cases, security review, certification, and written approval before any live transmission is enabled.
05
Monitor acknowledgements, exceptions, corrections, retention, and independent reconciliation under the country’s approved process.
FIRST PRIORITY COUNTRIES
Ethiopia, South Africa, and Eswatini are the first priority test templates. This order is a planning priority only; it is not a statement of authority approval, partnership, certification, or live availability.
No Ministry of Revenue connection, taxpayer key, credential, fiscal-device approval, or live submission is active.
No SARS integration, eFiling access, taxpayer credential, certification, or live submission is active.
No Eswatini Revenue Service integration, fiscal-document approval, credential, certification, or live submission is active.
FOR GOVERNMENTS, BUSINESS GROUPS & PARTNERS
E-POS AI welcomes a structured review of legal requirements, approved technical routes, security controls, certification evidence, business onboarding, and post-launch reconciliation. Any future live integration must protect both public accountability and lawful business privacy.