Fiscalisation 2.0 is a technical project that rarely fits under one vendor's roof. Point of sale, ERP and the EDI/Peppol layer are three different domains with different release and certification cycles. That is exactly why Pupilla, Megatrend and REDOK are entering a strategic alliance — so customers can buy the end-to-end solution under a single contract.
This article explains the three roles, how a message travels from the POS terminal to the Tax Authority's CIS service, and the concrete customer benefit of a single SLA across the chain.
Three partners, three layers
Pupilla covers the point-of-sale layer — terminals in retail, hospitality and services. Their software fiscalises a single transaction and issues the customer-facing fiscal receipt.
The Megatrend group runs the ERP layer — from small companies on the Pantheon package to mid- and large-sized organisations on Megatrend ERP and specialised industry editions. The ERP consolidates all POS transactions, runs accounting, payroll, inventory and reporting.
REDOK, part of the Megatrend group with 37+ years of B2B/EDI specialisation, runs the layer that talks to external systems: the EDI network for B2B partners, the Peppol Access Point for European e-invoicing, and the role of information intermediary with the Tax Authority for fiscalisation.
How a message travels through the chain
- POS (Pupilla) issues a receipt → fiscalises it against CIS → returns JIR and ZKI to the terminal.
- At end of shift or in real time, aggregated POS data syncs into the ERP (Megatrend / Pantheon).
- The ERP books the receipt, updates stock and triggers downstream B2B processes (e.g. auto-replenishment to suppliers).
- B2B documents (purchase orders to suppliers, e-invoices to non-retail customers) flow through the REDOK gateway into the EDI or Peppol network.
- For audit purposes, every stage is kept in the REDOK e-archive with a qualified timestamp for 11+ years.
Value of a single contract
The classic model is one quote per layer — three contracts, three SLAs, three support contacts. When something breaks, the customer spends days establishing „whose“ question it is. The Pupilla–Megatrend–REDOK alliance changes that: one contract covers all three layers, one SLA tracks end-to-end resolution time, one dispatcher in support routes the ticket to the right technical team.
For Fiscalisation 2.0 specifically, this means the customer no longer needs to know where the fiscalisation error sits — when reported to Pupilla or Megatrend support, the first triage steps already involve REDOK if the issue turns out to be CIS communication.
Which company sizes should consider this model
The model is especially useful for retail and hospitality with 5+ locations that already carry a mix of POS, ERP and B2B obligations. Smaller companies with a single POS and no B2B traffic usually do fine with one vendor; large retail chains tend to run in-house development — so the mid-market is the sweet spot.
If you run a business in that range and Fiscalisation 2.0 is on your roadmap for the next 6 months, the REDOK team can — in coordination with Pupilla and Megatrend colleagues — prepare a joint assessment. Reach out through the contact form and we will set up a joint call.