{"id":7026,"date":"2026-10-28T11:00:09","date_gmt":"2026-10-28T11:00:09","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sagemas\/?p=7026"},"modified":"2026-10-28T11:00:10","modified_gmt":"2026-10-28T11:00:10","slug":"ar-invoices-adjustments-integration-between-crm-to-sage-intacct-gumu","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagemas\/2026\/10\/28\/ar-invoices-adjustments-integration-between-crm-to-sage-intacct-gumu\/","title":{"rendered":"AR Invoices\/Adjustments integration between CRM to Sage Intacct | GUMU™"},"content":{"rendered":"\n

In our earlier post on connecting Sage Intacct and Sage 100 to Microsoft Dynamics 365<\/strong><\/a>, we covered the core quote-to-cash flow: accounts, contacts, quotes, sales orders, and invoices and payment status coming back from Sage. Since then, Intacct customers have kept asking us one thing: what about the invoices we raise in CRM that have nothing to do with a sales order?<\/em><\/p>\n\n\n\n

So, we built it. GUMU™ now reads Invoices and Credit Notes from Dynamics 365 CRM and creates them in Sage Intacct as AR Invoices<\/strong> and AR Adjustments<\/strong>.<\/p>\n\n\n\n

Not every invoice starts with a sales order
<\/strong>Plenty of billing never touches order entry: service retainers, consulting hours, project milestones, membership fees, expense recharges. In many companies the account manager decides what to bill, and they work in CRM.<\/p>\n\n\n\n

These CRM invoices are financial records, not sales documents. Each line carries a GL account<\/strong>, an amount and a description instead of an item and a quantity. Pushing them through Order Entry in Intacct makes no sense. What finance wants is an invoice in Accounts Receivable that posts straight to the GL accounts chosen on each line, which is exactly what an Intacct AR Invoice does.<\/p>\n\n\n\n

What’s new in the integration<\/strong><\/p>\n\n\n\n

Two flows have been added to the original object list:<\/p>\n\n\n\n

\n
Data Object<\/mark><\/strong><\/td>Direction<\/strong><\/td>Notes<\/strong><\/td><\/tr>
Customer \/ Account records<\/td>Bidirectional<\/td>Master record ownership must be agreed before go-live<\/td><\/tr>
Contacts<\/td>Dynamics 365 \u2192 Sage<\/td>Sales-owned; finance needs read access for billing<\/td><\/tr>
Quotes \/ Opportunities<\/td>Dynamics 365 \u2192 Sage<\/td>Triggers order or invoice creation in Sage<\/td><\/tr>
Sales Orders<\/td>Dynamics 365 \u2192 Sage<\/td>Must map to correct Sage entity and chart of accounts<\/td><\/tr>
Invoices (from Sales Orders)<\/td>Sage \u2192 Dynamics 365<\/td>Finance-owned; sales needs visibility for account management<\/td><\/tr>
Payment Status<\/td>Sage \u2192 Dynamics 365<\/td>Enables collections follow-up without system-switching<\/td><\/tr>
CRM Invoices (GL-based)<\/strong><\/td>Dynamics 365 \u2192 Sage Intacct<\/strong><\/td>Created as AR Invoices; each line posts to the GL account set in CRM<\/strong><\/td><\/tr>
CRM Credit Notes<\/strong><\/td>Dynamics 365 \u2192 Sage Intacct<\/strong><\/td>Created as AR Adjustments against the customer and original invoice<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n<\/div><\/div>\n\n\n\n
\n

How it works<\/strong><\/p>\n\n\n\n

Users keep raising invoices in Dynamics 365 the way they do today. Once an invoice reaches the agreed “ready” status, GUMU picks it up, makes sure the customer exists in Intacct, and maps the header (customer, dates, terms, reference, currency, entity) and every line (GL account, amount, memo, dimensions such as department, location, class or project). The AR Invoice is created in Intacct and posts to AR and the GL like any other invoice. The Intacct reference and sync status are then written back to CRM, so anyone can trace the invoice in either system.<\/p>\n<\/div>\n\n\n\n

Credit notes follow the same path and land in Intacct as AR Adjustments. We use adjustments because they reduce the customer’s balance without touching the original invoice. What was billed stays as billed, the credit sits as its own document, and finance can apply it to the right open invoice. That’s a clean trail for your auditors.<\/p>\n\n\n\n

If something fails, say an inactive GL account or a missing dimension, GUMU flags the record in CRM with the reason. The user fixes it there and it goes through on the next sync. No re-keying in Intacct.<\/p>\n\n\n\n

What finance should settle before go-live<\/strong><\/p>\n\n\n\n