An account manager sends a quote from Business Central. The PDF is correct, the customer receives it, and technically nothing has gone wrong. Still, the message looks different from everything else this account manager sends: no familiar signature at the bottom, none of the Outlook add-ins the sales team uses for logging and follow-up, and a message body that was written in an editor they only see when they’re inside Business Central.
This is a recognizable situation in organizations working with Dynamics 365 Business Central, and it says less about the quality of the system than about where the boundary between two environments happens to fall.
Business Central generates documents (quotes, invoices, orders) as PDFs based on report layouts and attaches them to an email automatically. That part works reliably, and PDF generation is seldom where the trouble starts.
Before sending, the built-in email editor lets the user change the recipients, adjust the subject line and rewrite the message body. Basic formatting is available and extra attachments can be added, so the email doesn’t have to go out exactly as the template produced it.
With the Microsoft 365 email connector, the message can be sent from the personal email address of the logged-in user. The customer then sees the account manager’s own name in the From field instead of a generic company mailbox. Sent messages are logged in Business Central, so there’s a record of what went out.
The real limits are subtler and only show up in daily use.
The email editor in Business Central is a simplified editor, built for the job it has to do inside the ERP system. It covers the essentials, and it isn’t the environment your salespeople spend their day in. The Outlook signature with the company logo, the disclaimer and the direct dial number isn’t applied.
The Outlook add-ins the team relies on, from CRM logging to scheduling tools, aren’t available at the moment of sending. And the formatting options are narrower than in the editor everyone already knows.
There’s also a question of scope. Business Central offers an email action on the document types Microsoft has provided it for. Anything outside that set falls back on the manual route: print to PDF, save the file, open Outlook, attach it by hand.
As an IT manager, you’re looking at a familiar tension. Business Central is built as a controlled system that enforces process discipline, while your employees are used to communicating from Outlook, where they have the freedom to shape a message around the relationship they’re building.
The most workable answer connects the two systems at the point where they actually meet, which is the moment of sending. That’s what Edit in Outlook does: an app from Q-Team Solutions that you install directly from AppSource within Business Central.
Business Central prepares the email, including the PDF attachment and the email template. Edit in Outlook then creates a standardized email file that opens in Outlook itself, where the employee finishes the message and sends it from their own account.
The email opens in the full Outlook environment. The message doesn’t stay inside Business Central; it lands in Outlook, with everything your employees have configured there.
Your own signature and Outlook add-ins are available. Because the message is composed in Outlook, the standard Outlook signature is applied and the add-ins your organization uses work as they normally do.
Employees work in the editor they already know. No switching between two different email editors and two different sets of formatting options.
The message is sent as an ordinary Outlook email. It leaves through Outlook and lands in the Sent Items folder, in the same archive your colleagues search every day when they need to retrieve what was communicated.
No personal email configuration in Business Central. Sending from an employee’s own Outlook account requires no per-user email setup within Business Central.
Usable for every document type. Where the standard email functionality is limited to the documents Business Central provides an email action for, Edit in Outlook can be applied across the board, including the document types where your users now print, save and attach by hand.
Installation runs through AppSource and takes around five minutes, without a consultant, and there’s a free trial month to test the app in your own environment first.
The question isn’t whether Business Central is capable enough for sending documents, because the standard functionality covers more ground than most organizations realize. The question is where you want your people to be at the moment a document goes to a customer: in a simplified editor inside the ERP system, or in the mail environment where they do the rest of their work.
For internal notifications and high-volume automated messages, the standard route is fine and often preferable. For quotes, invoices and other documents that carry a customer relationship, it’s worth checking whether the last step matches the way your employees actually work.
Want to know more about the email integration in Business Central or try Edit in Outlook for a month? Get in touch with Q-Team Solutions at info@q-team.nl or +31 30 820 1333.
