View

Holded integration with Vergo: what syncs and how

Vergo connects to Holded through its public API and posts coded spend as purchases, payments, contacts and expense-account entries.

What does the Vergo + Holded integration do?

  • Coded card spend posts into Holded as purchase invoices with their payments recorded
  • Supplier invoices captured, coded and approved in Vergo, then posted through the purchases endpoint
  • Contacts created in Holded when a supplier or an employee payee does not exist yet
  • Accounts read out of Holded, so every transaction is coded to your own expense accounts before it lands
  • Reimbursements handled through the contacts-and-purchases path, since Holded has no expense claim object — the employee is set up as a payable contact and settles through the ledger you already run
  • Receipts read line by line by AI and attached to the entry, so review replaces re-keying
  • Vergo connects directly through the public Holded API — nothing needed from your team or the vendor

Card spend posted as paid purchases

Vergo codes each card transaction to the right account and posts it into Holded as a purchase with its payment recorded — on the cards your business already has, since Vergo does not issue cards.

AP automation as Holded purchase invoices

Captured supplier invoices post into Holded via the purchases endpoint against contacts Vergo creates when needed, with payments recorded when made.

Reimbursements through the contacts-and-purchases path

Holded has no expense claim object, so Vergo runs the claim and approval workflow and posts the coded entry with the employee handled as a payable contact.

App information

Developer
Vergo
Integration method
API
API type
REST
Deployment
Cloud
What syncs
Purchase invoices, purchase payments, contacts, expenses-account entries; accounts read out
How the connection is made
Self-serve: Vergo connects directly via the public Holded API — nothing needed from the customer or the vendor.

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 Holded?

Yes. Vergo connects through the public Holded API, self-serve, and posts coded spend into Holded as purchase invoices with payments, contacts and expenses-account entries.

Can Vergo post supplier invoices into Holded?

Yes. Captured invoices post via POST /api/v2/purchases against a contact Vergo creates if needed, and payments are recorded on the purchase via the payments endpoint.

What data syncs between Vergo and Holded?

Vergo reads accounts out of Holded, and posts purchases, purchase payments, contacts and expenses-account entries back in — coded card spend, AP and reimbursements.

How long does the Holded setup take?

Holded is hosted and the API is public, so setup is authorizing the connection and mapping accounts — no server work or partner approval.

Does Holded have built-in expense management?

Holded exposes expenses accounts but no expense claim object and no journal entry endpoint. Vergo runs coding, capture and reimbursement workflows and posts results through Holded's purchases and contacts endpoints.

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.