Key takeaways
- ERP integration and a mapped coding structure — GL accounts plus the projects, departments or locations you track — must be in place before provisioning field users.
- Approval workflows should match your existing control structure, routing by project, amount, or GL account as needed.
- Pilots with a few teams or regions help surface issues before full rollout to every field team.
- Training and ongoing support are critical to driving adoption among field employees who work away from the office.
- Vergo's text-based system eliminates the need for app downloads and reduces onboarding friction for field teams.
Where should you go next?
- Learn more about Vergo Expense Management
- Learn more about Vergo AP Invoice Automation
- Learn more about Vergo Employee Reimbursements
What prerequisites are needed before onboarding field employees?
Before onboarding field employees, you need ERP access and admin credentials to sync data and provision users from your accounting or ERP system. Your coding structure should match the ERP: GL accounts plus the dimensions you report on, such as project, department, location, work order or customer — whatever your technicians, installers, sales reps or service crews actually charge to. Approval hierarchies must be defined, deciding who reviews expenses by project, cost center or employee level. Stakeholder alignment matters: field managers, supervisors and accounting must back the change to drive adoption. Without these prerequisites, field employees hit coding errors, approval delays or confusion about which project or cost center to charge, all of which slow adoption and create rework for accounting.
How do you implement the system step by step?
Start by integrating with your ERP or accounting software, mapping expense data to the right GL accounts and dimensions so transactions flow into the right places. Configure approval workflows from your defined hierarchy, routing by project, GL account, employee or dollar threshold as your structure requires. Provision field users with access tailored to their roles and the projects, regions or cost centers they work in. Pilot the system with a few teams or regions, gathering feedback from field staff about what works and what causes friction. Train on the new workflow, including in-person support and simple resources for employees who are rarely in the office. Monitor adoption, data quality and user feedback continuously, adjusting workflows, training materials and configuration as patterns emerge.
A practical example
A commercial HVAC service company rolling out expense management across fifteen service regions might start by integrating with its ERP and mapping GL accounts, departments and service projects. It configures approvals so expenses under $500 route to the regional service manager, while larger amounts need controller review. For the pilot, it picks three regions with engaged managers and trains those technicians over two weeks, watching which steps cause confusion. Feedback shows that sending receipt photos works well, but technicians struggle to pick the right project when they cover several customer sites in a day. The company refines training and adds visual guides. Vergo removes this friction by proposing the coding by inference from your own accounting structure and history, so new vendors are coded on first sight without rule libraries or keyword lists. After validating with the pilot group, it rolls out to the remaining twelve regions over the following month, using lessons learned to streamline training and support.
What are common pitfalls to avoid?
Ignoring field adoption is the most frequent mistake: rolling out a system without enough training and support leads to incomplete data and workarounds. Mapping the coding structure incorrectly to your ERP sends expenses to the wrong accounts or dimensions, requiring manual correction and undermining trust in the system. Skipping the pilot and deploying to every team at once amplifies workflow or configuration issues, making them harder to diagnose. Leaving field managers out of approval setup can produce routing that does not match how teams control spend, creating bottlenecks or bypasses. Delaying ERP integration and relying on manual entry defeats the purpose of automation, leaving accounting with the same rework as before and lowering the system's perceived value to field employees.
How Vergo handles this
Vergo simplifies field employee onboarding by letting employees handle everything by text message, with no app to download and no portal login. That removes the biggest adoption barrier for field teams who rarely use company software. Connecting your existing cards involves no card applications, no re-issuing, and no banking change, so employees keep using the cards they already carry. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project, or skip approval flows entirely and let policy flags catch only what breaks a rule. Vergo proposes the coding by inference from your own accounting structure and history, with no rule library to build and no keyword lists to maintain; new vendors are coded on first sight. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Transactions are ready to code the moment they happen, with no waiting for clearing, and once they clear they sync into your accounting or ERP software. Card spend, employee reimbursements, and AP invoices run through one coding model with the same coding, same review, and one reconciliation. Learn more at https://www.getvergo.com/products/expense-management
Related questions
Frequently Asked Questions
How long does it take to onboard field employees to a new expense system?
It depends on your ERP integration, approval design and pilot scope. With text-message submission there is no app to roll out, so most of the time goes to setup and a short pilot.
What are the most common issues with rolling out a new expense system?
The biggest pitfalls are too little buy-in from field managers, mapping GL accounts and dimensions incorrectly, and delaying the ERP integration — leading to manual data entry and poor adoption.
Do I need IT involvement to set up the expense system?
You'll need some IT support to connect your ERP and provision users, but the expense workflow itself can be configured and rolled out by your accounting and operations teams.
How does Vergo's expense system integrate with my ERP?
Vergo integrates with ERPs such as Business Central and QuickBooks, reading your GL accounts, projects and dimensions so expenses sync with full coding.



