An invoice with a QR code a phone can read

What the document carries

Helm builds the invoice in the structure the Saudi e-invoicing rules describe, and stamps three things onto it.

• A QR code that a phone camera reads. Helm encodes it with its own encoder, and an independent decoder proves it scannable on every build.
• A hash chain. Each invoice carries a counter that rises by exactly one, and the hash of the invoice accepted before it.
• A digital signature over the canonical document, with the workspace certificate.

A draft is editable, and issuing is the point of no return

An invoice stays a draft while you correct it.

Issuing stamps the QR code, the hash and the chain position, posts the ledger entry, and cannot be undone.

A void produces a credit note. It never rewrites the document that was issued.

Getting paid

Every issued invoice gets a hosted page. The client opens the link and pays by card, with no login.

A client can also have a portal link that lists their own invoices, and only their own.

A card payment settles once. A repeated notification from the payment provider cannot post the money twice.

Answers

Does Helm submit my invoices to the authority?

A person issues each invoice, and the invoice carries the QR code, the chain and the signature. Helm never files anything on your behalf without a person.

What happens to the counter if an invoice is rejected?

A rejected submission keeps the counter value it consumed, and it never becomes the predecessor of the next document. The chain stays honest.

Can I edit an invoice after I issue it?

No. Issuing is irreversible by design. You void it and issue a credit note, which is what an audit trail requires.

Read next