Chartered Accountant Interview Questions

"I did my articleship at a mid-sized firm, so I got a broad mix. Most of my time went into statutory audits of manufacturing and trading companies, plus some tax filings and a couple of internal audit assignments. By my second year I was handling receivables, payables and inventory on my own for smaller clients, and I attended stock counts and drafted the first cut of the management letter. The work I'm proudest of is a vendor reconciliation I did that found duplicate payments the client later recovered. If I did it again, I'd push earlier to understand why we chose each procedure, not just how to perform it. I got that understanding late, and it would have made me faster and better at spotting what matters."

"Practice has been great for me. Auditing many different businesses taught me how numbers can go wrong and how to test them quickly. But I've always been on the outside looking back at decisions someone else made months earlier. What I want now is to be inside one business, owning the close, the forecasts and the controls, and seeing whether my advice actually changes what happens next quarter. This role pulls me because it combines reporting with business partnering, so I'd use my audit background on day one while learning the commercial side properly. I'm not leaving to avoid pressure. Month-end in industry has its own deadlines, and I'm comfortable with that."

"When I looked at your firm, two things stood out. You have a strong base of listed and larger private clients in manufacturing and financial services, and your audit teams are small enough that newly qualified people run fieldwork early. My articleship was mostly manufacturing, so I can add value quickly, and I want exposure to larger groups with consolidation and more complex controls. In two years I'd like to be running fieldwork on mid-sized audits, reviewing juniors' files, and handling client conversations on findings myself. I'd also like to get involved in the data analytics work your firm talks about, because I think that's where audit is heading."

"On a distribution client, I was doing cut-off testing on sales and noticed several large invoices dated the last two days of the year. When I matched them to delivery notes, the goods had actually left the warehouse in the first week of the new year. I pulled the full list of invoices around year-end to see how wide it was, and the total was above our performance materiality. I took the evidence to my senior, and we raised it with the finance manager, who admitted the sales team had pushed to hit an annual target. The client booked the adjustment, and we added a point to the management letter about cut-off controls. What I learned is to size the problem properly before raising it, so the conversation is about facts."

"I'd raise it immediately while we're still on the floor, because once the count ends the evidence is gone. I'd recount those items together with the client's counter to rule out my own mistake, and look for a cause, like wrong units of measure, items in the wrong location, or goods received but not yet logged. If the differences are real, I'd extend my test counts in both directions, from the floor to the count sheets and from the sheets to the floor, and ask the client to recount the affected area. I'd note the cut-off documents as well. Then I'd tell my senior that day, because several errors could mean the count itself can't be relied on, which changes how much work we need on inventory."

"Losing the main lender is a clear event that may cast significant doubt on the company's ability to continue as a going concern, so it becomes a key area of the audit. I'd ask management for their assessment covering at least twelve months from the year-end, with cash flow forecasts and their plans, like refinancing, selling assets or cutting costs. Then I'd test those plans for evidence, for example term sheets from new lenders, not just intentions, and stress the forecast assumptions. If a material uncertainty remains but the plans are reasonable and the accounts disclose it properly, the report gets a separate section highlighting that uncertainty. If the disclosure is inadequate, we'd modify the opinion. And if the going concern basis itself isn't appropriate but the accounts still use it, the opinion would be adverse."

"It starts before we accept. We check the client's integrity, our independence and whether we have the right skills, and we contact the previous auditor where the rules require it. Once accepted, we sign an engagement letter setting out responsibilities. Then I'd get to know the business: how it makes money, its industry, its systems and key controls, and I'd run analytical review on the latest numbers to spot unusual movements. From that we set materiality and identify the risks of material misstatement, including significant risks like revenue recognition and management override. Opening balances need attention in a first-year audit too. Finally, we write the strategy and plan: which controls we'll rely on, what substantive testing covers each risk, the timing, and who does what."

"It comes down to two questions. Is the problem a material misstatement, or were we unable to get enough evidence? And is its effect pervasive, meaning it spreads across the accounts, or confined to one area? A qualified opinion is used when the issue is material but not pervasive, either a misstatement or a limitation of scope, and we say the accounts are fine except for that matter. An adverse opinion is for a misstatement that's both material and pervasive, so the accounts as a whole don't give a true and fair view. A disclaimer is when we couldn't get enough evidence and the possible effects are material and pervasive, so we don't express an opinion at all. An emphasis of matter paragraph, by contrast, doesn't modify the opinion. It just draws attention to something properly disclosed."

"On one audit, the client's finance manager resigned three weeks before the filing deadline, and half the schedules we'd been promised weren't ready. I sat down with my manager and split the file into what could wait and what couldn't. We focused on the high-risk areas first: revenue, inventory and the bank. I asked the client's controller for a named person each day and a short list of documents, rather than one big request they'd ignore. I also flagged early to my manager that we might need an extra person, and we got one for a week. We signed on time, and nothing on the file was cut. The lesson for me was to raise the resourcing problem early, not in the last week."

"On a group audit last year I ran fieldwork with three trainees. On day one I walked them through the risk assessment, so they knew why revenue and inventory got the most attention, and then gave each one clear areas with a short note on what good evidence looked like. I reviewed files daily in small pieces rather than all at the end, which meant problems got fixed while the client's people were still around. One trainee kept documenting what he did but not why, so I sat with him on two sections and showed him how a reviewer reads a file. By the end his files needed far fewer review points. We finished on budget, and two of them asked to be on my next job."

"I keep a simple routine. I read the updates from the standard setters and my professional body when they come out, and I go through my firm's technical bulletins every week, usually on a Friday afternoon. When a change affects my clients, I read the actual standard or the law, not just a summary, because summaries often skip the transition rules. I also do my continuing education hours properly rather than at the last minute. On sharing, when a client group moved to the new lease rules, I made a one-page note with a worked example for the team and walked the client's finance team through what their numbers would look like. Teaching it made sure I really understood it."

"I was working with the founder of a small software company who couldn't understand why his profit looked lower than his bank balance suggested. Customers paid a year in advance, and he'd been counting that cash as income. Instead of talking about standards, I compared it to a gym membership: if someone pays for twelve months, the gym hasn't earned it all on day one, it earns it month by month as it provides the service. So the cash sitting in the bank was partly money he still owed in service. That clicked for him straight away. He then asked the right question, which was how much cash he could safely spend, and we built a simple monthly view for him."

"At a retail client, I proposed a write-down on slow-moving stock that had barely sold in over a year. The finance director pushed back strongly, saying a promotion would clear it. I listened properly, because he might have known something I didn't, and asked for evidence: the promotion plan and any sales since year-end. The post-year-end sales showed most of it was still sitting there, and the planned discount would bring the price below cost anyway. I laid that out calmly and brought my manager in, so the director could see it wasn't just a junior's opinion. He accepted a smaller write-down than my first number, based on the stock that had sold. We agreed, and he later asked us to help tighten their stock ageing report."

"At a manufacturing client, our testing turned up three problems. Purchase orders were often raised after the invoice arrived, one person could both add suppliers and approve payments, and bank reconciliations were running a month late. Before writing anything, I ranked them. The supplier and payment access was the serious one, because it opened the door to fraud, so it went first. For each point I wrote what we found with a real example, the risk in plain words, and a fix that fitted their small team, like a second approver on supplier changes rather than a new hire. My manager and I went through it with the finance manager first, so there were no surprises and we could record their response and a date. The access issue then went in writing to the audit committee as a significant deficiency. It was fixed by our next visit."

"First I'd look at my own request list. Clients often stall when it's a long generic list, so I'd cut it down to what's truly needed, in priority order, with a named person and a date against each item. Then I'd call the finance lead rather than send another email, ask what's getting in the way, and agree a daily check-in for the next week. Sometimes it's just that they're short of staff, and I can offer to pull reports myself if I'm given access. If items still don't come, I'd tell my manager early so the partner can speak to their senior people, and we'd put the deadline risk in writing. The worst outcome is the client being surprised on the last day."

"Early in my career I prepared a tax computation and carried forward a loss figure from the prior year's draft instead of the final filed return. The difference was small but real. I caught it myself when I was tying the computation back to the filed documents before review. I told my manager straight away, corrected it, and checked every other client file I'd prepared that season for the same error. I found one more. Since then, I always tie opening balances to the final signed or filed document, never a working draft, and I added that as a line on our team's preparation checklist. Owning it quickly meant it cost an hour, not a client's trust."

"First I'd make sure I understood the expense. If the goods or services were received this year, it belongs in this year, whenever the invoice is paid. Assuming it does, I'd tell the CFO plainly that I can't move it, because it would misstate the accounts and put both of us in breach of our professional code. I'd keep it calm and practical: the auditors will likely find it in cut-off testing anyway, and a restatement would be far worse than missing a target. I'd offer what we can do honestly, like explaining the one-off cost clearly in the results commentary. If he insisted, I'd put my concern in writing and take it to the audit committee chair. I'd rather have a hard conversation now than sign something false."

"I'd treat it as a fraud indicator, not proof. There can be innocent reasons, like a family business that was disclosed. I'd first confirm the match from the vendor master and payment records, and look at the size, timing and approvals of the payments. I wouldn't mention it to the employee or anyone who could be involved. I'd take it straight to my engagement manager and partner with the evidence, and document what I found. From there, the team would reassess fraud risk, likely extend testing on that vendor and on who can change supplier bank details, and communicate it to a level of management above the people involved, or those charged with governance. Whether it needs reporting outside the company depends on the country's rules, so the partner would decide that."

"I'd tell the engagement partner or our ethics team before doing any work on the file. A close family member in the client's finance team creates a familiarity and self-interest threat, and it's worse if they have influence over the accounting records or the statements. It's not my call to decide it's fine because I'd be fair. Even if I would be, the audit has to look independent too. In most cases the answer is that I come off that engagement, and the firm records the decision. I'd also check the firm's independence declaration process, because this is exactly what it exists to catch, and I'd rather raise it myself on day one than have it come up later."

"For me, scepticism means I don't accept an explanation just because it sounds reasonable or comes from someone senior. I look for evidence that backs it up. Day to day, that means corroborating what management tells me with documents or a third party, noticing when one piece of evidence contradicts another, and pushing harder on estimates like provisions, where there's room for bias. It doesn't mean treating the client as a suspect. I keep the tone neutral: I'll say something like, this is part of how we test every client, could you help me find the support for this? Most people respond well to that. And if a client gets defensive about a routine request, that's worth noticing too."

"I wouldn't just write it off because it's small. A small net difference can be two large errors that happen to offset, or a sign of cash going somewhere it shouldn't. I'd re-perform the reconciliation myself from the bank statement and the ledger, check each reconciling item, especially old unpresented cheques and deposits in transit, and see whether they cleared after year-end. I'd also check the bank confirmation for accounts or balances we hadn't picked up. If I still couldn't explain it, I'd tell my manager before sign-off, not after, and let them decide whether the file can be signed, with the work documented. Usually it turns out to be a timing or posting error, but I'd want evidence of that, not an assumption."

"Materiality is the size of misstatement that could change the decisions of people using the accounts. I'd start with a benchmark that fits the entity: profit before tax for a steady profitable company, revenue or total assets when profit is volatile or close to zero, and expenses for a not-for-profit. I apply a proportion to it using firm guidance and judgement, then adjust for things like public interest or known risks. Performance materiality is set below that, because we don't test everything. If each area is tested to full materiality, small undetected and uncorrected errors across many accounts could add up past the overall figure. We also set a clearly trivial threshold below which differences aren't collected. Some items, like related party or director pay disclosures, matter by nature regardless of size."

"Audit risk is the risk that we give a clean opinion on accounts that are materially wrong. It has three parts. Inherent risk is how likely an account is to be misstated before any controls, which is higher for estimates or complex judgements. Control risk is the chance the client's controls won't catch it. Together those form the risk of material misstatement, which we assess but can't change. Detection risk is the chance our procedures miss the error, and that's the part we control. So if an area has high inherent risk and weak controls, we accept less detection risk. That means more substantive testing, larger samples, more persuasive evidence like external confirmations, and doing it closer to year-end rather than at an interim visit."

"I'd start from the risk the control is meant to address. For design, I ask whether the control, if it works, would actually prevent or catch a material error, and I confirm it's in place, usually with a walkthrough of one transaction from start to finish. For operating effectiveness, I test whether it worked consistently across the whole period. For a manual control like a manager approving journals, I'd pick a sample through the year and check for evidence of review, and that the reviewer had the right authority and actually followed up exceptions. For an automated control, like a three-way match in the system, a smaller test can be enough, but only if the general IT controls around access and program changes are working. Any deviation means I find out why before deciding whether I can still rely on it."

"Step one is identifying the contract. Step two, the performance obligations: here I'd check whether the licence and the support are distinct. Usually they are, because the customer can use the software without the support. Step three is the transaction price, including variable amounts like volume rebates or performance bonuses, constrained so we don't book revenue that's likely to reverse. Step four is allocating that price to each obligation based on relative standalone selling prices, so a bundle discount is spread across both unless it clearly relates to one. Step five is recognition. The support is delivered across the year, so that portion is recognised over time. For the licence, if it's a right to use the software as it exists at the start, revenue is recognised at a point in time when the customer can use it. If it's a right to access software the seller keeps changing, it's recognised over time."

"First I'd confirm the parent actually controls the entity, then make sure both use the same accounting policies and reporting date, or adjust for differences. Then we add the accounts together line by line. Where the parent owns less than all the shares, the outside shareholders' share of net assets and profit is shown as non-controlling interest. The parent's investment is cancelled against the subsidiary's equity at acquisition, and goodwill is what the parent paid plus the non-controlling interest, less the fair value of the net assets acquired. For intragroup items, the group can't owe itself money or sell to itself, so intragroup receivables and payables, sales and purchases, and dividends are removed. If one company sold goods to another at a profit and they're still in stock at year-end, that unrealised profit is eliminated from inventory and from profit."

"Deferred tax exists because accounting profit and taxable profit recognise some items at different times. Say a company buys a machine for 100. In the accounts it depreciates slowly, so after year one it's carried at 80. The tax rules allow faster depreciation, so its tax base is 60. That difference of 20 will reverse later, when the company pays more tax than its accounting profit suggests, so we recognise a deferred tax liability of 20 times the tax rate. A deferred tax asset comes from the opposite: expenses booked now but deductible later, like some provisions, or unused tax losses. But we only recognise that asset to the extent it's probable there'll be enough future taxable profit to use it, which is where the audit judgement comes in."

"A direct tax is charged on the person who bears it, like income tax on an individual or corporate tax on a company's profits. An indirect tax is collected by a business on behalf of the government as goods and services move along the supply chain, like VAT or GST, and the final consumer ultimately bears it. The input tax credit is what stops that tax stacking up at each stage. A business pays tax on its purchases, charges tax on its sales, and pays the government only the difference. So each business effectively pays tax only on the value it adds. The exact conditions differ by country, but usually you need a valid tax invoice, the purchase must be for taxable business use, and some items are blocked from credit."

"I'd start with operating cash flow, since under the indirect method it begins with profit and shows the adjustments. Common reasons are working capital: receivables grew because sales rose or customers pay slower, inventory was built up, or suppliers were paid faster. There may also be non-cash income in profit, like a fair value gain, that brings in no cash. Then I'd look at investing activities, because a company can be profitable and still spend heavily on new equipment or an acquisition. Finally, financing: repaying loans or paying dividends uses cash without touching profit. So I'd walk through those three sections and point to the two or three biggest lines. If most of it is receivables growing faster than sales, that's the one I'd dig into."

"I'd start with the cash conversion cycle: how many days it takes to turn stock and receivables into cash, minus how long we take to pay suppliers. I'd work out receivable days, inventory days and payable days, and look at the trend over several periods and against similar businesses, because a healthy level varies a lot by industry. Then I'd go below the ratios. For receivables, I'd look at the ageing and any concentration in a few customers. For inventory, slow-moving and obsolete stock. For payables, whether a better-looking cycle just means we're paying suppliers late, which can hurt supply. What worries me most is receivable days rising faster than sales, stock building while sales flatten, or the business using a short-term overdraft to fund long-term growth."