Storno and error handling

After invoice generation, modifications may be needed or connection may error.

Storno (invoice cancellation)

When needed

• Customer dispute (amount mismatch)
• Wrong customer data (bad company name)
• Sale cancellation post-invoice

How

1. Bookinda → Sales → sale row → Invoice tab
2. Storno button
3. Confirm
4. Invoice in Billingo becomes invalid (not deleted)
5. Billingo-document-id removed from Bookinda sale record

What "cancel" means

Invoice status is "Invalid." Visible in Billingo (audit trail) but uncountable in books.

New invoice after storno

If cancelled sale needs new invoice:

1. Sale record returns to "no invoice"
2. Auto-invoice ON: new invoice auto-generates
3. Auto-invoice OFF: manual

Common errors

"Auth failed" / "401 Unauthorized"

• API-key invalid or revoked
• Fix: new API-key + Disconnect / Reconnect

"Document block not found"

• Picked block deleted in Billingo
• Fix: Connect → Edit → new block pick

"Invalid customer data"

• Customer company data incomplete (name yes, tax ID no)
• Fix: complete on customer profile

"Currency / VAT mismatch"

• Config mismatch (e.g., trying EUR but HUF tenant)
• Fix: Connect → Edit → currency

"Network error" / "Timeout"

• Billingo API temporarily unreachable
• Fix: wait 5 min, auto-retry

"NAV Online error"

• NAV server unreachable or invoice XML wrong
• Fix: "Resend to NAV" in Billingo UI

Audit trail

Every invoice operation logged:

• Bookinda side: Sale → Invoice tab → "History"
• Billingo side: Invoice → "Activity log"

Re-connect

If API-key invalidated:

1. Billingo: generate new API-key
2. Bookinda: Connect → Disconnect
3. Bookinda: Connect → paste new API-key
4. Test → Save

Best-practice check

Weekly

• Connect → Billingo status ACTIVE?
• All new PAID sales have invoice?

Monthly

• Billingo audit: Bookinda invoices match?
• Storno count normal (1-2% normal, 5%+ issue)?

Quarterly

• API-key rotation (security best-practice)

When to use it

Scenario 1, customer dispute Customer complains: "Different amount." Storno → new invoice with correct data.

Scenario 2, customer company data later Customer says later: "With company data." Storno → add company data on profile → new invoice.

Scenario 3, refund post-invoice Customer regrets, refund. Storno + refund transaction.

Scenario 4, API-key lost You accidentally made public. New generation + reconnect.

Tips

• Storno is permanent, don't do unnecessarily.
• Customer company data added later requires new invoice.
• API-key rotation every 6-12 months for security.
• Connect status checked weekly, no ERROR connections.

Related articles

• Billingo overview
• Setup
• Auto-invoice