Skip to main content

Webhook event types

Webhook Types​

The HR API currently uses these event types:

CategoryWebhook TypeWhat it does
Onboardinglegal_entity.onboardingReceive information about Legal Entity onboarding status
Invoiceinvoice.outgoingReceive information about invoice processing stage
Invoiceinvoice.incomingReceive information when incoming invoice is received
Credit notecredit_note.outgoingReceive information about credit note processing stage
Credit notecredit_note.incomingReceive information when incoming credit note is received
Tax Data Documenttax_data_document.outgoingReceive information about Tax Data Document processing stage
Payment reportpayment_report.outgoingReceive information about payment report processing stage
Rejection reportrejection_report.outgoingReceive information about rejection report processing stage

The credit_note.* events carry the same payloads as their invoice.* counterparts: the event type is picked from the document type, so a credit note never triggers an invoice.* event and vice versa. Subscribe to both families if you want to be notified about every document.

Subscribe only to the events your application handles. The API Reference remains the source of truth for the supported event catalogue and payload contract.

Onboarding Events​

Use legal_entity.onboarding to follow the onboarding of a Legal Entity: it is sent when the status of its document exchange or fiscalisation confirmation changes, for example after A-Cube's automatic check. The event carries both confirmation statuses:

{
"eventId": "019a5c24-1e2f-7a3b-8c4d-5e6f7a8b9c0d",
"eventType": "legal_entity.onboarding",
"legalEntityUuid": "0199e7c2-3d4e-7f5a-8b6c-7d8e9f0a1b2c",
"taxId": "48780941616",
"documentExchangeConfirmationStatus": "confirmed",
"fiscalisationConfirmationStatus": "not_confirmed"
}

When a check fails, the reason is on the Legal Entity: use the GET /legal-entities/{uuid} endpoint.

Document Events​

The invoice and credit note events carry the document's identifier, number and new status:

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

Tax Data Document Events​

tax_data_document.outgoing covers every Tax Data Document type, incoming (U) too: "outgoing" means sent to the Tax Authority. The event carries the Tax Data Document and the document it refers to; referencedDocumentUuid is null for an external document.

{
"eventId": "019a5c20-3c4d-7e5f-8a6b-7c8d9e0f1a2b",
"eventType": "tax_data_document.outgoing",
"taxDataDocumentUuid": "0199e8d3-1a2b-7c3d-8e4f-5a6b7c8d9e0f",
"taxDataDocumentType": "outgoing",
"referencedDocumentUuid": "0199e8a1-2b3c-7d4e-8f90-a1b2c3d4e5f6",
"referencedDocumentType": "invoice",
"referencedDocumentDirection": "outgoing",
"status": "accepted"
}

Report Events​

payment_report.outgoing and rejection_report.outgoing tell you the Tax Authority's answer to a payment or rejection report. Both carry the same body: the report, its Legal Entity, and the document it refers to; documentUuid is null for a report filed by reference.

{
"eventId": "019a5c22-7d8e-7f9a-8b1c-2d3e4f5a6b7c",
"eventType": "payment_report.outgoing",
"reportUuid": "0199e8f5-6a7b-7c8d-9e0f-1a2b3c4d5e6f",
"legalEntityUuid": "0199e7c2-3d4e-7f5a-8b6c-7d8e9f0a1b2c",
"documentUuid": "0199e8a1-2b3c-7d4e-8f90-a1b2c3d4e5f6",
"documentNumber": "2026-Invoice-0001",
"status": "accepted"
}

Document Lifecycle & Events​

Document processing is asynchronous. A successful POST creates the resource first; delivery and tax reporting continue afterwards.

  • For outgoing documents, use invoice.outgoing, credit_note.outgoing and tax_data_document.outgoing events and check the document status to confirm delivery.
  • For incoming documents, use invoice.incoming and credit_note.incoming to retrieve and import the new resource.
  • For payment and rejection reports, use payment_report.outgoing and rejection_report.outgoing to learn whether the Tax Authority accepted them.
  • If a webhook is delayed, use the collection and detail endpoints as a fallback.

Keep exchange and tax reporting as separate status concepts. A document may be delivered while its Tax Data Document is still being processed, or one of the two operations may fail independently. See Documents lifecycle for the statuses.