Revenue Reconciliation
Identified approximately £100k in ARR discrepancies, which were recovered.
- Role
- Revenue Operations Contractor
- Timeframe
- 2 weeks
- Stack
- HubSpot
- Verified outcome
- £100k ARR discrepancy identified and recovered.
- Skills demonstrated
- Revenue integrityCross-system reconciliationData analysis
The challenge
- What was happening?
- ARR figures were inconsistent across commercial systems.
- Why did it matter commercially?
- Unreconciled discrepancies mean revenue that is contracted but not correctly recorded or billed.
- Limitations of existing systems
- No native integrations and no sync in place — data sat in disparate systems with different owners.
- What needed to change?
- Discrepancies needed to be identified and corrected.
The architecture
A conceptual model for comparing subscription terms across CRM, contract management and billing, detecting discrepancies and flagging exceptions for review.
The implementation
- 01
Compare records across systems
Compared revenue data between systems to surface mismatches.
- 02
Identify discrepancies
Identified approximately £100k in ARR discrepancies.
Outcome
Beyond recovering the discrepant revenue, the work left the data in a healthier state. Every account now has a single agreed figure with a clear source of truth, which has improved data hygiene and given the team confidence in the numbers they report and bill from. Because the rules are set across the organisation rather than fixed record by record, the reconciliation is future-proofed: billing stays consistent and correct as contracts renew and terms change.