issue_date_before_series_last_issue_date
When it is issued, the invoice takes the date of the day of issue, and the series already has an issued invoice with a later date (for example, one created with a future date), so issuing it would break the date order of the series. Nothing was issued and no number was consumed: the draft stays as it was. `error.message` names both dates.
| Code | Type | HTTP | Category |
|---|---|---|---|
issue_date_before_series_last_issue_date | invalid_request_error | 422 | Invoices |
Cause
When it is issued, the invoice takes the date of the day of issue, and the series already has an issued invoice with a later date (for example, one created with a future date), so issuing it would break the date order of the series. Nothing was issued and no number was consumed: the draft stays as it was. error.message names both dates.
What to do
Move the draft to another series of the same kind with series_id and issue it, or repeat the issue from the date of that last invoice onwards. If the invoice was created in that same call with options, the draft already exists (the 422 does not undo it): issue THAT draft, or move it to another series, instead of repeating the creation, which without the same external_id would create another one. Changing issued_on does not help: an issued invoice always carries the date of the day of issue.