What ACCAs PER Actually Looks Like Day to Day

Most ACCA content explains PER as a bureaucratic checkbox: "36 months of relevant experience, get it signed off, done." That description is technically accurate and genuinely unhelpful, because it tells you nothing about what actually filling that requirement feels like across the months you're doing it, at your actual desk, alongside actual exam prep.

What PER actually is, structurally

To reach full ACCA membership, beyond passing all the exams, you need 36 months of relevant work experience in an accounting, finance, audit, or related role, and you need to achieve 9 specific performance objectives: all 5 Essentials (professionalism and ethics, stakeholder relationship management, strategy and innovation, governance risk and control, leadership and management) plus any 4 Technical objectives chosen from a list of 17 covering areas like audit, tax, financial reporting, and financial management.

Each objective has 5 specific elements, tasks, skills, and behaviours you need to genuinely demonstrate in your actual workplace, not just claim. Once you've done that, you write a 200 to 500 word statement for each objective, describing specific examples of your work that show you've met it, and submit it to your Practical Experience Supervisor (a workplace mentor, usually a qualified accountant) for review and sign-off.

Progress across all of this is tracked in ACCA's own online system, called My Experience, where you log objectives as you complete them and your supervisor reviews and approves each one individually. There's also an annual PER return required to confirm your ongoing progress, meaning this isn't a single end-of-journey submission but a running record you build and update across the full 36-month period, alongside whatever pace you're clearing exams at.

Worth being precise about the Essentials specifically, since they apply to everyone regardless of role: Professionalism and ethics asks you to demonstrate acting honestly, keeping client and workplace information private, and behaving correctly under real workplace pressure, not simply reciting the ethics content you studied for the exam. Stakeholder relationship management asks for genuine examples of managing expectations with a client, colleague, or manager, real friction worked through, not a hypothetical scenario. The other three, strategy and innovation, governance risk and control, and leadership and management, similarly ask for lived workplace evidence rather than theoretical understanding, which is exactly why they can't be completed through study alone, regardless of how well you've prepared for the exams covering similar concepts.

What a real month of working toward PER actually looks like

Here's the part the bureaucratic description skips entirely: PER isn't a separate task that happens alongside your job, it's a lens you apply to work you're already doing. A month working toward the Technical objective on audit evidence, for instance, doesn't mean doing anything different at your desk. It means, at the end of a specific engagement where you genuinely gathered and evaluated audit evidence, sitting down and writing an honest account of what you actually did, what judgment calls you made, and what you learned, in a way that maps onto that objective's 5 specific elements.

This is where PER genuinely differs from exam preparation in feel. Exams reward memorised technical knowledge under timed pressure. PER rewards honest, specific reflection on real work, written in your own voice, describing actual decisions rather than textbook answers. Some ACCA affiliates find this genuinely harder than the exams, not because the content is difficult, but because writing an honest, specific 300-word reflection on your own professional judgment is a different muscle than answering a scenario-based exam question, and it's a muscle most people haven't built much before starting PER.

A realistic month, for someone actively working through PER alongside a full-time job, often looks like this: no dedicated "PER time" carved out separately from work, but a habit of jotting down brief notes right after a meaningful task or decision, while the specifics are still fresh, rather than trying to reconstruct the details weeks later when preparing the formal statement. Students who wait until they're ready to submit an objective before trying to recall what they actually did months earlier often produce vaguer, less convincing statements than those who capture specific details close to when the work actually happened.

There's a genuine skill-building arc across the 36 months worth naming too. Early statements, written when you're still new to both the job and to reflective writing itself, often read more generically, closer to a job-description summary than a genuine reflection on judgment and learning. By the later objectives, most students have developed a clearer sense of what specificity actually looks like in these statements, concrete decisions, genuine uncertainty faced and resolved, actual outcomes, rather than a polished but generic account of "responsibilities held." If your early statements feel weaker than you'd like, that's a normal part of building an unfamiliar skill, not a sign you're doing PER wrong.

The part that catches people off guard: choosing objectives strategically

A genuinely practical piece of advice that surfaces repeatedly from people who've been through PER: choose Technical objectives that align closely with what you're actually doing at work, not what sounds most impressive or most aligned with your eventual career ambitions. If your day-to-day role is heavily audit-focused, choosing audit-related Technical objectives means you'll naturally accumulate the evidence you need through work you're already doing. Choosing a Technical objective in an area your actual role barely touches, tax planning, say, when your job is 90% audit fieldwork, means manufacturing evidence for an objective your real work doesn't naturally generate, a much slower and more frustrating path than working with your actual role rather than against it.

This also affects how willing your supervisor is to sign off your objectives. A supervisor reviewing a statement about work they've actually observed you doing can sign off confidently and quickly. A supervisor reviewing a statement about an objective that doesn't map to your visible day-to-day work has less basis to confirm it honestly, which can mean slower sign-offs, more back-and-forth, or a supervisor understandably hesitant to confirm something they didn't really see you do.

It's also worth being strategic about sequencing, not just selection, of your Technical objectives across the full 36-month period. Rather than deciding all four upfront and working toward them in parallel from month one, some students find it more natural to let the first year of work reveal which technical areas they're genuinely developing real depth in, then formally selecting objectives that match that emerging strength, rather than committing early to a fixed set of four before having enough workplace experience to know which ones will actually fit well.

What happens if your current job doesn't generate the right experience

This is a genuinely common, quiet source of stalled PER progress: your job might not naturally touch the specific technical areas ACCA's objectives cover, or you might not have a supervisor genuinely willing or positioned to review and sign off your work. Some students let this drift for months or years without addressing it directly, partly because ACCA's own PER system is deliberately self-directed and opt-in, there's no automatic reminder pushing you toward it the way exam sitting dates do.

The practical response, when this happens, is a direct conversation, either asking your current manager whether specific tasks or a project could be reshaped to generate qualifying experience, or actively seeking a role, rotation, or even a different employer where the day-to-day work naturally maps onto ACCA's objectives. This isn't a failure of your current job, it's simply a mismatch between what that specific role generates and what PER specifically requires, and it's worth naming and addressing directly rather than letting it drift indefinitely.

There's also a quieter emotional dimension to this drift worth naming honestly. Watching peers who started ACCA around the same time steadily accumulate signed-off objectives, while your own PER progress stalls purely because your specific role doesn't generate the right evidence, can feel like a personal shortfall even when it genuinely isn't one. The gap usually has far more to do with which team or project someone happened to land on than any difference in capability or effort, and treating a stalled PER timeline as a reason to have the direct, sometimes uncomfortable conversation about reshaping your role, rather than as evidence you're somehow falling behind, tends to be the more accurate and more productive read of the situation.

Where Artha fits

Writing an honest reflection on your own professional judgment, for an audience of one supervisor who has to actually believe it, is a strangely exposing task that doesn't get talked about much outside ACCA-specific forums. CA Talks on Artha exists for the quieter, more honest version of that conversation, with someone else who's also mid-PER, figuring out how to write about their own work honestly, without performing false confidence about a stalled objective or a supervisor relationship that isn't quite working.

Closing

PER was never really a separate hurdle bolted onto the exams, it's a different kind of work entirely, honest reflection instead of memorised recall. So looking at your actual current role, does it genuinely generate the kind of evidence PER needs, or is it time for a direct conversation about reshaping it, before another few months pass without real progress on this specific front?