How does Vergo connect to Infor LX?
Infor LX exposes documented interfaces and Vergo posts approved bills through them. The access model is customer-provisioned — your IT team enables the interface once in your own environment, then Vergo handles the mapping. The system runs on-premise, and the interface sits inside your environment alongside it. The vendor reference is Infor LX documentation.
What does AP automation with Infor LX replace?
The manual version is familiar: invoices arrive by email, someone saves them to a folder, a coder assigns company, division, and cost center, a manager approves by reply-all, and a clerk retypes the whole thing into Infor LX. Every hand-off is a place for an invoice to sit for a week.
Vergo captures the invoice, reads the header and line detail, applies the coding rules you set, and routes it for approval. Approved bills post into Infor LX over its API — the ERP still owns the ledger, the payment run, and the vendor master.
How does approval routing work?
Rules are set on the dimensions Infor LX already uses: amount thresholds, divisions and cost centers, and vendor. An invoice charged to one cost centre routes to the manager who owns it; anything above a limit escalates. Approvers act from email or the phone, and every approval is stamped on the bill so the audit trail travels with the document rather than living in an inbox.
Exceptions behave the same way. A bill that fails a match, arrives without a PO reference, or codes to an account nobody owns stops in Vergo with the reason attached. It does not reach Infor LX until a person resolves it, which is the point — the ERP should not be the place you discover a bad invoice.
What do manufacturing teams get out of it?
Teams are discrete manufacturers running LX on IBM i. The gain is timing: coded, approved payables appear against divisions and cost centers while the period is still open, so the accrual is a report rather than an estimate. Vergo also carries card spend and reimbursements on the same coding rules, which means one approval path instead of three.
How long does it take to get running?
Enabling API access on the LX side is the one task that belongs to your team. After that, Vergo maps the chart of accounts and your divisions and cost centers, loads the approval rules, and runs a parallel cycle before you cut over.
This is not an ERP project. Nothing is reconfigured inside Infor LX; Vergo reads the structure that is already there and posts against it, so the work is rule-setting and vendor onboarding rather than development.
Does Infor LX already do this?
Infor LX handles the payables ledger, the payment run, and the vendor master, and it does those well enough that replacing them is not the goal. What sits outside the ERP is the front half: receiving a document, reading it, deciding who approves it, and chasing the person who has not. Vergo covers that half and hands the finished bill to Infor LX.
Does Vergo post bills into Infor LX?
Yes. Approved bills are written into Infor LX through its documented interfaces. Your IT team provisions access once, then Vergo maps your chart of accounts and divisions and cost centers.
What happens to invoices that fail a match?
They stop in Vergo as exceptions with the reason attached, and nothing posts into Infor LX until a person resolves them. The ERP never receives a bill that has not cleared approval.
Can approval rules follow our divisions and cost centers?
Yes. Rules are built on amount thresholds, vendor, and the divisions and cost centers already defined in Infor LX, so routing matches your existing authority matrix rather than a new one.
How long does implementation take?
The dependency is your IT team enabling API access on the LX side. After that, mapping and rule setup typically run in parallel with one normal AP cycle before cutover.
