Engagement path

How a financial audit of a tax portal application actually proceeds in this practice—from the first pack you send to the letter your finance lead can act on.

Two colleagues reviewing documents together at a wooden table

Working method

Six stations from intake to letter

Use this path when you want the same language between the preparer, the approver, and whoever will clear exceptions.

01

Name the portal and the window

We confirm which filing portal, which entity, and which period. A pre-filing review of Form C is not the same engagement as an e-Invoice sample. Vague “look at our tax” briefs are sent back for a sharper ask.

02

Take the pack as it stands

You send the draft application, working papers, and the approval trail you already have. We do not rebuild your books. We read what you intend to put through the portal.

03

Sample and trace

Selected lines are traced from source records into portal fields. Attachments and declarations are checked for completeness. Mapping errors are written down with the field name the preparer will recognise.

04

Walk the assembly

On Jalan Rasah or on a shared screen, we watch how the pack is assembled and who can change it. Controls that exist only as a habit are noted as such.

05

Rank the exceptions

Findings are ordered by whether they would distort the application, fail a portal check, or merely need a file note. Each item has an owner suggestion—preparer, payroll, tax agent, or board pack.

06

Issue the letter

You receive a findings letter and, if you asked for it, a short close call before the filing window. We do not click submit unless a separate letter says we will stand in as filing support.

When this path fits

Built for teams who already have a filing calendar

If you are still choosing a tax agent or opening a first MyTax profile, start with your agent. Come here when a pack exists and you want it read before it becomes the portal’s record.

See the engagements