Skip to main content

Accounting Systems

Feed your accounting system — typically SAP, or whichever finance package your organisation runs — with the money side of ticketing activity.

Every sale, refund, and payment recorded in SECUTIX produces accounting lines: one row per amount, already tagged with the accounting codes set up for your organisation. Your integration receives those rows and records them in your accounting system.

Integrations are built from two flows, and the second one is only needed by some customers:

  • Outbound — SECUTIX sends the financial data to you. Accounting lines are delivered to your endpoint as they are produced. Order data can be added alongside when you need the commercial detail behind an amount.
  • Inbound — your system confirms payments it collected (optional). When money arrives outside the platform — a bank transfer, an ESR/BVR slip, or any external payment method your finance team tracks — your system tells SECUTIX which bank payment settled which file, so the ticketing side is closed too.

Example use cases​

  • Feed sales and payment lines into SAP — or whichever finance package you run — as financial activity is produced.
  • Retrieve the commercial detail behind an amount (basket composition, purchasing contact, per-operation breakdown) alongside the accounting lines.
  • Reconcile bank transfers and ESR/BVR slips collected outside the platform against the reservations or installment schedules they settle.
  • Pull financial data on demand for a batch export when your finance process runs on its own schedule rather than in real time.

Architecture Overview​

Accounting Systems Integration Architecture

Integration Steps​

The numbered steps below correspond to the flows shown in the architecture diagram. Both outbound feeds are configured by your SECUTIX administrator, who registers your ingestion endpoint URL and its authentication (none, Basic, or API key) — see Webhook Configuration for the full setup procedure, and Authentication & Authorization for obtaining API credentials.

  1. Accounting Lines Feed — the backbone of the integration. SECUTIX pushes accounting lines to your endpoint as financial activity is produced. Each line carries a lineId, an amount with its currency, a type (SALE or PAYMENT), and a list of elements — the field/value pairs that describe it, including the accounting codes. SALE lines say what was sold; PAYMENT lines say how it was settled, so a single order normally produces both. Your platform implements the receiving endpoint. API reference: Push Accounting Lines.

  2. Order Data Feed (optional) — accounting lines are deliberately narrow: amounts and codes, not the commercial story behind them. When your processes need that story — basket composition, the purchasing contact, per-operation detail — add the finalized orders feed alongside. Each completed order is pushed with its operations, payment details, and contact number. Your platform implements the receiving endpoint. API reference: Push finalized orders. If you prefer to pull this data on demand instead, Read Order and Search Orders expose the same content.

  3. Reconcile External Payment (optional) — needed when your accounting system owns the bank statement. For each bank line you have matched to a customer, call the platform so it settles the corresponding reservation or installments: the call finalizes a reservation as a sale, or progresses an installment schedule oldest-first, and books any leftover on the contact's credit note. It is synchronous and handles one bank line per call, with idempotency provided by payment.reference combined with payment.valueDate — so a replayed line never books twice. An importOptions.mismatchPolicy decides what happens when the bank amount doesn't match the expected total exactly. Full walkthrough: How to import an external payment. API reference: Reconcile External Payment.