Case study · Insurance · Invoice Processing
From Days to Hours: Invoice Processing in Insurance
Invoice Processing was the step everything else waited on. It now runs itself on the same stack — live in half a day, judgement calls still going to a person.
Invoice Processing Time
Process today's insurance invoices.
Acme Supplies
PO-4471 · matched
Northwind Co.
PO-4472 · matched
Initech LLC
price +6% vs PO
Meridian Group
no PO on file
3 AI agents · 5 tools connected · live in half a day · no code
- Company
- Insurtech company
- Team size
- 15-80 employees
- Industry
- Insurance
- Time to live
- Half a day
- Agents deployed
- 3 AI agents
- Tools connected
- 5 integrations
The context
Why Invoice Processing is hard in insurance.
Nothing about invoice processing is complicated on a single instance. What makes it expensive in insurance is volume arriving through submissions, ACORD forms, carrier portals, claims notices, and renewal lists, against the renewal date and the claims service standard. Miss the window and the cost is not the minutes — it is a renewal that lapses because a form sat in someone’s inbox.
Constraints the build had to hold
Forms are structured, and messy
Extraction is checked against each form type’s expected schema. Failures escalate rather than get guessed at.
Carrier rules differ
Each carrier gets its own branch inside one pipeline, rather than a pipeline nobody maintains.
Coverage decisions stay licensed
Anything constituting advice or a coverage determination is prepared for a licensed producer, never issued.
The change
Same job. Two chains.
Every handoff in the left-hand chain is somewhere Invoice Processing used to wait. The right-hand chain has the same steps and none of the waiting.
By hand
- Invoice hits the shared inboxin any format a vendor invents
- Header and lines keyedthen matched to the PO by eye
- Approval walked aroundstalls on one traveller
- Posted, days later
discount window already gone
With agents
- Work arrives on any channelpicked up in seconds
- Capture agenthanded straight on
- Matching agenthanded straight on
- Approval agent
logged, and reviewable
When the work can happen
Before and after
What Invoice Processing cost them, and what replaced it.
The challenge
This insurtech company was processing hundreds of vendor invoices a month by hand, and the process had all the failure modes you would expect. Duplicate payments that were only caught at reconciliation. Approvals that sat in an inbox while the approver was travelling. Line items matched to the wrong purchase order because two POs from the same vendor looked similar at a glance.
The full background
With 15-80 employees and a growing supplier base, the insurance team had two options as volume rose: add headcount to AP, or accept a longer cycle and worse controls. Neither was attractive. The finance lead put it plainly — the department was spending most of its capacity on the invoices that were completely routine, which left almost nothing for the small number that genuinely needed a human to look hard at them.
What they built
DeskFerry gave this insurance team an AP process that scales without headcount. Applied Epic, Gmail, and the team channel were connected in under two hours, and the extraction rules were tuned against a month of real invoices before anything went live.
How it was wired
Controls got stronger rather than weaker. Duplicate detection runs before the write, matching on vendor, amount, and invoice number rather than on filename. A first invoice from an unknown vendor is always reviewed by a person — the cheapest control against invoice fraud there is. Every posting writes an entry naming the source document, the rule applied, and the result, so month-end reconciliation reads a log rather than reconstructing a story. Close stopped waiting on AP because AP stopped being behind.
The impact
What changed, measured the same way on both sides.
Before and after across the metrics that matter for insurance Invoice Processing.
Invoice Processing Time
Dramatically faster
Processing Cost per Invoice
Major savings
Error Rate
Major reduction
Early Payment Discounts Captured
Significant increase
Monthly Invoice Volume
Major throughput increase
How these were measured
- Baseline
- The "before" column is the team’s own measurement of their manual invoice processing process, taken over the four weeks before anything was connected.
- Comparison
- The "after" column is the same measurement repeated on the same process once the agents were live, so both sides count the same things in the same way.
- Why no percentages
- These are composite scenarios built from patterns across many deployments, not one audited customer’s books. Directional language is the honest way to report that — your own numbers will depend on your volume, your process, and your starting point.
A day, either side
The same day, before and after.
What Invoice Processing actually looked like for this insurance team — the version they described in the first call, and the version they run now.
Before DeskFerry
9:00
Invoices arrive in a shared inbox. Print, stamp, key, file.
11:00
Match line items against the PO by eye. Two do not agree.
14:00
Chase an approver who has been in meetings all day.
Day 12
An early-payment discount expires unnoticed.
Month end
Close slips because the insurance ledger is still catching up.
After DeskFerry
9:00
Invoices were parsed and matched to POs on arrival overnight.
9:05
Clean matches are posted. Variances are queued with the discrepancy highlighted.
11:00
Approvals go to the right approver with one tap, chased automatically.
Day 2
Early-payment discounts are taken because nothing waited in a pile.
Month end
Close runs on a ledger that was never behind.
The build
The 3 agents that run it.
One job each, with an explicit handoff between them. Splitting Invoice Processing this way is what makes a failure legible — you can see which step it went wrong at instead of debugging one agent that does everything.
- 01
Capture agent
Trigger
An invoice arrives by email or portal
Extracts header and line items, identifies the vendor, and normalises the format regardless of who sent it.
Agent 1 of 3 in the Insurance workflow.
- Passes a structured invoice to matching.
- 02
Matching agent
Trigger
An invoice is captured
Matches lines against the purchase order and receipt in the ledger, and quantifies any variance rather than just flagging it.
Agent 2 of 3 in the Insurance workflow.
- Clean matches go to posting; variances go to a named approver with the difference highlighted.
- 03
Approval agent
Trigger
An invoice needs a human decision
Routes to the right approver by amount and cost centre, chases on a schedule, and escalates before the insurance payment term expires.
Agent 3 of 3 in the Insurance workflow.
How they did it
From nothing to production in half a day.
No code, no IT ticket, no vendor implementation team. These are the steps in the order this team took them.
Step 01
Mapped the current workflow
Every step of the manual invoice processing process, including exceptions — and which of them a person should keep.
Step 02
Built it in DeskFerry
Applied Epic and DocuSign as sources, insurance decision logic, automated actions and alerts.
Step 03
Ran it in parallel
One week alongside the manual process. Edge cases flagged for review rather than actioned.
The stack
Nothing was replaced. Everything was connected.
The insurance team kept the tools they already ran — DeskFerry sits between them.
Applied Epic
Policy, submission, and renewal state
Salesforce
System of record for accounts and pipeline; every write is scoped to owned fields
DocuSign
Signature events that start the workflow the moment a deal is real
Gmail
Where the work arrives, and where drafted replies go back out
Google Sheets
The lightweight ledger the team already reads, kept current automatically
Invoice Processing handled end to end · hours, every time
What stayed human
The parts they deliberately did not automate.
Automating Invoice Processing end to end was never the goal. Removing the volume so the judgement calls got proper attention was.
Every variance
Price and quantity differences against the PO are quantified automatically and approved by a person. Nothing that costs more than expected posts without someone agreeing to it.
New vendors
A first invoice from an unknown vendor is always reviewed, which is the cheapest control against invoice fraud that exists.
The policy renewal rates question
Asked first by every insurance team. Agents run on the access the staff account already had, every action is logged, and any step can be stopped without unwinding what ran.
Takeaways
What transfers to your team.
The parts of this that are not specific to one company's tooling or volume.
- 01
No technical expertise needed — the people who own the invoice processing process built it.
- 02
Capacity scaled without headcount, which changed the unit economics.
- 03
Every decision is logged, so the workflow can be audited rather than trusted.
- 04
Leadership got invoice processing numbers in real time for the first time.
In their words
“The difference is night and day. Our insurance clients used to wait days for invoice processing to be completed. Now it happens in minutes, and the quality is consistently higher than what we achieved manually. Customer satisfaction scores went through the roof.”
Composite — written from what teams running this workflow report, not a single named customer.
FAQ
Questions people ask about this build.
Automating Invoice Processing in insurance — what it takes, and where it stops.
How long does it take to set up invoice processing automation for a insurance business?
This team was live in half a day. Pre-built insurance templates cover the wiring, so most of that time goes on your business rules rather than on connecting things. No code.
How many AI agents does invoice processing automation actually need?
3 here: capture agent, matching agent, approval agent. The split matters more than the count — one job and one handoff each means a failure tells you which step broke. One agent doing everything does not.
What results can a insurance business expect?
The figures here are directional, not audited — composite scenarios, not one customer's books. What transfers is the shape: routine volume stops needing a person, exceptions surface instead of sinking, and nothing waits for office hours. Your numbers depend on your volume and starting point.
How does DeskFerry handle insurance data and access?
Agents run on the same access the staff account already had — throughput widens, permissions do not. Every action is logged with what it read and changed, and any step can be stopped without unwinding what ran. DeskFerry holds no formal insurance certification, so scope it as you would any other system in your control environment.
What still needs a person?
More than most automation pages admit. Anything outside the rules stops and goes to a named owner with context attached, rather than being guessed at. The rules themselves are changed by people — agents never widen their own tolerances. The carve-outs this team kept are named above.
What tools does this connect to?
1,500+ integrations. This build used Applied Epic, Salesforce, DocuSign, Gmail and Google Sheets; most insurance stacks are a variation on that. CRM, email, chat, databases, and industry-specific software all connect without code.
Run this in your own stack.
Describe how Invoice Processing should work at your insurance business, in a sentence. DeskFerry builds the agents, wires your tools, and takes the routine volume from there. Start free — no credit card.
Or start from a template — Invoice Processing agent for Insurance.
Keep exploring
Related case studies.
The same job in another industry, or another job in this one.
More Insurance case studies
Invoice Processing in other industries
Composite scenario — built from patterns across many insurance Invoice Processing deployments rather than one customer's books. Figures are directional; your own depend on your volume, process, and starting point.