The work
At RealPage, I led billing recovery and reconciliation work, defining requirements for corrections and coordinating fixes across Finance, Revenue Operations, Engineering and Data.
Billing errors were causing revenue leakage and recurring manual investigation before month-end close. The work needed to support billing for failed transactions while addressing the problems that kept producing those failures.
What I led
- Prioritized revenue recovery, corrective fixes and preventive controls.
- Defined field mappings, transformation rules, and validation and reconciliation requirements.
- Coordinated delivery across software engineering, data teams and billing operations.
- Helped map current and future workflows and update operating guidance with the teams doing the work.
Recover, correct, prevent
Recovery supported billing for transactions that had failed. Corrective work addressed order-to-billing integrity, bundle accuracy and calculation issues. Preventive work included upstream controls, clearer exception information, updated runbooks and training.
The priorities gave teams a way to address the immediate billing problem while progressing longer-term fixes.
Recover
Support billing for transactions that had failed before month-end close.
Correct
Address contract, order, product-mapping and billing-rule problems.
Prevent
Improve upstream controls, exception information and operating guidance.
Turn discrepancies into requirements
Billing exceptions included missing order matches, inconsistent customer or property identifiers, and product or bundle configuration problems.
I translated those discrepancies into field mappings, transformation rules and reconciliation requirements. That gave the delivery teams a definition of what correct, importable billing lines should look like and how to check them.
Support billing while the underlying fixes progressed
An interim Alteryx process converted failed billing rows into importable lines before month-end close. I defined the mappings, rules and validation requirements and coordinated the work with Revenue Operations.
The data-warehouse and implementation teams built the Alteryx model. Software and data teams worked through a shared delivery process while the underlying billing corrections progressed.
How results were validated
Recovered revenue, rejected billing records and Revenue Operations time spent investigating exceptions were agreed success measures upfront. Finance produced and validated the recovered-revenue and rejected-record results.
Outcome
The program recovered approximately $1M and reduced rejected billing records by at least 85%, validated by Finance.