e-invoicing

Status sequence

The SCICloudStatusCode values an outbound invoice passes through, and whether each one calls for waiting, fixing, or nothing at all.

When you submit an invoice, you move through the following status sequence. Track network delivery (MLR) and TDD reporting (eMLR) outcomes separately — a delivery success doesn't guarantee a reporting success.

Table 1. Submission status sequence
SCICloudStatusCode Event Meaning Action
102 Sovos validation Sovos accepted and validated the invoice. Wait. Continue polling.
216 MLR: network delivery The buyer's Access Point confirmed receipt (MLR AP). Delivery confirmed. Continue polling for TDD reporting outcome.
200 eMLR: TDD reporting Unimaze reported the TDD to the Slovak FA successfully (eMLR AP). TDD reporting confirmed. No further action required.
209 Workflow complete Both delivery and TDD reporting are resolved. Done.
400 Rejection The invoice was rejected. SCIGovtStatusCode in the notification tells you whether this was a network delivery rejection (MLR RE) or a TDD reporting failure (eMLR RE). Review the rejection reason in the notification. See Handle errors.
401 Technical or structural error Sovos identified an error before transmission. Nothing was sent. Fix the invoice and resubmit. See Validation errors.
408 Recipient not registered The buyer's PEPPOL participant identifier wasn't found in the Slovak SMP. Verify buyer registration. See Buyer not registered.
409 Recipient unreachable The buyer is registered but their Access Point couldn't be reached. Retry later. If the problem persists, contact Sovos support.
500 System error An unexpected system error occurred. Contact Sovos support if this persists.
Important:

400 covers two distinct outcomes — network delivery rejection (MLR RE) and TDD reporting failure (eMLR RE). Both map to SCICloudStatusCode 400. Check the SCIGovtStatusCode field in the notification to understand which event failed.

Confirm that a submission is complete

You're done when you receive SCICloudStatusCode 209 (workflow complete). This confirms both MLR (delivery) and eMLR (TDD reporting) resolved successfully.

If you receive 216 without a subsequent 200 or 209, keep polling — eMLR can arrive after MLR. Don't treat 216 alone as final.