Monitor NRUA/XBRL status

The NRUA Submissions widget summarizes team filings for the selected year and separates their operational state. This is a read-only guide: if you find a failure, record the evidence and escalate; do not reset, retry, or delete a filing to try to change its state.

Start the review#

1. Confirm the team and your property scope.
2. Find NRUA Submissions on the dashboard.
3. Check the selected year; it normally opens on the previous year.
4. Select refresh once if you need to reload local data.
5. Review all three columns, then the operations' NRA status.

A property owner should assess only authorized operations they recognize. Front desk staff may report a visible state but must not decide report scope or intervene in processing.

Read the columns#

Queued#

This can include records with these states:

• Generated;
• Presentation created;
• Files signed.

These are stages, not final confirmations. The card shows the period, operation, and known next step. If it does not change, record the state and latest visible time before escalating.

The widget shows reports here only when they fit Holidario's configured annual window. An existing report outside that window may not appear in the queue.

Failed#

Shows records in Error, the failed step, retry count, and next retry where available. The text may come from an external service or technical stage; do not interpret it as an instruction to change data at random.

The Retry control appears only to a person authorized to update filings. Do not use Retry, Reset, or Delete during a status review even when an action is visible: they alter the processing cycle and belong with the administrator who has verified the cause.

Submitted#

This column groups both Submitted and Accepted records. A card appearing here is not enough to claim final acceptance.

Open the corresponding operation and review NRUA Registry Submissions for the exact state, period, dates, and available identifier. Then compare the presentation in Sede Registradores.

Review operation NRA status#

The lower section groups:

• Valid NRAs, including valid and provisional states in this view;
• Missing NRAs, for missing, never-checked, or pending values;
• Invalid / revoked NRAs, with the known validation state and message.

Read the specific label. A provisional NRA is not equivalent to a valid one for every processing stage. If the validation date is absent, do not present the value as checked.

Review one operation#

On an operation with a validated NRA, NRUA Registry Submissions shows by year:

• CRU;
• exact state;
• generation and, where available, submission date;
• reservations and guests included;
• error message;
• XBRL file, when generated.

A downloadable XBRL proves generation, not submission or acceptance. Guest totals reflect data used when the report was generated; if they appear wrong, do not regenerate. Record the discrepancy and its source.

Warnings that do not prove readiness#

The absence of No digital certificate configured does not confirm that the certificate is complete, current, or accepted by the service. Evidence must come from guided implementation and the Sede Registradores state.

Do not interpret an empty queue as “everything filed” either. It may result from the selected year, processing window, authorization scope, or the absence of a generated report.

Recovery and escalation#

For a stalled, failed, or contradictory record, provide:

• team, operation, and year;
• visible filing ID and CRU;
• displayed state and step;
• last attempt and next retry;
• error message without personal data;
• NRA, state, and validation date;
• related Sede Registradores state, if present.

Do not include the certificate, password, XBRL, complete response, or traveller data in a normal ticket.

Expected result#

Every filing has an exact state checked on its operation, failures have an owner and evidence, and no intermediate stage is communicated as final acceptance.