Connect Your POS to E-invoicing: A Step-by-Step Guide for F&B Venues
Updated:
Connecting a POS to e-invoicing means every completed payment automatically issues an invoice, sends it to the customer and passes the data on as required. There are three ways: built-in integration, an API connection, or file export and import. Choose by venue size and technical capacity.
Three ways to integrate a POS with e-invoicing
The first two keep the invoice tied to the transaction at the moment of payment; the third drifts easily and slows the rush.
| Method | How it works | Best for |
|---|---|---|
| Built-in integration | The POS issues the invoice at the checkout screen without leaving the system | Venues that want the fewest steps, and multi-branch groups |
| API connection | The POS calls the invoice provider's API after each transaction | Venues with a technical team or their own invoice provider |
| File export and import | Export transactions from the POS and import them into invoicing software | Very small venues with few invoices who accept manual steps |
How data flows from payment to the tax authority
1. Close the bill at the POS
The cashier completes payment; the transaction carries items, discounts and payment method.
2. Issue the invoice
The system creates an invoice tied to that transaction and signs it with the venue's digital certificate.
3. Send to the customer
The customer receives it by the QR code on the receipt, by email or by phone number.
4. Pass the data on
Invoice data is transmitted to the tax authority in the form that applies to the venue's invoice type.
What to configure
In OneXEOS these details are entered once in the invoice settings of the Finance and Invoicing app, and the checkout screen then reuses them for every branch.
- The venue's tax code and legal entity details (name, address).
- The invoice symbol and form number from your e-invoice registration.
- A valid digital certificate used to sign invoices.
- Connection details for the invoice provider (account, access key) if you use an API.
- The rule for when to issue: on customer request or for every order.
Common errors and how to handle them
| Situation | What to do |
|---|---|
| Network drops at payment | Record the transaction in the POS; issue and transmit the invoice as soon as the connection returns, without falling back to handwritten orders |
| Wrong buyer tax code | Check details before issuing; if already issued, cancel, replace or adjust as the rules allow |
| Invoice must be cancelled or adjusted | State the reason, use the correct type of operation and keep the record |
| Digital certificate expires | Renew before the expiry date; track the date in the configuration |
Multi-branch groups, rollout time and cost
For a group, enter the invoice details at company level and apply them to each branch instead of configuring every counter; test each branch with one trial order.
Rollout time depends on the invoice registration and the number of points of sale; run a full trial shift before going live. On cost, invoice fees are usually charged per invoice issued, so estimate monthly bills before choosing a plan.
- Tax code, symbol, form number and a valid digital certificate are in place.
- Every sales channel runs through the POS.
- A sample invoice has been issued, cancelled and adjusted.
- Cashiers know what to do when the network drops.
- Shift-close revenue has been reconciled between the POS and the invoices.


