Request a quote
Hloliwe. Kucinisekisiwe.Checked. Verified.
Keep the accounting system you already use. Hloliwe connects it to ERS e-invoicing and shows your team the result of every invoice.
Run by Phones R Us (Pty) Ltd · Mbabane, Eswatini
The rules are specific. Hloliwe is built around them, from tax labels to buyer details and verification data.
Read the Eswatini requirementsEach line needs the right tax label before the invoice is fiscalised.
Source: ERS, VAT in EswatiniFiscal data must reach ERS within fifteen days of the document, unless ERS sets a shorter period.
Source: Fiscal-data Notice, July 2026The buyer's TIN, name and physical address travel with every business-to-business invoice.
Source: ERS Technical GuidelinesPrinted invoices carry a scannable QR code; electronic ones carry a verification link.
Source: ERS Technical GuidelinesAn emailed PDF is not the whole fiscal process. Where ERS requires electronic fiscal devices, a transaction must pass through an authorised system, receive its fiscal identifiers and be reported in the prescribed way.
That affects the details your team captures. Business-to-business invoices need buyer information. Products and services need the required codes and units. Corrections need the right document type and a link to the original transaction.
ERS can introduce requirements by taxpayer category or sector. Check the notice that applies to your business before setting a changeover date.
Sale or invoice data
Customer and item records
Invoice delivery
Accounting records
Controller-issued fiscal identifiers
Required buyer, item and tax information
Verification QR or link
Fiscal reporting and supporting records
The source record and fiscal record need to agree.
The ERS guidelines set out the information a fiscal document must carry. The controller provides fiscal identifiers and verification data; the invoice must show the details required for its transaction type.
The supplier's tax identity and the business-location information returned by the controller.
The buyer's TIN, name and physical address, with the document identified as B2B.
Item descriptions and codes, quantities and units, tax-exclusive unit prices, taxable amounts and the applicable tax labels. The invoice also shows its tax and total amounts.
The payment method and whether the transaction is a sale, refund or another prescribed document type. Adjustments need the required reference and explanation.
The controller's invoice number, fiscal time and invoice counter.
A scannable QR code on the printed invoice, or the verification link for electronic delivery, as the guidelines prescribe.
Main store · Mbabane
1 Sample Street, Hhohho
TIN 000000000
Office equipment (A)
Item code EQ-001 · Unit: each · Quantity: 1
10 November 2026 · 10:42:00
00000000-00000000-42
Invoice counter: 42/42NS
Supplier TIN, company, store, address and district come back from the SDC. The title marks the start of the fiscal part.
Cashier identification and POS accreditation number / product version. Buyer TIN is required for B2B and cancellation, not this ordinary sale.
Normal Sale; item name, tax label, quantity, unit, item code, tax-exclusive unit price and taxable amount. Include GTIN where available.
Tax label, VAT rate, tax value, taxable amount, total tax, total purchase and payment method. Tax values are returned by the SDC.
SDC time is the official fiscal time. The SDC invoice number combines RequestedBy, SignedBy and ordinal number; the SDC also supplies the invoice counter.
A printed QR contains the verification URL, internal data and digital signature. Minimum print size: 42 × 42 mm. An electronic invoice uses a clickable verification URL instead.
Every document follows the same path.
Your accounting package or till holds the transaction details. The connection needs to identify the correct document, business location and tax treatment.
Hloliwe maps the source record to the controller's required fields, including the buyer and item details needed for that document type.
The approved Sales Data Controller works with the ERS-issued Secure Element to fiscalise the transaction. It supplies the fiscal invoice details and verification data.
The invoice output must preserve the controller's fiscal information. The business needs a clear record of the result and any errors requiring attention.
The controller sends fiscal data to ERS. Fiscal signing, delivery to the customer and reporting to ERS are separate events.
Each connection is built for a specific product. The exact version and document types matter, so we confirm them in your setup review.
QuickBooks Desktop and other Sage products need their own assessment.
Hloliwe picks up finished invoices and credit notes from the Evolution database, including till sales. Cashiers and accounts staff work exactly as before.
Once an administrator approves the connection, Hloliwe picks up new invoices and sales receipts from your QuickBooks company and returns each fiscal result.
Hloliwe picks up approved sales invoices from your Xero organisation, with only the permissions it needs, and returns each fiscal result.
Hloliwe picks up tax invoices and credit notes from Sage Business Cloud Accounting. A credit note is sent only when it names the invoice it corrects.
Every business starts its invoices somewhere different. Tell us yours, and the setup review covers what matters for your trade.
Request a setup reviewTalk to us about your tills, accounting package and the information on each sale or B2B invoice.
We’ll ask about
Share the software you use and the product codes, units and tax treatment it records. We will review the connection your setup would need.
We’ll ask about
Tell us how you bill customers, take payments and correct invoices. The source system and document types will guide the review.
We’ll ask about
List the locations and tills involved, including where invoices are raised and who follows up processing errors.
We’ll ask about
The Hloliwe client portal shows what happened to each invoice after it left your accounting system.
Search by invoice number or system and see whether each one was accepted, rejected or is still waiting.
A rejected invoice shows the reason and the safe action to take, so your team fixes the source rather than guessing.
Check that each till and accounting connection is healthy and that the day's records are complete.
Client portal at app.hloliwe.com, shown with sample records.
A source document waiting to be sent is different from a fiscal invoice already signed by a controller.
Hloliwe's queue stores pending work and retries eligible submissions. If a document needs attention, later work on the same device is held rather than pushed past it.
Under the ERS framework, an approved external controller can fiscalise offline with its Secure Element and store the fiscal data for later reporting. The controller's capacity and audit rules still apply. Hloliwe works alongside that controller rather than replacing it.
The July 2026 Notice requires successful transmission within fifteen days of the fiscal document's creation, unless ERS prescribes a shorter period. Reporting should resume as soon as the approved setup permits.
During your setup review, we will ask about power backup, internet access and the controller arrangement your business needs.
Send and check the result
Keep unsent data securely
Reconcile, then catch up
Resume transmission after reconnection
Illustrative sequence, not measured performance. No elapsed-time scale.
Successfully transmit from fiscal document creation.
Unless ERS prescribes a shorter period. Real-time transmission remains the rule where available.Between the start of two E-SDC Proof of Audit cycles.
Keep audit data locally until Proof of Audit arrives.The supplier must document estimated offline invoice storage.
No universal invoice-count limit is stated here. E-SDC clock synchronisation is required at least every 48 hours.Hloliwe recovery must distinguish a known transport failure from an unknown fiscal result. An unknown result pauses processing for reconciliation; it is not blindly retried.
The client sign-in checks a password and an authenticator code.
PostgreSQL row-level policies restrict access to records within the authorised business context.
Staff administration sits behind Cloudflare Access. Staff API requests also check an Access token.
The platform records audit events. Database controls prevent ordinary updates or deletion of audit-event entries.
The client portal is at app.hloliwe.com. It shows each document with its processing result and any errors your team needs to fix.
Every client user signs in with a password and an authenticator code.
Database policies keep each business inside its own records.
Hloliwe staff tools sit behind a separate access gateway, and each staff request is checked again.
Events are written to an audit log that ordinary updates and deletions cannot change.
For ERS reviewers
The ERS guidelines cover the product version and its fiscal behaviour, supported by technical and administrative evidence. Our preparation separates platform controls from work that needs controller integration and fiscal testing.
| Guideline area | In Hloliwe today | Next step for accreditation |
|---|---|---|
| Product and deployment description | Cloud bridge scope and accounting-connector test records | Agree the POS component boundary and exact product version. |
| Access and record protection | Multi-factor sign-in, tenant database policies and protected audit-event records | Assemble the security evidence for the submitted product. |
| Interrupted processing | Persistent queue with ordered retries | Prove the chosen controller's continuity and audit path. |
| Required invoice data | Source-system connection work | Complete and test the Eswatini buyer, item, currency and adjustment mappings. |
| Fiscal invoice output and verification | Document-interface design | Preserve and render the controller's response, fiscal identifiers and verification data. |
| Technical and administrative review materials | Internal requirement mapping | Complete the manuals, required fiscal examples and signed conformity documents. |
ERS assesses the fiscal components and their behaviour. General platform controls do not replace the controller's Secure Element, fiscal signing or audit requirements.
Hloliwe is going through accreditation with the Eswatini Revenue Service under the 2026 Technical Guidelines. We will publish our ERS approval reference here once it is granted.
Live at hloliwe.com and app.hloliwe.com
CompleteRecorded working with four accounting systems
CompleteIn progress under the 2026 Technical Guidelines
In progressPublished here once ERS grants it
NextStart with a review of your exact product and version. Hloliwe's connection work is based on keeping the source system, but compatibility depends on the software and document types involved.
Sage 200 Evolution, Sage Business Cloud Accounting, QuickBooks Online and Xero are integration ready. Using other software? Tell us the product and version and we will confirm the connection.
See connection statusERS can set requirements and dates by category, sector or notice. Check the direction that applies to your taxpayer account with ERS or your tax adviser. The Notice's legal start date does not, by itself, establish your changeover date.
A PDF can display an invoice, but it does not by itself establish fiscalisation or reporting. Where an EFD is required, the approved fiscal process and required information matter.
A source queue can hold work for later processing. Offline fiscal issuance needs the approved controller and Secure Element arrangement, with its storage and reporting rules. We will review that requirement with your setup.
Plan for interrupted connectionsThe controller supplies verification data. The ERS guidelines prescribe a scannable QR on printed invoices or a verification link for electronic delivery.
The rules distinguish refunds, credit notes, debit notes and cancellations. The document needs the required references and reasons. Cloud credit-note mapping is still being completed, so document support must be checked during the setup review.
VAT-return filing is outside the current product scope. Your business remains responsible for its return and supporting records.
Tell us your accounting or POS product and version, branch and till count, the document types you issue and your approximate invoice volume. Include any power or connectivity needs.
No. It starts an enquiry about your setup. Account access and fiscal activation are separate steps.
ERS preparation statusPrice on request
The connection work depends on the system you use, the number of locations and tills, and the documents your business needs to issue.
Tell us what is already in place and what needs to change. Ask for a written scope that separates connection work from ongoing service and support.
Tell us where invoices are created and what your team needs to keep working. We will review the connection and explain the next steps.
