Kapta · 15/09/2026
Define a rule for each event and keep the booking linked to payments and documents. Amending a booking, returning money and correcting a document are related operations, but they can happen at different times.
How should I prepare a deposit example?
Imagine a €200 booking with €50 initially paid and €150 received later. These are illustrative operational amounts. The integration should recognise one booking with two movements, without treating the second payment as a new €200 sale. Your accountant should define the documents required at each stage.
Should cancelling a booking delete the invoice?
The workflow should not automatically delete documents on cancellation. First identify the existing document, payment status and approved correction for the situation. A booking cancelled before payment has a different history from a fully paid booking.
What if only one participant cancels?
Compare line items and amounts before and after the change. Record the refund amount, remaining booking value and original document reference. Do not replace the history with a new total without preserving relationships between operations.
How can duplicate corrections be prevented?
Save the refund or amendment reference and its destination result. After a communication failure, recovery should check what already happened. The integration proposal should explain exception tracking and who validates ambiguous cases.
What should I send Kapta?
Prepare three anonymised examples: deposit followed by balance, full cancellation and fewer participants. Identify the invoicing software, who authorised the refund and the accountant's expected document. Available events and data need account-specific confirmation. Kapta FareHarbor integration.
How should the workflow be validated?
Follow every example from booking to document. Check expected payments, identified refunds and that repeated processing does not create another correction. Agree an initial review of the first transactions after activation.
