FISCAL COMPLIANCE

Fiscal compliance is built into EVA, not bolted on

Fiscalization, e-invoicing and digital tax reporting are part of the same platform that processes your transactions. Across every channel, from purchase to tax authority reporting, everything stays in one system. No jumping between systems or worrying about data getting lost.

Fiscalization, E-Invoicing and Digital Tax Reporting built into EVA

Over 45 entity types exported to your data lake. Orders, payments, loyalty, surveys, stock: everything EVA knows about your retail operation, in your infrastructure.

Three types, one record.  Fiscalization, e-invoicing and digital tax reporting all work from the same transaction data, without having to connect separate systems.

Always up to date. Regulatory changes are handled at the platform level, so retailers don’t need to manage separate compliance projects for every market.

Supporting your global footprint

EVA is ready for the world’s most important retail markets

EVA brings fiscalization, AML and transaction compliance into the same platform that powers your retail operations. From Europe and APAC to the Americas and Africa, local requirements are built into the transaction flow, so retailers can stay compliant without adding complexity for stores or customers.

Europe

AML checks are built into every in-store and online transaction, with configurable thresholds per country and guided staff workflows directly in the POS. This keeps local requirements consistent across every retail channel.

Europe

North & South America

Cash transaction thresholds and suspicious activity workflows support retail operations across North and South America. Requirements can be configured per market, keeping compliance embedded in everyday transactions.

North & South America

Asia Pacific

EVA covers key retail markets across the region, with jurisdiction-specific threshold configuration and compliant transaction logging. Local rules are handled within the transaction flow, without adding operational complexity.

Asia Pacific

Platform-native compliance

The fiscal process runs where the transaction runs

Most unified commerce platforms are built to process transactions. Fiscal compliance is often handled by third-party systems that sit outside, receiving transaction data, applying rules, and returning a result. That separation creates handoffs and gaps in context that are hard to close.

EVA works differently. Fiscal logic lives in the same platform as the basket, pricing, promotions, fulfilment and customer data. When the transaction changes, the fiscal record changes with it: they are the same thing.

The Unified Commerce difference

From checkout to tax authority, one unbroken chain

Person looking at iPhone

Endless Aisle

Sell here, ship anywhere. A Dutch store sells a product shipped from Germany to Belgium. EVA keeps the correct fiscal jurisdiction, VAT treatment and invoice routing connected.

Click & Collect Order

Click & Collect / Ship-from-Store

One order, one record. Online orders can be paid digitally and fulfilled from the nearest store. EVA keeps order, fulfilment and fiscal context connected.

Person receiving package

Cross-Border Fulfilment

Records follow the goods. When goods cross borders, EVA keeps origin, destination and fiscal movement connected in one record.

Tax rules

Open Baskets & Tax Holidays

Tax rules stay connected. When tax rules change during checkout, EVA keeps the applicable rate, transaction history and fiscal record connected.

Two people looking at EVA Mobile POS

Offline POS

Compliance works offline. Transactions can still be recorded and fiscally signed when connectivity drops. They sync automatically once the connection returns.

Person looking into a store

Promotions & Discounts

Discounts stay on record. Loyalty rewards, bundles and promotions remain part of the transaction, including the discount reason and resulting tax base.

Two people looking at EVA Mobile POS

Why Built-in Matters

EVA sees the transaction. EVA already knows the customer, fulfilment, route, discounts and tax status. Compliance is applied to the complete transaction, not a subset of data.

Three types of fiscal compliance

Fiscalization, E-Invoicing and Digital Tax Reporting

Fiscalization, e-invoicing and tax reporting each have different requirements. EVA handles all three from the same transaction record, within the same platform and without passing data between separate compliance systems.

Fiscalization

POS-level fiscal compliance. Country-specific fiscal rules, fiscal certificates and certified fiscal hardware requirements are handled as part of the transaction at the point of sale.

Fiscalization

E-Invoicing

Online fiscal compliance. Structured B2B and B2C invoices are generated from the same transaction data and routed through the required local network, without creating a separate fiscal process.

E-Invoicing

Digital Tax Reporting

Aggregate reporting fiscal compliance. Monthly or periodic submissions of all transactions to the tax authority are generated directly from EVA's unified data model.

Digital Tax Reporting

Global Reach

Built for the markets where compliance is hardest

Retail expansion rarely goes to easy markets first. The markets retailers most want to enter: France, Italy, Portugal, Poland, Romania, Hungary, Singapore and others, are precisely the ones with the most demanding fiscal requirements: mandatory real-time reporting, certified hardware, e-invoicing clearance, and periodic audit submissions.

EVA covers fiscal compliance across Europe, the Middle East, Americas, APAC, and Africa. For each market, fiscalization, e-invoicing and digital tax reporting are handled from one platform. When regulations change, the update is deployed centrally. No compliance project per retailer, no per-market implementation.

Unified commerce means compliance follows the entire transaction. From the first basket interaction to fulfilment, payment and return, EVA keeps the fiscal context connected.

EVA POS

Ready for every regulation

One fiscal platform for every local requirement.

EVA operates across Europe, APAC, the Americas, the Middle East and Africa, with particular depth in the markets known for demanding fiscal regimes: France, Italy, Portugal, Poland, Romania, Hungary, Singapore, and beyond. These are not markets where a generic compliance layer is enough.
Fiscal Setup
Certified fiscal hardware

The right fiscal setup for every market

Many markets require certified POS hardware, from dedicated fiscal printers and security modules to RT devices. EVA integrates the required hardware for each market and manages the relevant certification requirements as part of the platform.

Active in markets including Germany, Italy, France, Romania, Hungary, Poland and more.

Administration on Macbook
Real-time e-invoicing clearance

Invoices cleared as they happen

Several markets require B2B and increasingly B2C invoices to be cleared by the tax authority in real time. EVA generates compliant invoices and routes them through the correct national clearance network for each jurisdiction.

Active in markets including Italy, Poland, Romania, Hungary, Singapore and more.

Woman holding coffee
Periodic audit reporting

Fiscal reporting without reconciliation

Many markets require retailers to submit structured audit files of their transactions on a monthly or quarterly basis. EVA generates reports such as SAF-T and JPK directly from the transaction data model, without a separate export or reconciliation step.

Active in markets including Portugal, Poland, France, Norway, Austria and more.

Anti-Money Laundering woven into every transaction

EVA’s Anti Money Laundering module is built directly into the transaction engine. Suspicious thresholds are evaluated at the moment of sale, triggering a guided staff workflow right away. Everything happens within the same transaction flow, without separate systems, post-processing, or review queues.

Detection

Configurable cash and transaction thresholds per country. Automatic flagging when a customer or transaction crosses the limit, evaluated in real time.

Guided staff workflow

A step-by-step validation flow is triggered directly in the POS. Store staff are guided through the required checks without a separate AML system, paper forms, or extra training.

Full audit trail

Every flagged transaction, staff action, and override is logged, timestamped, and exportable for regulatory review. The record lives in the same data model as the transaction.

FAQ

Questions about Fiscalization in EVA

What is fiscalization, and how is it different from e-invoicing?

Fiscalization is POS-level fiscal compliance: the legal requirement to record, sign, and certify every sale at the moment it happens, often involving certified hardware (like Germany's TSE or Italy's Registratore Telematico). E-invoicing is the structured digital exchange of invoice documents between businesses or with government, via networks like Peppol or country-specific portals like Italy's SDI or Poland's KSeF. The third type, digital tax reporting, is the periodic aggregated submission of all transactions to the tax authority (SAF-T, JPK7M, and others). EVA handles all three from the same transaction record, without routing data through an external system for any of them.

Does EVA integrate with certified fiscal partners like Fiskaly or Pagero?

Yes. Certain countries require a certified fiscal service provider as part of the fiscal compliance chain. Germany's KassenSichV mandates a certified TSE, for which EVA integrates with Fiskaly. E-invoicing in Romania and Hungary is handled through Pagero. EVA manages these partner integrations centrally as part of the platform, so retailers do not need to source, contract, or maintain a separate fiscal integration per market. When a certified solution is updated or a new mandate is introduced, the change is deployed at the platform level, not as a per-customer implementation project.

How does EVA handle compliance for cross-channel scenarios like endless aisle or click & collect?

EVA's compliance is built into the transaction engine itself, not connected to it. A middleware tool like Avalara or Vertex receives a tax calculation request and returns a result. It does not know whether the transaction is an endless aisle order, a click & collect, or a ship-from-store. It cannot see the basket history. EVA does, because the compliance layer is inside the same platform that processes the transaction. The correct fiscal jurisdiction, invoice type, and reporting format are determined automatically, based on the full transaction context: fulfilment channel, warehouse location, delivery country, and customer type.

What happens with an open basket during a tax holiday?

An open basket created before a tax holiday, completed during it, must be handled correctly, and the other way around too. EVA registers the exact state of the basket at creation time and at completion time, records the applicable tax rate at each moment, documents why any delta occurred (including tax holiday triggers), and produces a fiscal record that satisfies audit requirements. This is only possible because EVA holds the full basket lifecycle. A middleware tool that receives a calculation request at checkout cannot see what the basket looked like when it was opened.

How does EVA stay current with changing fiscal regulations?

EVA maintains a dedicated compliance team that monitors regulatory changes across all supported markets. When Poland extends its KSeF mandate, Spain rolls out VeriFactu nationally, or Romania updates its eFactura schema, the change is managed centrally, not per customer. EVA integrates with certified fiscal solutions per country (such as Fiskaly for Germany, KSeF for Poland, or SDI for Italy) and keeps those integrations up to date as mandates evolve. For retailers, a new requirement is handled at the platform level, not as a customer-side implementation project.

What is SAF-T and which countries require it?

SAF-T (Standard Audit File for Tax) is a structured XML export of all accounting transactions, submitted to the tax authority on a periodic basis (monthly, quarterly, or on demand). Countries requiring SAF-T include Portugal (SAF-T PT), Poland (JPK, Poland's SAF-T variant), Norway (SAF-T Financial), Austria, Luxembourg, and others. EVA generates SAF-T files directly from the transaction data model, without a separate export or reconciliation step. The JPK7M (Poland's monthly VAT return) is also generated from the same data. No aggregation, no mapping, no manual intervention.