Record routine transactions from source documents while preserving classification, timing, and financial statement effects.
Routine transactions are recurring activities that arise from the entity’s normal operations. They can still create reporting errors when source documents are incomplete, timing is wrong, classification is careless, or the accounting system records the transaction mechanically without considering substance.
In Core 1, routine transaction questions test disciplined accounting, not memorized journal entries. The answer should identify the transaction, read the source evidence, determine recognition and measurement, record the statement effect, and explain any tax, assurance, finance, or control consequence when relevant.
| Routine area | Common transaction | Reporting risk |
|---|---|---|
| Revenue and receivables | Sales, billings, collections, returns, discounts. | Premature revenue, cut-off errors, uncollectible balances, gross-versus-net errors. |
| Purchases and payables | Supplier invoices, accruals, prepaids, rebates. | Missing liabilities, wrong period, expense-versus-asset errors. |
| Inventory | Purchases, production, write-downs, shrinkage. | Incorrect cost, obsolete inventory, count errors, cut-off issues. |
| Payroll | Wages, bonuses, vacation, benefits. | Accrued liabilities, classification, payroll remittance, related-party compensation. |
| Capital assets | Additions, repairs, depreciation, disposals. | Capital-versus-expense errors, useful life estimates, impairment, gain or loss errors. |
| Debt and interest | Borrowings, repayments, covenant fees, interest accruals. | Current classification, missing interest, covenant disclosure, financing cost treatment. |
The answer should not stop at “record the invoice.” It should explain the financial statement effect.
Routine transactions are driven by evidence. A source document tells you what happened, but it may not tell you the accounting answer by itself.
| Source document | What it helps prove | What still needs judgment |
|---|---|---|
| Customer contract | Rights, obligations, price, delivery terms. | Revenue timing and performance status. |
| Sales invoice | Billing amount and date. | Whether revenue was earned and collectible. |
| Shipping document | Transfer or delivery evidence. | Whether control or risks passed under the framework. |
| Supplier invoice | Amount payable and expense or asset description. | Period, capitalization, allocation, and tax treatment. |
| Payroll register | Compensation amounts and deductions. | Accruals, benefits, bonuses, and related-party reasonableness. |
| Bank statement | Cash movement. | Classification, cut-off, and completeness. |
| Board approval | Authorization. | Whether recognition criteria are met. |
Use documents together. A sales invoice without delivery evidence may not support revenue. A supplier invoice dated after year-end may still relate to goods received before year-end.
Every routine transaction can be checked through four questions:
| Question | Example issue |
|---|---|
| Recognition | Has the entity incurred a liability for goods received before year-end? |
| Measurement | Is the amount net of discount, rebate, foreign exchange, or tax? |
| Classification | Is the cost inventory, prepaid expense, capital asset, repair, or operating expense? |
| Timing | Does the transaction belong before or after year-end? |
This framework is often faster than trying to remember an entry first.
Recurring transactions can be high risk when volume is large, systems are weak, or incentives are present.
Examples:
The case response should reflect materiality and risk. A small prepaid adjustment may be low priority; a recurring revenue cut-off issue near a covenant threshold may be central.
When an entry is needed, write it as a consequence of the analysis.
| Scenario | Entry logic |
|---|---|
| Goods received before year-end but invoice arrives after year-end. | Recognize inventory or expense and accrued liability if the obligation exists. |
| Customer paid in advance for future services. | Recognize cash and a liability until services are performed. |
| Repair invoice includes a major betterment. | Split expense and capital asset if facts support different treatment. |
| Inventory count shows damaged goods. | Assess write-down or loss based on recoverable amount and evidence. |
| Interest has accrued but not been paid. | Recognize interest expense and payable. |
If numbers are not provided, describe the direction of the adjustment and the statement effect.
Routine transactions can affect other Core 1 areas:
| Link | Example |
|---|---|
| Tax | Accounting income may need reconciliation to taxable income; GST/HST and payroll remittances may require support. |
| Assurance | Source documents and controls affect evidence reliability. |
| Finance | Revenue timing, working capital, and debt classification can affect ratios and covenants. |
| Controls | Missing approvals, reconciliations, or access controls can cause recurring errors. |
| Strategy | Revenue quality or cost classification can affect performance interpretation. |
Mention these links only when they affect the decision. Do not turn every routine entry into a long multi-competency answer.
Use this order for routine transaction questions:
| Pitfall | Better approach |
|---|---|
| Recording from invoice date only. | Use the underlying transaction date and performance or receipt evidence. |
| Treating routine transactions as immaterial by default. | Consider volume, risk, incentives, and stakeholder impact. |
| Jumping to a journal entry before classification. | Determine recognition, measurement, classification, and timing first. |
| Ignoring source documents. | Use contracts, invoices, shipping documents, receiving reports, and bank evidence together. |
| Overcomplicating simple entries. | Keep routine entries concise but explain material statement effects. |