Follow the document, from source to fiscal result.

Hloliwe's integration work starts with the invoice in your accounting system or till. The source data needs to reach the fiscal controller in the required form, and the returned fiscal information needs to stay with the document.

Prepare the source record

Identify the document type, business location, item details and tax treatment. B2B records also need the buyer's TIN, name and physical address.

Fiscalise through the controller

The approved controller works with the ERS-issued Secure Element. It supplies the fiscal invoice information and verification data.

Keep the result and follow reporting

Customer delivery and reporting to ERS are separate events. The business needs to monitor errors and keep the supporting records.

Agree the interruption plan

Queued source work is different from offline fiscal issuance. Check the controller's local capability and the applicable reporting limits before choosing a setup.

From your system to the fiscal record
Proposed invoice architectureYour business system: Accounting / ERP or till / POS. Creates the source transaction. Hloliwe connector: Picks up the source document. Preserves its revision. Hloliwe cloud: Validate · prepare · queue. Retry only when safe. Sales Data Controller: V-SDC: virtual, online. E-SDC: external, local option. ERS.EIS back end: Receives fiscal data from SDC. Reporting is tracked separately. Fiscal response → customer: SDC invoice no + verification URL. QR on paper; link electronically. Your business system connects to Hloliwe connector. Hloliwe connector connects to Hloliwe cloud. Hloliwe cloud connects to Sales Data Controller. Sales Data Controller connects to ERS.EIS back end. Sales Data Controller connects to Fiscal response → customerYour business systemAccounting / ERP or till / POSCreates the source transactionHloliwe connectorPicks up the source documentPreserves its revisionHloliwe cloudValidate · prepare · queueRetry only when safeSales Data ControllerV-SDC: virtual, onlineE-SDC: external, local optionSDC + Secure Element signERS.EIS back endReceives fiscal data from SDCReporting is tracked separatelyFiscal response → customerSDC invoice no + verification URLQR on paper; link electronicallyHloliwe portalSource document and fiscal resultDelivery status and any exceptionsProposed invoice architectureYour business system: Accounting / ERP or till / POS. Creates the source transaction. Hloliwe connector: Picks up the source document. Preserves its revision. Hloliwe cloud: Validate · prepare · queue. Retry only when safe. Sales Data Controller: V-SDC: virtual, online. E-SDC: external, local option. ERS.EIS back end: Receives fiscal data from SDC. Reporting is tracked separately. Fiscal response → customer: SDC invoice no + verification URL. QR on paper; link electronically. Your business system connects to Hloliwe connector. Hloliwe connector connects to Hloliwe cloud. Hloliwe cloud connects to Sales Data Controller. Sales Data Controller connects to ERS.EIS back end. Sales Data Controller connects to Fiscal response → customerYour business systemAccounting / ERP or till / POSCreates the source transactionHloliwe connectorPicks up the source documentPreserves its revisionHloliwe cloudValidate · prepare · queueRetry only when safeSales Data ControllerV-SDC: virtual, onlineE-SDC: external, local optionSDC + Secure Element signERS.EIS back endReceives fiscal data from SDCReporting is tracked separatelyFiscal response → customerSDC invoice no + verification URLQR on paper; link electronicallyHloliwe portalSource document and fiscal resultDelivery status and any exceptions
Proposed ERS integration. The SDC and its Secure Element perform fiscal signing; the cloud queue does not create a fiscal invoice. Controller fiscalisation, ERS reporting and delivery are separate stages. Source: ERS Technical Guidelines §§1.11, 7.6.1–7.6.2; technical alignment review, 28 October 2026.
An outcome, not just a sent message
Source

Created in your system

Invoice starts in your books.
No fiscal outcome yet.

Checked

Captured and checked

Source revision retained.
Invalid data needs correction.

In progress

Prepared for submission

Request recorded before sending.
Sending is not acceptance.

Alternative results and recovery paths

Accepted

Confirmed fiscal result

Confirmed result retained. Delivery is tracked independently.

accepted / slip_ready
Needs attention

Review before retrying

Refused: review source data. Unknown: reconcile; do not resend.

refused / submission_unknown
Correction

Correct at the source

New revision or linked correction. Credit note for issued invoices.

changed_after_issue

The final three panels describe alternative outcomes and recovery, not automatic sequential transitions. A failed report never triggers a second fiscal submission.

The states Hloliwe tracks for every document. Source: API migration baseline.sql source_state / attempt_state / delivery_state; console document model.
Request a quote