Connecting your POS to your ERP or invoicing software
Connecting the till to an ERP or invoicing software starts with deciding who issues the invoices, because with VERI*FACTU you cannot have two systems numbering the same sales. Then you choose which data travels and in which direction, and sometimes exporting for your accountant is enough. We explain how to decide and when you need a custom connector.
To connect a POS to an ERP or invoicing software you need to decide three things, in this order: who invoices each sale (with VERI*FACTU, a single system, without two numbering sequences for the same sales), which data travels and in which direction (catalogue, stock, customers, sales) and whether you really need a connector or exporting the sales for your accountant is enough. When the system has no ready-made connection, one is written to measure.
The question usually comes out of frustration: someone types in the counter sales twice, the stock in the management software never matches the till, or the accountant asks every month for a file that has to be put together by hand. The temptation is to ask for «everything to be connected to everything». This article helps you put the decision in order before spending on a connector, and to know what to ask whoever is going to build it.
First: who issues the invoices
It is the decision most often forgotten and the one that causes the most problems. The Spanish regulation on invoicing systems (Real Decreto 1007/2023, known as VERI*FACTU) requires the software that issues invoices to chain each record to the previous one, so that it cannot be altered, with its QR code and with the records sent to the Spanish Tax Agency (AEAT) or kept available to it. The dates from which it is mandatory have changed several times; check the current calendar of the Tax Agency.
If the till invoices and the ERP does too, each sale can end up with two invoices and two numbering sequences. That is why, before talking about connectors, you need to choose a clear split:
- The till invoices the counter (and, if you wish, the online store orders), and the ERP receives the sales already invoiced for accounting, stock or reports.
- The ERP invoices and the till simply takes the payment and passes the sale on. This requires the ERP to be an invoicing system that complies with the regulation and the connection to be reliable even without internet.
- Each one invoices its own sales, with different series: for example, the till the counter and the ERP the sales to trade customers. It works as long as nobody invoices the same transaction twice.
Which data is synchronised and in which direction
Not everything has to go both ways. Usually each piece of data has an «owner», the system where it is edited, and the others read it. This table helps you decide:
| Data | Where it is usually edited | What should happen |
|---|---|---|
| Catalogue and prices | In the ERP or in the online store | The till receives them, so each item is not typed in twice. |
| Stock | It moves in all of them | Each sale, purchase or return subtracts or adds in one place and the others find out. |
| Customers | Wherever they are created | A customer with a price list or agreed prices has the same ones at the till. |
| Counter sales | At the till | They reach the ERP or the accounts without being typed in again. |
| Online store orders | In the store | A single system invoices them and stock goes down only once. |
| Purchases from suppliers | Wherever the goods are received | Stock goes up where it is sold. |
The clearer it is who owns each piece of data, the simpler, cheaper and more reliable the connector turns out.
Sometimes exporting for your accountant is enough
Very often what is requested as «connecting the POS to the invoicing software» is really getting the sales into the accounts. That does not always need a connector: it is enough for the till to export what the accountant needs in the format of their software, plus a report when the till is closed.
Before commissioning anything, ask your accountant which software they use and which file suits them best. If the till already exports it, you save the development.
When you need a custom connector
These are the signs that exporting is no longer enough and connecting the systems pays off:
- The same things are typed in twice every day: new items, prices or sales.
- The ERP owns the stock, because purchasing and receiving are done there, and the till needs to know straight away.
- There are trade customers with price lists or agreed prices that have to be the same at the counter.
- Several warehouses or several shops share the same goods.
- The online store is not on a platform with a ready-made connection and has to be handled like the others.
If none of these apply, exporting is probably enough. If several do, the connector pays for itself with the hours the team stops losing and the errors that stop happening.
What the process of a custom connector looks like
Every system is different, so a serious connector has no catalogue price. A sensible process is this:
- Explain which system you use and which data has to go from one to the other.
- Review what that system allows: an API, exchange files or its database.
- Get a clear answer: what can be connected, what cannot, who invoices what and how much it costs.
- Build the connector and test it before touching the live system.
- Get the till up and running with test sales and training for the team.
What to ask whoever builds it
- What happens if the internet goes down? The till has to keep selling, and the movements have to wait and be sent automatically later.
- What happens if the ERP does not respond? One system being down cannot bring the other to a halt.
- How are duplicates avoided? A sale sent twice must not subtract stock twice or create two invoices.
- What cannot be connected? Better to know before starting than to find out once the connector is built.
- Who maintains it when a version changes? Software gets updated and the connector has to keep up.
How we solve it at Rekire
RKR POS is till software for Windows that is, at the same time, the shop's invoicing system, built for Real Decreto 1007/2023. It already connects to PrestaShop, WooCommerce and Shopify, and from your VERI*FACTU start date it also invoices the paid orders from the website, with no duplicate numbers. For accounting it exports to ContaPlus, Contasol, a3, ClassicConta and Odoo, and emails a report when the till is closed: if your accountant works with one of them, start there.
If your store is on another platform, or what you have is an ERP or management software, we connect it to measure: we have been building connectors and integrations for years and have integrated stores with more than 40 suppliers. We explain how we work on the page about the POS connected to your ERP or invoicing software. The connector is quoted after looking at your system; the RKR POS licence for the first till, €990 + VAT as a one-off payment, is separate.
Frequently asked questions
Can any POS be connected to any ERP?
It depends on what each one allows: an API, exchange files or access to its data. Before starting, you need to see what each system offers.
Can the till and the ERP both issue invoices?
They can, with different series and different transactions, but never the same sale twice. With VERI*FACTU it is best to make it very clear who invoices what.
Which is better, exporting or synchronising?
If you only need to get the sales into the accounts, exporting is usually enough. If stock, prices or customers change in both places every day, synchronising pays off.
How much does a custom connector cost?
It depends on the system and on the data that has to travel. The usual approach is to quote it after reviewing what your software allows.