The invoice list date range uses the operation date when there is one
date_from and date_to on the invoice list now match the operation date when the invoice has one, and the issue date otherwise.
ChangelogBreaking
Before, date_from and date_to always matched the issue date. Now they match the operation date (operation_date) of invoices that have one, and the issue date of the rest. Both bounds stay inclusive.
What else changed
- Who notices: anyone issuing invoices whose operation date falls in a different period from the issue date. Those invoices now appear in the range of their operation date.
- Exports are not affected: the
filters.date_fromandfilters.date_toof an export still match the issue date.
Endpoints
- GET/v1/companies/{company_id}/invoices
date_from/date_tomatch the operation date when set - GET/v1/invoicesSame change on the deprecated route
Where to go next
Exports add a Suplidos sheet for disbursements
When an exported invoice has `SUPLIDO` lines, the Excel export adds a `Suplidos` sheet with one row per source invoice.
Sorting by invoice number is numeric, and payment_date survives a correction
`sort_by=invoice_number` orders by series and then by number (`F-9` before `F-10`), ties are broken the same way, and `payment_date` stays after rectifying or voiding.