What does the Vergo + xTuple PostBooks integration do?
- Sync card transactions, employee reimbursements and AP invoices into xTuple PostBooks through one coding model
- Read G/L accounts, posted G/L transactions, vendors and projects out of xTuple PostBooks so spend is coded to your own structure, not a generic chart
- Code every transaction by AI inference from your accounting structure and history — no rule library to build, and new vendors coded on first sight
- 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 spend into xTuple PostBooks as vouchers, with vendors created when a payee is new; PostBooks stays the system of record
- Work with the corporate, fuel and personal cards your business already holds — Vergo does not issue cards
Expense management coded to your projects
Card transactions from the cards you already hold arrive in Vergo, are coded to G/L account and project, and post into PostBooks as vouchers — no statement re-keying.
AP automation through the voucher workflow
Supplier invoices are captured and matched to vendor records, then posted via voucher/create and voucher/post so they are ready for the normal payment run.
Reimbursements through employee-as-vendor vouchers
Approved out-of-pocket expenses post as vouchers against an employee vendor record, settling through the same AP process as supplier bills.
App information
Security and compliance
Encryption
Infrastructure
Access controls
Audits
Frequently asked questions
Does Vergo integrate with xTuple PostBooks?
Yes. Vergo connects through xTuple's public REST API and posts spend into PostBooks as vouchers — no involvement needed from xTuple or your IT team.
Can Vergo handle AP automation for xTuple PostBooks?
Yes. Supplier invoices are captured in Vergo, coded, and posted through voucher/create and voucher/post, with vendor/create used for new payees.
What data syncs with xTuple PostBooks?
Vergo reads glaccount, gltransactions and project records, and writes vouchers, voucher payments and vendors. Expenses are coded to your existing G/L accounts and projects.
How long does setup take with an on-premise PostBooks instance?
Connection is self-serve against your instance's API. Setup is typically a single session: authenticate, map accounts and projects, and start posting.
Does xTuple PostBooks have built-in expense management?
PostBooks handles vouchers and AP once data is in the system. Card feeds, receipt capture, approvals and expense coding happen upstream — that is the layer Vergo provides.
Discover more integrations
.png)
.png)
.png){kind=logo}
.png)
White-glove onboarding and customer support.
