Engagement process

How a Dev Layer Grid financial audit of subscription billing applications moves from first call to signed findings pack.

Planner and laptop on a desk during project scoping

1. Scoping call

We confirm the entity, period, billing application, and why the review is needed — external audit support, diligence, processor change, or internal doubt about the numbers. Materiality and sample size expectations are set here so fieldwork does not surprise your team.

2. Access letter & exports

You grant read-only access or scheduled exports: charge events, customer plan history, credit notes, and processor settlements for the period. We provide a short checklist so IT and finance know what to pull once.

3. Fieldwork

Analysts reconcile totals, select samples, and document exceptions. Seniors review every material item. If a sample reveals a systemic issue — for example, proration logic that ignores a contract clause — we expand testing inside the agreed fee band or pause to re-quote.

4. Draft findings

You receive a draft findings pack: narrative, exception list, and suggested adjustments. Factual comments from your team are welcome within an agreed window. We do not negotiate away exceptions that the evidence supports.

5. Closing session

We walk finance (and, if you choose, your external auditor) through the pack. The final PDF and workbook follow within two business days of that session.

Where work happens

On-site days are available at Level 7, 39 Phuket Road, Mueang Phuket 83000, or at your office by arrangement. Many engagements run fully remote with screen-share walkthroughs.

Ready to begin?

Request an audit or review flagship engagement details.