Skip to main content
Download OpenAPI

Receive an invoice

When a supplier issues an electronic invoice to one of your onboarding companies, A-Cube acts as the certified receiving platform (PA-R). The system automatically intercepts, validates, and stores the incoming document. The inbound communication workflow is split into real-time arrival notifications followed by compliant regulatory feedback.

Part 1: Automated Notification & Download​

Your system does not need to look for new incoming documents. As soon as an invoice clears central system routing, A-Cube triggers an asynchronous Webhook notification under the invoice.inbound.received event type. This payload contains the core metadata of the document along with a unique invoice_id, which you can use to pull down the complete structured file data at your convenience.

  • Inbound Arrival Notification: Webhook event invoice.inbound.received

  • Download Inbound Invoice Details: GET /invoices/inbound/{invoice_id}

Sample Arrival Webhook Payload​

{
  "event": "invoice.inbound.received",
  "invoice_id": "inv_in_88",
  "supplier_siret": "12345678900012",
  "supplier_name": "CONSTRUCTION ALPHA SAS",
  "total_tax_exclusive": 1250.00,
  "currency": "EUR",
  "format": "UBL",
  "received_at": "2026-06-08T09:15:22Z"
}

Part 2: Submitting Mandatory and Optional Lifecycle States​

Under the French mandate, receiving an invoice requires the buyer to actively report its processing lifecycle back to the supplier and the tax authority. Your system must provide interfaces or API integrations allowing your users to push state updates back to A-Cube.

Through our lifecycle endpoint, you can transmit two types of business states:

  1. Mandatory Statuses: You are legally required to submit a state update if your user decides to refuse the document entirely (210 Refused). Furthermore, if your company operates under a regime where VAT is due on payments (TVA sur les encaissements), you must strictly submit a 212 Payment received status once the invoice is settled.

  2. Optional Statuses: To optimize business communications and prevent supplier friction, you can optionally transmit internal progression milestones such as 204 In hand (Processing started), 205 Approved, or 207 In dispute.

  • Submit an Inbound Status Update: POST /invoices/{uuid}/lifecycle

Sample Status Update Request Payload​

{
  invoiceStatus:210
}

Interoperability Warning: While A-Cube supports the complete catalog of French business statuses, keep in mind that optional states require end-to-end alignment across all platform corners to safely reach the supplier's ERP. Legally mandatory statuses (210, 212) are guaranteed to route directly to the supplier and the PPF registry.

Last updated on