HESTA direct submission
CampOne already aggregates the data BFS needs for the federal accommodation statistics (HESTA). This adapter submits it directly via the eHESTA API every month, replacing the manual CSV upload workflow. The CSV download stays available as a fallback.
See also: HESTA & Compliance → Overview for what the statistics cover and how the data is collected.
What it gives you
Section titled “What it gives you”- Auto-submit on the 5th of each month (configurable per tenant)
- Tracks every submission with its BFS acknowledgement ID and current status
- Re-poll status of pending submissions every 4 hours
- Receipt download stored in the integration log
- CSV fallback at
/admin/meldescheine/export/hesta-csv/remains available
Prerequisites
Section titled “Prerequisites”HESTA registration is per-campground — each accommodation has its own BUR-Nummer (establishment code) issued by BFS. CampOne can’t pre-register on your behalf.
What to ask BFS:
- The current eHESTA XML technical specification (PDF — not on the public site)
- The registration procedure for your BUR-Nummer
- API username / password for submissions
- The submission endpoint URL (test + production)
- Whether you can register CampOne as a centralised technical sender on behalf of multiple BUR-Nummern
A ready-to-send German email template lives at docs-internal/handoffs/integrations-outreach-emails.md. Or contact BFS directly:
- Email: hotelstatistik@bfs.admin.ch
- Phone: +41 58 461 12 55
What you’ll paste into CampOne
Section titled “What you’ll paste into CampOne”Settings → Integrations → Vendor Adapters → HESTA direct:
| Field | Description |
|---|---|
| Hotel code | Override of the per-tenant meldeschein_hotel_code if needed (usually leave blank) |
| Submission endpoint | URL provided by BFS |
| API username / API password | Per-tenant credentials from BFS |
| Submission format version | Default 2024 — confirm with BFS |
| Auto-submit | Tick to enable monthly automatic submission |
| Submission day of month | Default 5; the auto-submit fires on this day for the previous month |
| Environment | Test until BFS confirms production |
Click Save, then Test connection. The probe queries an obviously-non-existent ack ID and treats the resulting 404 as success (credentials valid, ID just not found).
What gets submitted
Section titled “What gets submitted”For each month the data set is identical to the CSV path: per-country counts of arrivals (within the month) and overnight stays (overlap days), aggregated from the Meldeschein records. The XML is shaped per the BFS technical spec; the CSV equivalent column structure is preserved for cross-checking.
You can submit a month manually from the settings card (Submit month…) — useful for testing or for re-submitting after a correction.
Submission states
Section titled “Submission states”Each submission moves through:
- Pending — sent to BFS, awaiting processing
- Accepted — BFS confirmed the data is valid
- Rejected — BFS rejected; the receipt explains why
The settings card shows every submission with its state and a Refresh button to poll BFS for the latest status.
Support contacts
Section titled “Support contacts”- BFS Hotelstatistik: hotelstatistik@bfs.admin.ch · +41 58 461 12 55
- BFS eHESTA login portal: https://www.esurvey.bfs.admin.ch/eHESTA/LoginPage.aspx?langCD=1
Limitations
Section titled “Limitations”- Until BFS provides a sandbox handshake, the XML envelope shape is best-effort and may need a one-file adjustment when they confirm the exact spec.
- Per-month submission is the unit; resubmitting a month replaces the previous submission for that period.
- Multi-establishment aggregator submissions (one CampOne instance submitting on behalf of multiple BUR-Nummern) need confirmation from BFS — ask in your initial email.