Source ERP · 90 of 105

CRMPro → Salesforce — Sage Intacct: what the shipped templates set up

This is the capability summary the dlake CLI repository publishes; whitelisted customers fetch the operational skill with "dlake admin get_skill dlake-crmpro-salesforce/erps/sage-intacct". It extends the dlake-crmpro-salesforce skill, which holds what is true whatever the source ERP. Both directions for this pair are summarised at /integrations/sage-intacct-salesforce/.

CRMPro → Salesforce — Sage Intacct: what the shipped templates set up

This is a capability summary, not an operating guide. To receive the operational skill you must be a registered, whitelisted Commercient customer. Whitelisted customers fetch it with dlake admin get_skill dlake-crmpro-salesforce/erps/sage-intacct (or list_skills) against the Commercient admin plane. Existing customers who need access or help: contact support@commercient.com. New customers: contact sales@commercient.com to become a customer and be whitelisted.

dlake-crmpro is the parent skill and the authority for everything general: the CRMPro tools, process configuration and field list, the sync history, how source data is selected, and what a run that finds nothing does. Read it first; this page does not repeat it. dlake-crmpro-salesforce is the destination skill this page is a child of, and the authority for the Salesforce conventions that hold across every ERP: read it first, then come back here for what this source’s own templates set. This page grows as the catalogue does.

1. What the templates deliver

GroupBusiness outcomeObjectsSource tables and views
Employee SyncERP Employee data becomes Commercient Sage Intacct Employee Managed Custom Object in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.Commercient Sage Intacct Employee Managed Custom Objectemployees
Warenouse MasterERP Warehouse data becomes Commercient Sage Intacct Warehouse Managed Custom Object in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.Commercient Sage Intacct Warehouse Managed Custom Objectwarehouses
AccountIn addition to creating the Account record from your ERP customer records, Commercient syncs over the entire Accounting AR Customer record into a Commercient AR Customer object which is a Managed Custom Object (MCO). A lookup field is provided to lookup to the default AR Customer record MCO from the Account record. New records are created, existing ones updated, and records removed in the ERP are deleted.Account, Commercient Sage Intacct AR Term Managed Custom Object, Contact, Commercient Sage Intacct Customer Managed Custom Objectcustomers, the writeback transaction log, AR terms, contacts, employees
CRM OwnershipThe templates push User to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.User—
ProductERP Item, warehouse details per item, Warehouse data becomes Commercient Sage Intacct Item Managed Custom Object, Commercient Sage Intacct Item Warehouse Information Managed Custom Object, Product in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.Commercient Sage Intacct Item Managed Custom Object, Commercient Sage Intacct Item Warehouse Information Managed Custom Object, Productitems, item warehouse information, warehouses
InvoiceBoth Open and Historical invoices are synchronized. Open invoice changes, such as a balance change, or a terms change are reflected in the CRM as they sync based on the frequency of the sync you have chosen (every hour, for example). New records are created, existing ones updated, and records removed in the ERP are deleted.Commercient Sage Intacct AR Invoice Managed Custom Object, Commercient Sage Intacct AR Invoice Item Managed Custom Object, Commercient Sage Intacct AR Invoice Payment Managed Custom ObjectAR invoices, AR invoice lines, items, AR invoice payments
Sales orderCommercient will sync the Sales Orders from the ERP Sales Order Entry module to the Commercient Sales Order Header (MCO) objects in CRM. In the CRM, customer service and sales people can visualize the status of the order such as on hold, backorder, forward order, scheduled for delivery, whether it has shipped, and completion status. New records are created, existing ones updated, and records removed in the ERP are deleted.Commercient Sage Intacct Sales Order Document Managed Custom Object, Commercient Sage Intacct Sales Order Document Entry Managed Custom Objectsales order documents, sales order document lines, items

2. The process rows the templates create

Each template’s setup writes one process configuration row. These are the values it sets; a column the inserts never set is not listed.

Display nameDestination objectMatching keyRun sequence
Get AccountAccountCommercient AR customer code1
Employee SyncCommercient Sage Intacct Employee Managed Custom ObjectCommercient external key2
AccountAccountCommercient AR customer code3
TermCommercient Sage Intacct AR Term Managed Custom ObjectCommercient external key4
Customer MasterCommercient Sage Intacct Customer Managed Custom ObjectCommercient external key5
Warenouse MasterCommercient Sage Intacct Warehouse Managed Custom ObjectCommercient external key6
ProductProductCommercient external key (earlier package)7
Item MasterCommercient Sage Intacct Item Managed Custom ObjectCommercient external key11
Itemwise WarehouseCommercient Sage Intacct Item Warehouse Information Managed Custom ObjectCommercient external key12
Sales order HeaderCommercient Sage Intacct Sales Order Document Managed Custom ObjectCommercient external key13
Sales order LineCommercient Sage Intacct Sales Order Document Entry Managed Custom ObjectCommercient external key14
Invoice HeaderCommercient Sage Intacct AR Invoice Managed Custom ObjectCommercient external key15
Invoice LineCommercient Sage Intacct AR Invoice Item Managed Custom ObjectCommercient external key16
Invoice PaymentCommercient Sage Intacct AR Invoice Payment Managed Custom ObjectCommercient external key17
Customer To Account Reverse lookupAccountCommercient AR customer code18
Item To Product Reverse LookupProductCommercient external key (earlier package)19
ContactContactCommercient external key20
Get UserUserId22
(unnamed)Accountid23

Every one of these inserts the active setting as 0, so an imported process is inactive until an operator activates it.

3. The views

“Change detection” names which of the three kinds dlake-crmpro defines the view’s own filter makes it; where a view’s shape is not one of those three the column is left empty and the view’s own filter is the authority.

ViewChange detectionSource tables
employee feedinsert + updateemployees
account feedinsert + updatecustomers
AR terms feedinsert + updateAR terms
customer feedinsert + updatecustomers, employees
warehouse feedinsert + updatewarehouses
product feedinsert + updateitems
item feedinsert + updateitems
item warehouse feedinsert + updateitem warehouse information, warehouses, items
sales order feedinsert + updatesales order documents
sales order line feedinsert + updatesales order document lines, items
invoice feedinsert + updateAR invoices
invoice line feedinsert + updateAR invoice lines, items, AR invoices
invoice payment feedinsert + updateAR invoice payments, AR invoices
account reverse lookup feedinsert onlycustomers
product reverse lookup feedinsert + updateitems
contact feedinsert + updatecontacts, customers
account customer code clearing feedinsert + updatecustomers, the writeback transaction log

4. Order of work

The templates set run sequence from 1 to 23. A run processes active rows in ascending run sequence, which is the order the templates put them in:

  • 1 — Get Account
  • 2 — Employee Sync
  • 3 — Account
  • 4 — Term
  • 5 — Customer Master
  • 6 — Warenouse Master
  • 7 — Product
  • 11 — Item Master
  • 12 — Itemwise Warehouse
  • 13 — Sales order Header
  • 14 — Sales order Line
  • 15 — Invoice Header
  • 16 — Invoice Line
  • 17 — Invoice Payment
  • 18 — Customer To Account Reverse lookup
  • 19 — Item To Product Reverse Lookup
  • 20 — Contact
  • 22 — Get User

These views read another process’s sync output, which is what makes the order a dependency order: the row appears in the view only once the process that writes that sync output has run, so a parent flows on one run and its children on the next.

  • account feed reads retrieved user sync output
  • account reverse lookup feed reads account sync output, customer sync output
  • contact feed reads account sync output
  • customer feed reads account sync output, AR terms sync output, employee sync output
  • item feed reads product sync output
  • item warehouse feed reads item sync output, warehouse sync output
  • invoice feed reads account sync output, customer sync output
  • invoice line feed reads invoice sync output, item sync output
  • invoice payment feed reads account sync output, customer sync output, invoice sync output
  • product reverse lookup feed reads item sync output
  • sales order feed reads account sync output, customer sync output
  • sales order line feed reads sales order sync output, item sync output

5. Field mapping

Each template carries its intended mapping in field mapping.

TemplateObjectMapped fieldsFirst ERP → Salesforce pairs
Get AccountAccount18Commercient AR customer code column → Commercient AR customer code, Billing street → Billing street, Billing country → Billing country, Billing city → Billing city, Billing state → Billing state
Employee SyncCommercient Sage Intacct Employee Managed Custom Object76Record number → Record number, Employee identifier → Commercient employee identifier, Social security number → Commercient social security number, Job title → Commercient title, Location identifier → Location identifier
AccountAccount18Commercient AR customer code column → Commercient AR customer code, Billing street → Billing street, Billing country → Billing country, Billing city → Billing city, Billing state → Billing state
TermCommercient Sage Intacct AR Term Managed Custom Object19Description → Description, Status → Commercient status, Record number → Record number, When modified → Commercient last modified date, When created → When created
Customer MasterCommercient Sage Intacct Customer Managed Custom Object93Account → Account, Sage Intacct term (related record) → Sage Intacct term (related record), Sage Intacct salesperson (related record) → Sage Intacct salesperson (related record), Record number → Record number, Customer identifier → Commercient customer identifier
Warenouse MasterCommercient Sage Intacct Warehouse Managed Custom Object21Record number → Record number, Location identifier → Location identifier, Parent key → Commercient parent key, parent account lookup → Commercient parent identifier, Parent name → Commercient parent name
ProductProduct11Product code → Product code, Commercient external key (earlier package) → Commercient external key (earlier package), Description → Description, Family → Family, Category 1 → Category 1 (custom field)
Item MasterCommercient Sage Intacct Item Managed Custom Object70Product → Product (custom field), Record number → Record number, Item identifier → Commercient item identifier, Status → Commercient status, Monthly recurring revenue → Commercient monthly recurring revenue
Itemwise WarehouseCommercient Sage Intacct Item Warehouse Information Managed Custom Object30Sage Intacct item (related record) → Sage Intacct item (related record), Sage Intacct warehouse (custom field) → Sage Intacct warehouse (custom field), Record number → Record number, Item identifier → Commercient item identifier, Warehouse identifier → Commercient warehouse identifier
Sales order HeaderCommercient Sage Intacct Sales Order Document Managed Custom Object49Account → Account, Sage Intacct customer (related record) → Sage Intacct customer (related record), Record number → Record number, Document number (Epicor Eagle) → Document number (Epicor Eagle), Document identifier → Document identifier
Sales order LineCommercient Sage Intacct Sales Order Document Entry Managed Custom Object88Record number → Record number, Sage Intacct item (related record) → Sage Intacct item (related record), Sage Intacct sales order header (related record) → Sage Intacct sales order header (related record), Document header number → Document header number, Document header identifier → Document header identifier
Invoice HeaderCommercient Sage Intacct AR Invoice Managed Custom Object92Account → Account, Sage Intacct customer (related record) → Sage Intacct customer (related record), Record number → Record number, Record type → Record type, Record identifier → Record identifier
Invoice LineCommercient Sage Intacct AR Invoice Item Managed Custom Object83Record number → Record number, Sage Intacct invoice header (related record) → Sage Intacct invoice header (related record), Sage Intacct item (related record) → Sage Intacct item (related record), record key → record key, Account key → Account key
Invoice PaymentCommercient Sage Intacct AR Invoice Payment Managed Custom Object20Sage Intacct invoice header (related record) → Sage Intacct invoice header (related record), Account → Account, Sage Intacct customer (related record) → Sage Intacct customer (related record), Record number → Record number, Payment key → Commercient payment key
Customer To Account Reverse lookupAccount2Commercient AR customer code column → Commercient AR customer code, Commercient Sage Intacct customer (related record) → Commercient Sage Intacct customer (related record)
Item To Product Reverse LookupProduct2Commercient external key (earlier package) → Commercient external key (earlier package), Sage Intacct item (related record) → Sage Intacct item (custom field)
ContactContact12account lookup → account lookup, Commercient external key → Commercient external key, Family name → Family name, Given name → Given name, Email → Email
(unnamed)Account2Commercient AR customer code column → Commercient AR customer code, id → id

6. Community templates

The catalogue carries 57 community templates for this pair. A community template is authored in a tenant rather than shipped with the product, and it imports the same way as any other. Its own names, notes, field mapping and SQL are tenant content, so what this section states is what the set amounts to: how many templates there are, what they default to doing, which destination objects they write and which groups they fall in. They are not part of the shipped set described above.

  • Templates: 57
  • Default operations: insert on 57, update on 57, delete on 57
  • Marked as circular sync: 0
  • Licence groups they span: 9
  • Destination objects: Account, Product, Commercient Sage Intacct AR Invoice Managed Custom Object, Commercient Sage Intacct Customer Managed Custom Object, Contact, Commercient Sage Intacct AR Invoice Payment Managed Custom Object, Commercient Sage Intacct Employee Managed Custom Object, Commercient Sage Intacct Item Managed Custom Object, Commercient Sage Intacct AR Invoice Item Managed Custom Object, Commercient Sage Intacct Item Warehouse Information Managed Custom Object, Commercient Sage Intacct Sales Order Document Managed Custom Object, Commercient Sage Intacct Sales Order Document Entry Managed Custom Object, Commercient Sage Intacct Warehouse Managed Custom Object, Commercient Sage Intacct AR Payment Managed Custom Object, Commercient Sage Intacct AR Term Managed Custom Object, Customer (custom object), Price book entry, Product Matching (custom object)
  • Template groups: Account, Product, Invoice, Sales order

7. Verifying

The detail of this section is part of the operational skill. Whitelisted customers fetch it with dlake admin get_skill dlake-crmpro-salesforce/erps/sage-intacct.

8. Where this sits

dlake-crmpro is the general operating surface — the CRMPro tools, the setup and transaction tables, field mapping, and the source view contract that applies to every destination. This page adds what the shipped Sage Intacct → Salesforce templates set up. dlake-crmpro-salesforce is the destination skill this page sits under: its own text is the authority for the Salesforce conventions that hold across every ERP, and its ERP table lists this page alongside every sibling ERP page for this destination. For the extract leg that fills the source data, see dlake-normalsync; for the on-premises agent that runs it, dlake-syncagent; for the writeback leg, dlake-txdownloaderpro; for standing an integration up, dlake-integration-setup.

How to get started

  • Already a customer: the operational skill tells you how to connect, choose what to sync and run it. Fetch it with dlake admin get_skill dlake-crmpro-salesforce/erps/sage-intacct, or ask support@commercient.com.
  • New to Commercient: contact sales@commercient.com. Becoming a customer includes registration and whitelisting, after which the operational skills and tools are available to you.