Exact SES.HOSPEDAJES period
Export only the period you are actually filing in Spain.
Informative Model
Import SES Hospedajes into the informative model for filing in Spain
This page is focused on import operations: move SES.HOSPEDAJES communications into the informative model, complete missing fields, and prepare final filing in Spain. BnCheck is multiplatform and works on Mac, Windows, and mobile.
What you need for a clean SES import
Before you copy data from SES.HOSPEDAJES, prepare this baseline to avoid mapping errors:
Property reference inventory
Keep CRU and NRUA ready per accommodation unit.
Purpose coding policy
Define how purpose codes will be assigned by stay type.
Date and occupancy control
Check check-in, check-out, and guest count before import.
Duplicate handling criteria
Identify split or repeated bookings before final mapping.
Filing environment ready
Have certificate and AutoFirma ready for Registrars submission.
What BnCheck validates during SES import
The objective is not only data transfer. It is also mismatch detection before final generation:
- CRU mapped to the right property unit for the imported period.
- NRUA aligned with the declared stay type.
- Purpose code available for each imported record.
- Guest count complete for each stay.
- Check-in/check-out dates without cross-system mismatch.
When these fields do not match, amendments are usually required.
Recommended SES.HOSPEDAJES import flow
Execution sequence to move from SES data to informative model with fewer corrections:
1) Extract period communications
Work with a closed block before validation starts.
2) Load and normalize
BnCheck structures imported stays for operational review.
3) Complete missing non-SES fields
Add NRUA, purpose, and required references where missing.
4) Resolve mismatches
Fix differences before final file generation.
5) Finalize filing in Registrars
Submit telematically once the model is validated in full.
Ready to file the Spanish Rental Deposit in Spain
Before filing, verify these checks and use the visual workflow to keep the submission package ready for the Registrars portal in Spain.
- Same guest count per stay in both sources.
- Same check-in and check-out dates.
- Bookings assigned to the right property.
- Purpose code aligned with each stay.
Frequent errors and quick fixes
Common telematic filing issues and how to solve them:
| Error | Fix |
|---|---|
| Malformed CRU | Validate format and mapping to the correct property. |
| Missing NRUA | Complete NRUA for each unit before file generation. |
| Same generic purpose for all bookings | Assign the right purpose code per stay. |
| Date mismatch vs SES | Align check-in/check-out with original communication. |
| Guest count mismatch | Review actual occupancy per booking and correct records. |
| Stay not allowed for the NRUA | Stays must be consistent with the NRUA type. Use the NRUA that matches tourist or seasonal use. |
N2 alternative and N2 software: what to expect
N2 for Mac has no native version. N2 for Windows works, but many teams in Spain prefer an N2 alternative that is web-based and multiplatform to prepare and validate data before filing.
Why Airbnb CSV is not enough
Airbnb CSV exports do not include all required filing fields. In NRUA Airbnb and NRUA Booking scenarios, consistency fields and references are often missing.