invoice.date.out_of_range
Document date inside the Header reporting window
Every Invoice / Payment / WorkDocument / StockMovement date must fall inside Header.StartDate – Header.EndDate.
What this checks
Every <Invoice>, <Payment>, <WorkDocument> and <StockMovement> must carry a document date that falls inside the Header's reporting window:
Header.StartDate ≤ DocumentDate ≤ Header.EndDateThe "document date" tag varies by element:
Invoice.InvoiceDatePayment.TransactionDateWorkDocument.WorkDateStockMovement.MovementDate
Why AT cares
The Header declares the reporting period. A document dated outside that window is either a cross-month leak (your ERP scooped up something it shouldn't have) or a wrong fiscal-year extract. AT rejects either way.
Examples
| Header window | Document date | Verdict |
|---|---|---|
| 2026-01-01 → 2026-01-31 | 2026-01-15 | ✓ |
| 2026-01-01 → 2026-01-31 | 2025-12-30 | ✗ before StartDate |
| 2026-01-01 → 2026-01-31 | 2026-02-01 | ✗ after EndDate |
How to fix
- Confirm the Header period matches the SAF-T extract you actually meant to ship.
- If the document date is wrong, correct it in your ERP and re-export.
- If the document genuinely belongs to a different period, extract that month's SAF-T separately.
Related
- Header dates — the window this rule reads from.