What can be said about MegaPay integration?
Only what is verifiable. Intelligo MegaPay is enterprise Irish payroll, now owned by SD Worx, and it publishes no public developer documentation. There is no API reference to cite and no object names worth listing, so Vergo names none and claims no write into MegaPay. Where a connection is possible, it goes through the vendor, and Vergo runs that conversation rather than handing it to the customer's payroll team.
What does Vergo do for MegaPay customers?
It takes on everything before the payroll entry. Employees photograph receipts when they spend, select the expense category and the cost centre or department, and submit from their phones. Claims route to the approver your structure defines, with your policy enforced at submission — receipt thresholds, category limits, approval authority by role.
At each reimbursement cut-off Vergo produces the period's approved claim list: grouped by employee, coded to the values your payroll expects, every line linked to its receipt image and its named approver. Payroll reviews and enters a list instead of assembling one from email.
Why does an enterprise employer care?
At enterprise scale, expense claims stop being an annoyance and become a control problem. Hundreds of small payments, approved inconsistently, coded by whoever was quickest, with receipts held in a dozen places. When an auditor asks how a category is controlled, the honest answer in a manual process is usually "by the person who checks them".
Vergo makes the control explicit: the rule is configured, applied at submission, and recorded. Exceptions are visible as exceptions rather than dissolving into the batch.
What does the audit record contain?
Per claim: the spender, the date, the amount, the purpose, the category and cost centre, the approver and approval time, and the receipt image. The record is immutable after the fact and searchable, which is what turns a revenue query into a search rather than a project.
What about mileage and subsistence?
Mileage is calculated from the journey at the rates you configure rather than typed in as a total. Subsistence and other category rules are configured once and enforced everywhere, so the policy that exists on paper is the policy the system applies.
What does finance see each period?
Reimbursement spend coded to the cost centre that incurred it, in the period it happened, with each line traceable to a receipt and a named approver. Categories that grow quietly stop being a monthly total someone assembles by hand and start being a number that can be trended and challenged.
It also makes staff turnover survivable: the reasoning behind an approval stays attached to the claim, so a question asked after the approver has moved on is answered from the record.
How long does setup take?
Employees can submit on day one. The configuration work is mapping expense categories and cost centres to the values your MegaPay entries use, and mirroring your approval hierarchy — both are settings, not development.
Does Intelligo MegaPay have public API documentation?
No. MegaPay publishes no developer portal or public API reference; integration is arranged through SD Worx as the vendor.
Does Vergo integrate with MegaPay?
Vergo connects with MegaPay for reimbursements. It prepares approved, coded and receipted claim lists per period and does not claim a direct write into payroll.
How are policy rules enforced?
At submission. Receipt thresholds, category limits and approval authority are configured once and applied to every claim, with exceptions visible rather than absorbed.
Is the claim record auditable?
Yes. Spender, amount, purpose, coding, approver and receipt are held together per claim, unchanged after the fact and searchable.
