TRA reporting for every guest, from the same check-in.
TRA is Colombia's tourism registry, run by MinCIT, where lodging providers report their guests. Unlike SIRE, it has a documented PMS API. Sixto builds each guest's report from the check-in, keeps a copy, and sends it with the token for each of your tourism registrations (RNT).
Live. Sixto builds each guest's TRA report from the check-in and sends it with your RNT token.
Every guest, one registration flow
National and foreign guests
What it does
Know what moves, and what stays put
Arrows describe data direction relative to Sixto.
Every guest, main and companions
The main guest and each companion are reported, Colombian or foreign.
One token per RNT
Each registration has its own token, stored encrypted and managed in Filing, so a property with several RNTs files correctly.
A copy of every report
Every report is stored with TRA's response, so you can review what was sent.
Safe retries
Network errors are retried on a schedule. A timeout is checked before any resend, so a guest is not reported twice.
Cost in pesos
The stay cost is worked out from the reservation's money and converted to COP at the exchange rate when needed.
How it works
- 01
An Owner enters the TRA token for each RNT in Filing. Tokens are stored encrypted.
- 02
Guests complete the check-in form. Sixto builds each guest's report from it.
- 03
Sixto sends each report and records the response. Failures raise alerts.
What syncs
Common questions
Do I need a token?
Yes, one for each RNT, issued by TRA.
What happens if TRA is down?
Sixto retries and alerts your team, and a page monitor watches for changes in the TRA documentation.
Can I review a registration result?
Yes. The registration response is kept with the guest registration, so your team can review the result and handle anything that needs attention.
