Invoice processing · Production

Beyer Mechanical reduces invoice processing time by 60% and transforms month-end close with Stampli

The problem

Beyer Mechanical's AP clerks manually coded and routed 1,500 invoices per month using PaperSave, which was not integrated with their Sage Intacct ERP. Each PO lookup caused a 15–20 second system stall, PO matching was unreliable, duplicate invoices went undetected, and the lengthy individual-approval process meant books could not be closed on time.

First attempt

PaperSave spent 45 days attempting to integrate with Sage Intacct and failed, leaving PO matching unreliable and duplicates undetected.

Workflow diagram · grounded in source
1
Invoice capture via AI
Trigger
The automated AP process begins with AI-powered invoice capture.
▾ source quote
“Stampli has enabled the AP process to be fully automated, leveraging AI from invoice capture”
2
AI coding and approver selection
Ai action
Stampli's AI learns vendor invoices and automatically handles coding and approver selection.
▾ source quote
“Stampli's AI learns our vendors and the invoices they send, taking a lot of onus off the AP clerks”
3
Nightly PO import
Integration
Service contract POs generated by a third party are imported into Intacct nightly.
▾ source quote
“service contract POs generated by a third party get imported nightly”
4
AP clerk review
Human review
AP clerks evaluate whether each invoice is a full or partial invoice.
▾ source quote
“The only thing the AP clerks need to do is evaluate if it's a full or partial invoice, and that's been the biggest time saver for us from the AP process”
5
Send approved invoices to Intacct
Output
Approved invoices are sent to Intacct for payment.
▾ source quote
“sending approved invoices to Intacct for payment”
Reported outcome

Stampli reduced invoice processing time by 60%, cut the invoice lifecycle to 48 hours or less, enabled month-end close by day 10, improved AP clerk resource efficiencies by 33%, and compressed monthly AP processing from approximately 50 hours to half an hour.

Reported metrics
Invoice processing time reduction60%
Invoice lifecycle48 hours or less per invoice
Previous invoice lifecycleat least five days
Month-end close achieved by dayday 10
Show all 14 reported metrics
invoice processing time reduction60%
invoice lifecycle48 hours or less per invoice
previous invoice lifecycleat least five days
month-end close achieved by dayday 10
invoices in at month close100%
invoice approval speed improvement60X faster
previous invoice approval time60 to 120 seconds
current invoice approval timeone second
monthly AP processing timeapproximately 50 hours per month can now be done in half an hour
AP clerk resource efficiency improvement33%
Sage Intacct integration timeless than 48 hours
monthly invoice volume1,500 invoices
PO lookup system stall time15-20 seconds
PaperSave integration attempt duration45 days
Reported stack
StampliPaperSaveSage Intacct
◆ Does this fit your context?

Compare to your context

Tell us your scale, team, and constraints. We'll show what changes at your size, what fails at your scale, and whether this case is a fit, needs adaptation, or won't scale to you. Free demo, no signup.

Compare to your context →
~30 seconds · free
Source
https://www.stampli.com/case-studies/beyer-mechanical/
Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

Stampli reduced invoice processing time by 60%, cut the invoice lifecycle to 48 hours or less, enabled month-end close by day 10, improved AP clerk resource efficiencies by 33%, and compressed monthly AP processing fr…

What tools did this team use?

Stampli, PaperSave, Sage Intacct.

What results were reported?

Invoice processing time reduction: 60%; Invoice lifecycle: 48 hours or less per invoice; Previous invoice lifecycle: at least five days; Month-end close achieved by day: day 10 (source-reported, not independently verified).

What failed first in this deployment?

PaperSave spent 45 days attempting to integrate with Sage Intacct and failed, leaving PO matching unreliable and duplicates undetected.

How is this invoice processing AI workflow structured?

Invoice capture via AI → AI coding and approver selection → Nightly PO import → AP clerk review → Send approved invoices to Intacct.

Related invoice processing cases

WHAT TO DO WITH THIS

Now compare it to your context

This case is one data point. Whether its pattern fits you depends on your volumes, your stack, and your exception load — that comparison is the step no case study can do for you.

Browse the Invoice processing cases →