Creating & sending invoices

ByteBill can create an invoice and transmit it over the PEPPOL network to another business.

Invoice creation is available only when the active organisation is connected over PEPPOL — see Connect to PEPPOL.

Opening the New Invoice screen

The entry point is a + button, on either:

• the Sent tab, or
• the empty home screen, when you have no invoices yet.

The + is hidden on the Received tab once you have invoices, and hidden entirely for organisations that aren't on PEPPOL.

1. Choose the customer

Pick who you're invoicing. To add someone, tap + next to Customer and fill in:

• Name
• PEPPOL id — for Norway this is 0192:<org number>, e.g. 0192:929347900
• Address
• Whether they are VAT-exempt

You can edit or delete customers from the same picker. See Customers and products.

2. Dates and currency

Set the invoice date and the due date. Currency is set automatically from your country — Norway gives NOK, the UAE gives AED.

3. Add invoice lines

One line per item or service. For each line:

• Product — tap + to create one (name, unit of measure, unit price, description)
• Units — the quantity. Unit price is pre-filled from the product and can be overridden on the line
• Unit of measure — from the list (Unit/each, Hour, Kilogram, …)
• Tax rate — see VAT on invoices

The net amount and tax are calculated for you — unit price × units, plus tax, rounded to two decimals. Running totals appear at the bottom.

4. Save draft, or send

Save draft keeps it for later. A draft has no invoice number yet.

Send issues it:

1. Review the customer, lines and totals.
2. Tap Send.
3. ByteBill assigns the next invoice number, builds the PEPPOL invoice and transmits it.
4. On success you see the number and the status sent, and the invoice appears in your Sent tab.

Invoice numbering

Invoice numbers are sequential with no gaps for your organisation — a legal requirement, and something ByteBill handles rather than trusting you to.

A number is only consumed when a send succeeds. A failed send never burns a number, so you won't end up explaining a hole in the sequence to anyone.

If a send fails

The app shows the reason. The two most common are an invalid unit of measure and a customer PEPPOL id that isn't in the 0192:<org number> shape. Fix the flagged field and send again. See Troubleshooting.