Per-ticket or roll-up: how to post sales to SAP Business One

A point of sale that posts to SAP Business One has one decision to make before anything else: does every ticket become an invoice, or does the day?

Per ticket

One A/R Invoice and one Incoming Payment per ticket. SAP holds every sale as its own document, with a drill-back from the invoice to the ticket and from the ticket to the invoice. Returns are credit memos based on the invoice, so the chain is complete. This is what e-invoicing regimes expect: one fiscal document per sale.

The cost is volume. A supermarket with thousands of tickets a day grows the invoice table fast, and SAP’s own reports slow down with it.

Roll-up

One invoice and one payment per company and day, with the lines aggregated by item and tax. The invoice table stays lean. The ticket detail does not disappear: it is written to user tables in SAP and kept in the point-of-sale portal with every event, tender and signature.

The cost is granularity in SAP itself. A return of a rolled-up sale is a credit memo against the day, and an e-invoice per sale has to come from the fiscal plug-in, not from the SAP invoice.

What CertiPOS does

• Per-ticket posting is the default, per company.
• Roll-up is a per-company option: tickets are marked deferred, batched per day, posted as one document with the detail in the @CP_TICKETS and @CP_TICKETLINES tables, and reversed by one credit memo.
• Both modes keep the same evidence: payload, answer, timing and catalogue code on every job; reversals proven live.

How to choose

Choose per ticket unless your volume makes SAP slow. If you must roll up, keep the fiscal foundation per ticket on the register, so the e-invoicing plug-in has what it needs when the regime arrives.