How does Vergo's AP automation connect to Epicor BisTrack?
Through the Epicor BisTrack API. Customer-provisioned — the BisTrack API sits in your environment, so your IT team enables access once and Vergo takes it from there. Epicor BisTrack is a cloud or on-premise system whose API supports reads and writes, so approved bills post into Epicor BisTrack instead of being retyped from a PDF. The vendor documents the interface publicly (Epicor BisTrack API documentation).
Your chart of accounts and your jobs, branches and cost codes come from Epicor BisTrack itself, so the values on a bill in Vergo are the ones your accounting team already uses. Nobody invents a code.
What happens to a vendor bill in Vergo?
Bills arrive however vendors send them — email, PDF attachment, a forwarding address. Vergo reads the vendor, date, amount, invoice number and line detail off the document and presents it for review with coding pre-filled from how similar bills were handled before.
From there it follows your approval rules: by amount, by vendor, by department or project. Approvers see the bill itself alongside the coding, approve from their phone or email, and the audit trail records who approved what and when. A bill nobody has approved does not post.
Duplicate invoices are caught before approval rather than discovered during an audit, and bills sitting unapproved stay visible instead of quietly ageing in an inbox.
What posts into the ledger?
The approved bill: vendor, invoice number, date, amounts, line coding and the approval record. Because the Epicor BisTrack API supports writing, it lands as a posted payable rather than a draft awaiting re-entry, and the source document stays attached in Vergo for anyone who needs to see it later.
Vergo also reads from Epicor BisTrack, so the vendor list and the jobs, branches and cost codes an approver sees are the current ones. When accounting adds a code, it shows up in Vergo without anybody maintaining a second list.
What does the AP team stop doing?
Keying. The manual sequence — open the PDF, retype the header, split the lines across jobs, branches and cost codes, walk it round for a signature, then enter it in Epicor BisTrack — collapses into reviewing what Vergo has already prepared and approving it.
The second gain is visibility of committed cost. When bills are approved and posted as they arrive rather than in an end-of-month push, the payables picture in Epicor BisTrack is current, and anyone reviewing costs is not working around a stack of invoices that have not been entered yet.
Who is this for?
Teams on Epicor BisTrack with enough vendor bills that AP entry has become somebody's recurring job, and with approvals that currently happen over email or on paper. If bills need splitting across multiple jobs, branches and cost codes, the coding time saved is usually larger than the entry time.
Card spend and employee reimbursements run on the same Epicor BisTrack connection, so all three routes into the ledger share one set of coding rules and one approval trail.
Does Vergo work with Epicor BisTrack for AP?
Yes. Vergo connects through the Epicor BisTrack API, and approved vendor bills post into Epicor BisTrack with their coding applied.
How does Vergo know how to code a bill?
It pulls your accounts and jobs, branches and cost codes from Epicor BisTrack and pre-fills coding based on how comparable bills were treated, which the reviewer confirms or changes before approval.
Does this work whether BisTrack is cloud or on-premise?
Yes. BisTrack is deployed either way, and in both cases the API sits in your environment: IT enables access once and Vergo connects against it. The rest of setup is mapping — branches, jobs and cost codes — followed by a reviewed pilot batch.
Can a bill post without approval?
No. Nothing reaches Epicor BisTrack until it has cleared the approval rules you configure, and every approval is recorded against the bill.
