Documents Development Version

Allows users to scan and retrieve documents while they work in Sage 200, with no additional document management software or indexing steps required. The document indexing information is stored within the Sage 200 SQL database for fast searching. The documents are stored within the Sage 200 attachments path to ensure all documents are backed up within your Sage backup plan.

What is a Development Version?

A Development Version is a phased early adopter release preceding a full release. Rather than all new features being released in the first iteration of a full release, we phase the new features across iterations of a ‘development release’. At the end of its development cycle, a full release is introduced and the development release retired, since it is essentially converted into a Full Release. For more information, please refer to the Sicon Release Policy.

Click here to view the Sicon Release Policy

Release notes:

270.1.1

New Features

[#16249] Added a new setting in `Customer Remittances` to use the remittance number in the `2nd Ref` field when receipting via documents, improving receipt matching and reconciliation for those who use internal references. The setting ensures existing processes are not disrupted and provides clearer control over how references are handled. The settings screen layout has also been improved for easier reading and less visual clutter
[#17139] The `Rules Based Engine` is now enabled by default in Document Automation, making rule application available to all users without needing to activate a preview feature. The `Preview Features` tab has been removed from the `Automation Settings` form, simplifying the settings screen and ensuring consistent access to rule options in document processing.
[#18000] • Added a new `Amend Query` option to the document processing menus, allowing queries on documents to be updated without removal. Users can now edit the `query code`, `query note`, or reassign the query to another user, with changes reflected immediately and assignment dates updated as needed. The option is only enabled when an active query exists, streamlining workflow and reducing unnecessary resets.
[#14899] The new `Remittance Reconciliation` feature in Document Automation streamlines the process of matching supplier payments to invoices, making it easier to identify unpaid items before issues arise. A dedicated `Remittance` tab in `Document Automation Settings` allows for tailored configuration of remittance processing. Enhanced controls, including the option to “Use Second Reference When Receipting via Documents,” improve receipt matching accuracy. The settings interface is now clearer and more organised, reducing confusion and helping ensure remittance statements are processed efficiently.
[#15466] A new `Remittance` tab has been added to the `Document Automation Settings`, allowing configuration of customer remittance processing. The setting to “Use Second Reference When Receipting via Documents” enables more accurate receipt matching and clearer control over reference handling. The settings layout is now cleaner and less crowded, making options easier to read and manage. This update helps reduce unmatched customer remittances and improves the overall reconciliation process.
[#15677] Uploading documents in the `Automation Drop Panel` now uses improved logic for the `Invoice`, `Credit Note`, and `Invoice/Credit Note` buttons. Selecting `Invoice` or `Credit Note` ensures the document is always classified as the chosen type, bypassing the document recognition algorithm. This update reduces misclassification, speeds up processing, and makes document handling more predictable. The change significantly decreases support cases related to incorrect document type assignment.
[#15679] Uploading a document using the `Credit Note` button now ensures it is always treated as a credit note, bypassing the document recognition algorithm. This change reduces misclassification, speeds up processing, and makes document handling in the `Automation Drop Panel` more predictable.
[#15678] Uploading a document using the `Invoice` button in the `Automation Drop Panel` now ensures it is immediately classified as an invoice, bypassing the document recognition algorithm. This change delivers faster processing, reduces misclassification, and provides more predictable handling of invoices.
[#18141] Document Automation now uses the Microsoft Graph API instead of EWS for all Exchange 365 email processing, ensuring continued reliability as EWS is deprecated. The update improves mailbox integration, status visibility, and notification delivery for receipt, invalid, and error emails to both `admin` and `sender` addresses. Mailbox testing and setup feedback in the `Exchange 365` settings are clearer, and the `Download Email` button now leverages Graph for more consistent automation. This change may require Azure permissions updates and removes all dependencies on EWS.
[#18801] Email notifications in Document Automation now use the Microsoft Graph API instead of EWS, ensuring continued support as EWS is deprecated. This update improves reliability for sending receipt, invalid, and error notifications to both `admin` and `sender` addresses, and introduces clearer mailbox testing and setup feedback in the `Exchange 365` settings.
[#18589] Document Automation now uses Microsoft Graph instead of EWS for Exchange 365 email processing, ensuring continued operation after Microsoft’s EWS retirement. The `AutomationExchangeDownloadInstrument` and `ExchangeWebAPIServiceExtension` have been updated to support mailbox access, document retrieval, and notifications through Graph. Mailbox status and unread counts are now shown in setup, with improved feedback and guidance. This change may require Azure permissions updates and removes all dependencies on EWS.
[#18586] The `Email Integration` settings now use Microsoft Graph instead of EWS for Exchange 365 automation, providing a more reliable connection and clearer mailbox testing feedback. Auto Configure launches the Microsoft login flow, retrieves the `Tenant ID`, and verifies mailbox access through Graph, with improved error messages and support for webhook-triggered mail processing.
[#18587] The `Download Email` button on the processing screen now uses the Microsoft Graph API instead of EWS, improving reliability and mailbox integration for Exchange 365 automation. Mailbox status, unread counts, and processed emails are managed through Graph, with clearer setup feedback and support for webhook-triggered mail processing. This change ensures more consistent automation and aligns with Microsoft’s latest integration standards.

Date applied: June 3, 2026