Skip to main content
Save 30% on your first year

Governments

Digital receipt mandates that reach the citizen

Your mandate already captures the fullest record of household spending a state has held, yet almost none of it reaches the person who paid. Smartbills delivers it back.

Smartbills returns the fiscal record to the citizen's wallet, shows households their own spending and gives the statistics office anonymized totals.

Compliance the citizen can check for themselves

A fiscalization regime is designed so the state can see the merchant, and it rarely gives anything back to the person who paid. Here the citizen can verify any receipt against the authority’s record, report a sale that never happened and see what a year of consumption tax actually cost them.

  • Citizen-side verification against the authority’s own record
  • Consumption tax itemized and totalled for the person who paid it
  • Anonymized price series at full merchant coverage

A household that can finally see its own money

Financial literacy programs teach principles to people who can’t see their own numbers. This works the other way round: an itemized, categorized record of what a household actually spent, produced as a by-product of a mandate that already exists.

  • Spending by category across the year, line by line
  • Recurring charges surfaced, including the unused subscription
  • Nothing is sold back to the citizen, and no advice is pushed

The households with the least slack gain the most

A medical or childcare credit goes unclaimed because nobody kept the receipt for a year, and the people who lose out are the ones most likely to be moving house or working two jobs. A fridge that dies at fourteen months is an inconvenience in one household and a crisis in another.

Data sovereignty built into the architecture

None of the outcomes above require the administration to hold a purchase history. That comes from how the system is built, which a contract clause on its own could never guarantee. The administration remains the system of record, and Smartbills is a delivery and verification layer above it.

The gap today

The citizen's side of the mandate starts at checkout.

Our mandate is satisfied at the point of sale, which is exactly where the citizen’s side of it should begin.

The fiscal record the administration receives reaches the citizen’s wallet within seconds, in the national format.

We have to buy demand for receipts with a lottery or a single-purpose app, and interest fades once the prize does.

Citizens ask for a receipt that carries a warranty clock, a return window and a running tax total for the year, and no prize fund is needed to get them asking.

The richest consumption data the state holds is used once, for compliance, and then sits unused.

The statistics office receives anonymized price, category and coverage series, and no purchase history ever leaves the citizen’s wallet.

Integrations

Works with the tools you already use.

Your accounting software, bank feeds and card program, with data syncing in both directions.

See all integrations
  • QuickBooks
  • Xero
  • Sage
  • FreshBooks
  • Wave
  • MYOB
  • Zoho Books
  • NetSuite
  • SAP
  • Oracle
  • Dynamics 365
  • Square
  • Shopify
  • Clover
  • Toast
  • Lightspeed
  • WooCommerce
  • Stripe
  • PayPal
  • Adyen
  • Wise
  • Plaid
  • Chase
  • Bank of America
  • Wells Fargo
  • RBC
  • TD
  • BMO
  • Scotiabank
  • Desjardins
  • Brex
  • Ramp
  • Float
  • Mercury
  • Gusto
  • ADP
  • Deel
  • Rippling
  • Google Drive
  • Dropbox
  • OneDrive
  • Box
  • Gmail
  • Outlook
  • Google Analytics
  • Snowflake
  • Looker
  • Databricks
  • Google Cloud
  • Metabase
  • Slack
  • Microsoft Teams
  • Notion
  • Zapier
  • Airtable
  • Salesforce
  • HubSpot

FAQ

Frequently asked questions

What people ask us before they sign up.

No. Smartbills doesn’t replace the fiscal device, the certified point-of-sale software or the platform you already run, and the mandate’s chain of custody stays exactly as it is. It is the citizen-facing layer that sits above an existing fiscalization regime.

Look at what each party ends up holding. The citizen holds their own itemized record and can delete it. The administration holds what the mandate already gives it, plus counts of receipts delivered, verified and reported missing. Nobody gains a per-person purchase history they didn’t already have, because we don’t build the join that would produce one.

Two models cover almost all of them. The first is real-time B2C fiscalization, where each receipt carries a verification code the citizen can check, as with Croatia’s Fiskalizacija. The second is structured e-invoicing on EN 16931 with a national CIUS, which is where the EU is heading under ViDA and where Portugal, Italy and Poland already are.

Yes, alongside what it already collects. Statistical agencies have built consumer price indices on retail scanner data for two decades, but coverage has always been the weak point: independent retailers, small formats and rural areas are thin or missing. A fiscalization mandate is the opposite, because every registered merchant is in it by law. The aggregation thresholds must be set by the statistics office itself.

In most cases, nothing new. Merchants on a point-of-sale platform Smartbills already connects to start sending receipts as soon as the program is switched on. For the others, the fiscal device already produces the record the mandate requires, and that output is what we ingest.

In your jurisdiction, on infrastructure you approve, under a data-processing agreement written against your own framework. It’s usually the first question a ministry asks, and it should be.

No, and the architecture is what keeps that answer true over time. What flows back is aggregate participation and compliance data: how many receipts reached a wallet, how many were verified, and where missing fiscalization was reported. Citizen-level data stays with the citizen, and any access to it is consent-based, scoped and logged.

It can, but it doesn’t have to. A lottery pays for demand with a prize fund, while a wallet earns the same demand by making the receipt useful at tax time too. Where a lottery already runs, the wallet is the obvious place to hold the entries.

Nothing is taken away from them. Paper, and whatever channels the mandate already provides, carry on exactly as before, and no entitlement, rebate or claim may depend on having a wallet. A program built the other way round would shut out the citizens least able to absorb it.

Merchants and platforms pay Smartbills to deliver receipts, the same model that runs outside any government program. The citizen side is free, and it isn’t funded by advertising against citizen data or by selling that data. A public deployment is a paid integration covering the ingestion mapping, the in-jurisdiction infrastructure and the reporting the administration needs.

With a bounded pilot in one region or one merchant category, measured on receipts delivered, receipts verified and wallet retention (installs tell you very little). It’s the honest way to learn what participation looks like in your market before either side commits to a national rollout.

Get started

The other half of your receipt mandate

Tell us which regime you run and we’ll show you what its citizen side could look like.