Skip to main content
Understanding the Sage 200 Integration

An overview of The Layer's integration with Sage 200

Written by Raymond Carrel
Updated this week

The Layer offers the ability to integrate with the Sage 200 as an external finance system.

This allows you to sync invoice and payment transactions between the two platforms.

Please note, this integration is for the Sage 200 Cloud version.

Before you start

It's important to understand that the setup process for Sage 200C isn't straightforward. Multiple parties need to be involved, and it will take approximately 2 weeks end-to-end to get the API connection set up.

  1. Obtain Global Admin Access - Firstly, we, or the third party, need to ensure we have global admin access to the tenant. This is crucial for configuring settings and permissions that may be required for the integration.

  2. Determine Configuration Responsibility

    • If a third party is involved, delegate the configuration task to them. Ensure there's a clear agreement and understanding of responsibilities between the customer and the third party.

    • If we are responsible, which is a chargeable service, we issue a quotation and proceed with the necessary preparations, including any required paperwork and communications with Sage.

  3. Initiate Configuration with Sage

    • Submit the necessary paperwork and requests to Sage to initiate the configuration process. This typically involves linking the Microsoft account with Sage and may require purchasing an Enta E1 or E2 account for integration purposes.

    • Await confirmation from Sage that the initial setup process has been initiated.

  4. Approval Waiting Period - There might be a waiting period for Sage to approve and process your request. The duration can vary, so it's important to have realistic expectations and communicate these with all stakeholders.

  5. Enable Sage API

    • Once the initial link is established, you'll need to get the Sage API enabled. This usually requires submitting a support ticket through the client's Sage account.

    • It's often preferred that this request comes directly from the client, especially if the account is managed by them. Ensure this step is communicated clearly to avoid any delays.

  6. Finalisation and Testing

    • After the API is enabled (which might take approximately 7 days), the API link should be created. At this point, you can remove the global admin access if it's no longer necessary.

    • Conduct thorough testing to ensure the connection is stable and functioning as expected. This includes testing all relevant API endpoints and ensuring data flows correctly between systems.

What is synced?

Customer records

We sync The Layer customer records with Sage customer records, with key details on customer contacts.

Example customer record in Sage 200:

Transaction enquiry for the customer (accessed from Customers List in Sage).

This includes information such as balances, credit limits and on-hold statuses. The Customer Sage Balances side-widget summarises this information.

Layer Invoices as Sage Invoice Transactions

Invoices in The Layer will sync and be sent as invoice transactions to Sage. These will be offset by payments / receipts.

Transactions: Payments and receipts

Language differs somewhat between The Layer and Sage 200 when it comes to a customer making payments against their invoice. The Layer views this from the customer's perspective and refers to this as a payment, whereas Sage refers to this from the business' perspective as a receipt.

Payments from customers made against Layer invoices will be sent to Sage, where they will be shown as receipts.

This works in reverse, too. Receipts in Sage will be sent to The Layer, where they will be displayed as payments.

These Sage - Layer payments will be shown in an area of Settings called Sage Transactions. From here we can reconcile these payments with invoice records in The Layer. Once this is done, these payments will be visible on the invoice itself and reflected in any balances.

Credit notes and any refunds will also be sent to Sage from The Layer. Refunds will be displayed as receipts.

Other mappings

Layer sub-companies as Sage companies

If your instance of The Layer is configured to use sub-companies, these can be mapped to different Sage companies that exist within the same Sage account.

Layer payment methods and Sage bank accounts

Different Layer payment methods can be mapped to different bank account entities in Sage 200.

Nominal codes

Nominal codes will be synced between both systems.

Related articles

Did this answer your question?