Tevalis Ideas Portal
When a site hosts a large booking with a pre-payment (e.g. £X), front-of-house teams need a simple, secure way to take payments without risking that the total spend exceeds the pre-paid amount. Payments on Account (PoA) enables POS users to tender individual transactions against an allocated balance, rather than relying on a shared bar tab.
Multi-point ordering: Ideal for large venues and competitive socialising where guests order from several bars/counters; a single shared tab isn’t practical.
POS performance: Transactions are closed off one-by-one, keeping terminals responsive and avoiding large, unwieldy open tabs.
Spend control: A maximum spend (the pre-paid value) is tagged to the account so the remaining balance is always clear at the point of sale.
Create/locate the booking account and tag the Maximum Spend to match the pre-paid amount (£X).
Tender each sale to the account as normal; the system decrements the remaining balance after every transaction.
Real-time balance checks warn users if a transaction would exceed the remaining allowance, prompting manager approval or an alternative tender.
Mid-session adjustments: If the customer increases their budget, authorised users can update the Maximum Spend safely, with an audit trail.
Permissions: Limit who can set/adjust maximum spend and who can override spend limits.
Auditing: All adjustments and tenders are recorded against the booking account.
End-of-event reconciliation: Use the account summary to confirm total spend vs. pre-payment and settle any balance or refund as required.
Current Workaround:
Some teams monitor spend via the X Report. This approach is not recommended: it is manual, open to human error, and does not enforce the spend limit at the point of sale. Use Payments on Account with a tagged Maximum Spend for secure, real-time control.
