Brick Books → Guides
Everything from opening Brick Books for the first time to handing a finished year to your accountant, explained in plain English.
If you have just bought Brick Books, work through the first three guides in order: installing it, setting it up, bringing your existing books across.
It takes about twenty minutes and gets your orders flowing in automatically.
The rest can wait until you actually need them. And if you are not registered for sales tax, you can ignore that guide entirely.
Downloading Brick Books, opening it for the first time, and understanding where your books actually live.
Guide 2The steps that decide whether everything Brick Books calculates afterwards is right.
Guide 3Getting your existing spreadsheet or bank CSV into Brick Books without retyping everything.
Guide 4Getting your API keys, dealing with the BrickLink whitelist step that catches almost everyone out, and bringing in your order history.
Guide 5Adding an entry by hand, attaching a receipt, and understanding how categories affect your profit.
Guide 6Getting receipts into Brick Books, how they are filed, and how to bring in a pile of old ones.
Guide 7Sending receipt photos into Brick Books, and deciding whether you want to open the program itself on your phone.
Guide 8One of the most common mistakes in reseller bookkeeping, and the year-end step that fixes it.
Guide 9For sellers registered for VAT, GST, sales tax or an equivalent tax. If you are not registered, you can skip this guide.
Guide 10Recording trips to the post office, stock pickups and other business travel, in kilometres or miles.
Guide 11The health check, what each finding means, and which problems Brick Books can safely fix for you.
Guide 12Taking a safe copy of your books, keeping another copy somewhere else, and what happens when you restore one.
Guide 13The pack for your accountant, what is in it, and the short list to work through before you send it.
Guide 14The questions people ask once they are using Brick Books, answered in plain words.
Tell me about it on the report a problem page, or send a question from the contact form. A real person reads them, the same one who wrote the program.