Schedule an invoice

The invoice moves to scheduled and nothing fiscal happens yet: it keeps its BORRADOR placeholder number, no series counter is consumed and nothing is registered with VeriFactu.

Scheduling never burns numbering.

What happens at scheduled_for. A sweep runs every minute and, on the first pass at or after that instant, it: (1) assigns the definitive correlative number of the series at that moment, not when you scheduled — so a document scheduled today and issued next month takes the number that corresponds to next month; (2) freezes the recipient and issuer snapshots as of that instant, which is what the PDF and the fiscal XML will show; (3) moves the invoice to sent; (4) queues the VeriFactu alta to AEAT asynchronously when the company is enrolled; and (5) emails the client only when scheduled_action is issue_and_send and the client has an email on file — with scheduled_action: draft the invoice is issued but never delivered, and issue_and_send without a recipient email still issues it, silently skipping the delivery.

Time zone. scheduled_for is an ISO 8601 date-time.

If it carries an explicit offset (2027-01-15T09:00:00Z, …+01:00) that offset is honoured; without one it is read in the account's server time zone, Europe/Madrid.

Resolution is minute-level: expect issuance within about a minute of the instant you asked for, never before it.

If the scheduled issuance fails, each invoice is isolated in its own transaction: the failing one stays scheduled with its date in the past, the error is logged, the rest of the batch is unaffected and the next sweep retries it.

A successful issuance is never repeated, because scheduled → sent can only happen once.

Limits: only a draft can be scheduled (any other status returns 422) and scheduled_for must be strictly in the future (422 otherwise).

While it is still scheduled you can call unschedule to return it to draft, or reschedule to move only the date.