Cyprus statutory audit season: a PBC playbook

By the time audit season is fully underway in Nicosia and Limassol, a partner’s inbox is a war of attrition. Bank confirmations are half back. The representation letter is “with the client’s lawyer.” Two juniors are chasing the same fixed-asset register on two different threads, and the tracker that was supposed to keep everyone honest was last accurate a week ago. The technical work is not the problem. Getting the evidence in, cleanly and once, is.

This is a playbook for running the prepared-by-client list through a Cyprus statutory audit as a controlled process rather than an email pile-up. The PBC list is broken in its usual spreadsheet-and-email form for reasons we have written about before. Here is how to run it instead.

Build the PBC as a Pack, not a Word list

Start by turning the PBC list into a Pack: your firm’s reusable set of Request Item templates for a statutory audit. Each line of the old list becomes a Request Item with a proper title, instructions, a sample format where it helps, and a required document type. Bank confirmations, signed financial statements, the representation letter, the fixed-asset register, lease agreements, related-party details, tax computations. Each is a discrete ask rather than a bullet in a document nobody can act on individually.

The Pack is written once and reused every year. You are not rebuilding the audit request list from memory each season. You are refining a standard procedure that gets a little better each time you run it.

Clone last year’s engagement to start from the right asks

You rarely start from nothing. Most of this year’s audit looks like last year’s. So clone the prior-year Engagement to open the new Period with the same asks already in place. The prior year is the best possible template: it reflects the client’s actual structure, the confirmations you genuinely needed, and the schedules that gave you trouble.

Because each Period snapshots the Pack as it stood when the Period was created, cloning does not disturb the historical record. Last year’s Period stays exactly as you ran it. This year’s inherits the shape and moves on.

Set owners and due dates, then send the Period

With the requests in place, assign each Request Item an owner on the client side and a due date. The Client Owner is the default assignee and the escalation point, but individual items can sit with whoever actually holds the document, so the bank letters go to finance and the lease agreements go to the person who signed them.

Then send the Period. The client receives passwordless access to a portal that shows, per item, what is needed, what is awaiting your review, and what is done. There is no login to forget the night before a deadline. There is a plain view of what is still missing.

Let reminders chase so your people do not

Once the Period is live, the routine chasing should not be a person’s job. Clivanta’s reminders read from the live, stored status of each Request Item, so they only ever chase what is genuinely outstanding, defined as items still in requested or needs revision. They escalate on a steady cadence and copy in the Client Owner rather than firing a burst of urgent emails.

When a client genuinely cannot get to an item this week, they can pause the reminder with a logged acknowledgment. The cadence quiets, the item stays open, and it comes back on its own. You keep both the relationship and the record, and your manager’s attention stays on the exceptions that actually need judgement.

Review, request revision, accept to Evidence

As documents arrive, they land against the specific Request Item that asked for them, with full version history. Your reviewer works through the current submission and makes a decision.

• If it is wrong, move the item to needs revision with a structured reason: wrong period, wrong entity, illegible scan, missing a signature. The client sees precisely what to fix, and the superseded file is retained as a previous attempt rather than deleted.
• If it is right, accept it. Acceptance promotes the uploaded Document to Evidence on the permanent engagement record, carrying the reviewer’s identity and a timestamp. A raw file becomes something you have formally relied on, and the record knows the difference.

This is the step email cannot replicate. In a thread, an attachment that was “fine” and a document you formally accepted as audit evidence look identical. Here, acceptance is a decision with a name and a time attached.

Export the file for the workpapers

When fieldwork closes, the audit file assembles itself from what you have already done. Export the Evidence index PDF, the ZIP of accepted Evidence, and the CSV of metadata straight into the workpaper file. You are not reconstructing a story from an inbox six months later. The story, from first ask to final acceptance, is already recorded in each item’s immutable activity log.

What the playbook is really for

None of this changes what a statutory audit is. The judgement, the sampling, the risk assessment remain the partner’s work, and the audit and tax use case shows where that work sits in the wider flow. What the playbook changes is where the hours go. When the collection runs itself, the expensive people spend the season on judgement, not on the tenth follow-up for a bank letter.

Audit season will always be busy. It should not be spent chasing.