What is the state of Humi's API?
Closed. Humi, now part of Employment Hero, runs a partners API in closed beta that is requested through vendor support rather than self-served from a developer portal. What third-party directories describe — employee reads, time-off reads, a GET on additional incomes, a POST for time worked — is unverified against vendor documentation and shows no reimbursement write endpoint.
So Vergo does not claim to write reimbursements into Humi. Access is arranged through the vendor's partner route, and Vergo runs that request rather than leaving a customer to chase it.
How does Vergo handle reimbursements for Humi customers?
By owning everything up to the payroll entry. Employees photograph receipts at the point of spend, pick the expense category and the department or cost centre, and submit from their phones. Claims route to the approver your structure defines. Policy rules run at submission, so a missing receipt or an over-limit claim is caught before it reaches anyone in payroll.
At your reimbursement cut-off, Vergo produces the approved claim list for the period — grouped by employee, coded to the values your payroll uses, each line linked to its receipt image and its named approver. Payroll works from a reviewed list rather than assembling one.
Why does this matter to a Canadian SMB?
Humi's customers are small enough that the payroll administrator is also the HR administrator and often the office manager. Expense claims are the task that expands to fill whatever time is left: chasing receipts, guessing at coding, waiting on a manager's reply, then retyping amounts that were already written down once.
Moving capture to the employee and approval to their manager cuts the payroll job to review. The saving is not dramatic per claim; it is dramatic per year.
What does the record look like afterwards?
Every claim keeps who spent, when, how much, what for, which category and department it was coded to, who approved it, and the receipt. That record is searchable and does not change after the fact, which is what makes a later question about a payment a one-minute answer.
What about mileage?
Mileage is calculated from the journey at the rate you configure, so the number reaching payroll is derived rather than asserted. The same approval path and receipt rules apply to every other category.
What does the payroll administrator stop doing?
Opening attachments, guessing at coding, chasing managers for a yes, retyping totals, and filing receipts somewhere they can be found again. All four of those steps are where numbers change and receipts disappear, and none of them require payroll expertise.
What remains is review and entry from a list that is already approved, already coded, and already receipted — which is the part of the job that actually needs the payroll administrator's judgement.
How do we start?
Invite employees, mirror your approval structure, and map expense categories and departments to match what your Humi payroll entries expect. Employees can submit on day one.
Does Humi have a public API?
Not an open one. The partners API is in closed beta and requested through Humi support; no public reimbursement write endpoint is documented.
Does Vergo write reimbursements into Humi?
No. Vergo prepares an approved, coded and receipted claim list each period; payroll enters the reimbursement amounts into the Humi run.
Who approves claims?
The manager your approval structure names. Approval happens in Vergo, before anything reaches payroll.
Are receipts kept?
Yes, attached permanently to the claim record along with the coding and the approval, and searchable later.
