Payments & settlement

An invoice being issued and an invoice being paid are two separate events, and your books record both.

Settling an invoice you received

When you pay a supplier invoice, record the payment against it. ByteBill books Dr Accounts payable / Cr Bank — the payable disappears, the bank balance drops, and the invoice moves out of what you owe.

Settling an invoice you sent

When a customer pays you, record it against their invoice. ByteBill books Dr Bank / Cr Accounts receivable.

One-tap "received & paid"

If an invoice arrives and you pay it immediately, you don't have to do the two steps separately. The one-tap action confirms the purchase and creates and confirms the linked payment in a single move — atomically, so you can never end up with one half posted and the other missing.

Settle later

You can also confirm the purchase now and settle it whenever the money actually moves. The invoice sits in Unpaid until you do, which is what you want — that total is only useful if it's true.

Partial payments

A settlement can be for less than the full amount. The remainder stays outstanding on the invoice.

Choosing the bank account

Settlement asks which bank account the money moved through. If you keep more than one, this is what keeps each account's balance meaningful.

Voiding a payment

If you record a payment in error, void it. Because a paid purchase is stored as a linked pair of vouchers, voiding handles both sides together — you can't reverse the payment and leave a phantom purchase behind, or vice versa.