Reverse invoice and error handling
Reverse instead of storno-cancel, common errors, connection restart
Reverse invoice and error handling
Számlázz.hu doesn't support "cancel" (invalidation) operation. Instead it generates a reverse invoice with negative amount that offsets the original.
Reverse invoice
What it means
- Original invoice stays (not deleted, not invalidated)
- New invoice generated with negative amount (e.g., -10,000 HUF)
- Together they net to zero
When needed
- Customer dispute (amount mismatch)
- Wrong customer data
- Sale cancellation post-invoice
How
- Bookinda → Sales → sale row → Invoice tab
- Storno button (UI calls it "Storno" but in Számlázz.hu it's "reverse")
- Confirm
- New reverse invoice generated in Számlázz.hu
- Számlázz.hu-document-id removed from Bookinda sale record
New invoice after reverse
If sale needs new invoice:
- Sale record returns to "no invoice"
- Auto-invoice ON: new invoice auto-generates
- Auto-invoice OFF: manual
Common errors
"Auth failed"
- Token invalid or revoked
- Fix: new Számla Agent token + Disconnect / Reconnect
"Invalid customer data"
- Customer company data incomplete
- Fix: complete on customer profile
"Currency / language not supported"
- Bad config
- Fix: Connect → Edit → currency / language
"Network error" / "Timeout"
- Számlázz.hu API temporarily unreachable
- Fix: wait 5 min, auto-retry
"Tax number invalid"
- Customer tax ID wrong format
- Fix: fix on customer profile (e.g., "12345678-1-23" format)
"NAV Online error"
- NAV server unreachable or XML wrong
- Fix: "Resend to NAV" in Számlázz.hu UI
Audit trail
- Bookinda side: Sale → Invoice tab → "History"
- Számlázz.hu side: Invoice → details
Reverse invoice shows both invoices (original and reverse).
Re-connect
If token invalidated:
- Számlázz.hu: Settings → Számla Agent → new token (or revoke + new)
- Bookinda: Connect → Számlázz.hu → Disconnect
- Bookinda: Connect → Számlázz.hu → paste new token
- Test → Save
Best-practice check
Weekly
- Connect status ACTIVE?
- All new PAID sales have invoice?
Monthly
- Számlázz.hu audit: Bookinda invoices match?
- Reverse count normal (1-2% normal, 5%+ issue)?
Quarterly
- Token rotation possible (security)
Reverse vs Cancel (Számlázz.hu vs Billingo)
| Számlázz.hu | Billingo | |
|---|---|---|
| Operation name | Reverse | Cancel |
| What happens | New negative invoice generated | Original invoice "Invalid" |
| Original retention | Yes, two invoices in series | Original stays but invalid |
| Audit trail | Two invoices visible | One invalidated |
| Bookkeeping treatment | Two items offsetting | One invalid |
Hungarian bookkeeping generally prefers reverse (transparency).
When to use it
Scenario 1, customer dispute Customer complains about amount. Storno button → reverse invoice generated (-10,000 HUF). New invoice with correct amount.
Scenario 2, customer company data later Customer says later: "With company data." Storno → reverse invoice. Add company data on customer profile. New invoice with company data.
Scenario 3, sale cancellation post-invoice Customer regrets, refund. Storno → reverse invoice. Refund transaction in Bookinda finance.
Scenario 4, token lost You accidentally made token public. Revoke + new token in Számlázz.hu. Bookinda reconnect.
Scenario 5, multi-currency dispute Customer asked for EUR but HUF was sent. Storno → reverse. New invoice in EUR via Számlázz.hu UI (manual).
Tips
- Reverse invoice doesn't invalidate original, both visible in audit trail.
- Hungarian bookkeeping prefers this (transparent vs invalidation).
- Adding customer company data later requires new invoice (can't rewrite existing).
- Token rotation every 6-12 months for security.
- Connect status checked weekly, don't leave ERROR connections.
- NAV errors handled at Számlázz.hu level, Bookinda only does generation.