CMiC + Go Fig
Connect CMiC to Go Fig for daily job cost, committed cost, and WIP reconciled across one construction ERP and loaded into the Excel your finance team already uses.
CMiC is a single-database construction ERP that larger contractors use to run financials and project controls together, but even with one database the answers a controller actually needs (actual vs estimate by job and cost code, committed costs against the GL, retainage, and a current WIP schedule) still tend to mean a CMiC report, an Excel export, and a private workbook that goes stale within days. Go Fig does not replace CMiC. It connects to your CMiC data, syncs the job cost, general ledger, accounts payable, accounts receivable, and subcontract detail, reconciles it against your other systems, and loads fresh, traceable job-cost data into the Excel your project accountants already use, automatically, every day. Celeste, Go Fig's AI analyst, can then answer 'which jobs are trending over at completion' with a real audit trail back to the cost code and transaction. Your financial data stays in your environment. It is never pasted into a public chatbot and is never used to train an outside model. Celeste works only on your data, with a full audit trail.
Key facts
- System role
- Connects to CMiC, does not replace it
- Sync grain
- Cost code and transaction level
- Reconciliation
- Committed cost and retainage vs GL
- Historical backfill
- Multi-year job-cost and GL detail
- Auth
- Read-only service account via CMiC API or Oracle DB
What you can do with CMiC data in Go Fig
Actual vs estimate by job and cost code
CMiC job-cost estimate, committed, and actual amounts pulled together so a project accountant sees remaining budget by job, phase, and cost code every morning, instead of running ERP reports and rebuilding the variance in a private spreadsheet. Overruns surface early, not at close.
Committed cost and subcontract reconciliation
Open subcontracts and purchase commitments reconciled against AP invoices and the GL, so the committed-cost figure in the WIP schedule ties to the actual contracts and vendor invoices rather than report views that lag behind the postings.
WIP, retainage, and over/under billing daily
Cost-to-date, estimated cost at completion, AR contract billings, and retainage combined into a WIP schedule that refreshes every day. Percent complete, earned revenue, and over/under billing stay current so bonding capacity is sized off a live schedule across the whole portfolio.
Data available from CMiC
Go Fig extracts and normalizes the following data from your CMiC account:
How to connect CMiC
Provision a read-only CMiC service account
Create a dedicated read-only service account scoped to the job cost, GL, AP, AR, and subcontract data you want exposed, through either CMiC's API or its Oracle database. Keep it separate from your human operators so audit trails stay clean and confirm the endpoint or database is reachable from the connector.
Confirm your company and ledger structure
Confirm which CMiC company and ledger contain the jobs and accounts you want to sync. Multi-company contractors can scope one connection per company and consolidate across them in Go Fig.
Pick the historical window
Choose how far back to backfill. Three to seven years of job-cost and GL detail is typical for larger contractors rebuilding job-cost trends, retainage history, and WIP before switching to daily incremental sync keyed on transaction date.
Wire up the job-cost and WIP flows
Go Fig ships starter flows for actual vs estimate by job, committed-cost reconciliation, retainage, and a daily WIP schedule. Point them at your CMiC connection and the controller has a working monthly close pack on day one, with drill-down back to cost code and transaction detail.
Authentication: CMiC runs on an Oracle database and also exposes integration APIs. Go Fig connects either through CMiC's API or directly to the database using a dedicated read-only service account scoped to the job cost, GL, AP, AR, and subcontract data you want exposed, separate from your human operators so audit trails stay clean.
Common Questions About CMiC Integration
Does Go Fig replace CMiC?
No. CMiC stays your construction ERP and system of record for financials and project controls. Go Fig connects to it, reconciles CMiC's job-cost and GL data against your other systems, and loads fresh, traceable job-cost data into the Excel your finance team already uses. Your project accountants keep working exactly as they do today.
CMiC is already one database. What does Go Fig add?
A single database keeps your modules consistent, but the controller still rebuilds the WIP, the variance, and the committed-cost reconciliation in Excel every month off ERP reports. Go Fig loads that fresh and traceable into the Excel your team already uses every day, and reconciles CMiC against the other systems that live outside it, such as banking, bonding, and any specialty project tools.
Can Go Fig produce a daily WIP and handle retainage?
Yes. Go Fig combines cost-to-date and estimated cost at completion with AR contract billings and retainage held to produce a WIP schedule that refreshes every day. Over/under billing and retainage land in your Excel automatically, so you stop rebuilding the WIP by hand each month and bonding capacity is sized off a live schedule.
Is our financial data safe with Celeste?
Yes. Your financial data stays in your environment. It is never pasted into a public chatbot and is never used to train an outside model. Celeste, Go Fig's AI analyst, works only on your data and every answer carries a full audit trail back to the underlying job, cost code, or transaction.
How current is the CMiC data inside Go Fig?
Daily incremental sync is the default, keyed on transaction date, so each morning the finance team opens an Excel that already reflects yesterday's job-cost, AP, and AR activity. Contractors in active billing cycles can sync more frequently if the on-call analyst needs near-real-time job-cost visibility.
