Sage 200 (Spain) accountancy integration

Breww integrates with Sage 200 (Spain) (Sage 200c España) as one of its automated accountancy integrations.

Note: This integration is currently in early access. If you'd like to use it, please contact the Breww support team and we'll enable it on your account.

Most of the general setup process (mapping customers, choosing accounts, sync settings and enabling the sync) is the same as for all of Breww's automated accountancy integrations, so please read the main Accountancy guide first. This page covers the ways in which Sage 200 (Spain) works differently.

How this integration is different

There are two important differences from Breww's other accountancy integrations that are worth understanding before you start:

Invoices are uploaded as delivery notes (albaranes), not as invoices. Spain's Verifactu anti-fraud regulations don't allow invoices to be created directly via the Sage 200 (Spain) API, so Breww uploads each invoice as a pending delivery note instead. You then invoice the delivery note within Sage 200 (Spain) to produce the compliant factura. See Invoices and credit notes below.
Your Sage products appear as your "accounts" in Breww. The Sage 200 (Spain) API doesn't provide access to nominal/ledger accounts, so instead Breww downloads your Sage 200 (Spain) products (along with your company's bank accounts) and presents these as the accounts list in Breww. See Accounts (your Sage products) below.

Before you connect

To avoid sync issues later, please make sure the following are in place in Sage 200 (Spain) before enabling the sync:

Matching VAT rates. Every VAT percentage you use on invoices in Breww must also exist as a VAT tax rate in Sage 200 (Spain) (found in Sage under Settings → VAT tax rates). Sage will reject invoice lines with a VAT percentage that doesn't match one of its configured rates.
At least one existing delivery note. Breww determines which Serie (series code) to use for its uploads by looking at the most recent delivery note in Sage 200 (Spain). If you've never created a delivery note, please create one manually in Sage first (any Serie).
At least one existing negative delivery note (devolución), if you'll be raising credit notes in Breww. As above, Breww picks up the Serie for credit notes from your most recent negative delivery note (typically the RE series).
At least one Store (warehouse). Sage 200 (Spain) requires a Store on each delivery note line. Breww will automatically use your first Store.

In Breww, every customer that will be synced needs:
A VAT/CIF/NIF number set on their customer record in Breww.
A reference set in Breww (this becomes the customer's code in Sage 200 (Spain)).

If any of these are missing, Breww will raise a sync message explaining exactly what needs to be fixed (see Sync messages).

Connecting Breww to Sage 200 (Spain)

To connect, navigate to Integrations → Accountancy and click the Set up Sage 200 (Spain) integration button. You'll be redirected to Sage to sign in with your Sage ID and authorise Breww's access, and then returned to Breww.

If your Sage subscription contains more than one company, Breww will ask you to choose which company you'd like to sync with as part of the connection process.

As with all of Breww's accountancy integrations, nothing will sync until you enable the sync, so you'll have time to map your customers and accounts and review the settings first.

Accounts (your Sage products)

When you import accounts in Breww (via the Accounts & tracking categories section of the integration configuration), the list you'll see is made up of:

Your products from Sage 200 (Spain), which act as your sales accounts.
Your company's bank accounts from Sage 200 (Spain), which are used for payments.

This is because the Sage 200 (Spain) API doesn't expose nominal/ledger accounts, and every line on a Sage delivery note must reference a Sage product. So, when you set your default sales account in Breww (or set an account against a specific Breww product, customer or customer type), you're really choosing which Sage product those invoice lines will be recorded against in Sage 200 (Spain).

Note: Every invoice line uploaded from Breww must resolve to a Sage product, so make sure you've set a default sales account before enabling the sync.

Customers

Customers work in much the same way as Breww's other accountancy integrations, with one key difference: Breww cannot create new customers in Sage 200 (Spain) automatically.

You can download your Sage 200 (Spain) customers into Breww and map them to your Breww customers using the Map and download customers tool, as described in the main Accountancy guide.
Once a customer is mapped, updates you make to them in Breww will be synced to Sage 200 (Spain).
If you invoice a Breww customer who isn't mapped to a Sage customer, Breww will raise a sync message. To resolve it, create the customer manually in Sage 200 (Spain), then map them to the Breww customer and retry.

Remember that every synced customer needs a VAT/CIF/NIF number and a reference in Breww (the reference becomes their customer code in Sage).

Invoices and credit notes

When you invoice an order in Breww, the invoice is uploaded to Sage 200 (Spain) as a pending delivery note (albarán). Creating invoices directly via the API isn't permitted under Spain's Verifactu anti-fraud invoicing regulations, so the final, compliant invoice (factura) must be generated within Sage itself.

Warning: You must invoice the delivery note within Sage 200 (Spain). Breww's upload creates a pending delivery note only — until you invoice it in Sage, no factura exists, and payments for that invoice cannot be uploaded from Breww (see below).

Credit notes raised in Breww are uploaded as negative delivery notes (devoluciones). Just like invoices, the factura rectificativa is then created within Sage 200 (Spain).

Payments

Payments sync in both directions:

Sage → Breww: When a payment is recorded in Sage 200 (Spain) against a factura, Breww traces it back to the original delivery note it uploaded and records the payment against the matching invoice in Breww.
Breww → Sage: Payments recorded in Breww are uploaded to Sage 200 (Spain), but only once the delivery note has been invoiced in Sage. If you record a payment in Breww before invoicing the delivery note in Sage, Breww will raise a sync message asking you to invoice the delivery note first — once you have, the payment will upload on the next retry.

What's not supported

Due to limitations of the Sage 200 (Spain) platform and its API, the following aren't supported by this integration:

Suppliers and supplier invoices (bills) — the supplier mapping tools and supplier sync options are hidden for this integration.
Voiding — voiding an invoice or credit note in Breww won't be reflected in Sage 200 (Spain); you'll need to handle this within Sage.
Payments on account — Sage 200 (Spain) has no concept of an on-account payment; every payment must be attached to a specific receipt.
Uploading credit note allocations — allocations made in Sage will sync down to Breww, but allocations made in Breww won't be uploaded.
Tracking categories and balance sheet syncing.

For a side-by-side comparison with Breww's other accountancy integrations, see the data flow tables in the main Accountancy guide.