Skip to content
v26.3

VERI*FACTU: Checking the Connection and Resubmission

This chapter applies to Spain only. It describes the tab that shows whether the reports to the tax authority AEAT are arriving — and how to resubmit a document after a fault has been fixed.

Do you operate in Germany?

Then this chapter does not apply to you. The German counterpart is TSE in daily POS use.

Where to find it

Settings → Finance → VERI*FACTU. The tab only appears on Spanish installations. If submissions have failed permanently, the tab itself shows a counter badge with the number — you do not have to open it first.

What the tab shows

Area Content
Connection to the AEAT Environment (sandbox or live), endpoint, whether the taxpayer is configured, the AEAT certificate with expiry date or load error in plain text, and whether additional signing is active (XAdES)
Counters Number in the backlog, number permanently failed, number successfully reported, and the date of the oldest document still in the backlog
Two lists Backlog and permanently failed documents, each with error message, number of attempts and time

The lists are capped, the counters are not

Each of the two lists shows at most 200 documents. If there are more, further rows are missing from the list — the counters above still show the full number.

Backlog or permanently failed — the difference

A document that cannot be reported to the AEAT immediately first lands in the backlog. DiKAS automatically retries the report from there every two minutes, up to ten times.

State What it means What you need to do
Backlog (Pending) The submission is still waiting — e.g. because the AEAT was briefly unreachable. The automatic retry continues. Usually nothing. If a document stays in the backlog for a long time, check the connection at the top of the tab (certificate, endpoint).
Permanently failed (Failed) The automatic attempts are used up, or the AEAT has permanently rejected the document (e.g. wrong tax number). The automatic retry gives up — without your action the document stays unreported to the AEAT forever. Clarify the cause, then resubmit (see below).

Fix the cause first, then resubmit

The Resubmit button puts a document back into the queue so that the automatic retry tries it again. But it fixes nothing by itself — a document that failed because of an expired certificate or a wrong tax number will fail again after resubmission and appear in the same list once more.

The right order:

  1. Read the error message — it is shown next to the document in the "Permanently failed" list.
  2. Fix the cause — depending on the message, e.g. renew the AEAT certificate or correct the taxpayer details.
  3. Only then resubmit — individually per document or collectively for all permanently failed documents.

Resubmission is a deliberate action, not automatic

This is intentional: a permanently misconfigured business (e.g. wrong NIF) should not keep running endlessly against the AEAT. Resubmission only makes sense once the cause has been fixed.

Next Steps