ByteBook Training Handbook

The standards behind the work

Screen by screen: which standards apply where

Chapter 198 min read

One table that takes you from the thing you are looking at to the document that governs it.

The map

ByteBook screenWhat you are doingAccounting standardAuditing standard
InvoicesRecognising revenue, raising a tax invoiceNZ IFRS 15.31
Bills to payRecording a liability and an expenseNZ IAS 1.54ISA (NZ) 500.6
Bank & codingCoding transactions and reconcilingISA (NZ) 505.10
Reports → Profit and lossReporting performanceNZ IAS 1.99
Reports → Balance sheetReporting positionNZ IAS 1.15, NZ IAS 1.54
Reports → Cash flowClassifying cash movementsNZ IAS 7.10, NZ IAS 7.18
Reports → OutstandingAged debtors and creditorsNZ IFRS 9.5.5.15ISA (NZ) 505.10
GSTBuilding the return from the ledgerISA (NZ) 520.5
Tax formsCurrent tax working papersNZ IAS 12.46
TransactionsReading the entry behind a documentNZ IAS 8.42ISA (NZ) 230.8
Audit trailProving the record has not changedISA (NZ) 500.7
Assurance → A07Manual entriesISA (NZ) 240.32
Assurance → A09Cut-offNZ IAS 10.8ISA (NZ) 560.6
Assurance → A11Large and round expensesNZ IAS 16.15ISA (NZ) 500.7
Assurance → A14Reproducing the reportsISA (NZ) 500.6
Sealed packsClosing and protecting a periodISA (NZ) 230.14
Setting up rolesWho may change the booksPES 1 R112.1

How to use it

Three ways, depending on what you are doing.

When you are learning a screen. Read the row before you start. Knowing that the bank reconciliation is tied to the standard on external confirmations changes how you read the page: you stop looking for a balance that agrees and start looking for evidence that comes from outside the business.

When something looks wrong. Find the row, open the standard, and read the paragraph. The standard usually tells you what the correct treatment is and, just as often, what it is not.

When you are writing a working paper. Cite the paragraph. Not the standard's name, not the general topic: the paragraph. A reference that cannot be checked is not a reference.

A worked example: a bank line coded as an expense

Suppose the bank statement shows $1,150 paid to a supplier, and you code it to expenses when it should have been a payment against a bill.

  1. What is wrong? The supplier's balance still shows as unpaid, and an expense has been recorded twice: once when the bill was entered, and again from the bank line.
  2. Which accounting question is it? Whether the expense is recognised at the right amount in the right period — a matter of faithful representation NZ IAS 1.15.
  3. Which procedure catches it? A05, creditors, which reports money the business owes and checks for a bill paid twice. The GST figures move as well, which A06 will see.
  4. Which auditing standard applies? The reliability of the bank statement as evidence ISA (NZ) 500.7, and the requirement that misstatements found during the audit are accumulated and communicated ISA (NZ) 450.8.
  5. How is it fixed? Void the bank transaction and code it against the bill. Both the wrong entry and the correction stay in the record, and ISA (NZ) 230.8 explains why that matters.

That five-step shape — what is wrong, which accounting question, which procedure, which auditing standard, how to fix it — is the shape of a working paper. It works for a mis-coded bank line and for a misstated provision alike.

Arrow keys, or the buttons