Kapta · 15/09/2026
The connection should turn booking data into an appropriate invoice workflow, with references that let staff trace payments, changes and refunds. Start by agreeing with the finance team when documents should be issued and which data should be transferred.
What should be agreed before automation starts?
Identify the seller, the payment recipient and the invoice issuer. Direct bookings, partner sales and walk-up purchases may follow different workflows. For each workflow, define the event that authorises issuance and the identifier that prevents a document from being created twice.
How should HUF and EUR bookings be prepared?
Include booking currency, payment currency, gross amount, discounts and fees in the assessment. Do not treat amounts in different currencies as equivalent or infer currency from a visitor's country. Ask your accountant for the applicable invoicing and exchange rules, then test representative examples before enabling automatic issuance.
What happens when a booking is refunded?
Returning a payment and correcting a fiscal document are separate operations. The Számla Agent documentation includes document creation and reversal operations. The actual workflow should link the refund to its original document, choose the appropriate operation and send exceptions for review.
How can the connection be checked?
Test a paid booking, a price change, a partial refund and a partner purchase. For each case, find the same reference in the booking, payment and document. Ask Kapta to assess the FareHarbor–Számlázz.hu workflow using anonymised examples; gate admission should retain its own reference.
