All insights
AI & Automation

How AI is Transforming Finance & Accounting Operations

A healthcare network. $1.5B in annual revenue. 14 entities. 50,000 invoices per year across 6,000 pages of supporting documentation — EOBs, remittance advice, payer correspondence.

Published2 min read
How AI is Transforming Finance & Accounting Operations
AI & Automation2 min read
Share

Part of: AI-native finance operations: what it actually means

A healthcare network. $1.5B in annual revenue. 14 entities. 50,000 invoices per year across 6,000 pages of supporting documentation — EOBs, remittance advice, payer correspondence.

Three full-time AR staff. 47-day average collections cycle.

The before state: every document was read manually. A staff member would open an EOB, identify the payer, match it to outstanding AR, post the payment, and flag exceptions. For 50,000 invoices. Per year.

The problem wasn't headcount. They had enough people. The problem was that manual document review at that volume carries an irreducible error rate — mismatched postings, missed denial codes, exceptions sitting in a queue for 11 days before anyone touched them.

At 47 days average collections, the finance team was leaving approximately $2.3M in float at any given point.

What we built:

A document extraction pipeline that reads EOBs and remittance advice, identifies payer, payment amount, denial codes, and exception flags — then posts matched transactions automatically and routes everything below the confidence threshold to a human queue with a score attached.

Three decisions that made it work:

  1. We trained on their document corpus, not a generic model. Healthcare payer documents vary enough by payer that a general extraction model produces a 61% match rate. Client-specific training moved it to 91%.
  2. We built confidence scoring into every transaction. Every automated posting carries a score. Anything below 0.82 routes to the human queue. That threshold was calibrated against 6 months of historical data — not guessed, not defaulted.
  3. We deployed on the client's infrastructure. The data never leaves their environment. This resolved the compliance and audit questions in week one instead of month four.

Results at 90 days in production:

→ 91% of invoices processed without human review → Collections cycle: 47 days to 31 days → Exception queue clearance: 11-day average to 2.4 days → Denial catch rate up 34% — the model flags codes that manual review was missing entirely

The AR team didn't shrink. It shifted. Two of the three staff now manage exception escalations and payer relationship issues — work that actually requires judgment.

The 31-day collections cycle on $1.5B in revenue is worth approximately $4.1M in recovered float. The engagement covered its cost in the first billing cycle.

This is what a production AI deployment looks like. Not a pilot. Not a proof of concept. A system that runs, that has a confidence threshold, that has an audit trail, and that produces a number you can put in the board deck.

#ProductionAI #FinanceTransformation #HealthcareFinance

Continue Reading

More From the Insights Blog.

View all insights
From ChatGPT pilot to production system: the architecture decisions that matter
AI & Automation

From ChatGPT pilot to production system: the architecture decisions that matter

The ChatGPT pilot is a conversation. The production system is an architecture. The gap between the two is where the majority of AI deployments die — and it is not because the pilot was wrong. It is because the architecture decisions that determine whether the pilot can scale were never made.

Read post
The handover document every production AI engagement should leave behind
AI & Automation

The handover document every production AI engagement should leave behind

When a production AI engagement ends, there is exactly one artifact that determines whether the system survives the consultant's exit: the handover document. Most engagements do not produce one. The system runs for nine months and then quietly degrades, because the knowledge of how it was built lives in an inbox the consultant no longer reads.

Read post
Why your IT team cannot ship the AI deployment your CFO is asking for
AI & Automation

Why your IT team cannot ship the AI deployment your CFO is asking for

When a CFO asks IT to "deploy AI for payables automation," the request lands in a department that is structurally not configured to deliver it. This is not an IT failure. It is a category error in how the work was assigned. Four structural mismatches: 1. IT teams measure uptime; AI deployments require judgment. IT is graded on whether systems are available. AI is graded on whether the system's outputs match the operational reality of the business. The first is a network problem; the second is a finance problem. They share almost no skills and no metrics.

Read post

Get Started

From Reading to Doing.

Every Best Practicify engagement begins with a 45-minute advisory session — a direct conversation with the practitioner who will lead the work, with enough information at the end to make a sound decision about whether the next step is a proposal, an RFP, or something else.