Clouddatasynccom

Audit approach

How Clouddatasynccom plans, tests, and reports on intercompany transaction audits — from scope letter to findings discussion.

Why a dedicated approach page

Intercompany work fails when scope is vague. This page explains how we move from first call to final letter so you know what to expect before fees are agreed.

1. Briefing

We learn your entity structure, known disputes, statutory audit dates, and whether Inland Revenue or board questions are driving the timeline. No fieldwork starts here — only enough detail to draft a scope letter.

2. Scope letter

The letter names entities, periods, deliverables, fees, deposit, access requirements, and exclusions. You accept in writing before document requests go out.

3. Document request list

Typical requests include:

  • Entity chart and shareholding summary
  • Trial balances and intercompany subledgers
  • Sample sales and purchase invoices between group companies
  • Management recharge packs and allocation worksheets
  • Prior findings or auditor management letters touching related parties

4. Fieldwork

Associates perform reconciliations and sample tests under manager supervision. Unusual items are raised early so you can locate supporting files while the team is still on site or on the file exchange.

5. Draft findings discussion

You see draft exceptions before the letter is final. Wording can be clarified; facts are not softened to remove an unsupported charge.

6. Final letter and working papers

You receive a PDF findings letter and an indexed working-paper set. Retention of copies follows our privacy notice; originals of your ledgers never leave your control in a way that blocks your own close.

Natural next actions