View

Macola integration with Vergo: what syncs and how

Vergo reads Macola through ECI's shared ERP API and posts coded entries into Macola.

What does the Vergo + Macola integration do?

  • Bring card transactions, employee reimbursements and AP invoices into one coding model for Macola
  • Read the chart of accounts and job structure out of Macola so spend is coded to your own structure
  • Code every transaction by AI inference from your accounting structure and history — no rule library to build
  • Read receipts line by line, predicting the coding from what was actually bought rather than the vendor name on the header
  • Show why each coding was chosen, so review is confirmation rather than re-coding
  • Post coded entries into Macola through its API — Macola stays the system of record
  • Work with the corporate, fuel and personal cards your business already holds — Vergo does not issue cards

Expense management on your existing cards

Every company card feeds one approval flow. Vergo codes each transaction to the right account, job or work order at the point of spend, then posts the entry into Macola.

Reimbursements coded like everything else

Employees submit claims from their phone; Vergo codes and approves them and syncs them to your payroll or AP for payment, and the entries reach Macola through the same sync as card spend.

AP capture ahead of the ledger

Supplier invoices are read on arrival, coded and approved before any entry is generated — Macola receives payables that are already decided.

App information

Developer
Vergo
Integration method
API
API type
REST
Deployment
On-premise
What syncs
Chart of accounts and job structure (read via ECI's ERP API); coded entries posted into Macola
How the connection is made
Customer-provisioned — the API access sits in your environment; your IT enables it once, then Vergo does the rest.

Security and compliance

Encryption

All data is encrypted in transit and at rest using AES-256 encryption.

Infrastructure

Vergo operates on SOC 2-compliant infrastructure with geographically redundant, continuous backups.

Access controls

Role-based access controls keep employees, approvers and finance in their own lanes.

Audits

Regular third-party security audits are conducted to maintain data protection standards.

Frequently asked questions

Does Vergo integrate with Macola?

Yes. Vergo reads your structure from Macola through ECI's ERP API and posts coded entries — card spend, reimbursements, AP — into Macola. Macola stays your system of record.

Can Vergo code card spend to Macola jobs and work orders?

Yes. Vergo reads your account and job structure through the API and codes each transaction at the point of spend, so nothing arrives at month end as an uncoded lump.

What data does Vergo read from Macola, and what comes back?

Vergo reads the chart of accounts and job structure via ECI's product-agnostic ERP API (published Swagger). It posts coded entries into Macola.

What does setup involve, given Macola is on-premise?

The API runs on ECI's shared developer portal and activation is the gate — your IT enables it once for your installation, and Vergo does the rest. Nothing is installed on your servers.

Does Macola have built-in expense management?

Macola is manufacturing ERP; it is where coded entries land. Vergo handles card feeds, receipts, coding and approvals in front of it.

Discover more integrations

Vergo integrates with every ERP and accounting software, plus the payroll platforms reimbursements flow through. Browse by industry.
Support

White-glove onboarding and customer support.