Verifiable invoicing for Spain
Verifactu requires every invoice to create a registration record, each record to keep the previous record's fingerprint, and the sequence to be submitted to the AEAT. Cord builds that chain per organization: the SHA-256 fingerprint is generated at issue time, the record can't be edited, and a correction never rewrites the past: it creates a new record.
What is built
- A tamper-proof chain per organization: the database blocks changes to the fingerprint, content, sequence and type of a signed record.
- Decoupled submission with retries: issuing and submitting are separate steps, so an AEAT outage never stops you from invoicing. Submission batches records, honors the wait time the AEAT asks for and keeps every response.
- Incidents fixed from the invoice: the detail view shows the last record's status with the AEAT's code and reason, and "Correct and resend" creates the right correction record without changing amounts.
- A certificate per company: each business connects its electronic certificate, validated before it's stored encrypted.
- Verification QR on the PDF: at the top of the first page, at the size the regulation requires, and only when the invoice has a real record.
- Responsible statement: the system itself publishes the producer's statement with the same data that travels in every record.
Why it is in beta
Verifactu is switched on. As soon as a business in Spain connects its electronic certificate in Settings › Tax profile, every invoice is registered with the AEAT with its chained fingerprint, and its PDF carries the verification QR. The engine was verified against the official fingerprint vectors and the AEAT's WSDL and XSD, and it stays in beta until the first accepted submission; the status of each submission shows on the invoice detail. Without a certificate, a Spanish account's document is a pro forma, and Cord shows no QR, fingerprint or submission status that doesn't exist.
Obligation dates
Under Royal Decree-law 15/2025, published in the BOE, Verifactu is mandatory from January 1, 2027 for corporate income tax payers and from July 1, 2027 for everyone else. These are the regulation's dates, not Cord delivery dates.
How it works
The organization connects a valid Spanish certificate.
On issue, Cord creates the record, sequence and linked fingerprint, with no network dependency.
A separate process submits the record to the AEAT, keeps the response and lets you fix rejections from the invoice.
Availability and scope
Switched on in Spain: every invoice is registered with the AEAT as soon as the business connects its certificate. In beta until the first accepted submission. Each registered invoice counts toward the tax-compliant invoice allowance, from Starter.
Clear limits
Without a certificate, the Spanish document is a pro forma: no false QR or Verifactu status is shown. An invoice with IGIC, IPSI or equivalence surcharge is rejected when issued on this rail.