Vergo connects with Aurion using the web services enabled in your own Aurion environment, and prepares approved employee reimbursements in the import format your pay run expects. Because Aurion's reference documentation is not public, the interface details are confirmed during onboarding.

Yes. Claims are collected with receipts, coded to your cost centre structure, and approved in Vergo. Approved amounts are prepared as a documented batch in the import format your Aurion pay run expects.

That depends on what the access enabled for your organisation exposes, since Aurion's reference documentation is not public. In every case Vergo produces approved reimbursements in the pay-run import format; where the enabled services allow reading employee and cost centre data, Vergo uses it for matching and coding.

The access is enabled in your own Aurion environment, so timing depends on how quickly your IT completes that one step. Vergo takes it from there and configures approval routing and coding in parallel.

Aurion advertises REST and SOAP web services, but the reference documentation is not published — the access is enabled within your own environment. Vergo confirms the available interface rather than assuming it.