Glossary
Short definitions for readers of this public guide. Wording is explanatory, not legal.
| Term | Meaning |
|---|---|
| Auto-generated invoice | Invoice the platform creates from structured booking report data submitted over the API, without someone retyping the reservation. |
| Auto-approval | Buyer configuration that approves qualifying invoices without manual clicks, subject to thresholds and periodic caps. |
| Available balance (buyer) | Funds presented as immediately usable for supported actions such as early settlement or transfers, subject to provider connectivity and policy. |
| Booking report | Structured payload sent over the API (single booking or batch) that describes travel inventory or services sold; the primary input for automatic invoice generation. |
| Buyer | Organisation that purchases travel inventory or services from sellers and runs approvals and settlement through Expereon. |
| Collateral balance (buyer) | Funds presented as backing approved obligations, often showing free, used, and utilisation metrics. |
| Connection (buyer–seller) | Mutual commercial link inside the product, with settings for trust, terms, and sometimes automation. |
| Deposit / withdraw / transfer | Buyer funding actions between bank or provider rails and the balances surfaced in Expereon. |
| Dispute | Structured disagreement on an invoice, potentially escalating to mediation. |
| Draft invoice | Seller-prepared invoice not yet submitted for buyer action. |
| Funding history | Chronological record of deposits, withdrawals, and transfers between available and collateral balances for audit. |
| Integration (API) | Machine-to-machine access using keys, REST-style calls, and optional webhooks. |
| Manual approval | Configuration where humans must approve every invoice before it becomes a binding obligation. |
| Organisation | Tenant container for users, settings, counterparties, and financial configuration. |
| Overdue | State indicating settlement did not complete by required deadlines—triggers operational follow-up. |
| Payout / off-ramp (seller) | Movement from in-platform settlement form to external wallet or bank rails where supported. |
| Pending settlement | Post-approval phase where an invoice awaits settlement according to terms and balance source. |
| Refund | Buyer-initiated reversal request reviewed by seller, with system execution when approved. |
| Sandbox | Non-production environment for safe integration testing. |
| Seller | Organisation supplying travel services and receiving settlement for approved invoices. |
| Trust mode | Buyer-level posture combining manual approval, automation thresholds, pauses, and periodic limits. |
| Utilisation | Measure of how much collateral capacity is consumed versus remaining headroom. |
| Wallet (seller) | Crypto-style address or hosted wallet capability used to receive programme settlement. |