Syncing reimbursements with Computer Ease requires mapping each expense to job, phase, and cost code before any transaction posts to the GL. Vergo connects directly with Computer Ease, applying that cost code structure automatically so reimbursements land on the correct job without manual reclassification.
Prerequisites Before You Start
Before configuring any reimbursement sync with Computer Ease, have these elements in place:
- Admin access to Computer Ease. You need write permissions to the AP module and the ability to create or modify vendor records. Reimbursements typically post through AP as employee vendor payments.
- A finalized job and cost code structure. Computer Ease uses a job > cost code hierarchy. Every reimbursable expense must map to a valid job number and cost code — confirm these are current and complete before importing any data.
- A defined approval hierarchy. Decide who approves reimbursements before they reach the accounting team. In construction, approvals typically route through the project manager for job-specific expenses and a department head for overhead costs.
- Employee vendor records. Computer Ease processes employee reimbursements through vendor accounts. Each reimbursable employee must have a corresponding vendor record set up in the system.
- A chart of accounts mapping for expense categories. Identify which GL accounts correspond to common field expense types — fuel, materials, per diem, tools — so categorization is consistent from day one.
Step-by-Step: Syncing Reimbursements with Computer Ease
- Set up employee vendor records in Computer Ease. Create a vendor record for each employee who submits reimbursements. Use a consistent naming convention (e.g., last name, first name) and assign a vendor type that distinguishes employees from trade vendors for reporting purposes.
- Define your expense category-to-cost-code mapping. Build a reference table that translates expense categories (fuel, lodging, subcontractor meals, small tools) into Computer Ease cost codes. This mapping is the backbone of the integration — errors here cause job cost misreporting.
- Configure the AP entry template for reimbursements. Set up a repeatable AP voucher template in Computer Ease that includes fields for job number, cost code, and expense date. Standardizing the template reduces manual keying and enforces consistent data structure.
- Establish the data import format. If you're importing reimbursement data from an external system or spreadsheet, Computer Ease accepts structured import files. Define the required fields: vendor ID, invoice date, job number, cost code, amount, and description. Validate the format against a test import before going live.
- At this stage, decide whether approvals route by job or by cost threshold. Job-based routing works well for project-heavy firms; threshold-based routing (e.g., anything over $500 requires a PM sign-off) suits overhead-heavy environments. Document this logic so it can be enforced upstream before data reaches Computer Ease.
- Run a pilot with one project and one pay period. Select a single active job. Process one cycle of reimbursements end-to-end — submission, approval, import, and posting — before rolling out company-wide. Verify that costs appear on the correct job cost report in Computer Ease.
- Reconcile posted transactions against source receipts. After the pilot posting, pull the job cost detail report in Computer Ease and match each line to the original expense submission. Identify any coding errors and trace them back to the mapping table.
- Document the process and train accounting staff. Write a one-page SOP covering import file preparation, vendor ID lookup, and error handling. Field supervisors and PMs who code expenses need to understand how their cost code selections affect job cost reporting downstream.
Common Pitfalls to Avoid
- Incomplete cost code mapping before go-live. Importing expenses with unmapped categories forces manual reclassification in Computer Ease — a time-consuming fix that creates reconciliation risk.
- Skipping the pilot project. Going company-wide without a controlled test run means errors surface across dozens of jobs simultaneously, making root-cause analysis difficult.
- Not configuring employee vendor records in advance. Missing vendor IDs cause import rejections. Discovering this mid-cycle delays reimbursement payments and erodes field team trust in the process.
- Ignoring field team adoption. If crews submit expenses on paper or in inconsistent formats, the data reaching your import file will be unreliable regardless of how well Computer Ease is configured.
- Timing ERP sync to close cycles. Avoid initiating a new integration setup during month-end close. Posting errors during a close period can affect WIP schedules, overbilling calculations, and financial statements.
How Vergo Simplifies This
Vergo is a construction finance platform with a native integration to Computer Ease, along with Sage 100/300, Viewpoint Vista/Spectrum, Procore, Foundation, QuickBooks, Acumatica, CMiC, COINS, Epicor, Jonas, and Deltek. The job code mapping described in Step 2 is handled automatically through Vergo's ERP sync — expense categories are matched to your existing Computer Ease cost codes without manual spreadsheet maintenance.
How Vergo Helps
Vergo is a card-agnostic expense management platform built for construction. Connect any corporate or project credit card and get full visibility and control over field spending.
- Job-cost coding at the point of capture — field teams assign job number, cost code, and cost type from their mobile device before the receipt leaves the job site.
- Per-job spend controls — set card limits by project, cost code, or cardholder so spending stays within approved budgets.
- Mobile receipt capture — superintendents and PMs photograph receipts on-site with automatic data extraction.
- Role-based approval workflows — route expenses through project managers, job-level approvers, and controllers based on your org structure.
- Vergo integrates natively with major construction ERPs, syncing coded expenses directly into job cost and general ledger without manual re-entry.
Related Questions
Frequently Asked Questions
How long does it take to implement a reimbursement sync with Computer Ease?
Most construction accounting teams complete the setup in two to four weeks. The largest time investment is building the expense category-to-cost-code mapping and cleaning up employee vendor records. Running a single-project pilot before full rollout adds a week but significantly reduces errors at scale.
Does syncing reimbursements with Computer Ease require IT involvement?
Not always. Computer Ease AP imports are file-based and manageable by accounting staff with admin credentials. IT involvement is typically needed only if you are connecting an external system via API or automating file transfers through a scheduled task or middleware layer.
What causes reimbursement import errors in Computer Ease?
The most common causes are missing or inactive vendor IDs, invalid job numbers, and cost codes that no longer exist in the system. Validating the import file against active Computer Ease records before posting — rather than after — catches the majority of errors before they affect job cost reports.
How should construction reimbursements be categorized for job costing in Computer Ease?
Each reimbursement line should carry a job number, a cost code, and a cost type — typically labor burden, equipment, or general conditions depending on the nature of the expense. Per diem and travel are often coded to a dedicated overhead job or a G&A cost code rather than a billable project.
Can Vergo automate the reimbursement-to-Computer Ease posting process?
Yes. Vergo's native Computer Ease integration maps approved reimbursements to job numbers and cost codes automatically, then posts them directly to the AP module. This eliminates manual import file preparation and reduces the accounting team's data entry workload while keeping job cost data current in real time.
What approval workflow should construction firms use for field reimbursements?
Best practice is a two-step approval: the project manager approves job-coded expenses before they reach accounting, and the accounting manager reviews for coding accuracy before posting. Firms with high reimbursement volume often set a dollar threshold — below it, PM approval alone is sufficient; above it, a controller review is required.