What a mapping is, and is not
Each section below explains how the output of Auditor Alpha relates to a framework. It is a description of where our evidence may be useful, not a claim that using Auditor Alpha makes you compliant.
Auditor Alpha is not an audit, an assurance opinion or a certification. It gives your finance team and your auditors evidence to review. Whether a control meets a framework is a judgement for your auditors and advisers.
SOX-style revenue completeness controls
Many internal control frameworks expect a business to show that revenue it earned was billed. Auditor Alpha checks every closed-won HubSpot deal against Xero invoices and records the result, so a monthly reconciliation can be shown rather than described.
- Relates to: completeness of revenue and billing controls
- What we provide: a record of each check, each alert and each decision your team made
- What we do not provide: control design, testing of operating effectiveness or a SOX opinion
IFRS 15 and ASC 606 revenue recognition
Revenue recognition depends on contracts, performance obligations and timing. Auditor Alpha does not apply these standards. It can show where a contract recorded in the CRM has no matching invoice, or where amounts differ, which may be useful when your team prepares recognition workpapers.
- Relates to: evidence that contracted revenue was invoiced
- What we do not do: allocate transaction prices, judge performance obligations or recognise revenue
UK GDPR and data handling
Auditor Alpha connects to HubSpot and Xero with read-only OAuth and processes only the records needed for reconciliation. Data is encrypted in transit and at rest. Our Security page, Privacy notice and Subprocessors list describe how data is handled.
Audit-trail expectations
External auditors usually want to see what was checked, what was found and what was done about it. Auditor Alpha keeps each reconciliation run, its alerts and the review decisions together, so they can be exported and shared.