Treat it as one chain of events
The booking starts payment. Payment updates the stay. The guest chooses the document. Once the agreed conditions are met, the system creates the document, sends it and prepares access. Every step uses the same reservation data.
Payment needs to return to the reservation
Redirecting to a payment page is only half the job. Confirmation needs to come back, match the right reservation and trigger the next steps. Nobody should have to check a bank account by surname.
Receipt or invoice? Let the guest choose
The form can ask which document is needed. When a guest provides Polish business details and a tax number, the configured process can prepare a structured invoice and send it through the national e-invoicing system. Other stays can follow the agreed receipt and fiscal-printer workflow.
Fiscal rules, document timing and exceptions must be agreed with the accountant and matched to current law. The system follows the approved process. It does not invent one.
Create access only when the data is right
Once payment and required details are complete, time-limited access can be generated automatically, delivered to the right person and recorded in the event history.
The owner sees exceptions, not routine
The dashboard should surface unpaid bookings, rejected documents, missing details and access errors. That leaves human attention for decisions that need it.
Current KSeF information is published by the Polish Ministry of Finance.
Want to fix this in your property?
We can start with one problem or map the complete process. No presentation theatre.
Let's talk