EFRIS day to day
Once it is set up, you do not press anything. This page is what to expect, and where to look when something needs attention.
When you sell
| You do | Filed as | Customer gets |
|---|---|---|
| Issue an invoice | fiscal invoice (or receipt — see below) | fiscal number on the invoice |
| Sell at the till | fiscal receipt | FDN and antifake code on the printed receipt |
A counter sale is filed as a receipt because that is what it is. Filing every till sale as an invoice would misstate what the business does.
Invoice or receipt?
Decided by whether you are registered for VAT:
- VAT registered → invoices go as tax invoices
- Not VAT registered → everything goes as a receipt, because a taxpayer without VAT cannot issue a tax invoice
Set this in Settings → Business. Getting it wrong is refused by URA rather than filed incorrectly.
A bad connection never stops a sale
Fiscalising happens after the sale is recorded and cannot undo it.
If URA is unreachable, the sale still goes through and the receipt prints "Not yet fiscalised with URA" rather than a number it does not have. The sale waits in the queue.
This is deliberate. Refusing a sale because a tax authority's server is down is not a trade any shop would accept, and it is not the customer's problem.
Pausing the till
Settings → EFRIS → Filing at the till → Pause
There are real reasons to stop sending for a while: URA is down, you are training staff on the till, or a certificate is being replaced. Pausing leaves your device, keys and catalogue registration exactly as they are, and invoices are unaffected — the two are paused separately.
Pausing stops sending, not recording
A sale rung up while paused is still on your books and still in the queue, exactly as when URA is unreachable. The receipt prints "URA filing is paused" rather than a fiscal number it does not have.
A business registered for EFRIS is required to file its sales. The queue is what lets you do that when you resume — press Try again and everything that waited goes.
The pause is recorded with the time and who made it, and the page says so while it is on.
The queue
Settings → EFRIS shows everything not yet filed.
| Status | Means | What to do |
|---|---|---|
| failed | URA refused, or was unreachable | Try again |
| blocked | The request could not be built | Fix the cause, then try again |
| paused | Filing is off for that channel | Resume, then try again |
paused and failed are kept apart deliberately: one is a decision somebody made, the other is a fault. Conflating them would send you looking for a problem that is not there.
Try again rebuilds invoices from scratch, so a commodity code you have since set is picked up. A till receipt is resent as it was recorded — it keeps no line rows to rebuild from.
Nothing is ever marked filed without URA's number
There is no optimistic tick and no invented reference. If the queue says a sale has not been filed, it has not been filed.
What your customer sees
A fiscalised document carries URA's fiscal number (FDN) and an antifake code. Anyone can check it against URA directly:
EFRIS portal → Fiscal Document Validation — enter the fiscal document number and URA confirms what it holds.
That is the point of the whole exercise: the customer can verify the document without taking your word for it.
Keeping the catalogue current
Two things happen per product, and both are one-off:
- A commodity code — URA's classification of what it is
- Registration — putting your version of it in URA's goods list
A new product needs both before it can be sold on a fiscal document. The readiness list on the EFRIS page counts them, and Register with URA sends anything outstanding.
Do this before the selling day, not during it
A till receipt cannot be rebuilt later. A product sold before it was registered stays unfiled until you raise the sale again.
Your device certificate expires
Certificates are usually issued for a year. Smart Business Book shows the expiry on the EFRIS page and warns thirty days out.
When it lapses, fiscalising stops — and the refusal reads like a credential problem rather than an expiry. Generate a new keypair, upload it, and register the new thumbprint, exactly as in Getting ready at URA.
What is not automated yet
Being straight about the edges:
| Credit notes | Not implemented. A refund or cancellation is not filed with URA — handle it in the EFRIS portal |
| Returns at the till | Same: the sale is reversed in your books, not at URA |
| Batch upload | Sales are filed one at a time. Fine at any volume a shop reaches, but not a bulk import |
| Excise duty | Not handled. Businesses selling excisable goods need more than this |
| Stock quantities | EFRIS can track stock; Smart Business Book does not send it |
The desktop till behaves the same way
The Windows till prints its own receipts, so it is told the same thing: whether EFRIS is on, whether the till is paused, and what URA said about each sale.
An offline sale prints before it can possibly have a fiscal number — there was no connection to get one. The receipt says so, the sale syncs when the connection returns, and the fiscal number is filed against it then. The till keeps what URA gave back, so a reprint carries the number the first copy could not.
If any of these matter to you, say so — they are known gaps, not oversights.
Related
- When URA refuses — every error and its real cause
- Commodity codes — coding the catalogue
- Going live — moving off the test environment