Nuqta

National e-invoicing, in detail

This is the most important thing the software does, and the thing most often broken elsewhere. So here it is in full rather than one line.


What the software actually does

It builds a complete UBL 2.1 document for the invoice, submits it to the Income and Sales Tax Department, and receives the signed code the department returns. The code printed on your invoice is theirs — not one we generate.

14 rules learned by rejection

The department rules are not all written down plainly, and most become known when an invoice comes back rejected. Each of the 14 rules in the software cost a rejection before it was known — and all of them are proven by actual acceptance, not by reading a guide.

The queue waits, it does not drop

When the line goes down, or the department returns a temporary error, the invoice waits in the queue. The queue runs on its own every minute, and backs off further when an outage drags on rather than hammering the service.

And the part that matters: there is no cap on retries. The invoice stays in front of you with its state until it lands — and on the Invoices screen there is a Send button on every invoice that has not landed — for when you do not want to wait for the next round.

The invoice number and identifier are reserved the moment it is issued, not the moment it is sent. Your sequence is intact even if an invoice sits in the queue for hours.

The difference between an invoice you fix and one you lose

There is a large difference between the department rejecting your invoice and the submission failing, and most systems conflate the two.

A rejection carries a named reason from the department — something in the invoice needs a human hand, and the software stops you there. But their server being down, or a cafe wifi portal answering with a page instead of a reply, is a transient failure: it stays in the queue and goes on its own.

Conflating them means one of two things: you chase an invoice with nothing wrong with it, or you forget a rejected one until the department reminds you.

And no false success

The most dangerous thing an invoicing system can do is tell you "fine" when it does not know. In Nuqta the word "accepted" is only written when the department says so. And we never generate a QR code locally under any circumstances — a code of our own making prints a paper that looks official and is not, and that lands you in a problem it does not solve.

What you need before you start

You must be registered with the Income and Sales Tax Department on the national e-invoicing platform, and hold your credentials from them. You enter these once in the settings screen, and there are six:

Once entered, a button tests the connection — press it before your first sale and be sure.

  • Tax number
  • Registered name
  • Income source sequence
  • Client-Id
  • Secret-Key
  • Taxpayer classification