Skip to main content
A sales return invoice has the same fields, lines and rules as a purchase invoice — see that page for required fields, the customer snapshot, line rules, Lot/serial number tracking, line identity on update and sharing. This page only covers what is different for a sales return invoice.

​
Numbering

Send InvoiceNumber as "Next" to generate it automatically from the SATİADEFATNO number series (this invoice type does not use the e-Invoice numbering). "Next" cannot be sent on update, and InvoiceNumber must be unique in the company among sales return invoices.

​
Warehouse movement

Every line’s generated warehouse movement is inbound for a sales return invoice (the customer sends goods back, so stock increases), so Lots/SerialNumbers follow the inbound rules (each Lot entry creates a new lot, each serial number registers a new one).
No real sales return invoices exist yet in the data used to build this API, so the inbound direction of the generated warehouse movement is inferred from the inbound/outbound convention of the other invoice types, not directly verified. Report any discrepancy you find.

​
Customer ledger

A sales return invoice’s customer ledger entry is a credit (it reverses the debit a sales invoice would have created). If it has already been closed by a payment, the invoice’s customer, amount and currency can no longer be changed, and the invoice cannot be deleted (3015).