Hands-Free Invoicing for 300+ Hospital Facilities
Around 500 invoices a month were produced and sent mostly by hand, clustered at period end. We automated the full lifecycle and moved every facility's recipients and attachment rules into configuration.
- Service
- Business Transformation
- Industry
- Revenue Cycle & Finance
- Region
- United States
- Engagement
- SES (specialist engineers)
Outcomes
- 300+ facilities billed automatically
- ~500 invoices/month hands-free
- Recipient rules as configuration
Stack
Power Automate · Power BI · SQL · SharePoint · Email automation
Written byOriental Nippon Team
A US revenue-cycle operator bills more than three hundred hospital facilities, some monthly and some weekly. Each invoice has to be generated from current data, formatted correctly, addressed to the right people, and sent with the right attachments.
Around five hundred invoices a month were being produced and sent largely by hand. The work piled up at period end, exactly when the team was busiest.
The problem
- Period-end crunch. Days of every month went into assembling and sending invoices.
- Drifting configuration. Recipient lists, subject lines and attachment sets were kept by hand and slowly went out of date.
- High cost of a mistake. An invoice sent to the wrong facility is a billing error and a data-handling incident at the same time.
- Two cadences. Monthly and weekly cycles had to run side by side.
| Before | After | |
|---|---|---|
| Invoices per month | ~500, mostly manual | ~500, fully scheduled |
| Facilities | 300+ | 300+, each with its own rules |
| Recipient rules | Kept in people's heads and inboxes | One configuration set per facility |
| Switch-over check | n/a | A full period compared invoice by invoice |
What we built
End-to-end invoice automation
Data refresh, generation, export and formatting for both monthly and weekly cycles.
Mapped distribution
Recipients, subject lines, body text and attachment rules per facility, kept as configuration.
Scheduled runs
Each cycle runs on time and reports what it did.
A comparison record
Evidence that automated output matched manual output before anything went live.
Each invoice now moves through a fixed lifecycle, and every step is logged:
Technology and the role it played
| Technology | Role in this project |
|---|---|
| SQL | Current billing data for each facility |
| Power BI | Refresh and rendering of invoice output |
| Power Automate | Generation, export and mapped distribution |
| SharePoint | Per-facility configuration and archived output |
| Scheduled email | Delivery on the monthly and weekly cycles |
How we delivered it
For the first live cycle, every invoice went to an internal mailbox instead of to hospitals. Only after a full period had been checked invoice by invoice did anything go to a facility.
- Map every facility. Cadence, recipients, format and attachments in one configuration set.
- Automate generation. Output validated against what the team produced by hand.
- Automate distribution. Pointed at an internal mailbox first.
- Parallel cycle. A full period of automated invoices compared with the manual ones.
- Switch over by cadence. Monthly first, then weekly.
01Requirement mapping
2–3 wks
Per-facility cadence, recipients, format, attachments
02Generation automation
3–4 wks
Refresh, export, formatting
03Distribution automation
2–3 wks
Mapped recipients, subjects, bodies, attachments
04Parallel cycle
4 wks
A full period compared invoice by invoice
05Switch-over
2 wks
Monthly first, then weekly
Risks and how we handled them
| Risk | How we handled it |
|---|---|
| An invoice reaches the wrong facility | First live cycle sent only to an internal mailbox |
| Automated invoices differ from manual ones | A full period compared invoice by invoice before switch-over |
| Recipient lists drift again | Recipients, subjects and attachments kept as configuration, not in inboxes |
| Both cadences breaking at once | Monthly switched over first, weekly only after it was stable |
Outcome
Days of manual period-end work are gone, and invoices go out on schedule without anyone touching them.
The step we would point to is the parallel cycle. For a process that touches billing, comparing every invoice before sending anything automatically is the only responsible way to switch over.
What the client keeps
- Automation definitions and source
- The per-facility distribution configuration
- The parallel-run comparison record
- Run-monitoring setup
Sources and further reading
- Power Automate documentation, Microsoft Learn
- What is Power BI?, Microsoft Learn
- Parallel change, Martin Fowler
Facing something similar? This is the kind of work our Enterprise & Digital Transformation team delivers every day. Talk to us about your stack.
