Skip to main content
Pending validationOdoo 20.0Community and Enterprise

Communication to the AT failed or is pending

Symptom​

You clicked Communicate to the AT on an invoice (or a series) and:

  • the message in the corner of the screen says there was a communication with no answer or rejected;
  • the invoice's AT field, in the Certified document block, shows Unknown or Rejected instead of Accepted;
  • when you try to Resend or communicate again, the Invalid Operation window appears.

This article covers the communications fiscaldoo makes, document by document. The monthly communication of invoicing, by SAF-T file filed on the Portal das Finanças, is in How to communicate invoices to the AT and see the history.

Message​

Right after Communicate to the AT, in the top right corner:

“Communication with the Tax Authority. Accepted: 0, rejected: 0, no answer: 1.”

At the same time, the invoice's AT field changes to Unknown.

On a rejection, the same message says “rejected: 1” and the AT field shows Rejected.

In the communication record (see “What to check”), the Message field explains what happened. The two texts seen in the demo, with no answer:

“The Tax Authority did not say whether it accepted it.”

“No answer from the Tax Authority within the time limit.”

When you click Resend on an Unknown communication before checking the status:

“Check the state with the Tax Authority before resending: it may already have received this communication and a second one could duplicate it.”

After five attempts on the same communication:

“This communication already had 5 attempts (limit 5). Check the cause of the failure before creating a new communication.”

When you click Communicate to the AT on a series whose last communication got no answer:

“The last communication of series "NC U26" got no answer from the Tax Authority, which may already have registered it. Open that communication and check its state with the Tax Authority before communicating again.”

All the messages were triggered in the demo database, where the AT is replaced by a simulator that can answer “accepted”, “rejected”, “no answer” or “timed out”. The parts in italics change with the document.

Verified causes​

  • The AT did not answer, or the answer did not arrive in time. fiscaldoo does not know whether the AT received the document and marks the communication Unknown. The AT may have received it; that is why fiscaldoo only lets you resend after a status check. For invoices and delivery notes, that check does not reach the AT today on a production database (see “How to fix it”).
  • The AT rejected the communication. The state is Rejected and the Error Code and Message are the AT's. In the demo, the simulator only answers “Simulated rejection”, with the code MOCK-0001 (or 99, when it simulates an authentication refusal). Pending validation on screen: the real AT's rejection messages, including those for rejected credentials, cannot be triggered in the demo (only the simulator is used).
  • The communication reached the attempt limit. Each Resend counts as one attempt; at the fifth, the same communication can no longer be resent.

What to check​

  1. The invoice's AT field: Unknown (no answer), Rejected or Accepted.
  2. The communication record. Open Accounting › Declare › Tax Authority › What is there to do with the obligations? and, under Supporting lists, Communications with the Tax Authority. The list has one line per communication, with the Document (for example Lançamento FT D26/25), the Service (Invoice, Series…), the State and the Attempts.
  3. In the record, the Error Code, the Message and the Attempts.
  4. Your profile. The Accountant sees the list and the record, but does not have the Check status and Resend buttons, nor Communicate to the AT on the invoice: only the Fiscal officer communicates and resends.

The list only has the communications made by fiscaldoo. It does not show what was filed directly on the Portal das Finanças without being recorded in fiscaldoo.

How to fix it​

The communication of an invoice or a delivery note is “Unknown”​

Until the fix arrives, with the Fiscal officer profile:

  1. Before resending, check on the Portal das Finanças, in e-Fatura, whether the AT already has the invoice: look it up by number among the invoices issued by the company. Pending validation on screen: the Portal das Finanças cannot be opened from the demo database (the real AT is not used in tests).
  2. If the invoice already appears in e-Fatura, do not resend. The communication stays Unknown in fiscaldoo: contact support with the data from “Information to send”.
  3. If the invoice does not appear, open the communication record (see “What to check”, step 2) and click Resend. If “Check the state…” appears, close the window, click Check status (no message appears, but the Status Checked At field now shows the time) and then Resend. Each resend needs a new check: after a resend, the Status Checked At field still shows the time of the previous check, but Resend is refused again with the same message. When the AT accepts, the communication becomes Accepted, and so does the invoice's AT field.
  4. If the resend ends up Unknown again, do not resend straight away: go back to step 1 and check again in e-Fatura whether the AT already has the invoice. In the demo, the communication of FT D26/45 (Fiscal officer profile, simulator with no answer) was refused on the 1st Resend, got Status Checked At after Check status, was resent (Attempts 2, still Unknown) and the next Resend was refused with “Check the state…”, with the field still at the time of the previous check.
Pending validation by a certified accountant: how to confirm the AT received an invoice communicated with no answer, and what to do if it ends up communicated twice.

In the demo database, the AT simulator answers the check as if there were an invoice query: the communication of one invoice became Accepted without resending; that of FS D26/6 stayed Unknown with Status Checked At and became Accepted after Resend (Attempts 2); with the check also unanswered, nothing changed. These results only exist in the simulator: on a production database, an invoice or a delivery note never becomes Accepted with Check status alone.

While an invoice's communication is Unknown, the invoice has no Communicate to the AT button and cannot be cancelled: I cannot cancel an invoice or another certified document.

Who does it: Fiscal officer.

The communication was “Rejected”​

  1. Read the record's Error Code and Message: they say what the AT refused.
  2. Fix the cause. If the AT refused the credentials, check the sub-user, the password and the certificate in How to connect fiscaldoo to the Tax and Customs Authority. An issued invoice cannot be changed: if the error is in the document, the correction is a credit note or a cancellation, decided with the certified accountant.
  3. Click Resend on the record, or Communicate to the AT on the invoice. On a Rejected communication, Resend does not ask for a check first. In the demo, the rejected communication of FT D26/36 was accepted on the second send.

Who does it: Fiscal officer.

The attempt limit was reached​

Do not insist on the same communication: first find out why it fails (the Message of each attempt). Once the cause is fixed, click Communicate to the AT on the invoice: fiscaldoo creates a new communication, with attempts counted from zero. In the demo, the communication of FS D26/7 was rejected with 5 attempts; then Communicate to the AT on the invoice created another communication, which was Accepted.

Who does it: Fiscal officer.

A series' communication got no answer​

  1. In the Communications with the Tax Authority list, open the line for the Series service with the state Unknown (the Document is the series) and click Check status. For series, the check really does ask the AT which series it knows: if the AT has the series, the communication becomes Accepted; if not, it stays Unknown with Status Checked At, and you can click Resend.
  2. If it became Accepted, open the series and check the Validation code. In the demo, series NC U26 became Accepted after the check, but with no code on the series; the code was in the Answer tab of the communication record ("validation_code": "AKJVWLK5").
  3. In that case, do not communicate the series again. On the series, click Register validation code (Portal), type the code from the Answer and click Register. The series gets the code and can be activated as in The series has no AT validation code (ATCUD).

Who does it: Fiscal officer.

Communicating and checking do not create journal entries.

Pending validation by a certified accountant: consequences of an invoice left without an accepted communication by the monthly deadline, and whether, in that case, the monthly communication by SAF-T file replaces it.

Expected result​

  • The communication record becomes Accepted and so does the invoice's AT field.
  • On a series, the Validation code is filled in.
  • There are no two accepted communications for the same document.

When to contact support​

  • The invoice already appears in e-Fatura and the communication is still Unknown in fiscaldoo.
  • A series' communication is still Unknown after several checks, on different days.
  • The attempt limit was reached and the new communication fails with the same message.
  • The state changed to Accepted but the invoice's AT field did not change.

Information to send​

  • The document number (for example FT D26/34) or the series, and the company.
  • The Request (the code of the communication record), the State, the Attempts, the Error Code and the Message, copied from the record.
  • The time in Sent At and, if any, in Status Checked At.
  • Whether or not the invoice appears in e-Fatura.
  • The profile you logged in with.