Seller verification
Anyone can create a seller, so sending in a seller's name needs proof that you may act for it. E-mail delivery and real Peppol need a verified seller; issuing, downloading and the sandbox do not.
How a seller gets verified
- Attest that the seller authorised you:
POST /sellers/{id}/attestationwith{"confirmed": true}(or in the portal). - Automatic checks: the VAT ID is checked with the EU's VIES service and compared with the name. If you use the
VAT ID as the seller's Peppol address (scheme
9930, e.g.DE136695976), the check binds it too. - Review when the checks are not enough: upload a commercial-register extract, trade registration or signed
authorisation with
POST /sellers/{id}/documents(PDF, PNG or JPEG, at most 10 MB, 2 MB on the current instance size); we review it.
GET /sellers/{id}/verification shows the state (lower case, e.g. unverified, pending_review, verified), the reason
codes and the history. Typical reasons: checks.pending, vat-id.missing, vies.invalid, name.mismatch,
attestation.missing, plan.trial.
Changes
A verification belongs to the verified data. Invoices issued under other seller data (e.g. after a rename) cannot be
sent by e-mail or Peppol as that seller (403 seller.not-verified); issue a credit note and a new invoice.