Legal and compliance
Interpret historical NRUA/XBRL status
Historical boundary for a legacy NRUA/XBRL screen that is no longer available in Holidario.
- I own or administer an agency
- I manage operations
- I work at the front desk
- An agency manages my properties
- Agency
On this page
Legacy boundary: Holidario no longer exposes the NRUA queue, operation panel, or background processing. Use the organization's current external procedure; the remaining content documents the retired screen only.
The retired NRUA Submissions widget summarized team filings for the selected year and separated their operational state. This is a read-only guide: it explains how to interpret evidence you kept from that screen. Holidario no longer offers retrying, resetting, or deleting a filing, and no earlier state should be reported as acceptance without checking it in Sede Registradores.
Start the review#
- Scope Confirm team and authorized resources Start with the active team, report year, and operations inside your authorized property scope.
- Widget Read the queue state The retired queue showed Queued, Failed, and Submitted as summary columns; use only evidence you already hold.
- Operation Check the exact operation state The retired panel distinguished generated, filing created, files signed, submitted, accepted, and error; it is no longer shown.
- Registry Compare Sede Registradores A local submitted state or XBRL file was never final acceptance; compare the presentation directly in the Registry.
- Escalation Send evidence to an authorized owner Provide team, operation, year, filing ID, CRU, state, time, and a sanitized error without changing the record.
Holidario no longer shows NRUA Submissions on the dashboard or the operation panel. To review an earlier filing:
- Confirm the team and your property scope.
- Gather the evidence you already hold from the retired screen: screenshots, notes, identifiers, or downloaded XBRL files.
- For each record, identify the operation, report year, and last recorded state.
- Compare the presentation directly in Sede Registradores or with the person responsible for the external procedure.
- Escalate any discrepancy with the information in Recovery and escalation, without trying to change the record.
A property owner should assess only authorized operations they recognize. Front desk staff may report a state recorded in the evidence but must not decide report scope.
Read the columns of the retired screen#
Queued#
This could include records with these states:
- Generated;
- Presentation created;
- Files signed.
These were stages, not final confirmations. The card showed the period, operation, and known next step.
The widget showed reports here only when they fit Holidario's configured annual window. An existing report outside that window might not appear in the queue.
Failed#
Showed records in Error, the failed step, retry count, and next retry where available. The text could come from an external service or technical stage; do not interpret it as an instruction to change data at random.
The retired screen offered Retry, Reset, and Delete to people authorized to update filings. Those actions no longer exist, and an attempt recorded before the retirement does not prove the cause was resolved.
Submitted#
This column grouped both Submitted and Accepted records. A card appearing here is not enough to claim final acceptance.
The operation's NRUA Registry Submissions panel, which showed the exact state, period, dates, and identifier, is no longer shown. Compare the presentation directly in Sede Registradores.
NRA status the widget showed#
The lower section grouped:
- Valid NRAs, including valid and provisional states in that view;
- Missing NRAs, for missing, never-checked, or pending values;
- Invalid / revoked NRAs, with the known validation state and message.
Read the specific label recorded in your evidence. A provisional NRA was not equivalent to a valid one for every processing stage. If the validation date is absent, do not present the value as checked.
Retired operation panel#
On an operation with a validated NRA, NRUA Registry Submissions showed by year:
- CRU;
- exact state;
- generation and, where available, submission date;
- reservations and guests included;
- error message;
- XBRL file, when generated.
A downloaded XBRL proves generation, not submission or acceptance. Guest totals reflected data used when the report was generated; if they appear wrong, record the discrepancy and its source.
Warnings that do not prove readiness#
The absence of No digital certificate configured did not confirm that the certificate was complete, current, or accepted by the service.
An empty queue never meant “everything filed” either. It could result from the selected year, processing window, authorization scope, or the absence of a generated report.
Recovery and escalation#
For an earlier failed, incomplete, or contradictory record, give the person responsible for the external procedure:
- team, operation, and year;
- recorded filing ID and CRU;
- recorded state and step;
- last attempt and next retry, if recorded;
- 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 earlier filing has a state checked in Sede Registradores, discrepancies have an owner and evidence, and no intermediate stage is communicated as final acceptance.