Adam KimMECHANICAL ENGINEERING
Menu
← BACK TO PROJECTS

Engineering case study

Compliance QA report automation

A Python program I built for the compliance QA team at Fairstone Bank to transform Excel and Word inputs into a formatted report using a custom template and review-specific rules.

Fairstone Bank · Compliance QA team · Summer placement · Python

Project status
Completed during placement
Disciplines
Python / Document automation / Data transformation
My role
End-to-end program development & template design
COMPLIANCE QA REPORT AUTOMATION
Excel + Wordsource documents
Reporttables & sections

Extract · Transform · Assemble

01

Automating compliance QA reports

I built a Python program for the compliance QA team at Fairstone Bank to extract information from specified sections of Excel and Word files and assemble it into a final report. I developed the program and designed the report template, including placeholders for the content generated by each part of the workflow.

Developed for internal use at Fairstone Bank. Source code and company data are not shared publicly; this case study summarizes my contribution and the workflow.

02

Template-driven report generation

  • Read selected information from Excel worksheets and Word document sections.
  • Transform data formatting and adjust tense in report text where required.
  • Populate placeholders in my custom template with new tables and report sections.
  • Run individual parts of the report-generation workflow separately.
  • Apply specific processing rules for different review types.

The project required learning Python libraries for reading spreadsheets and Word documents, generating tables, and working with document templates.

03

Working with document structure

One of the hardest parts was handling Word content whose underlying XML and formatting structure complicated text processing. The text visible in a document was not always straightforward to extract or modify programmatically. Working through those document-structure issues, alongside learning the required libraries, was a major part of the development effort.

04

Result

My estimate is that preparing a report previously took roughly 3–6 hours and took about 5 minutes after automation. These are approximate workflow times from my experience, rather than results from a formal benchmark.

← All projects