Key takeaways
- CMiC supports employee expenses coded to company, job, cost code and category, with reimbursement through payroll.
- CMiC's eXpense mobile app, which let employees photograph receipts and submit them for approval, reached end of support on December 12, 2025. CMiC recommends Construct ESS - Expenses instead.
- CMiC's Imaging module imports card and expense transactions from outside providers as a data file plus images, and creates AP invoices with the images linked. That is a file import, not a live card feed.
- CMiC Workflow provides configurable approval routing aligned to company policies.
- Vergo works with any card from any bank, collects receipts by text, codes each line to job, phase, cost code and category, and posts coded card spend into CMiC.
Where should you go next?
- See the Vergo + CMiC integration
- How to automate expense management in CMiC
- Learn more about Vergo Expense Management
- Get started with Vergo
What CMiC includes for expenses
Partly. CMiC supports employee expenses coded to company, job, cost code and category, reimbursed through payroll. Expenses submitted from the CMiC eXpense app went to the relevant administrator for approval, and the app let employees photograph receipts and validate amounts. However, support for the eXpense app ended on December 12, 2025, and CMiC points users to Construct ESS - Expenses, which is not documented on CMiC's public pages. No receipt OCR is described.
For card spend, CMiC's Imaging module imports card and expense transactions from outside card and expense providers (a comma-delimited data file plus a ZIP of images) and creates AP invoices with the images linked. CMiC Workflow handles configurable approval routing. Bank feeds are not confirmed on CMiC's public pages.
Where a separate tool still helps
Even with CMiC's expense coding in place, someone still has to collect each receipt and decide the job, phase, cost code and category for every card line, often a superintendent choosing from a long list. Card spend that arrives as a file import is coded after the fact.
How Vergo handles this
Vergo works with any card from any bank — connecting your existing cards involves no card applications, no re-issuing and no banking change. Employees send receipts by text or from their phone, and Vergo chases missing receipts itself instead of waiting for a report. Vergo proposes the coding by inference from your own accounting structure and history — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought — the job, phase, cost code and category — not just the vendor name on the header, and every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. 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. For CMiC, Vergo's live integration covers expense management: coded card spend and its receipts posted into CMiC.
Frequently Asked Questions
Does CMiC have built-in expense management?
Partly. CMiC supports employee expenses coded to company, job, cost code and category, reimbursed through payroll, but its eXpense mobile app reached end of support on December 12, 2025. CMiC recommends Construct ESS - Expenses instead.
What happened to the CMiC eXpense app?
CMiC ended support for the eXpense app on December 12, 2025 and points users to Construct ESS - Expenses.
Can CMiC bring in card transactions?
Yes, as file imports rather than a live feed. CMiC's Imaging module imports card and expense transactions from outside providers and creates AP invoices with the images linked.
What does Vergo add for CMiC?
Card spend from any card and any bank, receipts collected by text, and coding to job, phase, cost code and category by inference from your history, posted into CMiC.
