# Connect retail receipts, POS fiscalization and ERP invoicing Treat a sale, a receipt, an invoice, a fiscal record and a card settlement as related records with different purposes. An ERP integration fails when it imports each as a new sale or assumes one successful message completes every obligation. Use the [retail document and store-close worksheet](#template) to define the flow for each selling channel. The guide's controls are operating recommendations. A local specialist determines the applicable fiscalization, receipt, invoice and reporting rules. ## Define the store and channel population List physical tills, web shops, mobile terminals, marketplace feeds and specialist billing systems. Record the legal seller, store location, transaction currency and source of the commercial sale. Separate payment devices from systems that issue or record the required tax document. Assign store operations to daily transaction completion, finance to sales accounting, tax to document and reporting scope, treasury to settlement and integration to message capture. A certified device or compliant billing component does not decide the complete process across these systems. Classify each transaction as the relevant receipt, simplified invoice, full invoice or other local document. Identify whether a record goes to an authority before issue, after issue or through a periodic report. Maintain separate completion evidence for customer delivery and authority processing. [ZATCA](https://erplocalization.com/glossary/global/#global-zatca) distinguishes standard and simplified tax invoices and its generation and integration phases. Those categories support different workflows; the invoice's retail origin alone does not determine the full treatment. [ZATCA, what is e-invoicing](https://zatca.gov.sa/en/E-Invoicing/Introduction/Pages/What-is-e-invoicing.aspx). ## Preserve one sale identity across documents Give each sale a stable source identifier. Connect receipt number, fiscal record, order, payment authorization and ERP posting to it. Keep a later customer invoice linked to that original sale rather than allowing the invoice interface to create revenue again. Ask tax how the local regime handles a later request for a full invoice. Record the permitted references, adjustments and reporting treatment. A later invoice may need additional information or a separate reporting action while representing the same underlying supply. Do not solve duplicate accounting by suppressing a required fiscal document. Preserve every required output and design the ledger import to recognize the common sale. Test a later invoice at the same till, through customer service and after a period has closed. Germany's cash-register guidance addresses receipt and recording-system obligations and the DSFinV-K data interface. Retaining a PDF receipt alone does not establish that the recording-system export is available. [BMF, cash-register law FAQ](https://www.bundesfinanzministerium.de/Content/DE/FAQ/FAQ-steuergerechtigkeit-belegpflicht.html). ## Work a store day with a refund and later invoice Consider a synthetic store day in a fictional currency and a fictional 10% tax regime. The store makes 100 sales, each 100 net plus ten tax, or 110 gross. Gross sales before returns total 11,000, comprising net sales of 10,000 and tax of 1,000. Two of those purchases are returned in full on the same day under the example's approved return procedure. The two linked refund records total 220 gross, comprising 200 net and 20 tax. Net activity for the day is 10,000 minus 200, or 9,800 net. Tax is 1,000 minus 20, or 980. Gross activity is therefore 10,780. Keep the separate amounts visible so operators can check each column. The source set contains 100 original sales and two return records. It does not become 98 original documents, because the original two sales remain in history. One customer also requests a full invoice for an existing 110-gross purchase. Assume the fictional local rules permit a linked invoice without another sale. The invoice is an additional document representation with no additional revenue. If the ERP imports it as another sale, gross activity wrongly rises to 10,890, an overstatement of 110. Suppose the initial receipts consist of 8,800 by card and 2,200 cash. Both 110 refunds go back to cards. Card net takings are 8,580, and cash takings remain 2,200. Together they equal 10,780. The card provider deducts a 100 fee and transfers 8,480. Record the 100 separately under the approved fee and tax treatment. Bank receipt of 8,480 plus fee of 100 reconciles to card net takings of 8,580. The lower payout does not reduce sales to 8,480. ## Reconcile totals without losing transaction detail Build the daily bridge from original sales, returns, discounts and other approved adjustments. Reconcile net, tax and gross by relevant rate and store. Confirm the sequence and identity of records as well as the totals. Where reporting allows aggregation, retain the detail needed to explain the aggregate and corrections. Singapore permits aggregation for specified categories, including POS supplies, under its GST InvoiceNow framework. That does not make aggregation universally available for every country or category. [IRAS, GST InvoiceNow requirement](https://www.iras.gov.sg/taxes/goods-services-tax-%28gst%29/gst-invoicenow-requirement). Keep store-close time, sale time, reporting period and settlement date separate. Card payouts can combine several trading days or arrive after the accounting period ends. Reconcile through a clearing account or another approved method instead of moving sales into the bank date. ## Handle returns and offline stores explicitly For each refund, preserve the original transaction, returned quantity, tax treatment, payment method and authorization. A warehouse return is evidence of stock movement, while a refund confirms cash movement. Neither automatically proves the other completed. If a store loses connectivity, use the approved local fallback for the actual device and regime. Record which documents were issued offline and what later reporting is required. A device's ability to print is not legal evidence that every outage condition is satisfied. After reconnection, query or reconcile the existing records before replaying them. Confirm that locally stored receipts and centrally accepted records represent the same sale. Identify duplicate reporting and missing reporting separately from duplicate ledger posting. ## Recover a failed store close If card settlement agrees but the fiscal export is short, leave the reporting exception open. The store finance owner checks record coverage, integration establishes the missing outcome and tax decides the permitted correction. Do not create a replacement sale solely to make the authority count agree. If a later invoice duplicated revenue, identify the affected import and reverse the duplicate accounting through the controlled process. Preserve any required customer document and its legal status. Fix the common-sale mapping before rerunning the population. - ☐ Every channel has a legal seller and authoritative sale source. - ☐ Receipts, invoices, fiscal records and payments share traceable relationships. - ☐ Later invoices cannot create duplicate revenue. - ☐ Returns preserve original documents and independent stock/cash outcomes. - ☐ Store totals reconcile to tax, clearing accounts and settlements. - ☐ Offline records have a verified fallback and recovery procedure. - ☐ Required device data and exports remain retrievable. Use [invoice reconciliation](https://erplocalization.com/guides/reconcile-e-invoices-erp-tax-return/) for period controls and [outage recovery](https://erplocalization.com/guides/e-invoicing-outage-recovery/) for uncertain submission results. Sources checked 17 October 2026. The German FAQ was available through indexed official text during a direct-access failure. The worked tax and fee assumptions are fictional and do not determine any national treatment. ## Worksheet: Retail document and store-close control Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment. Show the worksheet Use with [the retail guide](https://erplocalization.com/guides/retail-pos-fiscalization-erp/). Complete one record per legal seller, channel and applicable fiscal regime. ### Map the channel - Seller, store, jurisdiction and source systems: ____ - Receipt, invoice, fiscal record and reporting obligations: ____ - Approved later-invoice and return treatment: ____ - Source sale ID and related document identifiers: ____ - Store, finance, tax, treasury and integration owners: ____ ### Reconcile the day - Original sales count and net/tax/gross totals: ____ - Returns, voids and other approved adjustments: ____ - Net sales, tax and gross activity: ____ - Card, cash and other payment totals: ____ - Settlement clearing, fees and bank receipts: ____ - Accepted fiscal/reporting population and open cases: ____ Synthetic check: 100 sales at 110 gross total 11,000. Two returns total 220. Final activity is 9,800 net plus 980 tax, or 10,780 gross. Card net takings of 8,580 plus cash of 2,200 equal 10,780. A card payout of 8,480 plus a fee of 100 reconciles to 8,580. A later linked 110 invoice creates no additional sale under the example's assumptions. ### Test exceptions - Later full invoice retains original sale identity: ____ - Refund retains stock and cash decisions separately: ____ - Offline issuance legal basis and recovery evidence: ____ - Unknown submission query and duplicate prevention: ____ - Required device data and export retrieval: ____ - ☐ Each sale appears in the ledger once. - ☐ Required documents remain present even when they share a sale. - ☐ Settlement differences do not silently change revenue. - ☐ Store and reporting exceptions have named owners. Controller acceptance and date: ____ ## Related on this site - [Country pages](https://erplocalization.com/countries/): key facts with sources - [E-invoicing matrix](https://erplocalization.com/e-invoicing/): country × ERP support - [All guides](https://erplocalization.com/guides/) Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17. Related: [Glossary](https://erplocalization.com/glossary/) – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more). --- Canonical: https://erplocalization.com/guides/retail-pos-fiscalization-erp/ · Last updated: 2026-10-17 · Informational only; not tax, legal or implementation advice. Featured placements are paid or promotional and do not affect the compliance data. Data: CC BY-NC 4.0 (commercial use needs a licence: https://erplocalization.com/data-licence/), attribution "ERP Localization (erplocalization.com)".