Sending to the AEAT and VeriFactu errors
How to track submissions, what each status means and what to do if a record is rejected.
A record's statuses
| Status | Meaning |
|---|---|
| Sent | The AEAT received the record |
| Pending | Queued: it will be sent as soon as possible |
| Rejected | The AEAT didn't accept it: it needs checking |
| Not sent | VeriFactu wasn't on |
The VeriFactu sending queue shows how many records are pending and how many were sent.
Without internet
If the AEAT doesn't answer or there's no connection, you'll see AEAT unreachable, will retry. Do nothing: submissions go out on their own, in order, when the connection is back.
A rejected record
The most common causes are:
- An incorrect tax ID for the venue or the client.
- A certificate that has expired or doesn't match the tax ID.
- Sandbox mode on with a production certificate, or the other way round.
Fix the data and tap Send to AEAT on the record. Also check the VeriFactu Logs in Fiscal Data.
Verify the chain
Hash Verification (VeriFactu) goes through your receipts by year and month and checks that each fingerprint matches the previous one. If one is missing, Repair Chain regenerates it.
A rejection you don't understand? Get a remote support code and we'll look at it with you.