Accounts payable · Production

Why Stonewall Kitchen chose Vic.ai for AP automation

The problem

Stonewall Kitchen's AP team manually processed invoices in Microsoft Dynamics Business Central and struggled to keep pace with growing operational demands, leading a new CFO to prioritize modernization and a search for efficiency gains.

Workflow diagram · grounded in source

Invoice received for AP processing

trigger

“The Stonewall Kitchen AP team, processing invoices manually in Microsoft Dynamics Business Central, struggled to keep pace with the team's growing needs”

AI-powered invoice processing

ai_action

“Vic.ai delivers true AI-powered automation, completely removing the manual effort behind invoice processing and enabling "touchless" AP workflows”

AI-driven PO matching

ai_action

“Stonewall Kitchen saw the value in Vic.ai's AI-driven invoice and PO matching capabilities — an area they had struggled with for years in Microsoft Dynamics Business Central”

ERP data integration

integration

“improving data accuracy in Microsoft Dynamics Business Central”

Payment automation output

output

“Positioning to expand with payment automation as part of their longer-term goals with Vic.ai”

Reported outcome

Stonewall Kitchen selected Vic.ai and is positioned to achieve touchless invoice processing, automated PO matching, and scalable AP operations without adding headcount — these are anticipated outcomes, not yet confirmed production results.

Reported metrics

Manual workloadsignificantly reducing manual workloads

headcount required for growing AP workloadshandle growing workloads without adding headcount

Invoice processing efforttouchless invoice processing

Institutional knowledge dependencyreducing institutional knowledge dependency

Reported stack

Vic.aiMicrosoft Dynamics Business Central

Source

https://www.vic.ai/resources/case-studies/why-stonewall-kitchen-chose-vic-ai

Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

Stonewall Kitchen selected Vic.ai and is positioned to achieve touchless invoice processing, automated PO matching, and scalable AP operations without adding headcount — these are anticipated outcomes, not yet confirm…

What tools did this team use?

Vic.ai, Microsoft Dynamics Business Central.

What results were reported?

Manual workload: significantly reducing manual workloads; headcount required for growing AP workloads: handle growing workloads without adding headcount; Invoice processing effort: touchless invoice processing; Institutional knowledge dependency: reducing institutional knowledge dependency (source-reported, not independently verified).

How is this accounts payable AI workflow structured?

Invoice received for AP processing → AI-powered invoice processing → AI-driven PO matching → ERP data integration → Payment automation output.