How ENVE cut invoice cycle time by 85% in their first month

The problem

The inbox was the system

ENVE's AP process started, and often stalled, in email. Someone had to comb through every message that arrived, decide which ones were real invoices, and judge for themselves whether anything looked off or fraudulent. Real invoices were then forwarded around the company for approval, one thread at a time. Follow-ups happened by hand. The status of everything lived on a tracking list that someone maintained manually. When a question came in (has this been paid? where is this invoice?), answering it meant digging back through the inbox.

The data entry on the other side was just as manual. Every invoice was keyed into SAP Business ByDesign by hand: the header first, then each line item, one at a time. A missed detail could send an invoice back through review, and an approval thread could sit in someone's mailbox for days. The process added delay without giving finance better control or better information.

Coding that demanded real context

What made ENVE's AP genuinely hard wasn't just volume. It was judgment. ENVE's coding is dimension-heavy: every line needs the right GL account, cost center, and project ID, together. The vendor alone does not determine the answer. The same vendor can be coded differently depending on the type of purchase order behind the invoice, so the person doing the entry had to understand the purchase, not just read the paper.

The hardest cases were the invoices from overseas manufacturing partners. A single one can run a dozen pages and more than 80 line items, every line carrying its own coding decision, and keying one could tie up an afternoon.

The solution

The integration nobody else would touch

Most AP vendors struggled to integrate with SAP Business ByDesign at all. Several told ENVE they could, then couldn't make the connection work. And the few platforms that did claim a ByDesign integration shared a second problem: none of them tackled the email side. The inbox triage, the fraud judgment, the approval threads, the follow-ups all stayed manual. Adopting one of those platforms would have meant a large internal change, with ENVE adjusting its own process to fit the software, and the inbox problem left standing.

Clerked took the opposite shape. Instead of ENVE adapting to a platform, ENVE deployed agents that adapted to ENVE. Getting started came down to three things:

1. Define a couple of agents for the work: one reading the inbox, one processing invoices.
2. Give the agents rules and context on ENVE's daily workflows, so they handle things the way ENVE does.
3. Give the agent access to read reference data from the ERP and push invoices back into it.

After that, the agent assimilated itself into ENVE's workflows: same process, same ERP, minus the manual work.

An agent that runs in the background

The agent works whether or not anyone is at a desk. An invoice that lands in the inbox at midnight or over the weekend doesn't wait for Monday. The agent picks it up the moment it arrives, reads it, codes every line, and matches it, typically within minutes of the email hitting the inbox. Dozens of ENVE's invoices arrive outside business hours, and they're processed exactly like the ones that arrive at 10 a.m. By the time someone would have opened the email, the invoice is already prepared and sitting ready for review.

The team doesn't have to watch the system, either. The agent comes to them. It sends notifications and emails when something is assigned to you or needs your decision, with quick actions built in so an approval is one click. If something arrives late or sits too long, it nudges the right person. The work finds the team instead of the team hunting for it.

Only real work reaches the team

The agent now runs the inbox that used to run the team. It reads everything that arrives, filters out the documents that aren't real invoices, and screens every document for duplicates and fraud signals before a person ever touches it. It has caught hundreds of duplicate submissions on its own.

The result is a team that only ever sees genuine decisions. 84% of invoices flow through the entire journey (read, coded, matched, and booked) without a single human correction. The team's review is a look, not a fix.

For the roughly 16% that do need a touch, ENVE's team rarely edits fields by hand. They tell Clark, the agent's copilot, what to change, and Clark computes the changes across the whole invoice at once. More importantly, the team corrects Clark the way you'd teach a person: not "change this GL," but "this vendor's freight lines usually go to this account." The agent turns that into a rule and applies it going forward, including when to flag something, hold it, or route it for review. ENVE's team uses Clark more than any other Clerked customer.

An agent trained on how ENVE works

The agent didn't start from zero. It studied ENVE's AP records in SAP and built a working memory of how ENVE actually operates: roughly 350 memories covering vendor coding patterns, GL rules, and exceptions. It codes lines the way ENVE codes them, assigning GL account, cost center, and project ID together, informed by the purchase context. When finance wants a consistent choice applied, they tell the agent the rule in plain English, and it follows that instruction on every future invoice.

Its knowledge stays current, too. The agent syncs ENVE's reference data from SAP nightly (vendors, purchase orders, GL accounts, cost centers, project IDs), so every invoice starts from the current state of the ERP rather than a list that drifts out of date.

Custom agents for the niche work

Some of the most annoying AP work is small, repetitive, and specific to how one company operates. At ENVE, invoices often arrive before the matching receipt or purchase order exists in SAP. Traditional software would leave them stranded until someone remembered to recheck. ENVE deployed a custom agent for exactly this: it watches for newly arrived receipts and POs and automatically re-matches and updates the waiting invoices. A niche chore that used to depend on someone's memory now simply happens in the background.

Accurate enough to turn on auto-approvals

Finance teams are trained to be skeptical, and ENVE started conservatively: a person approved every single invoice. But the agent shows its work. Every field on every invoice carries its provenance, every Clark change is explained, and the accuracy number held at roughly 98% month after month. Watching that for a few weeks changed the question from "can we trust it?" to "what is this extra click buying us?"

So ENVE turned on auto-approvals. Now, the moment someone in AP validates an invoice, the agent approves it under ENVE's policies and posts it straight to SAP, with no re-keying and no approval thread waiting in an inbox. A person still validates every invoice; the agent does everything else. The team went from reviewing everything to trusting the agent with the approval step itself.

The results

• ~85%

  Faster invoice cycle time

• ~98%

  Field-level accuracy on booked invoices

• 84%

  Invoices approved and untouched by humans

• 100%

  Approved invoices posted to SAP automatically

• 2.3x

  Now they're supporting 2.3x the original volume with the same two-person team.

What other manufacturers can take from ENVE

1. Don't adapt your process to AP software. Deploy an agent that adapts to your process, inside the ERP you already run.
2. The inbox is half the problem. If automation doesn't read, screen, and answer the email, your team still owns it.
3. Teach in plain English. Corrections phrased as rules compound; corrections typed into fields evaporate.
4. Let accuracy earn autonomy. Start with every approval human, watch the numbers, and promote the agent when the extra click stops buying you anything.

Clerked builds AP agents for high-volume, hard-asset businesses: manufacturers running real ERPs, real POs, and real receiving workflows. See it on your ERP →