The need
Problem
Reporting depended on multiple manual deliverables and scattered source files. The process involved repeated work, inconsistent outputs, and opportunities for input errors.
The build
Engineering approach
I first built an Excel/VBA ETL workflow that ingested, transformed, and consolidated roughly 15 source files. It calculated reporting outputs and refreshed PivotTables and charts automatically.
I later moved the processing into a Python backend within an internal application. That work included data transformation, Excel generation and modification using OOXML, input validation, backend error handling, and frontend feedback for common input mistakes.
The result
Outcome
The workflow became part of an internal system used to generate standardized customer-facing reporting. The Python implementation improved processing capability, maintainability, support for larger datasets, and the feedback users receive when inputs need correction.
Looking back
Lessons & growth
Moving a working spreadsheet automation into an application required more than transferring calculations. Input validation, maintainable processing, and actionable error feedback became part of the solution.