NewProvince is only required for addresses in Spain
BeeL
Get startedMulti-NIFVeriFactuRulesStripeAPI referenceChangelog

Exchange simplified invoices for a full invoice

A new operation issues a full invoice in exchange for simplified invoices when the customer asks for one with their details. With VeriFactu it is now recorded as F3.


ChangelogNew

When a customer who paid with a simplified invoice asks for an invoice with their details, POST /v1/companies/{company_id}/invoices/simplified-exchanges issues a STANDARD invoice with the lines of up to 50 simplified invoices and the recipient you send. It is not a corrective invoice: it documents the same operations again, identifying the customer.

The new invoice lists the ones it replaces in replaced_invoice_ids, and each simplified invoice becomes VOIDED with the new void_cause value EXCHANGED, in the same act. The exchange invoice cannot be voided afterwards; if it is wrong, correct it with a corrective invoice.

When the invoice would be recorded with VeriFactu, the request answered 422 SIMPLIFIED_EXCHANGE_NOT_RECORDABLE and nothing was issued.

Update: with VeriFactu the exchange invoice is now issued and recorded as F3, and SIMPLIFIED_EXCHANGE_NOT_RECORDABLE only names a simplified invoice issued without VeriFactu. An F3 exchange invoice cannot be corrected yet. See Simplified invoice exchanges are recorded with VeriFactu.

What else changed

  • Rejections: 422 EXCHANGE_REQUIRES_SIMPLIFIED when an id is not a simplified invoice; 422 SIMPLIFIED_NOT_EXCHANGEABLE when it is not issued, or was already voided, exchanged or corrected; voiding the exchange invoice answers 422 EXCHANGE_INVOICE_NOT_VOIDABLE.
  • If you read void_cause with a strict enum, add EXCHANGED; replaced_invoice_ids is a new optional field on every invoice response.

Endpoints

  • POST/v1/companies/{company_id}/invoices/simplified-exchangesNew: a full invoice in exchange for simplified invoices

Where to go next