How Power Automate Invoice Approval Reduced Cycle Time by 80% for a Canadian Municipal Government

This case study explains how our team helped a mid-sized Ontario municipal government replace a fully paper-based accounts payable process with a Power Automate invoice approval workflow reducing invoice cycle time from days to hours, eliminating manual GL entry, and giving finance leadership real-time budget visibility during approvals. 

Executive Summary   

Invoice approval cycle time dropped by an estimated 80%, manual data entry and routing fell by roughly 15+ hours a week, and 100% of approved invoices now export directly into Great Plains without re-entry. Code Creators achieved this by replacing a fully paper-based, disconnected accounts payable process at an Ontario municipal government with a unified Power Apps solution comprised of a Power Automate invoice approval workflow, OCR-based data extraction, and a SharePoint Hub Site foundation, which gives finance leadership the real-time GL budget visibility at the point of approval for the first time. 

Industry: Municipal Government  

Main Challenge: Paper-based, disconnected AP process | Key Result: Full automated invoice approval workflow from email intake to ERP export 

 Result KPIs: 

1. 80% reduction in invoice approval cycle time 
2. 15+ hours/week saved on manual data entry and routing 
3. 100% of approved invoices exported to Great Plains without re-entry 
4. Real-time GL budget visibility introduced at the point of approval 

About The Client

The Client is a municipal government serving a community in Ontario, Canada, responsible for a broad range of public services funded and scrutinized under municipal accountability standards. Like most municipalities, every dollar spent from capital projects to routine operating expenses needs to be tracked, documented, and reportable on demand, both to residents and to auditors. 

The finance team processes a steady, high volume of vendor invoices, employee expense claims, and monthly Visa card transactions across multiple departments, each with its own budget lines and approval hierarchy. That operational complexity with multiple request types, multiple approvers, strict document retention rules for both capital and operating records made this a meaningfully harder environment for accounts payable automation than a typical single-department APprocess and made getting the approval routing and budget management logic right especially important as part of the Client’s broader digital transformation. It’s a pattern we see often across Power Apps government projects: the approval logic has to satisfy public accountability requirements that private-sector AP systems don’t. 

The Problem

The Issue 

The Client’s accounts payable process ran almost entirely on paper and email, with no automated invoice approval workflow of any kind. Invoices arrived by email, were printed, and were physically routed for review, with approvals returning through more email or interoffice mail. There was no central system of record, so there was no way to answer a simple question like where this submission currently sits? without checking multiple inboxes and physical folders by hand. This is the same underlying gap that drives most searches for invoice processing automation: a process that technically works, but only through constant manual tracking. 

The Impact   

AP clerks manually re-entered GL codes, department fields, and budget balances at every stage of the process, with no data connection between steps which was a common source of transcription error and duplicate payments, and a real gap in basic financial controls. Managers had to separately open the original email attachment just to see the invoice they were approving, adding friction to every single review. Vendor management ran off a static list nobody actively maintained, and expense management for employee claims followed no consistent rule set. For Visa card expenses, the AP team manually broke down monthly statements and distributed individual transactions to cardholders by hand every billing cycle – a recurring, fully manual effort that scaled with headcount rather than with better tooling. Leadership was already considering adding staff to keep pace, not because invoice volume had grown, but because the process itself generated unnecessary work at every step. 

The Risk   

Left unresolved; the risk went beyond day-to-day inefficiency. The audit trail was incomplete, and the archive inconsistent with a real compliance of exposure for a public body accountable to residents and subject to formal audit. Without a reliable system of record, the Client couldn’t consistently answer basic questions like “has this vendor already been paid,” and the Visa reconciliation process had no scalable path forward as transaction volume grew. For a municipal government bound by document retention requirements on both capital and operating expense records, that gap was a standing risk rather than a one-time inconvenience. 

What We Discovered – The Requirements 

Before building anything, we worked through the Client’s existing process end to end – mapping every handoff between email intake, printing, physical routing, manual GL entry, and final payment- to identify exactly where time and accuracy were being lost. 

The diagnosis surfaced several root causes: 

1. No System of Record: Invoice status lived in inboxes and physical folders, not a queryable data source, making status checks and audit prep manuals every time. 
2. Disconnected data entry: GL codes and budget figures were retyped at each stage with nothing linking them back to actual budget balances, so approvers were making decisions without real-time financial context. 
3. No Document metadata link: Invoice images and their approval metadata lived in separate places, forcing managers to cross-reference manually during every review. 
4. Fully manual Visa reconciliation: Monthly statement breakdowns and per-cardholder distribution had no automation layer at all. 
5. Three distinct request types, one ad hoc process: Vendor invoices, employee expenses, and Visa transactions were handled inconsistently, with no shared intake or approval logic despite overlapping approval hierarchies. 

From these findings, three technical requirements shaped the build: a single intake and approval surface instead of three, OCR to remove manual re-typing at the point of entry, and budget data surfaced live during approval rather than reconciled after the fact. This diagnosis also confirmed that the fix needed to be a genuine Power Automate approval workflow – triggered directly off the incoming AP email – rather than a digitized version of the existing manual steps. Getting there requires real process automation and stronger data governance around vendor records and GL data, not just a faster version of the same paper trail. 

The Solution

Objective: Replace three disconnected manual processes with one Power Apps interface backed by an automated invoice approval workflow, real-time budget checks, and direct ERP export. 

1. SharePoint Home Site as the Foundation. A SharePoint Hub Site became the central access point – navigation to all relevant areas, a permission-controlled document library, and a self-managed news section for the Client’s admin team. 
2. A Single Power App for Three Request Types. One unified Power App handles vendor invoices, employee expenses, and Visa card transactions. Selecting a request type dynamically shows only relevant fields. Vendor fields pull from an approved master list, with unrecognized vendors flagged rather than silently accepted. An invoice preview panel sits alongside the metadata fields so approvers never leave the form. 
3. Power Automate Invoice Approval Workflow. When an invoice email lands in the central AP inbox, a Power Automate flow classifies it, stores the attachment in SharePoint, creates the corresponding list record, and runs an OCR component to extract and pre-fill invoice data – turning data entry into a review-and-correct task rather than a type-from-scratch one. This workflow automation layer also runs duplicate invoice detection on invoice-and-vendor combinations before submission. 
4. Budget-Aware Approval Routing. Routing is automatic, based on department and dollar amount against the Client’s existing approval hierarchy. Entering a GL code during review immediately surfaces approved budget, year-to-date spend, and remaining balance – giving managers real budget management visibility at the point of decision; a 90%-of-budget threshold triggers a warning, and anything that would push a GL over its limit requires written justification before approval. 
5. Visa Card Workflow and Reporting. Monthly Visa statements (CSV/Excel) are parsed automatically into individual transaction records, assigned to cardholders, batch- or individually approved by managers, and exported to Great Plains alongside vendor invoices. A Power BI dashboard tracks volume, approval rates, budget-vs-actual by department, and monthly trends. 

We considered a lighter-weight option – automating only vendor invoices and leaving expenses and Visa transactions on the existing manual process – but the Client’s requirement for one unified system, plus the shared approval hierarchy across all three request types, made a single consolidated app the more defensible long-term architecture. 

Challenges Overcome    

Challenge 1: Reconciling Three Request Types in One Interface   

The Problem. Vendor invoices, employee expenses, and Visa card transactions each needed different fields, different approvers, and different data sources. Vendor invoices required vendor-master validation and OCR handling; expenses needed their own approval thresholds; Visa transactions needed cardholder-level visibility restrictions, so users only ever saw their own line items. Building three separate apps would have fragmented the audit trail – the exact problem the Client was trying to eliminate. 

The Resolution. We built conditional form logic keyed off the request-type selection at the top of the form, so the interface only ever surfaces the fields, validations, and approval routing relevant to that specific submission type, inside a single Power App and a single underlying data source. 

The Outcome. Staff work from one interface regardless of request type; approvers see a consistent review experience, and every submission – invoice, expense, or Visa transaction – flows into the same auditable record set rather than three disconnected ones. 

Challenge 2: Real-Time Budget Visibility During Approval   

The Problem. Surfacing accurate GL balances during approval required more than a periodic budget export – a static snapshot would go stale within days and undermine the whole point of showing budget data at the point of decision. 

The Resolution. We connected the approval screen directly to live budget data, so entering a GL code pulls current approved budget, year-to-date spend, and remaining balance in real time, with automatic warnings at 90% of budget and a required justification step for anything that would push a GL over its limit. 

The Outcome. Managers now make approval decisions with current financial context instead of reconciling budget impact after the fact, and over-budget submissions are caught before approval rather than discovered during month-end review. 

Results & Business Impact 

The Client now runs vendor invoices, employee expenses, and Visa card transactions through a single Power Automate invoice approval workflow instead of email and paper. 

KPI Snapshot 

1. ~80% reduction in invoice approval cycle time. 
2. ~15+ hours/week of manual entry and routing eliminated. 
3. 100% of approved invoices exported to Great Plains without re-entry. 
4. 0 manual Visa statement breakdowns required per month, down from a full manual process every cycle.

Submissions now move through in hours rather than days, and the improvement looks different depending on where you sit in the process. 

1. For AP clerks, OCR-based intake turns data entry into a review-and-correct task instead of a type-from-scratch one, and duplicate invoice/vendor combinations are flagged automatically before submission. The unrecognized-vendor check means clerks no longer chase down vendor master data manually mid-process. 
2. For Approving Managers, the invoice document and GL balance now sit in the same screen. Entering a GL code surface year-to-date spend and remaining balance immediately, so over-budget submissions are caught and require written justification before approval rather than being discovered during month-end reconciliation. 
3. For Cardholders and Department Managers on the Visa Workflow, the monthly statement upload replaces a manual breakdown-and-distribute process that used to take a full day. Transactions are parsed and assigned automatically; cardholders complete their own fields and attach receipts, and managers can approve individually or in batch. 
4. For the Mayor and Deputy Mayor, final sign-off on payment batches now happens against a read-only consolidated view rather than a stack of individual paper approvals, with the Deputy Mayor able to step in without a separate manual handoff when the Mayor is unavailable. 
5. For Finance Leadership, the Power BI dashboard gives a live view of invoice and expense volumes, approval rates, and budget-vs-actual by department – reporting that previously had to be assembled by hand. Records are archived by vendor and year and locked after final processing, closing the audit trail gap that was the Client’s original compliance risk and keeping the organization aligned with municipal document retention requirements for both capital and operating expense records. 

Client Testimonial   

“Before this, an invoice could sit in someone’s inbox for days, and nobody could tell you where it actually was in the approval process. If a vendor called asking about payment status, we were searching through email threads to find an answer. Now a clerk submits it, OCR pulls the details in, and it’s routed to the right manager automatically based on department and dollar amount. The real difference for us was budget visibility. Managers see the GL balance before they approve, not after, so we catch overspending before it happens instead of during month-end review. The Visa statement upload used to eat a full day every month; now it’s done in minutes. As a municipal government, we also needed an audit trail that holds up to scrutiny, and that’s built into the system now, not something we reconstruct after the fact.” 

John Mitchels – Operations Head 

READY TO MODERNIZE YOUR FINANCE PROCESSES?   

Facing a similar paper-based invoice approval process, disconnected budget data, or manual ERP re-entry? Schedule a consultation with our Power Apps team to discuss a practical automation path for your environment.