Accounting & Finance Integration

CMap + Sage Intacct

Project billing, costs and expenses, posted straight into your general ledger.
Raised once in CMap: no manual entry, no double keying.
You choose what is sent, and when.

What the integrations does

Billing out. Costs out. Receipts back.

Invoices, supplier costs and expense claims move between CMap and Sage Intacct, posted to the right entity, location and department with the account codes you have mapped for sales, purchases and expenses.
CMap
→
Sage Intacct
CMap
↔
Sage Intacct
Sage Intacct
→
CMap
Push sales invoices
Invoices post into Sage Intacct with their lines, account codes, locations and tax entries. AEC firms keep their stage and section billing intact; consulting firms push line by line. A copy of the document can travel with them.
CMap
↔
Sage Intacct
Sage Intacct
→
CMap
CMap
→
Sage Intacct
Push purchase invoices
Supplier invoices post against the right supplier/vendor as an AP bill, carrying the account code, location and department you have mapped. New suppliers/vendors can be created, and their details kept current, on the way through.
CMap
↔
Sage Intacct
Sage Intacct
→
CMap
CMap
→
Sage Intacct
Push staff expenses
Reimbursable claims post against the claimant as an AP bill, or an adjustment where the claim nets to a credit. Non-reimbursable company spend posts as a journal entry against the offset code you set.
CMap
↔
Sage Intacct
Sage Intacct
→
CMap
CMap
→
Sage Intacct
Pull sales receipts
The amount paid is read back off the Intacct invoice and written to the CMap invoice, with the paid date taken from the receipt date recorded in Intacct.
Why it matters

No more manual entry. No more double keying.

CMap runs your projects; Sage Intacct runs your books. This integration keeps them in lockstep.
The right document, every time
Expense claims are the awkward case. CMap works out whether each one belongs in Intacct as an AP bill, a journal entry or an adjustment, so nobody has to remember the rule.
Built for multiple entities
Locations and departments come straight from Sage Intacct and map to your projects and people, each business unit carries its Intacct entity ID, and the exchange rate source is set separately per transaction type.
Posted, but not set in stone
Transactions arrive in Intacct posted rather than parked in a queue, and your finance team can still adjust them right up until you close the period.
Built and maintained by CMap
A core CMap integration with no third-party middleware, and no background sync running behind your back. You choose what is sent and when.
getting set up

Guided from first connection to go live.

Sage Intacct is the most configurable of our finance integrations, so setting it up is a guided, step-by-step process rather than a handful of switches. You work through it with your CMap consultant during implementation, or with our support team if you add it later. We make sure you have everything you need to go live on CMap and the Sage Intacct integration together.

Connect your Intacct company
Sign in with your Sage Intacct company ID, user ID and password.
Line up your records
Customer and supplier/vendor IDs against the right companies and users in CMap.
Map your ledger and set options
Account codes, departments, locations, entities, tax rates and class IDs, plus exchange rate sources, journal settings and the flags that suit how you run Intacct.

Frequently asked questions

Is the Sage Intacct integration included in my CMap plan?

Yes, from the Growth plan upwards. Accounting integrations are part of the standard feature set on the Growth, Pro and Enterprise plans, on both the Consulting and AEC editions, so there is nothing extra to buy.

How are customers and suppliers matched?

By code, not by name. Each CMap company holds the matching Sage Intacct customer ID as its Finance System Account Code, and the supplier/vendor ID as its Finance System Supplier Code, in both cases without the Sage prefix letter. Expense claimants hold their supplier/vendor ID on their user record. Invoices linked to a company without a code cannot be pushed.

Does it handle AEC stage billing as well as consulting invoices?

Yes. AEC invoices are built from their budget sections and additional items, so stage billing carries through to Intacct. Consulting invoices are built line by line. Both arrive in Sage Intacct in the same shape.

Does it work with Sage Intacct multi-entity?

Yes. Locations and departments are read live from your Sage Intacct company and mapped in CMap, and each CMap business unit carries its Sage Intacct entity ID. You can set location and department defaults per project and per user. Note that a push sends transactions to the entity linked to the business unit of the user running it, so multi-entity firms usually use a dedicated finance admin account.

Is it automatic, or do I run it?

You run it. All transfers are on demand from the Finance area, so you choose what is sent and when, and there is no background sync. Transactions are pushed as posted, but can still be edited in Intacct until you close the period they fall into.

What data syncs between CMap and Sage Intacct?

From CMap to Sage Intacct: sales invoices and credit notes with their lines, account codes, locations and tax entries; purchase invoices as AP bills; and staff expenses as bills, adjustments or journal entries. From Sage Intacct to CMap: the amount paid on each sales invoice and the receipt date it was settled on.

Does CMap integrate with Sage Intacct?

Yes. CMap connects directly to your Sage Intacct company. Sales invoices, credit notes, purchase invoices and staff expenses raised in CMap post into Sage Intacct, and the amounts paid on those invoices are pulled back. It is a core CMap integration, built and maintained by CMap with no third-party middleware.

integrations

CMap, embedded in your wider tech stack

Sage Intacct is one of CMap's finance integrations, included from the Growth plan upwards, on both the Consulting and AEC editions, alongside the accounting, CRM and collaboration tools your business already runs on.

View all integrations