Kapta · 15/09/2026
Provide the full Sage product name, edition, country and hosting arrangement. 'We use Sage' is insufficient to confirm an integration because products have different interfaces and requirements.
Why does the edition matter?
Sage Active documentation, for example, describes its own API and supported environments. That does not establish that the same setup works with another Sage product. Sage Active API introduction.
What installation information should I collect?
Product and version, invoicing company, technical contact and modules in use. If a partner manages the installation, involve them in assessing access. Do not send credentials through the initial form.
What should come from FareHarbor?
The booking identifier, services, amounts and customer details. Also describe deposits and cancellations. The connection needs a clear rule for selecting the document and associating its result with the source booking.
How can I get a useful assessment from Kapta?
Send a product-identification screenshot without sensitive information and an anonymised transaction example. Ask for confirmation of the connection method and supported scope before assuming invoicing, stock and accounting will all synchronise.
