G3 Computing and G3 Principles of Accounts are different electives with different ways of solving problems. Computing develops the design and testing of computing solutions; Principles of Accounts develops the recording, interpretation and use of accounting information. Compare the work the student wants to learn, the school’s available combinations and the support needed to manage each subject.
For the 2027 SEC, the syllabus codes are Computing K349 and Principles of Accounts K342. Computing includes a lab-based examination as well as a written paper. Principles of Accounts has two written papers. The comparison below describes those national assessment schemes, while the school determines its offered combinations and selection arrangements. Check the correct syllabus for the student’s actual examination year.
- Compare Computing K349 with Principles of Accounts K342 using their actual tasks.
- Distinguish Computing’s written and lab papers from Accounts’ two written papers.
- Try small original examples of tracing, spreadsheet reasoning and accounting transactions.
- Look for explanation and checking, as well as correct answers.
- Ask the school about eligibility, resources and available combinations.
- Verify a future course requirement before treating either elective as essential.
Read by section
- Compare the actual assessment
- Computing: enjoy explaining how a solution works
- Accounts: understand the business event behind the records
- Compare debugging with checking accounts
- Look at the work the student will practise regularly
- Check the whole timetable
- Keep career claims precise
- Trace a small program before trying to improve it
- Test a solution against a precise requirement
- Understand a spreadsheet formula as a relationship
- Follow several business transactions through one example
- Distinguish cash, revenue, profit and amounts still owed
- Understand what a check can and cannot establish
- Make a reasoned Accounts decision from a scenario
- Look beyond programming to how information is represented
- Compare how the student responds to two unfamiliar tasks
- Arrange access and feedback before adding extra resources
- Official references and review date
Examination-year check: the codes and paper details on this page refer to SEC 2027. A student entering Secondary 3 in 2027 would normally sit the examination in 2028. Confirm the applicable year and syllabus with the school before buying materials or making a final choice.
Compare the actual assessment
| Subject and paper | Duration | Marks | Weight |
|---|---|---|---|
| Computing Paper 1: written | 2 hours | 80 | 60% |
| Computing Paper 2: lab-based | 2 hours 30 minutes | 70 | 40% |
| Accounts Paper 1: written | 1 hour | 40 | 40% |
| Accounts Paper 2: written | 2 hours | 60 | 60% |
Both papers are compulsory in each subject. Computing’s lab examination covers spreadsheets and programming, using the software specified in its syllabus. Accounts Paper 2 contains four compulsory structured questions. These details come from the official SEAB K349 Computing syllabus and SEAB K342 Principles of Accounts syllabus. Classroom projects or practice tasks should not be confused with a national coursework assessment.
Computing: enjoy explaining how a solution works
Using a device confidently is different from explaining how a computing solution is constructed. Ask whether the student enjoys breaking a problem into smaller steps, deciding what information is needed and checking whether the result meets the requirements.
The 2027 Computing syllabus includes computing fundamentals, algorithms and programming, spreadsheets, networking, and the impact of computing. Its programming environment includes Python and JupyterLab. Ask the school what experience it expects before the course and what it teaches from the beginning; do not invent prior programming as a universal entry condition.
For an original discussion example, imagine a program that counts how many numbers in a list exceed ten. Ask what should happen when the list is empty, when every number is ten, and when only one number exceeds ten. The learner need not start by writing code. First they can explain the rule and the result expected for each case.
This reveals an important distinction between a solution that works for one convenient example and a solution that satisfies the intended rule. If the output is wrong, encourage the student to trace where the result first differs from the expectation. Random changes may occasionally help, but they provide less understanding than a reasoned test.
Accounts: understand the business event behind the records
Principles of Accounts requires more than performing calculations. A student needs to understand what happened in a business, how it should be represented and what the resulting information can tell a decision-maker. Ask the learner to explain a transaction in ordinary language before using technical account names.
Consider an original simplified illustration: an owner puts $500 of personal money into a new business bank account as capital. The business has more cash, but that contribution is not sales revenue. The example helps distinguish where money came from from whether the business earned revenue. It isolates the distinction between capital and revenue.
For a second simplified example, a business sells goods for $120 cash; the goods cost it $70. Ignoring other expenses, the gross profit on that sale is $50. The cash received is $120, which is a different quantity. Ask the student to explain why the figures answer different questions instead of memorising that “profit means money”.
The course also asks students to interpret information and justify decisions. In the 2027 Accounts scheme, a scenario-based question requires a choice supported by accounting and non-accounting information. A numerically correct calculation may therefore be only part of a complete response.
Compare debugging with checking accounts
Both subjects reward careful checking, but the object being checked differs. In Computing, a student may compare a program’s behaviour with the specified requirement. In Accounts, the learner may check whether the treatment of a transaction and the information produced are consistent with the business event and the applicable principles.
Ask the student how they respond to an error. Can they describe it precisely, isolate a likely cause and test a correction? A learner who says only “it does not work” needs help identifying the point of failure. The same broad habit of patient investigation can support either subject, without making their content interchangeable.
Avoid assuming that getting a total to agree proves every entry is correct, or that a program producing one expected output proves the logic is correct in all cases. Ask what the check establishes and what it leaves uncertain. This makes checking an act of reasoning rather than a final ritual.
Look at the work the student will practise regularly
Request a representative classroom task from each subject. For Computing, ask about the mix of conceptual explanation, programming and spreadsheet work. For Accounts, ask about recording, preparation of statements, interpretation and written justification. Compare the student’s engagement with these tasks rather than asking which subject sounds easier.
Give the student room to be a beginner. A small unfamiliar task can show curiosity and how they use feedback, but it should not become an unofficial entrance exam set by a parent. The school’s criteria and the teacher’s assessment of sustained learning are the relevant basis for allocation.
Ask how resources and access are organised at school. A family should understand what equipment or materials are actually required before purchasing anything. Do not infer a need for an expensive computer, paid software or a particular tuition package from the subject title alone.
Check the whole timetable
Each elective sits alongside the rest of the student’s programme. Estimate the time currently needed for homework, correction and independent practice, and include CCA, travel and rest. Look for where deadlines may coincide. The most attractive individual subject may need a different combination around it to make the overall programme workable.
Ask the school how eligibility, class availability and timetable constraints affect the choice. National syllabus availability does not guarantee that both subjects are offered or can be taken together. A written school option form is a better starting point than a general online list.
Prepare a meaningful alternative and discuss it with the student. If the preferred choice is unavailable, the alternative should still have a clear reason and a practical learning plan. Ask what review arrangements apply after allocation, without assuming a later change is always possible.
Keep career claims precise
An elective can help a learner explore an interest, but taking Computing does not by itself guarantee a computing course, and taking Accounts does not qualify someone as an accountant. Equally, not taking one of these subjects should not be described as closing every later route into the field.
If a particular post-secondary programme is being considered, check its actual admission-year subject and grade requirements. Separate general entry eligibility from course-specific conditions. Ask the school’s guidance staff to interpret ambiguous wording and retain the source for a later review.
A useful final explanation from the student is specific: what kind of problem they want to learn to solve, what they already do reasonably well, and what they expect to find challenging. That gives parents and teachers a practical basis for support after the choice has been made.
Trace a small program before trying to improve it
The examples below are original learning illustrations, not official examination questions, school entry tests or evidence that a beginner must already know the subject. They show the kind of reasoning a learner can develop. For Computing, start with the counting rule introduced earlier: count how many numbers are greater than ten.
numbers = [8, 10, 12, 15]
count = 0
for number in numbers:
if number > 10:
count = count + 1
print(count)This short Python example prints 2. The value 8 does not satisfy the condition, and 10 does not exceed ten. The values 12 and 15 each increase the count by one. Ask the student to trace the value of count after each item rather than simply running the program and accepting the display.
| Current number | Is it greater than ten? | Count after this item |
|---|---|---|
| 8 | No | 0 |
| 10 | No | 0 |
| 12 | Yes | 1 |
| 15 | Yes | 2 |
Now change the condition to “greater than or equal to ten”. The value 10 should count, so the result becomes 3. This small change illustrates why the exact requirement matters. A program can run without an error message and still implement the wrong rule.
Ask what should happen with an empty list. Because no items are processed, the count stays at its initial value of zero. Then try a list containing only 10. The original rule should again produce zero. This is a useful boundary case because it distinguishes “greater than” from “greater than or equal to”.
A learner who enjoys tracing these changes may be interested in the reasoning behind Computing. If they find the notation unfamiliar, explain it before drawing conclusions about suitability. The relevant question is how they engage with a clearly taught idea and whether they can apply it to a related case, alongside the school’s actual criteria.
Test a solution against a precise requirement
Before writing a program, describe its input, required output and important conditions. For the counting example, the input is a list of numbers and the output is how many of those numbers exceed ten. The example assumes the supplied items are numbers. Handling unexpected text or other input would be a separate requirement to define and teach.
Prepare expected results before running the solution. For [11, 12], the expected count is 2. For [9, 10], it is 0. For [-2, 10, 11], it is 1. The negative value is still a number and does not meet the condition. These cases exercise different parts of the rule.
Suppose a student places count = 0 inside the loop. The program then resets the count for every item, so it may report a plausible answer for one list while failing on another. Tracing the values reveals the first point where the intended running total is lost. Randomly moving lines around without an explanation makes the correction harder to trust.
A useful debugging note has three parts: the input that exposed the problem, the expected result and the change that addresses the cause. After changing the program, rerun the relevant cases, including ones that worked before. This checks whether the correction solved the problem without creating a new one elsewhere.
Testing a few examples does not prove that every possible program is correct. It does provide evidence about the stated cases and helps expose mistakes. The scope of the claim should match the scope of the checks. This is why explaining the algorithm remains useful even when a program has produced several correct outputs.
For subject choice, notice whether the student is willing to investigate a discrepancy and revise their reasoning. Prior experience can be helpful, but the school should explain what is expected at entry and what will be taught. A family should not turn a short practice task into an invented national threshold.
Understand a spreadsheet formula as a relationship
Computing also includes spreadsheet work in the 2027 syllabus. A spreadsheet can calculate quickly, but the student needs to understand what each cell represents and whether a copied formula still expresses the intended relationship. Use a small invented materials list to make this visible.
Suppose column A contains item names, column B the quantity, column C the unit price and column D the line total. In row 2, three items cost $2.50 each, so the line total is $7.50. In row 3, four items cost $1.20 each, so the line total is $4.80. The combined amount is $12.30. These are hypothetical prices for the exercise.
A formula such as =B2*C2 in cell D2 expresses quantity multiplied by unit price. When copied down one row using ordinary relative references, it becomes =B3*C3, which uses the next item’s values. Ask the student to predict the copied formula before checking it in the spreadsheet.
Now suppose a hypothetical discount rate of 10% is stored in F1. A formula referring to $F$1 keeps that reference fixed when copied. A line-discount formula such as =D2*$F$1 therefore uses the relevant line total and the same rate. The dollar signs in the cell reference fix the column and row; they do not mean that the cell must contain currency.
For the combined $12.30 amount, a 10% discount is $1.23, leaving $11.07. Ask whether the spreadsheet’s result is consistent with that manual check. If a copied formula points to a blank cell or to the wrong rate, the result may look tidy while being incorrect.
Distinguish changing a value’s display from changing the value used in calculation. Showing two decimal places does not necessarily round the stored value in the same way as an explicit rounding operation. Follow the task’s instructions on precision and check the formulas, not just the appearance of the table.
This example illustrates relationships and references rather than a complete syllabus task. Use the software and conventions specified by the school and the current examination guidance. Before buying additional equipment or applications, ask what access the school provides and what the student actually needs for independent practice.
Follow several business transactions through one example
For Principles of Accounts, use a simplified fictional business to see how transactions connect. Assume there are no other transactions, expenses, taxes or adjustments in this illustration. The owner first contributes $2,000 to the business bank account. The business has an asset of $2,000 and owner’s equity of $2,000. The contribution is capital, not sales revenue.
The business then acquires inventory costing $600 on credit. It now has cash of $2,000 and inventory of $600, giving total assets of $2,600. It owes the supplier $600, so liabilities are $600 and equity remains $2,000. The accounting equation, assets equal liabilities plus equity, still holds.
Next, goods costing $250 are sold for $400 cash. Cash rises to $2,400 and remaining inventory falls to $350. The sale produces $150 of gross profit in this simplified example. With no other expenses assumed, equity rises to $2,150. Assets of $2,750 equal liabilities of $600 plus equity of $2,150.
Finally, the business pays $200 of the amount owed to the supplier. Cash falls to $2,200 and the liability falls to $400. Inventory stays at $350 and equity stays at $2,150. Paying an existing supplier debt is not a second recognition of the inventory cost or a new expense in this illustration.
| Stage | Cash | Inventory | Liabilities | Equity |
|---|---|---|---|---|
| Owner contributes capital | $2,000 | $0 | $0 | $2,000 |
| Inventory bought on credit | $2,000 | $600 | $600 | $2,000 |
| Goods sold for cash | $2,400 | $350 | $600 | $2,150 |
| Part of supplier debt paid | $2,200 | $350 | $400 | $2,150 |
Ask the student to explain each change in words before checking the totals. A correct final equation is useful, but understanding why cash, inventory, liabilities or equity changed is the central learning task. The example deliberately isolates a few ideas; actual course questions introduce further transactions and accounting requirements.
Distinguish cash, revenue, profit and amounts still owed
The linked example ends with $2,200 in cash, $350 in inventory and a $400 liability to the supplier. The cash balance is not the same as the $150 profit generated by the sale. It includes the owner’s original contribution and is affected by the timing of purchases, sales and payments.
Ask what would change if the $400 sale had been made on credit instead of for cash, with all other assumptions unchanged. At the moment of sale, the business would recognise an amount receivable from the customer rather than a cash receipt. The sale’s revenue and the cost of the goods still need to be considered. Receiving cash later would settle the receivable; it would not create the same sales revenue a second time.
This distinction helps explain why a profitable business can still need to pay attention to when money is received and paid. For the learning example, the important task is to identify which event occurred and which record changes. Avoid treating every increase in the bank account as revenue or every decrease as an expense.
For another hypothetical event, an owner withdraws cash for personal use. That should be distinguished from a business expense. Likewise, a business receiving a loan has more cash and a corresponding obligation to repay; the loan receipt is not earned sales revenue. The accounting treatment follows the nature of the event, not merely the direction in which money moves.
When choosing Accounts, notice whether the student finds these distinctions interesting and can explain them after instruction. Accurate arithmetic matters, but it serves a system of meanings. A learner who asks why a payment affects one account rather than another is engaging with an important part of the subject.
Understand what a check can and cannot establish
A balanced accounting equation or trial balance is useful evidence that certain numerical relationships hold. It does not prove that every transaction has been recorded correctly. An omitted transaction, for example, may leave both sides of a record unaffected and therefore escape a simple equality check.
Misclassification can also produce a plausible total. If an equipment purchase is treated as an expense when it should be recorded as an asset under the question’s stated circumstances, the records may still balance while the reported information is wrong. The student needs to return to the business event and relevant accounting principle, not merely adjust a number until the totals agree.
Use a short checking sequence: identify the source information, explain the event, determine the appropriate records, perform the calculation and inspect the resulting balances. If an inconsistency appears, trace it back through those steps. This is more informative than changing the final total without explaining the cause.
The comparison with Computing is useful here. A program that returns the right answer for [11, 12] may still use the wrong boundary condition and fail for [10]. In Accounts, a correct-looking total may hide a wrong classification. In both subjects, checking should test the intended meaning and relevant cases.
Keep the student’s original attempt alongside the correction. Ask what evidence exposed the error and why the new treatment addresses it. A clear explanation of a correction can reveal more understanding than an unexplained page of correct figures. The teacher can then decide which related task will show whether the understanding transfers.
Make a reasoned Accounts decision from a scenario
The 2027 G3 Accounts assessment includes a scenario-based decision question. Its specified task requires a decision supported by three reasons, using the relevant accounting and non-accounting information; this differs from the G2 task. Check the K342 scheme of assessment for the exact requirements.
Consider an invented practice scenario. A business needs 100 items within five days and has $1,000 of uncommitted cash available for this order. Supplier A quotes $8 per item, delivery in ten days and no replacement arrangement for defective goods. Supplier B quotes $9 per item, delivery in three days and a stated replacement arrangement for defective goods. Assume the quoted terms are the information supplied in the exercise.
A decision favouring B can be supported by three distinct reasons. First, the three-day delivery meets the five-day need, whereas A’s ten-day delivery does not. Second, B’s $900 total is within the $1,000 available, leaving $100 of that cash after the order. Third, the stated replacement arrangement offers a response if defective goods arrive, which A’s quoted terms do not provide.
Acknowledging the trade-off improves the explanation. A would cost $800 and save $100, but its delivery does not meet the stated deadline. The answer should explain why that saving is less decisive under these conditions. If the deadline or available cash changed, the decision might need to be reconsidered.
Three reasons should do three different jobs. Repeating “B is faster”, “B takes fewer days” and “B arrives sooner” expresses the same point repeatedly. Link each reason to a relevant fact and explain why it matters to the decision. Avoid introducing claims about supplier reputation, quality or discounts that the scenario does not provide.
This is a simplified teaching case, not purchasing advice for an actual business. It shows why Accounts includes reading, interpretation and written justification as well as calculation. A student choosing the subject should be willing to explain the significance of information, not only extract numbers from a table.
Look beyond programming to how information is represented
Computing is broader than writing a short program. The 2027 syllabus includes computing fundamentals, data-related ideas, networking and the impact of computing alongside algorithms, programming and spreadsheets. A family should ask the school for representative conceptual tasks as well as a coding demonstration.
An original information-design exercise might concern recording items in a lost-property system. Each item needs an identifier that distinguishes it from other items. A description such as “black bottle” may be useful for a human reader but is not necessarily unique. Two objects could share that description, so a system relying only on it could confuse their records.
Ask what information is necessary for the stated purpose and what would create avoidable problems. The system may need an item’s description, where it was found and its current status. A proposal to collect extensive personal information should be examined against the actual task and the school’s requirements. This is an ethical design discussion, not a claim about a particular legal obligation.
Then consider how the information changes. When an item is returned, its status should be updated consistently. If two copies of a record disagree, the user needs a way to know which is current. These questions connect representation, rules and the behaviour of a working system.
A learner may enjoy these conceptual decisions even before becoming fluent in programming syntax. Conversely, someone who likes copying short programs may need practice explaining what the data mean and what the solution must accomplish. Examining both kinds of work gives a more complete basis for choosing the elective.
Compare how the student responds to two unfamiliar tasks
Choose one small Computing activity and one small Accounts activity, with the teacher’s guidance where possible. Explain the necessary ideas first. The purpose is to observe engagement and learning, not to reward the student who happened to encounter a topic earlier outside school.
For Computing, the learner might trace the counting example and predict the result after changing the condition. For Accounts, they might explain why a credit purchase creates both inventory and an amount owed. Ask them to describe their reasoning in ordinary language before using specialised terminology.
Notice what happens after a correction. Can the student locate the earlier misunderstanding? Can they explain the new idea without repeating the adult’s words mechanically? Can they apply it to a related example? Those observations provide useful questions for the subject teacher, although they do not replace the school’s criteria or assessment of sustained work.
Ask the student which difficulty they would be willing to work on regularly. Someone may enjoy testing a program but find financial classification uninteresting. Another may like interpreting business events and prefer the structure of accounting records. A learner can also be interested in both; the school’s actual timetable then determines which combinations are available.
Avoid making the choice from one fast or slow attempt. Familiarity, instructions and support affect the experience. Use the activity together with recent schoolwork, teacher advice and the student’s account of their interests. The final reason should describe the learning they want to undertake rather than a reputation that one subject is easier.
Arrange access and feedback before adding extra resources
For Computing, ask what software environment and school access will be used, how work should be saved and what practice can be completed outside lessons. A learner needs to understand where their files are and how to resume a task, not merely have access to a powerful device. Follow the school’s stated requirements before purchasing additional hardware or applications.
For Accounts, ask how the teacher expects calculations, records and explanations to be presented. Keep examples of corrected work so that the student can see the relationship between the transaction and its treatment. Buying more question books will be less useful if the learner has not understood why the same classification error keeps recurring.
In either subject, clarify the permitted assistance for a particular task. A completed solution obtained from another person or a digital tool is different from the student’s independent work. When using work to discuss progress, make that distinction visible. Parents can help organise questions and deadlines while leaving the reasoning and assessed decisions to the learner.
For the basic syntax and reference behaviour used in the examples above, see the official Python tutorial on control flow and Microsoft’s explanation of relative and absolute cell references. These explain the tools; the SEAB syllabus and school instructions determine the course and examination requirements.
Finish the choice discussion with a clear next action: confirm an offered combination, ask about a resource, revisit a named concept or submit an informed preference. The elective should become a manageable programme of learning, with specific help available when the student encounters a difficulty.
Official references and review date
Reviewed on 15 November 2026 against SEAB 2027 G3 school-candidate syllabus directory and the subject documents linked above. For later cohorts, use the relevant examination-year syllabus. School-specific offerings, criteria and deadlines must be confirmed with the school.
Leave a Reply