e-invoicing

Outbound status codes

Every status an outbound Slovakia document can reach, with its attachments, whether it is terminal, and the action it calls for.

Received when you submit an invoice or credit note as a supplier.

The following codes are confirmed from the Confluence product events page (September 2026).

Table 1. Outbound status details
Event Code Attachment types Terminal? What it means What to do
Received 100 Canonical Invoice (canonicalinvoice.xml), Legal (legal.xml). No Sovos received your document. Continue polling.
Mapped 101 Legal (legal.xml) No Sovos mapped your SCI document to UBL XML. This step is skipped if you submitted a local format XML directly. Continue polling.
Validated 102 Legal (legal.xml) No Sovos validated the XML against the UBL schema. Continue polling.
Transmitted 104 Legal (legal.xml) No Sovos transmitted the XML to Unimaze. Continue polling.
Authorized 200 Canonical Invoice (canonicalinvoice.xml), Legal (legal.xml). No Unimaze processed the document and returned a confirmation number. Continue polling for workflow completion.
Distributed 204 n/a No The document was distributed. Continue polling.
PDF created 207 PDF (Pdf.pdf) No Sovos generated a PDF version of the invoice. Continue polling.
Archived 208 Legal (legal.xml) No The document was archived in the Sovos archiving system. Continue polling.
Completed 209 Legal (legal.xml), Canonical Invoice (canonicalinvoice.xml), PDF (Pdf.pdf). Yes ✓ The full workflow completed successfully. No further action required.
Rejected 400 Legal (legal.xml) Yes ✗ Unimaze rejected the document. Review the rejection reason. See Handle rejections.
Document error 401 Legal (legal.xml) Yes ✗ Sovos found a technical or structural error before the invoice reached the PEPPOL network. Nothing was transmitted. Fix the problem and resubmit. See Validation errors.
System error 500 — Yes ✗ An unexpected system error occurred. Contact Sovos support if the problem persists.
Tax authority unavailable 501 — Yes ✗ The Slovak FA was unavailable when Unimaze attempted Tax Data Document (TDD) reporting. Contact Sovos support. This is a Sovos-managed process.
Invalid parameters 502 — Yes ✗ The request contained invalid or missing input parameters. Check your request and resubmit.
Invalid credentials 503 — Yes ✗ The credentials used for transmission are invalid. Check your Unimaze credentials. Contact your Sovos implementation team.
Important:

209, 400, 401, 500, 501, 502, and 503 are all terminal. Once a document reaches any of these statuses, no further transitions occur.

Important:

Both MLR RE (delivery rejection) and eMLR RE (TDD reporting failure) return SCICloudStatusCode 400. The SCIGovtStatusCode field in the notification distinguishes between them.

The uniqueId UBL extension field contains a unique UUID generated by Unimaze. This appears in the legal XML returned after transmission.