Acumatica offers multiple ways to handle email communications to your customers and prospects: system email accounts, Exchange email processing and the Outlook add-in. There is often a place where all three may be useful to your organization, but it can be confusing on which one does what and steps needed to get the configuration working how you want it to. 

This is a quick breakdown of each option, what it is designed for, and how to think about which one fits your situation. 

System Email Accounts  

System Email Accounts are the standard email capability built into Acumatica, and they are included for all users at no additional cost. Think of them as your company’s operational email accounts configured inside the ERP. 

Common examples include addresses like purchasing@, sales@, invoices@, or no-reply@. These accounts handle outbound communications generated automatically by the system, such as invoice delivery, sales order confirmations, password resets, and new account notifications. They can also be set up to process incoming mail, for example, routing replies to a support address directly into Acumatica as cases. 

System Emails Accounts can be configured for individual users as well, though that setup is a bit more manual. Each system email account requires a licensed mailbox; aliases and distribution groups will not work here. 

The important distinction is that system emails accounts are designed for company-level and transactional communications. They are not the right tool for tracking personal email conversations or syncing an individual’s Outlook inbox with Acumatica. That is where Exchange Integration and the Outlook Add-in come in. 

Exchange Integration 

Exchange Integration is a paid add-on that creates a server-to-server connection between Acumatica and your Microsoft 365 or Exchange environment. Once it is configured, emails sent from Acumatica show up in your Outlook sent folder, and you can drag existing email threads from Outlook into Acumatica to sync them back. 

It also handles contacts, calendar and task synchronization, so people, meetings and to-dos stay consistent across both systems without anyone having to manually update either. 

The key feature is that it works in the background. Once Exchange Integration is set up for a user, emails originating from Acumatica are automatically tagged and tracked. There is no button to click. You can also see which emails have been synced by their Acumatica flag in Outlook. 

The Exchange Integration is a good fit for sales teams and others who need seamless data flow between Outlook and Acumatica without having to think about it. It is particularly well-suited for emails that originate in Acumatica, since the backend tagging system automatically handles tracking. 

A few things to know about setup: Exchange Integration requires OAuth authentication and an app registration in Microsoft Azure. The most common source of setup delays is incorrect permission configuration on the Microsoft side. The OAuth client secret also has a maximum two-year expiration, so someone needs to monitor and renew it before it lapses. When it expires, email stops flowing, and that is often the first sign something has gone wrong. 

Each user who needs Exchange Integration requires their own licensed mailbox. New employee onboarding should include the step of setting up permissions and syncing in Acumatica, which is easy to miss if it is not documented in your process. 

For clients who use our MSP services, we can handle the Microsoft-side configuration directly. For others, we work with your IT team and walk them through what is needed. 

Outlook Add-in 

The Outlook Add-in is also a paid add-on. It is a side panel in Outlook that lets users push emails directly into Acumatica records, with full control over where each email is filed. 

From the add-in panel, you can log an email to a contact, case, or opportunity. You can also create new records on the spot. And you can jump directly to the open record in Acumatica from the panel without switching applications. 

Unlike Exchange Integration, the Outlook Add-in is user-driven. You decide which emails get logged and where. That makes it useful when people want precise control over what ends up in Acumatica, particularly for sales, support, and accounting teams. 

If your team uses the AP Document Recognition module, the Outlook Add-in lets you push email attachments directly into accounts payable. That is one of the more useful integrations that tends to go underutilized. 

The functionality available in the add-in depends on which Acumatica modules you have installed. CRM, Case Management, and AP Document Recognition each add their own buttons and capabilities. It is worth reviewing what is available in your configuration, since many users do not realize the full range of the add-in’s capabilities. 

How to Decide 

Many organizations end up utilizing a mixture of the three options available depending on what works best for their users.  System email accounts handles transactional outbound email and can assist with automated case creation through the incoming email processing functionality. The Exchange Integration handles individual users who want their Acumatica emails to flow to Outlook automatically. The Outlook Add-in covers anyone who wants manual control over what gets logged. Our own team runs all three daily, and that is a common pattern for clients who are fully up and running. 

If you are trying to figure out where to start, a few questions help clarify the picture: 

  • Do you need automated, system-generated emails for invoices, orders, or notifications? Start with System Emails. It is included and handles the basics well. 
  • Do your salespeople or other users want their Acumatica emails to appear in Outlook automatically, with calendar and task sync? Exchange Integration is the right fit. 
  • Do users want to decide exactly which emails get filed, or does your team use AP Document Recognition for invoice processing? The Outlook Add-in gives them that control. 

Common Mix-ups 

A few assumptions come up regularly that are worth addressing directly. 

The Outlook Add-in does not auto-file everything. Users have to consciously click the Acumatica button and choose where to log each email. It does not run in the background. If your goal is automatic logging, Exchange Integration is the better fit. 

Exchange Integration requires proper configuration to work well. Misconfigured rules, expired client secrets, or missing Azure permissions can all cause gaps. It is powerful once set up correctly, but it is not a set-and-forget tool without some initial investment. 

System emails are not generally for personal correspondence. They are company-level senders for ERP-generated documents. Your personal Outlook mailbox is handled separately through Exchange Integration or the Add-in. 

Outlook and Exchange Integration are add-ons and are not included in every base configuration. Before building a workflow around either, confirm they are part of your Acumatica license. 

A Note on Activity Logging 

Regardless of which option you use, communications logged at the contact level bubble up to the company level in Acumatica. Activities logged at the opportunity or case level also roll up. The Related Entity field shows the source of each activity. 

The practical takeaway is that getting client communications into Acumatica, from any department, gives your whole team visibility into account history. That context tends to be most valuable when it has been built consistently over time. 

Next Steps 

If you are not sure which options are currently configured or whether they are set up correctly, a configuration review is a good starting point. The setup requirements are straightforward once you know what to look for, but small gaps in permissions or licensing can limit how well each option performs. 

For more details on configuring each option, Acumatica’s documentation covers System Emails, Exchange Integration, and the Outlook Add-in in detail. Fair warning: the help guides can be technical. An experienced implementation partner can help translate the configuration steps into the actions that actually need to happen in your environment.