Do employee reimbursements work with TriNet HR Platform (Zenefits)?
Yes. TriNet HR Platform, the product formerly sold as Zenefits, is hosted and exposes an API that Vergo connects to. Access is partner-gated: OAuth applications are issued after TriNet app review, and Vergo handles that application. Nothing is required from your team beyond authorising the connection. The platform's API reference is published at developers.zenefits.com.
What actually moves between Vergo and the platform?
Vergo reads. The core API is explicitly read-only — GET requests, with no payroll endpoints — so Vergo pulls People, Employments, Companies and TimeDurations to keep employee records aligned, and makes no claim of writing back into TriNet HR Platform. Approved reimbursement claims are generated in the format the pay run expects, and your team loads them. That boundary is set by the platform, not by a limitation on Vergo's side, and it is better stated plainly than glossed over in a marketing sentence.
What does Vergo do before anything reaches the pay run?
The claim itself is where the work is. Reimbursements arrive as photographed receipts, mileage logs and late spreadsheets, and each one needs evidence, a category and an approval before it becomes a payment. Vergo moves that onto the phone: the employee submits where the spend happened, photographs the receipt into the record, and codes it to the department or category your business already uses. Approvers see the amount, the receipt and the coding together, so approval is a decision rather than a chase.
How does a team use this day to day?
Claims come in through the period instead of piling up at cut-off. Because Vergo reads People and Employments from the platform, submissions attach to the right employee and the right employment record without anyone maintaining a parallel roster. When the pay run comes around, whoever owns payroll receives an approved, evidenced set of reimbursements to load — with the receipts retained in Vergo if anyone later asks what a payment covered.
What does setup involve?
Vergo submits the app review and handles connection configuration. Your team's involvement is the mapping conversation: which Vergo expense categories correspond to which reimbursement types, and confirming employee records reconcile between the two systems. One session, then a validation batch before anything runs at volume.
What does Vergo not do?
Vergo does not replace TriNet HR Platform, and does not write into it. HR records, benefits and payroll processing stay where they are. Vergo covers the reimbursement claim before payroll sees it and hands over clean, approved, evidenced data.
What should you confirm before committing?
Ask who owns reimbursement approvals today, how long a claim takes from spend to payment, and how many claims each period are paid without a receipt on file. Vergo will walk a sample of your own claims through the process before you commit.
Does Vergo integrate with TriNet HR Platform (Zenefits)?
Yes. The platform exposes an API and Vergo connects to it. Access is partner-gated — OAuth applications are issued after TriNet review, which Vergo applies for.
Does Vergo write reimbursements into TriNet HR Platform?
No. The core API is read-only and carries no payroll endpoints. Vergo generates approved reimbursements in the format the pay run expects, and your team loads them.
What does Vergo read from the platform?
People, Employments, Companies and TimeDurations — enough to attach each claim to the correct employee and employment record without maintaining a separate roster.
Does Vergo replace TriNet HR Platform?
No. It remains the system of record for HR and payroll. Vergo handles reimbursement claims — capture, receipt, coding and approval — before they reach the pay run.
