Oriental Nippon Development
Back to portfolio
Case studyUS revenue-cycle operator

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.

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.
BeforeAfter
Invoices per month~500, mostly manual~500, fully scheduled
Facilities300+300+, each with its own rules
Recipient rulesKept in people's heads and inboxesOne configuration set per facility
Switch-over checkn/aA 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

TechnologyRole in this project
SQLCurrent billing data for each facility
Power BIRefresh and rendering of invoice output
Power AutomateGeneration, export and mapped distribution
SharePointPer-facility configuration and archived output
Scheduled emailDelivery 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.

  1. Map every facility. Cadence, recipients, format and attachments in one configuration set.
  2. Automate generation. Output validated against what the team produced by hand.
  3. Automate distribution. Pointed at an internal mailbox first.
  4. Parallel cycle. A full period of automated invoices compared with the manual ones.
  5. Switch over by cadence. Monthly first, then weekly.
Delivery timelineIndicative total: 13–16 weeks
  1. 01Requirement mapping

    2–3 wks

    Per-facility cadence, recipients, format, attachments

  2. 02Generation automation

    3–4 wks

    Refresh, export, formatting

  3. 03Distribution automation

    2–3 wks

    Mapped recipients, subjects, bodies, attachments

  4. 04Parallel cycle

    4 wks

    A full period compared invoice by invoice

  5. 05Switch-over

    2 wks

    Monthly first, then weekly

Risks and how we handled them

RiskHow we handled it
An invoice reaches the wrong facilityFirst live cycle sent only to an internal mailbox
Automated invoices differ from manual onesA full period compared invoice by invoice before switch-over
Recipient lists drift againRecipients, subjects and attachments kept as configuration, not in inboxes
Both cadences breaking at onceMonthly 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

  1. Power Automate documentation, Microsoft Learn
  2. What is Power BI?, Microsoft Learn
  3. 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.