Sending Invoices

This is the right section for you if you are acting as a supplier and looking to send invoices to your customers.

Throughout this guide you will learn how to send invoices to the Procuros API.

PHP examples are included but you will likely also want to look at the relevant API calls in the API reference.

Table of Contents


These are usually the steps taken when sending an invoice to Procuros:

  1. Check, if this document should be sent via Procuros (see: Enabled Trade Partners)
  2. Verify this document has not already been sent (see: Tracking Document Status)
  3. Build the transaction payload to be sent via Procuros.
    1. If products being invoiced are subject to bottle deposit, add additional line items for bottle deposit (see: Bottle Deposits)
    2. Make sure taxes (mainly VAT) are correctly added to line items (see: Taxes (VAT))
  4. Send the transaction payload via the Procuros API


You will need an API token to authenticate.
We use a bearer token which has to be included in each request you send to the API.

Please read the Authentication section of our API reference for a detailed description.

Error Handling

The API will return a 2xx status code for successful requests. Anything else indicates an error.

Please read the Errors section of our API reference for a detailed description plus examples of how to handle them.

Send Invoices

The API call Send transaction is used to create transactions, including invoices.

The following fields are required:

  • type (Transaction type. In this case INVOICE)
  • content (The details of the invoice items.)

Inside the content you will need to build all invoice items. All details can be found in the INVOICE schema as described in the API reference.

An example request would look like:

// install dependency
// $ composer require guzzlehttp/guzzle


$client = new \GuzzleHttp\Client();

$transaction = [
  'type' => 'INVOICE',
  'content' => [
    'header' => [
      'invoiceIdentifier' => 'API-INV-2022-08-31-001',
      'invoiceDate' => '2022-08-31',
      'shippingNoticeIdentifier' => 'SFTP-SHIP-2022-08-31-001',
      'shippingNoticeDate' => '2022-08-31',
      'orderIdentifier' => 'SFTP-2022-08-31-001',
      'orderDate' => '2022-08-31',
      'requestedDeliveryDate' => '2022-08-31',
      'expectedDeliveryDate' => '2022-08-31',
      'paymentTerms' => [
          'payInNumberOfDays' => 30,
          'percentage' => 0
      'supplier' => [
        'identifiers' => [
            'domain' => 'GS1',
            'identifier' => 'C10000'
      'buyer' => [
        'identifiers' => [
            'domain' => 'GS1',
            'identifier' => 'C20000'
    'items' => [
        'lineNumber' => 1,
        'identifiers' => [
            'domain' => 'GS1',
            'identifier' => '2330010000019'
        'isDepositItem' => false,
        'quantity' => 10,
        'unitPrice' => 10,
        'tax' => [
          'percentage' => 19,
          'amount' => 1.9,
          'description' => 'MwSt. 19%'

$response = $client->request('POST', '', [
  'headers' => [
    'Accept' => 'application/json',
    'Authorization' => 'Bearer <your-api-token>',
  'json' => $transaction,

Mark Document Status

Finally, as per the instructions mentioned under Tracking Document Status you must now track the status of the document locally, based on the returned HTTP response.

The document should be marked with either status TRANSMITTED or NO_ACTION. If there is an error with the document and it is not accepted, do not mark it with a status so it may be retried. For more information on retrying failed documents, please see: Retrying Documents.

For example:

$statusCode = $response->getStatusCode();

if ($statusCode == 201) {
} else if ($statusCode == 202) {
} else {
  // No need to do anything if it's not accepted, in an error case the document should be retried.

Advanced Use Cases

When it comes to sending invoices, there are a number of advanced cases, such as Invoice Modifications.

Please see the Features section of our API reference for a detailed description of all advanced use cases.