Tax profile
The hotel's tax ID, regime and certificate, checked before they go out on an invoice with its name on it.
What it solves
The guest's invoice is issued by the hotel, with its tax ID and its regime. A regime that does not match its entity type is not caught at entry: it is caught when stamping fails, with the guest waiting for their invoice and the month already closed.
You notice it in things like these
- The first invoicing attempt reveals that the entered regime does not match the tax ID.
- Invoices go out under a legal name that is not the one on the certificate.
How it works
The entity type comes from the tax ID
Twelve characters means a company and thirteen means an individual, with a date inside that actually exists and no generic tax IDs. You do not pick it from a dropdown where you can pick wrong.
The regime has to match
It is checked when you submit for validation, before it reaches the review queue. An individual's regime on a company tax ID does not get past the screen itself.
Somebody checks it against the certificate
yaReserva sees the entity type next to the uploaded certificate and confirms it. That is the step between "I typed it right" and "it matches the document".
No validated profile, no publishing
The widget does not go live without an approved profile. And a revalidation in progress does not unpublish anything: invoicing continues with what was already approved, because switching off a hotel's sales over our own paperwork would charge it for our review queue.
Where it lives in the panel
- Hotel
- Tax profile
What it needs first
Your tax status certificate at hand, to upload it.
What it does not do yet
The limits, told by us
- The certificate PDF is not read automatically: the data is entered and the document uploaded so somebody can check it.
Carry on here
Shall we walk through it with your hotel on screen?
Half an hour, your rooms and your rates, and whatever questions you have. No commitment and no card.