Field notes · 4 November 2025
What group instructions should tell a component auditor
Materiality, significant risks, and reporting deadlines — the three sections that prevent component packs arriving incomplete.
When Seamless API Connectors coordinates component auditors for a Taiwan parent, incomplete packs usually trace back to thin group instructions — not lazy local teams.
Materiality cascade
State group materiality, performance materiality, and the threshold for reporting clearly trivial misstatements. Component auditors need numbers, not “use professional judgement alone.”
Significant risks at group level
If revenue cutoff or related-party transactions are significant for the group, say so explicitly for components that contribute those risks. Local auditors may otherwise design procedures only for local statutory risks.
Reporting package contents
List required schedules: adjusted trial balance, intercompany balances, subsequent events, and a summary of uncorrected misstatements. Give a hard receipt date that sits before your consolidation review — not the same day as the board pack.