Update notices

12 Nov 2026: Legal registration in the application, and who uploaded and sent an invoice

Two breaking changes in the application: a seller's legal registration is now mandatory, and an out-of-scope invoice now waits for its buyer's registration. A sales invoice also shows who uploaded and who sent it, and an invoice number is uploaded once per company.

OAuth API

No change

The OAuth API is not changed by this update

  • The legal registration rules of the OAuth API are the ones announced on 10 Nov 2026.
  • Nothing changes for API clients.

Application

Breaking change

A seller's legal registration is now mandatory in the application too

  • An invoice from your accounting system no longer goes on to the next step while its entity has no legal registration: it fails validation until you add it.
  • This also applies to invoices triggered through the API for the entity. Before, such an invoice went out with a stand-in registration.
  • The entity page shows an alert while a seller has not provided its legal registration, listing what is missing. It disappears as soon as everything is provided.
  • The edit form marks the legal registration fields as required for a seller: the number, the type, the issuing authority for a trade licence and the issuing country (two letters) for a passport.
  • A registration that contradicts itself, for example a number with no type, is refused when you save.
  • An invoice from your accounting system is refused (it fails validation) while the entity has not provided the registration.
  • The message lists what is missing and says to add it to the entity's details, in the application or through the entity update API, then send the invoice again.
  • Nothing is filled in for you. The TRN, the TIN and the participant id are never used as the registration number.
Why we changed this
  • Every invoice a seller sends carries its legal registration, the same as on the OAuth API, so the seller has to state it.
  • Until now the application treated it as optional, which let an incomplete entity be set up and then fail when its first invoice was built.
Reference

From the PINT AE Billing 1.0.4 specification. Each ID opens the rule on the Peppol documentation.

  • IBT-030The seller's legal registration identifier.
  • IBR-173-AE ↗The seller's legal registration identifier must state its type: TL, EID, PAS or CD.
  • IBR-150-AE ↗The seller's legal registration identifier must be present.
  • IBR-172-AE ↗A trade licence needs the authority that issued it.

What to do: Before your next invoices, provide the legal registration on every seller entity, in the application or through the entity update API. Invoices that already failed for this reason have to be sent again once it is added.

Setting up an entity →

Breaking change

A buyer's legal registration is asked only when the invoice needs it

  • An out-of-scope invoice or a credit note for goods or services no longer goes out on its own: it waits until the buyer's legal registration is given. Before, it went out with a placeholder.
  • An invoice from your accounting system no longer carries a placeholder registration for the buyer (the number 0000000, a trade licence type and the authority name "Trade License issuing Authority"). Those values were never real.
  • The buyer's registration is sent only when you state it completely: the number with its type, and the issuing authority for a trade licence or the country for a passport. A half-stated one is left out.
  • It is mandatory on an out-of-scope invoice and on a credit note for goods or services. Such an invoice is held, shown as "needs an answer", and asks for the registration on its Review PINT Mapping tab.
  • Your answer is remembered for that buyer: its later invoices, and its other held invoices, are sent with it.
  • On the PINT Mapping page the four Buyer Legal Registration rows start empty. Map the number to a field in your accounting system, or leave it empty to be asked when an invoice needs it.
Why we changed this
  • A registration the buyer never stated is invented data on a tax document, and the number 0000000 was sent on every invoice.
  • Asking only where the rule requires it keeps ordinary invoices flowing.
Reference

From the PINT AE Billing 1.0.4 specification. Each ID opens the rule on the Peppol documentation.

  • IBR-136-AE ↗The buyer legal registration identifier must be present on an Out of scope of VAT invoice and on a credit note related to goods or services.
  • IBR-180-AE ↗A buyer legal registration identifier on a 0235 buyer must state its type.
  • IBR-101-AE ↗A trade licence (TL) must carry the authority that issued it.

What to do: Nothing is needed for invoices that do not need the registration. If you invoice out-of-scope supplies, give the buyer's registration on the invoice when it asks, or map it on the PINT Mapping page, so those invoices are not left waiting.

PINT Mapping →

New

Uploaded by and Sent by on Invoice Details

  • On Sales Invoices, the Invoice Details tab shows Uploaded by, Uploaded on, Sent by and Sent on.
  • Each person is shown by name and by the email of their account, which cannot be changed, so a renamed member is still recognisable.
  • Sent by says how the invoice was sent: pressed Send, approved it, or approved by email link. It shows once Peppol accepted the invoice.
  • An invoice your accounting system sent on its own says Automatically; one sent through the API says Through the API.
  • A Tax Star support member who sent an invoice for you is shown as Tax Star support.
  • Uploads made before today show who uploaded them. Invoices sent before today do not show who sent them.
  • See Invoice Uploads.
Why we changed this
  • Owners and editors of a company can all upload and send invoices, and could not tell which of them uploaded or sent a given invoice, or when.

What to do: Nothing to do.

Invoice Uploads →

Changed

An invoice number is uploaded once per company, whoever uploads it

  • A spreadsheet row whose invoice number another member of the company already uploaded is now refused with "Duplicate — already uploaded".
  • Until now only your own uploads were checked, so two members could each upload, and send, the same invoice.
  • Uploads that already exist are not changed.
Why we changed this
  • The same invoice must not reach Peppol twice. PDF uploads were already checked across the company; spreadsheet rows now are too.

What to do: If an upload is refused as a duplicate, find the other member's upload on Sales Invoices before deleting anything.

Invoice Uploads →