Generate the INE report XML

Holidario generates and validates an XML file, but does not file it with INE. Although the screen is named INE submissions and contains submission states, the Send to INE button is disabled and the IRIA SOAP connection is not available as a supported journey.

The correct result inside Holidario is the Generated state, a downloadable XML, and reviewed values. The agency remains responsible for filing it through the applicable official method and retaining the receipt outside this flow.

Before you start#

You need the Agency plan, access to Finance > INE report, and report read and update permissions. Confirm with INE or the agency's adviser:

• whether the establishment and period must be reported;
• which INE communication is being answered;
• the 11-character Order number;
• the 8-character Control code;
• questionnaire email and language;
• official category in keys;
• employed staff during the period;
• days open and managing company when applicable.

First verify that the month's properties, operations, capacities, bookings, blocks, prices, and dates are correct. The XML is calculated from Holidario records; valid generation does not certify that those records match reality or determine the agency's legal obligation.

Do not share the Control code by email, chat, or a general support request.

1. Open the reference month#

1. Open Finance > INE report.
2. In INE submissions, select the year.
3. Find the month and select Start submission or Open review.
4. Confirm the INE review title and displayed month.

The grid uses one card per month. Even if the INE email names the first or second half-month period (quincena), the generated XML includes the full month. Check the visible dates under XML data period before continuing.

2. Complete credentials and period#

Under Credentials:

1. enter the exact Order number;
2. enter the exact Control code from that communication;
3. confirm the Notification email;
4. select the Questionnaire language;
5. verify again that the period belongs to the card's month.

Holidario retains certain stable establishment values for the next month, but the Control code must be checked against the applicable communication. Do not reuse a code by assumption.

3. Review staff and establishment#

Under Employed staff (required), enter:

• Unpaid staff;
• Permanent paid staff;
• Temporary paid staff.

The sum must be greater than zero to generate. Confirm that it represents the reference period, not merely the current workforce.

Under Establishment, review Category (keys) and Days open in month. Managing company is optional; complete it only when applicable and with verified data.

4. Review reference operations and prices#

Reference operation per modality groups accommodations by capacity. For each modality, you can:

• choose a specific operation; or
• leave Average (all) to use the group average.

The selection is remembered in that browser. Do not assume another person or device will use the same sample.

1. Confirm that each operation belongs to the team and correct modality.
2. Review Avg. price (Sun–Thu), Avg. price (Fri–Sat), and percentages of nights sold.
3. Compare one known booking and period before accepting the calculation.
4. If a modality shows No apartments in this modality, confirm whether none exists or operation capacity is missing.

Do not alter prices or bookings merely to produce an expected XML value. Correct the source record first when it is wrong, then recalculate.

5. Generate and download#

1. Review every section and select Generate XML only once.
2. Wait for XML generated.
3. Return to INE submissions and confirm Generated.
4. Reopen the review if you need to inspect XML preview.
5. Select the card's XML icon to download the file.
6. Store it according to the agency's document policy.

Generation replaces the monthly record's XML with the values reviewed at that time. Keep a controlled copy of the file actually filed and the receipt returned by the official channel.

Filing outside Holidario#

There is no supported product step that delivers the XML to INE, confirms receipt, or automatically stores an acceptance. File the document using the official procedure your agency has verified with INE.

Do not mark the work as filed merely because its state is Generated. Record the filing date, responsible person, filed file, and official receipt separately.

States and current boundaries#

• Not started: no monthly record exists yet.
• Draft: data exists, but no final reviewed XML does.
• Generated: a validated, downloadable XML exists; this does not mean filed.
• Error: generation or validation failed; there is no filing evidence.
• Submitted, Accepted, and Rejected: these exist in the model and interface, but the supported generation journey neither produces nor confirms them.
• Acknowledgment: valid only when an official document exists; Holidario does not obtain one through the available flow.

If the card says the XML uses an older range, open Regenerate XML and repeat the full-month review before filing it.

Errors, denial, and recovery#

• INE report is missing: confirm Agency plan, finance feature, and read-ine-submission.
• Review cannot be opened or saved: an administrator must review update-ine-submission; do not use another account.
• Period falls outside the month: return to the correct card and use the displayed full month.
• Staff total is zero: correct the three categories with the responsible person.
• XSD validation failed: retain the visible errors, correct the indicated data, and regenerate; do not file that document.
• A figure does not reconcile: verify the reference operation, dates, bookings, blocks, and source prices.
• XML is missing: confirm Generated and reload once before generating again.
• Retry appears: do not use it to attempt a live filing. That action belongs to the unsupported connection.
• Reset or Delete: these are not normal generation steps and can change or remove the monthly record; escalate before acting.

When requesting help, include the team, year, month, reference operation, state, and error text. Follow the support template, masking the Order number, Control code, email addresses, full XML, and guest data unless a secure channel is agreed.

Completion criteria#

The Holidario task ends when a second person has reviewed the data, the state is Generated, and the downloaded file matches the preview. The external obligation ends only when the agency files that exact document through the official method and retains its receipt.