Skip to content

How invoices post

With Books on, you keep working with invoices as you always have. Each time you save one, Books writes (posts) the entry it needs. This page shows what each action posts, so you and your bookkeeper know where every amount lands.

Each entry is a journal you can open from Accounting › Journals. See Books reports.

Raising an invoice

An invoice posts on its invoice date:

  • Debit Accounts Receivable with the invoice total, against the customer.
  • Credit each line's account with the line's amount before tax.
  • Credit each tax rate's account with the tax.

A US example: an invoice for a $1,000 repair (Service Revenue) and $200 of parts (Sale of Goods), with 8.25% sales tax.

Account Debit Credit
1200 Accounts Receivable 1,299.00
4100 Service Revenue 1,000.00
4000 Sale of Goods 200.00
2230 Sales Tax 99.00

In South Africa, an invoice for R10,000 of services with 15% VAT:

Account Debit Credit
610 Accounts Receivable 11,500.00
200 Sales 10,000.00
820 VAT 1,500.00

Every line needs an account, as in Xero. A line you didn't pick one for takes the account its Code matches, or its Pricebook item's account. If it still has none, the invoice isn't saved, and you're told which line to fix, for example "INV1234 line 2 (Website hosting) has no account. Pick one for it." This applies to invoices made by automations and recurring invoices too (when your books start, you pick an account for each automation whose lines have no code that names one: see Start your books). A line can't go to a bank account, an archived account, or an account only Books posts to (such as Accounts Receivable or Sales Tax). A combined tax rate splits its tax over each part's account. If tax rounding leaves a cent over, it goes to Rounding, so the entry always balances.

Converting a quote to an invoice posts the invoice, the same way.

Money is never refused because of a missing account. If a customer pays online for a quote or invoice that has a line with no account (an old quote, say), the payment is still recorded and the invoice still marked paid. The line's sale goes to your Suspense account and BaseCloud leaves a note naming the line. Pick an account for the line and save the invoice, and it moves out of Suspense; or move the amount with a manual journal.

Payments

A payment posts on its own, on the date paid, whatever it pays. When you record a payment, or a customer pays online:

Account Debit Credit
Undeposited Funds 1,299.00
Accounts Receivable 1,299.00
  • The whole payment posts, whether it pays one invoice, part of one, several, or none (a prepayment). Money that isn't on an invoice yet is the customer's credit: it stays in Accounts Receivable as a credit balance against them, so their balance there is what they owe less what they've paid ahead.
  • Applying credit posts nothing. Using a customer's credit on an invoice, by itself on a new invoice or with Apply credit, only says which invoice the money was for. It's already in your books.
  • The money goes to Undeposited Funds, money received but not yet matched to a bank line, unless you pick the bank account it was deposited to when you record it. A payment taken through Stripe or Paystack goes to Stripe Clearing or Paystack Clearing instead, when your chart has an account with that name. See Matching a payment to the bank.
  • Correcting a payment (its date or the account it went into) reverses its entry and posts it again. A payment matched to a bank line can't have its date or account changed: unmatch it first.
  • Money in another currency isn't posted. Your books are kept in one currency. A payment received in another currency is kept as the customer's credit, and BaseCloud leaves a note on the client: post a manual journal at the rate you were paid.
  • Removing a payment posts a reversal of its entry, so the invoice is owed again. Mark unpaid does the same when it removes the invoice's one payment.

Matching a payment to the bank

When you reconcile a bank line with the payments in it, they move from Undeposited Funds into the bank, on the date of the bank line:

Account Debit Credit
Business Bank Account 1,299.00
Undeposited Funds 1,299.00

A payout from your payment gateway that's less its fees posts the fee in the same entry. A $1,000.00 batch of Stripe payments paid out as $970.70:

Account Debit Credit
Business Bank Account 970.70
Merchant Fees 29.30
Stripe Clearing (or Undeposited Funds) 1,000.00

Unmatching the line reverses this entry, so the payments are back in Undeposited Funds.

Credit notes

A credit note posts on its own date, the reverse of an invoice:

  • Debit each line's account with the line's amount before tax. A write-off goes to Bad Debts instead.
  • Debit each tax rate's account with the tax.
  • Credit Accounts Receivable with the total, against the customer.

A credit note for $270.63 on the US invoice above (one line of Service Revenue, 8.25% sales tax):

Account Debit Credit
4100 Service Revenue 250.00
2230 Sales Tax 20.63
1200 Accounts Receivable 270.63

The invoice's own entry is never reversed or changed: the sale stays in the month it was invoiced, and the credit comes off in the month of the credit note. Voiding a credit note posts a reversal of its entry.

Refunds

A refund, money you paid back to a customer, posts on its date:

Account Debit Credit
Accounts Receivable 270.63
Undeposited Funds 270.63

It comes out of Undeposited Funds until you match it to the money-out line on your bank statement, which moves it to the bank. A refund of a sale posts the credit note and the refund, both on the same day. A refund you make in Stripe or Paystack is recorded and posted by itself, and the invoice it paid owes that money again until you credit it.

Editing an invoice

Your books are never edited. When you change an invoice's lines, amounts, tax or date, Books:

  1. Posts a reversal of the old entry: every line the other way round, so the two cancel out.
  2. Posts the new entry.

Both stay in your journals, so you can always see what the invoice said before and when it changed. Saving an invoice without changing anything that matters to the books posts nothing.

An invoice with money on it (paid, part paid, or with credit applied) can't be edited. Remove its payments first, or credit it. See What locks a document.

Voiding an invoice

Voiding an invoice posts a reversal of its entry. The invoice no longer adds to Accounts Receivable or your sales, and both entries stay in your journals.

Quotes

Quotes never post. A quote is an offer, not a sale. It posts only once it becomes an invoice.

Invoices that can't change

Books stops changes that would rewrite figures you've already reported:

The invoice is… Paid Edit Void
Dated on or before your lock date Yes, with a date after the lock date No No
Dated before your start date, once a lock date is set Yes, with a date after the lock date No No

The same goes for payments, credit notes and refunds: none can be recorded with a date on or before your lock date (by you, a workflow, the AI connection or the API), and a payment dated there can't be removed. Only money that arrives by itself through your payment gateway is recorded anyway; it posts on the day after the lock date.

When you try one of these, BaseCloud tells you why. In a bulk action on the Accounting page, they're skipped, and BaseCloud lists each one by its number with the reason.

To correct an invoice you can't change, post a manual journal in an open period. Ask your accountant if you're unsure which accounts to use.

Invoices from before your start date

Invoices dated before your start date are part of your opening balances. They never post to sales or tax, and they can still be paid, so you can collect what customers owed you when your books started.

Until a lock date is set, an invoice, credit note or payment dated before your start date can still be added, edited or voided. Each change moves that customer's opening Accounts Receivable: Books posts an Opening balance change journal, dated the day before your start date, between their Accounts Receivable and Historical Adjustment. This is how documents from your old system come over. See Moving to BaseCloud from another accounting system.