Why are reimbursements the last manual process in an ECC finance team?
Because they start outside every system. An employee pays for parking, a client lunch, a part, a hotel — and the record exists only as a receipt in a coat pocket. By the time it reaches finance it is a photocopy stapled to a form, weeks old, with no context. ECC handles the eventual posting perfectly well; the problem is everything that happens before the posting. Vergo moves the capture to the moment of spend, on the phone the employee already has.
How does a claim move through Vergo?
The employee photographs the receipt. Vergo reads the merchant, date and amount, and the employee selects the cost center and GL account. The claim goes to the approver who owns that cost center. Once approved, Vergo reimburses the employee directly to their bank account and posts the coded expense into SAP ECC. Mileage is handled the same way, with a rate applied to the distance rather than a hand-calculated figure on a form.
How does Vergo connect to SAP ECC?
SAP ECC is on-premise, so the interface sits inside the customer's own environment. The customer's IT team enables access once — the standard SAP interface layer, scoped to the company codes in question — and Vergo does the rest of the work from there. There is no partner queue to wait in and no vendor approval to chase, because the system belongs to the customer. SAP's own learning and documentation portal is at learn.sap.com.
Why keep reimbursements out of payroll?
Reimbursements pushed through payroll arrive on a payroll cycle, which can be a month after the employee spent their own money, and they arrive mixed into a payslip where nobody can see what was reimbursed for what. Paying them separately means the employee is repaid within days and the expense is coded to the cost center that incurred it, rather than to a payroll clearing account that finance untangles later.
What stops claims from becoming a policy argument?
Rules stated in advance. Per-category limits, a receipt requirement above a threshold, and a defined mileage rate are applied when the claim is submitted, so an employee learns immediately that a claim exceeds policy rather than three weeks later in a rejection email. Approvers see the receipt alongside the claim, which is the only evidence that ever mattered.
How does this reduce claim volume in the first place?
The cheapest reimbursement is the one that never happens. Most out-of-pocket spend exists because the employee had no company card for that purchase. Issuing a controlled Vergo card — limited by amount, category and duration — removes the claim entirely for recurring or predictable spend, leaving reimbursements for the genuinely unplanned.
What does finance have to set up?
The cost center and account mapping, the approval thresholds, and the reimbursement policy limits. IT enables ECC interface access once, since the system is on-premise in the customer's own environment. After that the process runs itself and finance reviews exceptions.
How quickly are employees reimbursed?
Vergo pays approved claims directly to the employee's bank account rather than waiting for a payroll run, so repayment happens within days of approval.
Does the reimbursement post into SAP ECC?
Yes. The approved claim posts into SAP ECC coded to the company code, cost center and GL account chosen when the claim was submitted.
Are mileage claims supported?
Yes. Distance is captured on the claim and the configured rate is applied automatically, so employees are not calculating figures by hand.
Can we cut the number of claims we process?
Usually, yes. Most out-of-pocket spend happens because no card was available. Issuing limited-purpose Vergo cards moves that spend onto a controlled card and out of the claims process.
