Skip to content

ByteBill documentation

Can’t find it? Ask support or watch a walkthrough.

Troubleshooting

The things that commonly go wrong, what each message means, and how to fix it.

On this page

Signing in

The SMS code never arrives. Use Resend code. Check the number is in international format with the country code (+47…). If it still doesn't arrive, your operator may be filtering it — tell us the number and roughly when you tried.

I've lost the phone with that number. Your number is your identity in ByteBill, so this needs us. Contact support — we'll verify you another way.

Invoices not appearing

A supplier says they sent it, but it's not here. Check, in order:

  1. The right organisation is active — the switcher is in the header.
  2. Your organisation is actually connected over PEPPOL — see Connect to PEPPOL.
  3. The supplier sent it to the right address. They need your PEPPOL id, 0192:<org number>.
  4. It was sent after you connected. Nothing sent before you connected can be recovered.

An invoice I just sent isn't in Sent. Pull to refresh, or reopen the app — the index updates a moment after sending.

Sending an invoice

The + button isn't there. Invoice creation only exists for organisations connected over PEPPOL — sending needs a PEPPOL address for the invoice to come from. Check the active organisation is connected; see Connect to PEPPOL.

The + is also hidden on the Received tab once you have invoices. Look on Sent.

The send failed with an error about the unit of measure. Unit of measure comes from a standard code list the network validates. Pick one from the list rather than typing your own.

The send failed with an error about the customer's PEPPOL id. It must look like 0192: followed by the nine-digit organisation number, no spaces.

I can't charge VAT. Your organisation isn't recorded as VAT-registered. If it should be, add your VAT number (NO999999999MVA) in the seller/VAT section. See VAT on your invoices.

Did the failed send use up an invoice number? No. Numbers are only consumed on success — a failure never leaves a gap.

Connections

A connection is stuck on "Setting up…". It usually goes active within a minute or two. Reopen Connections to refresh. If it stays that way, tell us.

Accounting

A voucher is on the wrong account. Confirmed vouchers are corrected by reversing and reposting rather than editing, so the audit trail stays intact. Post the correction — the original stays visible, as it should.

My "You owe" total looks wrong. The usual cause is a paid receipt tagged as an unpaid bill. See Capturing receipts and bills.

A return won't validate. The message names the problem — usually a voucher missing a VAT code or an employee record missing an A-melding field. Fix it in your books and prepare the return again.

Still stuck?

Send us a message. Include the organisation number, roughly when it happened, and the exact wording of any error. The app version from Preferences → About helps too.

Never send us passwords, PINs, one-time codes or API tokens — we don't need them, and we'll never ask.

Still stuck? Send us a message — or email support@bytebill.no.