The invoice is composed here and issued through Számlázz.hu or Billingo: NAV reporting is theirs. Gapless numbering, a storno as a second document, proforma in its own series, VAT exemption codes with their statutory wording, and payments as rows.
The customer accepts or declines on the link, and it shows on the deal at once. A decision is final: an accepted quote cannot go back to draft and be re-sent as though they had agreed twice. One button turns it into an invoice.
A number allocated when the draft becomes a document
Hungarian invoice numbering is gapless, so a draft has no number: it gets one at the moment of issue, from a yearly series, and a failed issue burns nothing. Payments are rows: partial, settled, overdue: the status is their sum.
Storno and proforma
An issued invoice is never "deleted": a storno is created, every line negated, from the same series, linked both ways. Proforma (DB-) and advance (EL-) invoices get their own sequences because they are not tax documents: they are never sent to the provider, and a proforma becomes the real invoice with one button.
VAT codes: AAM, TAM, KBAET, EUFAD37, FAD, HO, ATK, EAM
A zero-rated line on a Hungarian invoice is a claim, not a rate, and the document has to say which one. We use the NAV Online Számla codes, print the statutory wording, and hand both providers the same code. Foreign-currency invoices carry the MNB rate for the fulfilment date, with the VAT shown in forints.
Számlázz.hu and Billingo
Issue with one button, with the PDF stored here so the invoice outlives the provider account. Never issued twice, never from a draft, and after a timeout a reconciliation job finds out what happened on the other side. Without credentials it dry-runs.
Recurring invoices and time
A template plus a schedule, issued unattended: a retainer on the 31st goes on the 28th in February and back to the 31st in March, and one period produces exactly one invoice however often the job runs. Time is logged in minutes, billed grouped by rate, and an hour cannot be billed twice.
Card payment on the invoice
An invoice can carry a payment link through Stripe, Barion or SimplePay; the payment is recorded on the provider's confirmation, never on the browser coming back. The requests match the providers' published documentation.
The back office too
A cash book with numbered vouchers and closed days, delivery notes that move stock when issued, supplier bills, bank statement matching, and an accounting journal with a trial balance that posts itself from issued and paid documents.
How it goes
01
Quote
From products or free lines, with a covering note, on a public link.
02
Acceptance
The customer decides on the link; the decision is final and shows on the deal.
03
Invoice
One button carries the lines, discount and terms over. Issue allocates the number and hands it to the provider.
04
Payment
Payment recorded as a row; the hourly sweep marks what is overdue.
For real invoices, yes: they do the NAV Online Számla reporting, which we do not reimplement. Without a key everything can be tried, and issuing is a dry run.
What if I issued a wrong invoice?
You storno it: a second document with the lines negated, the original becomes cancelled, and the provider's copy is reversed too. Then you issue a new one. An issued invoice cannot be edited.
Can I invoice a customer abroad?
Yes. An EU business under reverse charge (EUFAD37 or KBAET with the statutory wording), a third country with the HO code, in foreign currency at the MNB rate.
Start free, pay for what you need
The core CRM is free for good, with no card; you can try every paid module for 14 days. If it doesn't suit you, export everything and leave: the data stays yours.