Skip to content
Holidario Documentation

Legal and compliance

Monitor the VeriFACTU overview safely

Distinguish queued actions, long-pending, rejected, and recent activity from the widget, then escalate without duplicating communications.

For
  • I own or administer an agency
Available on
  • Agency

The currently accepted public journey is to read the dashboard's VeriFACTU Submissions widget and escalate with the evidence it shows. Do not submit, resubmit, annul, or change an invoice during a status review.

The invoice detail tab and recovery controls are not yet part of this public journey. Do not use them as a prerequisite or a test path even when a link is visible.

Start with the team overview#

  1. Confirm the active team.
  2. Find VeriFACTU Submissions on the dashboard.
  3. Refresh once and note the visible time.
  4. Review all four columns from left to right.
  5. Record the visible invoice number, company, type, state, and relative time without opening the invoice.

The dashboard shows only each invoice's latest attempt in its submission columns. It is neither a complete historical record nor definitive tax evidence.

Read the four columns#

Enqueued actions#

A card here means a Submission or Annulment action is waiting for processing. It does not yet prove that a submission was created or that the authority responded.

A notice shown after requesting submission may mean the action was stored successfully. Always confirm it leaves the queue and a state-bearing attempt appears; do not communicate that initial notice as acceptance.

Rejected submissions#

Includes latest attempts in Rejected or Error during the previous 24 hours. The card shows company, type, and a short description where available.

A rejection older than that window can disappear from this column without being resolved. Do not close an incident only because its card has disappeared; escalate the known identifier.

Long pending#

Includes latest attempts still in Pending at least 24 hours after their submission time. Do not assume they are rejected or repeat the action. Record their age and escalate to check the result.

Recent submissions#

Includes attempts from the previous 24 hours in any state. It is an activity view, not a success list. Read each card's specific badge.

Decide the next step from the widget#

Queued action ≠ submission ≠ accepted result
  1. Queue Identify the waiting action A submission or annulment action in the queue proves only that processing is pending.
  2. Attempt Look for a state-bearing submission A submission record is later evidence, but pending, rejected, error, and recent still need their exact badge.
  3. Result Treat acceptance as a separate result A saved notice, an empty column, or recent activity does not prove that the authority accepted the invoice.
  4. Boundary Remain inside the dashboard widget Do not open invoice detail, a response payload, or an error modal as part of this public review journey.
  5. Escalation Escalate the visible summary Share the team, company, invoice reference, column, state, and time with an authorized reviewer without resubmitting or annulling.
Widget-only recovery Preserve the visible evidence and escalate. Do not duplicate communications or change the invoice to test a result.
Responsive visual summary; the complete content is also explained in the text.
  • Enqueued: wait for the agreed cycle and check once more.
  • Long pending: escalate with the exact date.
  • Rejected or error: retain the short visible description and escalate; do not turn it into instructions for random data changes.
  • Recent activity: read the specific badge; this column contains every state and does not mean success.
  • No card: do not conclude that everything was filed; it may reflect the 24-hour window, scope, or absence of a recent attempt.

A queued action is not a submission, a submission is not acceptance, and a saved notice is not an authority response.

Current detail and recovery boundary#

This guide does not provide steps for opening an invoice's VeriFACTU detail, interpreting a complete response, resubmitting, annulling, replacing certificates, or changing tax data. Those operations require assisted review and separately accepted access controls.

If a widget link opens a screen you cannot read, do not request a broader permission as the automatic solution. Preserve the visible evidence and escalate the case.

Information to escalate#

  • team and company;
  • visible invoice number and ID, where shown;
  • action or submission type;
  • column, state, relative time, and age;
  • short visible description without personal data;
  • time of the widget's last update;
  • expected and observed result.

Do not copy complete responses or tax/personal data to an unapproved channel. Never include a certificate, private key, password, or invoice contents. Send the case to [email protected].

If the widget is missing or empty#

  • confirm you have permission to read VeriFACTU submissions;
  • check whether the card is included in the current dashboard tab;
  • remember that recent and rejected columns cover only 24 hours;
  • refresh once; if it remains empty, escalate team, time, and expected invoice without trying to generate a submission.

Expected result#

Every queued action is distinguished from a submission, every column is interpreted within its window, and recovery reaches an authorized person without duplicating communications.

Browse all documentation Press ⌘K or Ctrl+K from any page.

Preparing search…