Skip to main content

Send invoice

The outbound invoicing module allows your system to send invoices to Croatian customers while simultaneously fulfilling the fiscalisation requirements. The communication workflow is split into two distinct operational parts: an initial asynchronous submission followed by continuous status monitoring.

For more details on supported formats, see Formats.

Submission and Detail Retrieval​

To send an invoice, send its UBL 2.1 XML to A-Cube. The platform validates the payload synchronously and responds immediately with a unique identifier (uuid). This ID is a critical piece of data; it must be stored in your database to fetch the current invoice details and processing state.

Sample Submission Response (202 Accepted)​

{
"uuid": "0199e8a1-2b3c-7d4e-8f90-a1b2c3d4e5f6",
"legalEntityUuid": "018f4a2e-7b3c-7f1a-b2c3-4d5e6f789abc",
"invoiceNumber": "2026-Invoice-0001",
"invoiceDate": "2026-11-01",
"dueDate": "2026-11-30",
"currency": "EUR",
"totalAmount": "1656.25",
"netAmount": "1325.00",
"direction": "outgoing",
"typeCode": "380",
"businessProcess": "P1",
"sender": {
"name": "Example Supplier d.o.o.",
"taxId": "48780941616"
},
"recipient": {
"name": "Example Buyer d.o.o.",
"taxId": "75608754333"
},
"status": "sent",
"downloaded": false,
"downloadedAt": null,
"createdAt": "2026-11-01T10:00:00+00:00",
"updatedAt": "2026-11-01T10:00:00+00:00"
}

Validation​

When you submit an invoice, A-Cube performs synchronous validation against both the UBL 2.1 schema and the business rules of HR CIUS 2025. The schema check verifies the structural correctness of the document, while the business rules enforce the constraints required for acceptance. If either check fails, the POST /invoices response returns the validation errors immediately, allowing you to correct and resubmit the document without waiting for a status update.

The error responses, with examples, are in the POST /invoices reference.


Delivery​

A-Cube delivers the invoice to the recipient's accredited service provider (ASP). The invoice then becomes delivered, undeliverable or delivery_failed: see Documents lifecycle for what each means and Tax Data Documents for what A-Cube files.

An undeliverable invoice must be delivered another way, for example as a PDF; don't send it again.

Sample Lifecycle Webhook Payload​

{
"eventId": "019a5c1e-4f2a-7b3c-9d8e-1f2a3b4c5d6e",
"eventType": "invoice.outgoing",
"documentUuid": "0199e8a1-2b3c-7d4e-8f90-a1b2c3d4e5f6",
"documentNumber": "2026-Invoice-0001",
"status": "delivered"
}

The event tells you that the status changed; read the invoice with GET /invoices/{uuid} for the details.

Configure your webhook handlers to catch these states automatically. This ensures your application's user interface can display when an invoice is delivered or can't be delivered without requiring manual calls.

Downloading invoices​

Listing your invoices​

Returns the paginated list of your invoices (both directions), sorted by the most recent first. See Search documents for the filters and pagination.