Reconcile before you visualize.
A polished dashboard cannot repair an untrusted data layer.
Sheet 05 / About / Active record
Finance systems operator working at the intersection of FP&A, automation, and judgment.
Profile summary
I build finance systems that make reporting faster, controls clearer, and analysis more useful. Day to day, that means budgets, forecasts, management reporting, extraction, reconciliation, consolidation, and delivery.
The technical layer matters because it creates time and trust. The operating layer matters because clean numbers still need context, challenge, and a decision. I enjoy working where those two layers meet.
This website is my public workbook: selected work, blog articles, social field notes, free courses, and labs that turn repeated finance patterns into reusable practice.
Primary field
FP&A
Planning and performance
Systems lens
E2E
Extract to decision
Education
MBA
Financial Management
Development
CPA
Designation path
Capability matrix
// Tools are listed with the operating problems they help solve.
Budgets, forecasts, variance analysis, management packs
Working knowledgePython, SQL, Excel/VBA, Power Query, Power BI
Working knowledgeReconciliation, validation, exception logs, auditability
Working knowledgeDecision framing, executive communication, operating context
Working knowledgeEducation & path
Carleton University · Sprott School of Business
Continuing professional development in Canada
Early banking and development-sector finance experience in Pakistan
Operating principles
A polished dashboard cannot repair an untrusted data layer.
Automation earns trust by clearly showing what it refused to process.
A finance system should be explainable, inspectable, and inheritable.
The model is useful only when it improves the conversation after it.
Public profiles