01 · Issue
A clear invoice before it becomes an official one. Customer, series, line items and taxes are reviewed in the same draft. You can get there from the editor, the POS, a quote or the API.
Electronic invoicing · VeriFactu Electronic invoicing.
See the journey ↓ Electronic invoicing.
With VeriFactu.
Cofactu lets you create invoices for your customers, review the data before issuing and check the result of the submission to the AEAT. It keeps the PDF and the related records so you can look them up again.
From draft to archive.
No invisible jumps.
02 · Validate
The system finds the errors before they go out. Cofactu checks the data that conditions the record: tax ID (NIF), date, amounts, invoice type and numbering.
03 · Prove
The document ends with proof you can look up. XML record, chained hash, QR and the official response stay attached to the invoice, with no parallel folders.
The journey of the document. Each chapter leaves a status you can understand and evidence you can check again.
Traceability is not
another task to do.
-
F-2026-0141
7b2e…04aa -
F-2026-0142
a3f8…91d4 -
F-2026-0143
4f1c…aa72 -
Each record's hash keeps the link with the previous one. If something needs reviewing, the context is already there.
What holds the invoice up Three layers to
Three layers to
issue with backing.
Official format XML compliant with Order HAC/1177/2024. 
Unbroken chain SHA-256 hash linked to the previous record. Authenticated submission Encrypted .p12 certificate, used to authenticate the communication with the AEAT (Spanish Tax Agency). One document · all its evidence
| Evidence | What is kept | Detail |
|---|---|---|
| XML | Submitted record | Order HAC/1177/2024 |
| QR | Verification included | Available on the PDF |
| CSV | AEAT response | A-MMURGK5EJU•••• |
Before and after issuing The invoice keeps working
The invoice keeps working
in the rest of Cofactu.
Its information starts in sales and feeds accounting, reconciliation and the tax calendar. No exporting or re-entering.
The essentials,
no small print.
The answers you need before issuing your first electronic invoice with Cofactu.
Read the VeriFactu guide →Does Cofactu generate VeriFactu records?
Yes. When you approve an invoice, Cofactu prepares the record in the required technical format, generates the chained hash and submits it to the AEAT through a certificate-authenticated connection.
What is stored after the invoice is sent?
The invoice keeps its PDF, its QR, the submitted XML record and, when the AEAT returns it, the response CSV (secure verification code). Everything stays linked to the same document.
What happens if the AEAT rejects an invoice?
The status and code stay visible in the history. Cofactu shows a practical explanation so you can fix the next step without losing context.
Do I need to install any software or plugin?
No. Cofactu runs in the browser. You upload your electronic certificate (.p12) once; Cofactu stores it encrypted with AES-256-GCM and uses it for every submission to the AEAT, which is automatic.
Start without risk Your next invoice
Your next invoice
can leave proof today.
No card. VeriFactu included in every plan. With the whole journey visible from the first document.
