When URA refuses
Every entry here is a refusal we have actually had back from URA, in the order you are likely to meet them. Several say something other than what is wrong, which is the reason this page exists.
Read the queue, not the invoice
The EFRIS page shows everything that has not been filed, with URA's own message and how many attempts it has had. Nothing is ever marked filed without URA's fiscal number, so if the queue says a sale is outstanding, it is.
Setting up
The key exchange fails, everything else passes
✓ Reached URA ✓ Clocks agree ✗ Opened the symmetric keyAlmost always the device public key. Your device carries one marked Default — URA's placeholder — until you upload yours. Everything URA encrypts for the device uses that row, so nothing you hold can open it.
Go to Device Management → Device Public Key Management and check the Public Key ID column. See Getting ready at URA.
It is not usually a wrong key file. If Smart Business Book shows a thumbprint, your key and certificate already agree with each other.
Longitude cannot be empty
Not a network fault, despite reading like one. URA requires longitude and latitude as numbers. Smart Business Book sends 0 when the fields are blank, which URA accepts — if you see this, something has put a non-numeric value in them.
The clock check fails, then passes a minute later
URA's sandbox answers from more than one machine and one of them is minutes ahead. Measured: four calls six seconds apart returned drifts of +4s, +463s, +2s, +1s, against a server whose clock was verified correct.
Smart Business Book re-samples before blaming your clock. If every sample drifts, check NTP on your server — but verify against another source first.
Filing an invoice
No URA commodity code on: <product>
The product has no commodity code, so the line cannot be classified. Set one in Products → URA EFRIS, then press Try again — the request is rebuilt.
See Commodity codes.
Not in URA's goods list: <product>
URA has never heard of the product. A catalogue has to be registered before its items can appear on a fiscal document.
Press Register with URA on the EFRIS page. This is separate from having a commodity code: the code says what the thing is, registration puts your version of it in URA's list under your SKU.
Item does not exist!
The same thing, seen from URA's side — the goods code on the line matches nothing registered. Register the catalogue.
invoiceKind: You have not registered VAT or VAT is not effective
You are not registered for VAT, so you cannot issue a tax invoice. The right document is a receipt, and Smart Business Book files one automatically once VAT registered is off in your business settings.
If you are VAT-registered with URA, turn that on in Settings → Business — otherwise every invoice will go as a receipt.
goodsDetails-->total: Multiply the quantity by the product of the unit price
URA checks the arithmetic itself: total must be exactly quantity × unit price, with two decimals. Smart Business Book computes it from the numbers it sends, so this should not appear — if it does, something has changed on the line after it was raised.
currency: invalid field value!
URA uses its own currency codes, not the ISO letters: UGX is 101. Handled for you; worth knowing if you are reading a raw response.
Partial failure!
An envelope-level message with nothing useful in it. The real reason is per item in the response body. Smart Business Book digs it out and shows that instead — which is how currency: invalid field value! was found.
Duplicates and retries
2001 — invoice already fiscalised
Not an error. URA already holds the document; we simply did not see the reply that said so. Smart Business Book records it as filed rather than retrying, because resubmitting a fiscalised document is the one thing that can create a duplicate at URA.
A sale shows as blocked
Retrying alone will not help — the request cannot be built. Almost always a missing commodity code. Fix the cause, then Try again: an invoice is rebuilt from scratch, so it picks the fix up.
A till receipt cannot be rebuilt
A POS sale keeps no line rows, so what was built at the moment of sale is what gets retried. Code and register your products before you start selling, not after.
Two that look like problems and are not
data is not a multiple of the block length — a compressed reply, not a corrupt key. URA gzips large responses. Handled.
The receipt says "Not yet fiscalised with URA" — the sale went through normally; URA was unreachable. It is in the queue. Press Try again when the connection is back. A sale is never blocked by URA being down.
Still stuck
Every refusal carries URA's own code and message, and the queue keeps them. Quote the code and the reference number to your URA contact — those two are enough for them to find the document.
Related
- Getting ready at URA — the portal side
- EFRIS setup — inside Smart Business Book
- Day to day — the queue and what customers see