Category: Sage 200
Sage have tested and support the integration of Sage 200 Professional and Microsoft (Office) 365 for builds prior to the 6th of October.
NOTE: supported builds of Microsoft (Office) 365 are dependent on the version of Sage 200 that you are running.
See how to check the version of your Sage 200.
Sage 200 version 2015 introduced a function where nominal ledger transaction narratives and transaction analysis codes can be amended and updated after transactions have been entered.
Accounting System Manager has a setting to prevent the cash book from being able to post the double-entry of a transaction into different accounting periods (which will cause a temporary misbalance on the trial balance).
To help with entering sales orders, it is possible to create stock lists of customers own preferred items.
Microsoft 365, Office 365, and Exchange 365 allow two different methods to authenticate users: Basic Authentication & Modern Authentication.
Please be aware that Microsoft has made basic authentication unavailable for Office/Exchange 365.
See how to check the version of your Sage 200 Add-on for Spindle Professional & Spindle Document Distribution.
Analysis codes can be used to identify accounts for enquiry and reporting purposes.
Audit Log was introduced in Sage 200 version Winter 2018 / v12.00.0027 primarily for recording changes to supplier bank details; the menu option is found under Accounting System Manager >> Audit Log menu, though you might like to add to the purchase ledger payment processing menu to make it easier to review changes to bank details when creating supplier payments.
Purchase ledger remittance advices cannot be re-printed if for example a copy remittance needs to be sent to a supplier; though if saved to Document Storage (introduced for remittances in Sage 200 version 12.00.0031) they can be picked up and re-sent from there.