Accounting

Accounting — From Evidence to Decisions

A case-led course in financial and management accounting

Accounting — From Evidence to Decisions

Accounting is not a list of rules. It is a disciplined answer to six questions:

eventevidencerecordmeasurementreportdecision\text{event} \rightarrow \text{evidence} \rightarrow \text{record} \rightarrow \text{measurement} \rightarrow \text{report} \rightarrow \text{decision}

This course follows that chain. Every chapter uses a small business fact pattern, shows the calculation or entry, and then states where professional judgement begins.

The running case: Northstar Cycles

Northstar Cycles Ltd. is a fictional UK e-bike business. It:

  • buys components and manufactures two bicycle models;
  • sells bikes on cash and credit terms;
  • bundles bikes with maintenance plans;
  • develops a customer app;
  • leases a warehouse and owns production equipment;
  • prepares external reports under an IFRS teaching baseline;
  • uses budgets, cost models and investment appraisal internally.

All Northstar amounts are in pounds sterling. Tax rates and discount rates are labelled as assumptions. Real-company examples are explicitly identified and never mixed into the fictional dataset.

What you should be able to do

By the end, you should be able to:

  1. translate a business event into balanced journal entries;
  2. explain why profit, cash and value are different;
  3. apply introductory recognition and measurement logic to revenue, inventory, receivables, long-lived assets, leases and tax;
  4. connect an adjusted trial balance to the four primary statements;
  5. calculate ratios and explain their operational drivers without relying on universal thresholds;
  6. use relevant costs, budgets, performance measures and discounted cash flows to support a decision;
  7. identify where IFRS, US GAAP, estimates or management-defined measures limit comparability;
  8. leave an audit trail from conclusion back to evidence and assumptions.

Before you begin

You need percentages, simple algebra and present-value arithmetic. You do not need prior accounting.

Take this three-minute diagnostic:

EventFirst conclusionWhy
A customer pays £2,400 now for two years of future service.Cash rises; revenue may not yet be earned.Payment and performance occur at different times.
Equipment is bought for £60,000 cash.One asset replaces another initially.Depreciation, not the whole payment, normally enters profit over use.
Reported profit rises while receivables and inventory rise faster.Investigate cash conversion.Growth may consume rather than release cash.
A special-order price is below full unit cost.Do not reject it yet.Unavoidable fixed allocations may be irrelevant when capacity is idle.

If any answer feels surprising, start at Financial Accounting. If all four are comfortable, use the chapter checks to move faster.

Course route

UnitQuestionMain output
1. Reporting foundationsWhat makes a number useful and supportable?Event and element analysis
2. Recording transactionsHow does evidence enter the ledger?Journal, ledger and trial balance
3. RevenueWhat has the entity actually delivered?Contract allocation and entry
4. Inventory and receivablesWhat amount is recoverable?Cost-flow and loss estimates
5. Long-lived assets, leases and taxWhich costs belong now and later?Carrying amounts and adjustments
6. Statements and cashHow do the records become reports?Linked statements and reconciliation
7. Analysis and comparisonWhat story do the reports support?Ratio tree and policy caveats
8. Cost foundationsWhat causes cost?Cost model and product cost
9. CVP and budgetsWhat should happen at a chosen activity level?Scenario and flexible budget
10. Control and performanceDid results improve for the right reason?Variance and KPI diagnosis
11. Short-term decisionsWhich future cash flows differ?Incremental decision table
12. Capital investmentDoes the project create value?NPV and sensitivity analysis
CapstoneCan you defend the whole chain?Record-to-report-to-decision memo

A repeatable study method

For each chapter:

  • Prepare — 30–45 minutes: read the case, reproduce the first table by hand and mark every assumption.
  • Work — 60–90 minutes: solve before opening the answer; use the browser-based Python cells to test changes.
  • Explain — 15 minutes: write one sentence each for the rule, the calculation and the decision consequence.
  • Audit — 10 minutes: trace every figure to a business fact, entry, estimate or source.

A typical pace is five to seven hours per unit. Screen-reader users can rely on the tables and text explanations; charts are supplementary. Interactive cells are optional and always have a worked static example beside them.

Three boundaries that prevent weak answers

1. Bookkeeping is not recognition

A balanced entry can still represent the wrong event or period. First decide what happened; then decide how to record it.

2. Standards are not estimates

A standard may require an expected-loss estimate, but it does not supply Northstar’s probability or forecast. State the rule, the evidence and the estimate separately.

3. Accounting is not valuation

Financial statements provide inputs to decisions. They do not automatically equal market value, replacement value or project value.

Evidence hierarchy

This course uses sources in the following order:

  1. IFRS Foundation and FASB material for reporting requirements and current projects;
  2. regulator filings and company annual reports for real disclosures;
  3. peer-reviewed research for explanatory and empirical insight;
  4. clearly labelled working papers for emerging questions.

The reading and evidence map records why each source is included. It is a selective teaching map, not a systematic or PRISMA review.

Current reporting window

The course was source-checked on 1 August 2026.

These developments change presentation, disclosure and data use; they do not remove the need to understand the underlying event and entry.

Choose your next page

Copyright © 2026