Quarterly reporting built around aging tools
The SMAA department relied on three aging Microsoft Access databases and a series of manual steps to prepare recurring fiscal reports and district review files. Staff moved information between program-administrator exports, payroll system extracts, spreadsheets, and Access, preparing data and checking results along the way.
The process involved employee-ID batching, text cleanup, matching records across systems, assembling payroll detail, preparing reimbursement documents, and organizing staff-pool exports for district review. Each reporting cycle depended on staff knowing how to move through the tools and handle their limitations.
Finding the bottleneck
The work was fragmented across applications, file formats, and staff knowledge. The replacement needed to preserve the reporting detail the department depended on while removing repetitive preparation and handoffs.
That meant understanding the meaning of the data, not just combining files. An employee could legitimately have payroll charged to several accounts. The program administrator's data and the payroll system could represent the same employee ID differently. District names could change while their identifying codes stayed the same. Those details shaped the processing and review workflows.
What I built
I built SMAART Reporter, a Windows desktop application that consolidates three recurring workflows.
Salary & Benefits reporting
Imports participant snapshots, prepares employee-ID batches for the payroll system, combines payroll exports, matches eligible participants to payroll, and generates an Excel report in the State survey layout. It preserves account-level detail and includes summaries and exception views for review.
District Reimbursement
Imports the State invoice workbook, links reimbursement lines to district records, highlights changes and exceptions, and lets staff review the import before saving. It calculates the configured fee and net reimbursement, maintains a historical ledger, and produces individual and combined check-backup PDFs plus clipboard-ready AP data.
Staff-pool review
Processes staff-pool exports into one review workbook per district. It brings staff from separate month-based sub-agencies together, identifies 10-, 11-, and 12-month groups, and organizes the output by cost pool and staff name.
Handling the real data
The application also handles practical data issues. Employee IDs are normalized for matching so leading zeros do not cause legitimate payroll to be missed. Account allocations remain separate rather than being collapsed into a single employee total. District reimbursement history is linked by district code, with spelling differences presented for staff review and previous naming choices remembered.
Source files and generated Salary & Benefits reports are organized by fiscal year and quarter. Staff can reopen a saved quarter and regenerate timestamped reports, retaining the inputs needed to revisit the work.
Built for staff to manage
SMAA staff can change the reimbursement fee rate, PDF output folder, ledger location, PDF instruction text, staff-pool review output folder, and district names and active status through Settings. Employee-ID batch size is adjustable in the reporting workflow as well.
These supported changes do not require source-code edits or a new application build. When a folder changes, district information needs updating, or reimbursement instructions need different wording, staff can maintain the tool themselves.
Historical reimbursement lines retain the fee rate used when they were imported. Changing the configured rate affects future approved imports rather than rewriting earlier calculations. The settings provide operational flexibility while preserving the context of past work.
What changed
Three Access-based processes were brought into one application organized around the department's recurring work. Repetitive cleanup, matching, calculations, and document preparation became application workflows, with exceptions surfaced for staff review.
The department gained a consistent way to prepare outputs, revisit prior quarters, and maintain routine settings. More of the process is expressed in the application and its operating guide, making it easier to repeat and hand over.
Staff still export source information from the program administrator and payroll systems, review the results, and complete the remaining reporting and fiscal handoffs. SMAART Reporter handles the preparation and processing between those steps.
My contribution
I translated the department's existing workflows into the desktop application, including import processing, record matching, report generation, reimbursement review, historical storage, PDF outputs, and configurable settings. I also built supporting reconciliation checks and a quarterly operating guide.