Building the Finance analytics capability
Finance reporting depended heavily on ERP inquiries and static cross-entity reports, limiting flexibility and creating fragmented views of financial performance.
I established shared revenue, OpEx, pricing, and forecasting reporting, designed the Finance–IT delivery process, and enabled independent use through training and a Revenue Report Manual.
Finance gained refreshable revenue validation and clearer spend visibility. Colleague feedback estimates about 1 hour saved per day for key Revenue Actuals users and 10+ FP&A review hours per OpEx reporting cycle.
Explore decisions and delivery
Judgment in practice
I traced Finance–IT friction to reporting flexibility and consistent calculations, then designed a shared process that both departments adopted. Finance defines requirements and the star-schema model; IT reviews, implements, and tests the data; I build reports from validated tables.
Delivery and adoption
I connected Revenue Actuals to the quarterly CFO dashboard and added quarter-to-date pacing, order-status, and shipped-not-invoiced views to support Finance forecasting reviews.
I gave Sales pricing comparisons across years, regions, and customers to assess discount patterns. Average selling price logic excluded returns and RMAs; colleague feedback estimates approximately 2 hours saved per period comparison.
For the same OpEx reporting work, colleague feedback also estimates a 20% reduction in manual reporting time through improved invoice validation and cost-centre visibility. This estimate may overlap with the 10+ review hours per cycle.
I helped design the sales-region model, prepared Salesforce region data, and contributed to reporting on sales trends and commission calculations. I linked D365 and Salesforce data to identify end customers behind distributor sales and implemented that mapping in Power BI.
I identified customer-address errors that could misattribute sales, initiated cleanup, and worked with Salesforce and D365 leads to implement controls. I also built product pull-through reporting that maps system sales and nearby consumables demand to help Sales explore opportunities and sales declines.
The commercial reporting dataset covered approximately 2 million rows, three years of history, 150 customers, and more than 1,000 SKUs. These figures describe the dataset, not company totals.
I delivered an executive insights AI agent for the CFO, CEO, and regional leaders, with business-user use confirmed. Parameterized DAX, structured responses, access restrictions, and regression tests are functional. I also built D365 query-support and Power BI ticket-intake agents; their adoption has not been measured.
I evaluated Microsoft Fabric’s Power BI Copilot, Dataflow Gen2, deployment pipelines, XMLA endpoints, data-lake integration, Git-based version control, and workload/capacity needs. I created a capacity-testing roadmap and success criteria and applied ALM Toolkit, Tabular Editor, and selective partition refreshes during the trial. This remains evaluation and trial work, with no completed production migration or measured efficiency gain claimed.
I also helped improve collaboration between Finance in Toronto and Accounting in Singapore by clarifying data requirements, surfacing concerns, and aligning stakeholders on shared reporting needs.
I queried data-lake and Salesforce-sourced data using SQL/SSMS to support Finance reporting.
I automated recurring month-end ERP data handling so the required information could reach reporting with less manual intervention.
Trusted in day-to-day Finance work.
A trusted Finance reporting tool
Finance users relied on live, refreshable Revenue Actuals reporting to validate booked revenue, align with Revenue Recognition, and avoid manual D365 pulls. Key users reported saving approximately one hour per day.
Stronger operating-expense visibility
Colleague feedback linked the OPEX dashboards to faster invoice validation, clearer spend visibility, and an estimated 20% reduction in manual OPEX reporting time.
Comparable pricing for Sales
Sales could compare pricing across years, regions, and customers to assess discount patterns. Excluding returns and RMAs from average selling price calculations saved time on period comparisons, based on colleague estimates.
Summarized from documented colleague feedback. No names or direct quotations are published.