AP Intermediate Commerce (BIEAP) common mistakes
AP Intermediate Commerce (BIEAP) · Understand the traps and how to avoid them.
In Accountancy, posting a debit entry to the credit column (or vice versa) while journalising, then balancing the ledger with the wrong side and forcing a 'suspense' plug instead of tracing the error.
Candidates memorise 'debit the receiver, credit the giver' as a chant without applying the modern rules (debit increases assets/expenses, credit increases liabilities/income/capital) to each specific account type. Under time pressure they write the amount in whichever column is nearer.
What to do instead
Before writing any entry, say the account name and its classification aloud in your head: 'Cash A/c - asset - increases - debit.' Practise 20 journal entries daily for two weeks, classifying each account first, and after each entry verify total debits equal total credits on that line. In the ledger, post only after confirming the side from the journal column, and never use a suspense account until you have checked the trial balance twice.
In Accountancy numerical problems (depreciation, bills of exchange, final accounts), skipping the adjustment entries given in the 'additional information' and presenting a Trading and Profit & Loss Account that ignores closing stock, outstanding expenses, or prepaid items.
Candidates treat the trial balance as the whole question and stop reading once they start calculating. Adjustments are usually printed after the trial balance, and under exam pressure the candidate rushes to balance the books and misses them.
What to do instead
Adopt a fixed routine: read the trial balance, then underline every line of additional information and write a two-column list - 'adjustment entry' and 'double effect (Trading/P&L and Balance Sheet)'. Closing stock affects Trading Account credit and Balance Sheet asset; outstanding expense affects P&L debit and liability; prepaid affects P&L credit and asset. Tick each adjustment off as you incorporate it, and reconcile the final Balance Sheet totals before moving on.
In Business Studies, answering 'state the features/importance of...' questions with a single long paragraph of general management talk instead of the required number of distinct, labelled points.
The paper awards marks per point, but candidates write what they remember as prose and lose marks for missing points even when the content is broadly right. They also confuse 'features' with 'functions' or 'objectives' because the terms are studied together.
What to do instead
Train point-wise answers: for a 4-mark question write four numbered points, each with a bold keyword heading and one explanatory sentence. Build a one-page revision sheet per chapter listing the exact command words (features, functions, importance, limitations, types) and the number of points the textbook gives for each. Before writing, count the marks to decide the number of points, and never merge two points into one sentence.
In Economics, drawing a demand/supply or cost curve without labelling the axes, the curves, the equilibrium point, and the direction of the shift, and then explaining the movement in words that contradict the diagram.
Candidates learn definitions verbally and treat diagrams as decoration. They also mix up 'movement along the curve' (price change) with 'shift of the curve' (other determinants), so the diagram and the explanation disagree.
What to do instead
Use a fixed diagram checklist every time: label both axes with the variable and units, label each curve (D, D1, S, MC, AC), mark the original and new equilibrium with coordinates, and add arrows showing direction. Then write one sentence tying the diagram to the cause: 'A rise in consumer income shifts demand right from D to D1, raising equilibrium price from P to P1.' Practise redrawing each syllabus diagram from memory weekly.
In Economics, confusing related concepts in definitions - e.g. writing 'increase in demand' when the question asks about 'expansion of demand', or mixing micro and macro examples - and losing the definition mark.
These paired terms are taught close together and differ by one condition (price change versus other determinants; individual versus aggregate). Candidates revise by reading rather than by contrasting, so the distinction blurs in the exam hall.
What to do instead
Maintain a two-column 'confusable pairs' table (expansion vs increase in demand, contraction vs decrease, stock vs supply, GNP vs GDP, explicit vs implicit cost) with the distinguishing condition in one line each. Test yourself by covering one column. In the exam, underline the exact term in the question and write its one-line definition before the explanation.
In Computer Applications/IT, writing syntax from memory with missing punctuation - unclosed quotes, missing semicolons, wrong brackets, or SQL keywords in the wrong order - and losing marks on otherwise correct logic.
Candidates focus on understanding the concept and underestimate how strictly syntax is marked. They also practise by reading code rather than typing it, so muscle memory for punctuation never develops.
What to do instead
Type every program and query at least twice on paper and once on a machine; never copy-paste during practice. Memorise the skeleton of each construct (SELECT ... FROM ... WHERE ... ORDER BY; if ... else; for loop with initialisation, condition, increment) as a template, then fill in the specifics. In the exam, re-read each line checking quotes, semicolons, and brackets before moving on, and dry-run the code with sample values.
In Computer Applications/IT, describing the output of a program or the result of a query without dry-running it, and giving the wrong output for loops, counters, or conditions.
Candidates recognise the code pattern and assume the obvious result, missing off-by-one errors, the effect of a condition failing on the first iteration, or NULL handling in SQL.
What to do instead
Always trace with a table: columns for iteration number, variable values, and condition result, one row per pass. For SQL, list the rows of the source table and mark which survive the WHERE clause before applying SELECT. Practise ten short traces a day, and for each one write the final output only after the last row of the trace table.
In Commerce Practical Work, presenting a project or record book without the required structure - missing index, acknowledgement, objectives, methodology, observations, conclusion, or bibliography - or submitting calculations that do not reconcile with the stated data.
Candidates treat the practical as a formality and copy a friend's format, so they do not know the marks are allocated section by section. They also complete the write-up at the last minute and never cross-check figures.
What to do instead
Obtain the official project guidelines and build a template with every required heading before writing content. Keep a dated log of work done each week. Before submission, run a self-check: index matches page numbers, every table has units and a source, totals reconcile, conclusion answers the stated objective, and bibliography lists every source cited. Get one peer to verify the arithmetic independently.
In English Communication and Comprehension, answering comprehension questions in copied phrases from the passage or in note form, instead of complete grammatical sentences, and misreading 'in your own words' or 'infer' questions as literal recall.
Candidates are trained to find the answer line and lift it, which earns partial credit at best. Time pressure pushes them to skip the instruction line, and they do not distinguish literal, inferential, and evaluative question types.
What to do instead
Read the questions before the passage, then read the passage once. Underline the instruction verb in each question (state, explain, infer, compare, give your opinion). Answer in a complete sentence that restates the question's key term, and for inference questions add the reasoning clause ('This suggests ... because the passage says ...'). Practise with a 5-minute-per-passage timer and check subject-verb agreement and tense in each written answer.
In the Second Language paper (Telugu/Hindi/Sanskrit/Urdu), making script and spelling errors - wrong vowel signs (matras), incorrect conjuncts, or sandhi/grammar forms - and translating answers mentally from English instead of composing in the target language.
Candidates prepare by reading and memorising, not by writing, so the hand is unpractised in the script and the grammar patterns are not automatic. Thinking in English first produces literal translations with wrong case endings and word order.
What to do instead
Write at least one page of the target script daily, copying passages and then writing them from dictation. Keep a personal error list of matras, conjuncts, and case endings you repeatedly get wrong and test yourself on it weekly. For grammar sections (sandhi, samasa, vibhakti, tenses), memorise the rule with two worked examples each. When composing answers, build sentences from target-language patterns you have practised rather than translating word by word.