Billing responses are used by the customer to inform the supplier of the status of the handling of an invoice or credit note.

Response flow

The status of an invoice must advance in the following sequence, but any status may be the first one used or may be omitted.

• AB – Message acknowledgement
• IP – In process
• UQ – Under query (may be repeated before moving forward)
• CA – Conditionally accepted
• RE – Rejected
• AP – Accepted
• PD – Paid, can be in steps, partially paid and then paid.

In some cases, depending on the agreement between the seller and the buyer, an Accept or Reject can be considered final states, whereas in other scenarios, the Paid status can be considered final.

flowchart LR
    S1@{ shape: start } --> AB
    AB --> IP
    IP --> UQ
    UQ --> CA
    CA --> RE
    RE --> S4@{ shape: stop }
    RE --> AP
    AP --> S4@{ shape: stop }
    AP --> PPD
    PPD --> PD
    PD --> S4@{ shape: stop }

Response elements

Structure

A billing response is sent with POST /transactions/submit-billing-response. Next to messageHandling, the request body has an invoiceResponse object with these properties:

details is a list of { "type", "value" } pairs: type identifies the element that needs to be corrected, for example BT-13 (Purchase order reference), and value contains its correct value.

Complete examples are in Billing response: Use cases.

In billing responses there are three types of codes that need to be specified. These are:

• Status, such as UnderQuery, Accepted, Paid.
• Reason, such as ReceiverUnknown, ItemQualityInsufficient, QuantityIncorrect.
• Action, such as ProvideInformation, IssueNewInvoice, CreditFully.

Here you can find more information about the values accepted for each element.

Status

The status element is validated against the Invoice status code (UNCL4343 Subset) list.

You need to use one of the following values:

Reason

Each entry in the reasons list has a reason code. It accepts the values defined in the Status Clarification Reason (OpenPEPPOL) list.

The values are as follows:

Action

To specify which actions the buyer expects from the seller in order to resolve the reported issues, use the actions list.

Each entry has an action code (required), an optional actionDescription and optional details.
The action property must be provided according to the Status Clarification Action (OpenPEPPOL) list, as described in the following table:

Croatia: rejection reason code

When you reject an invoice from a Croatian supplier (status Rejected), rejectionReasonCode is required. It is ignored for other suppliers.

Unimaze then reports the rejection to the Tax Administration. See Customer may register a rejection for the recommended way to reject a Croatian invoice, and On the supplier side for how the supplier receives the rejection.