POS Invoice
Pronunciation: PEE-OH-ESS IN-voys
Definition
A POS invoice is an invoice or payment request created from a point-of-sale transaction and linked to a physical-store basket or service interaction. It can support immediate payment, delayed collection, crypto QR presentation, customer account billing, or business purchase documentation. It should remain linked to the register, store, cashier, basket, and any later payment or cancellation. POS Invoice should remain distinct from its payment sessions so late transfers, refunds, credits, and exchange-rate changes do not rewrite the original commercial document.
Overview
A POS invoice is an invoice or payment request created from a point-of-sale transaction and linked to a physical-store basket or service interaction. It can support immediate payment, delayed collection, crypto QR presentation, customer account billing, or business purchase documentation. It should remain linked to the register, store, cashier, basket, and any later payment or cancellation. When implementing POS Invoice alongside Invoice Amount, the invoice should remain distinct from its payment sessions so late transfers, refunds, credits, and exchange-rate changes do not rewrite the original commercial document.
Important risks include duplicate invoices, wrong customer, stale crypto quotes, incorrect tax, cashier manipulation, payment and basket mismatch, and lost receipt evidence.
Systems should preserve POS and invoice IDs, store, terminal, employee, items, tax, amount, currency, payment instructions, attempts, and final receipt.
For POS Invoice, the operational boundary with Invoice Confirmation and Invoice Amount should be explicit. Identifiers for POS Invoice should connect those records without allowing either linked status to overwrite its own state.
Operational controls for POS Invoice should reconcile the requested balance with every accepted payment, fee, conversion, refund, write-off, and credit. When POS Invoice interacts with Invoice Confirmation, the system should distinguish document status from payment status, preserve who changed each field and why, and define how expired instructions, partial payments, excess payments, disputed items, and transactions received after cancellation are handled.
For POS Invoice, the invoice and the payment used to settle it should remain separate records. When POS Invoice interacts with Invoice Confirmation, the invoice defines the commercial obligation, parties, amount, denomination, tax, due date, and revision history; payment records hold quotes, addresses, transaction identifiers, confirmations, fees, refunds, and settlement. In the relationship between POS Invoice and Invoice Amount, keeping these layers separate prevents a late payment, repricing event, or refund from silently changing the document originally issued to the customer.
Key Takeaway
POS invoices connect store baskets with payment obligations and require exact register, employee, tax, payment, status, and receipt linkage.
Sources
- Peppol BIS Billing 3.0 — OpenPeppol (2026-08-01)
- OxaPay API Reference: Generate Invoice — OxaPay (2026-08-01)