Skip to main content
Every fiscal document in Fire goes through two separate acts, at different moments, and each one leaves its own block on the order. Most confusion comes from mixing them up, so this page names them once and every other fiscal page builds on it.

​
The two acts

fiscalRepresentation never says the document was authorized. It holds the numbers printed at the till. The authority’s verdict is fiscal.authority, and the current status is fiscal.status in the fiscal events, lastKnown.fiscal.status in every other event. The three can legitimately disagree for a while.

​
Two ways a document reaches Fire

Both acts happen. The till numbers first through Fire, prints, injects the order, and the provider later reports the verdict through the fiscal callback.
  • data.fiscalRepresentation is populated from the moment the order exists.
  • data.fiscal.authority appears when the callback arrives.
  • fiscal.providerCode is generic.
Other countries can also report through the fiscal callback without numbering first. What matters for a consumer is the same in every case: the verdict is always fiscal.authority, with the same shape, whichever way it came in.

​
The whole cycle

What happens between the callback and the events — which event fires for each outcome, and how every field travels — is in From the callback to the events.

​
Four words for “status”

The same fact is named differently depending on where you read it. They are not interchangeable:

​
Where to go next

From the callback to the events

Which event fires for each callback, and where every field lands.

Fiscal callback

The contract your provider sends.

Numbering from the till

Act 1, step by step, for points of sale and kiosks.

Becoming a fiscal provider

What a provider implements on both acts.