Using Sage 200 with Sage Network

Note - information

Sage Network and Sage Connect are currently only available if you have registered as an early adopter.

To register your interest, join our early adopter program for Sage Network and Sage Connect (opens in a new tab).

Note - information

This feature is only available from Sage 200 Professional 2024 R2 version onwards.

Useful info

How PDF documents are stored and synchronised

If you have selected Include PDF documents in Sage Network Setup, PDF documents will be uploaded automatically to Sage Network. Your PDF documents will be will be uploaded to Sage Network when the invoices or credit notes have been printed (or emailed) and have been posted (after being printed).

The PDF documents that are synchronised with Sage Network are stored on your Sage 200 server in the folder \\<YourServer>\Sage\NetworkSync\<CompanyNumber>\, and are organised into the following folders:

  • SOPInvoiceCredit: Invoices and credit notes that have been printed (or emailed), but not posted. When you post these transactions, the documents will be moved to the invoice folder ready to be synchronised.

  • INVInvoiceCredit: Invoices and credit notes generated from Project Accounting Billing that have been printed (or emailed), but not posted. When you post these transactions, the documents will be moved to the invoice folder ready to be synchronised.

  • invoice: Invoice and credit note documents that have been printed (or emailed) and posted, and are ready to be uploaded in the next sync.

  • pending: Invoice and credit note documents that have been printed (or emailed), but were placed in the pending transactions file when they were posted. When you use Update pending transactions to add these transactions to the Sales Ledger, these documents will be moved to the invoice folder ready to be synchronised.

  • uploaded: Invoices and credit note documents that have already been uploaded to Sage Network in a sync. These documents are stored in case you need to run a full sync, but they are not included in a regular sync.

Sage 200 generates the PDFs with a filename based on the internal transaction IDs, as this ensures that the filename is unique. Note that the filename for a document will change as it is processed. For example, the filename for a printed invoice will change when the invoice is posted.

If you use an additional document management solution with Sage 200, you may need to set this up so that the PDFs it produces are synchronised. See Using Sage 200 document management solutions with Sage Network (opens in a new tab).

Security and firewall settings

To communicate with Sage Network, Sage 200 needs to be able to access certain URLs.

  • https://api.network.sage.com

  • https://api.sbc.sage.com

  • https://network.sage.com

Restoring company data from a backup

When you restore your company database from a backup, Sage 200 will detect the change and show a Sage 200 Database restored message if you are currently connected to Sage Network. You will need to run a full sync to make sure that your Sage 200 data is up to date in Sage Network.

When you restore your company database from a backup, Sage 200 will delete PDFs from your server for any invoices and credit notes that are no longer in your company database.

If you use a third-party document management solution, Sage 200 will delete all PDFs from the addon folder for invoices and credit notes that have been printed and not posted. This means that after a restore, any current unposted invoices or credit notes will not have a PDF produced by your third-party document management solution. When you post these invoices or credit notes, they will be synchronised to Sage Network with a PDF document that uses the default Sage 200 layout.

Moving to a new Sage 200 server

Follow this process if you are currently connected to Sage Network and are going to move your Sage 200 server to a new machine. It's important that you disconnect Sage Network and remove the add-on on your current server, and then set up Sage Network again on the new server.

On your current Sage 200 server machine:

  1. Disconnect Sage Network.

    See Disconnect Sage Network.

  2. Remove the Sage Network add-on in System Administration.

    Open Add-Ons and Remove the SageNetworkIntegration add-on.

  3. Back up your Sage 200 administration (configuration) database and all of your company databases.

On your new Sage 200 server machine:

  1. Restore the backups of your Sage 200 administration (configuration) database and all of your company databases.

  2. Install Sage 200 Professional on the server.

    For more information on installing Sage 200, see Install Sage 200 Professional on the server (opens in a new tab).

  3. In System Administration, connect to your administration database, and test connections to your companies.

  4. Install the SageNetworkIntegration add-on (SBDX).

    Follow all of the steps in Install the Sage Network add-on.

  5. Set up Sage Network.

    Follow all of the steps in Set up Sage Network.

Troubleshooting

Database restored

You will see a Sage 200 Database restored message if you have restored your company database from a backup.

You will need to run a full sync to make sure that your Sage 200 data is up to date in Sage Network.

For more information on how restoring company data affects Sage Network, see Restoring company data from a backup.

Connection expired

If you see a Sage Network Connection Expired message, you will need to reconnect by logging in using the Sage account that you used to set up Sage Network.

If you can't reconnect at this time, you can reconnect later by opening Sage Network Setup.

Your company data will not be synchronised to Sage Network until you reconnect.

Sync did not complete within timeout period (Timeout)

You will see a Sync did not complete within timeout period message in the sync results if the sync hasn't completed in the expected time.

To resolve this, try running the sync again.

Thread was being aborted (Error)

You will see a Thread was being aborted error in the sync results if IIS was restarted on the server when a sync was in progress.

To resolve this, try running the sync again.

How do I change the Sage account that is used to connect?

If you want to change the Sage account email address that you used to enable Sage Network, please contact our support team.