Case study / 2026
Timesheet Anomalies Automation
Operational reporting workflow for a team reconciling employee hours across two timesheet reports.
01 / Context
The problem
Manual comparison of timesheet entries created delays, missed exceptions, and inconsistent follow-up.
A team needed to compare employee hours reported by two systems and identify discrepancies.
02 / Contribution
What I built
Implemented Power Automate flows to receive two reports through Outlook, save them into SharePoint folders, run scripts, compare summarized data, and email a CSV anomaly report.
The design decision
The biggest win was preparing summarized datasets first, so the comparison logic stayed structured and easier to troubleshoot.
Scope
- Receive two report attachments through Outlook
- Store each report type in controlled SharePoint folders
- Summarize raw report data before comparison
- Generate and email a CSV anomaly report
03 / Structure
How it works
Built as an end-to-end reconciliation pipeline for two recurring timesheet reports received through email.
- Outlook mailbox acts as the intake channel
- Power Automate handles attachment identification, SharePoint storage, script orchestration, CSV creation, and email distribution
- SharePoint document libraries separate source files by report type
- Excel Scripts prepare summarized datasets before reconciliation logic runs
Through the workflow
- User sends the required reports to the configured mailbox
- The intake flow saves files into the correct SharePoint folders
- The processing flow runs scripts, compares summarized data, and identifies anomalies
- Users receive a CSV report for review and correction follow-up
04 / Operation
Controls and upkeep
- Separate source folders reduce accidental file mixing
- Script-based summarization keeps comparison logic simpler
- Flow run history supports troubleshooting when reports, scripts, or email delivery fail
Keeping it useful
Known operational checks include confirming both reports were received, validating folder placement, reviewing script execution, and checking whether the CSV email step completed.
05 / Result
The outcome
Provided a repeatable reconciliation pattern with structured anomaly reporting for review.
The workflow produces a CSV of reported-hour discrepancies for the team to review.
Discuss a similar project