Inventory of software and copying
A list of everything the business uses and, crucially, every point where someone copies, exports or forwards data from one program to another.
An electrical wholesaler in Valencia uses a3ERP for orders and invoices, a warehouse management system on the shop floor, HubSpot for its sales reps and A3nom for payroll. Each package does its own job well. The trouble lies between them: reps' orders are retyped into the ERP, warehouse dispatches are checked against the ERP in a spreadsheet, and warehouse overtime reaches payroll by email. Every copy is a chance to get it wrong and an hour gone. Integration means each item of data is entered once, in the program it belongs to, and everything else receives it automatically. The technical side nearly always has an answer; the hard part is agreeing which program is in charge of what and cleaning up the duplicates already there.
What we connect, and how we make sure it keeps running when nobody is watching.
A list of everything the business uses and, crucially, every point where someone copies, exports or forwards data from one program to another.
For customers, items, prices, stock, employees and documents, one source system is chosen. Everywhere else, those fields become read-only.
Connections to a3ERP, a3innuva, Sage 50, Sage 200, Holded, ContaSol, Odoo, SAP Business One or Business Central via API, the vendor's connector, or file exchange where nothing else is available.
Bringing invoice flows into line with Verifactu, or TicketBAI if your company files in the Basque Country, getting ready for mandatory B2B e-invoicing under the Ley Crea y Crece, and sending Facturae invoices to FACe for public bodies.
Joiners, leavers, clock-ins and payroll variables passed between your HR system, Factorial or A3nom and Microsoft 365, so a new starter also gets an account and permissions.
If a system stops responding, messages wait and are resent. Errors that need a human decision go to a named person with an explanation attached.
A log of every run and an alert when a flow has gone quiet for longer than normal.
Timing depends more on the state of the data than on how many connections there are. We fix it after reviewing a real sample.
We go through real extracts from each system. Duplicates, different codes for the same item and empty fields nearly always surface here.
Which program owns which data, what happens when they clash and who gets which alert. Management signs it, not just IT.
Integrations developed and tested with copies of your data in which personal details have been replaced.
For a few weeks the manual process carries on in parallel so results can be compared. Once they match, it is retired.
If a field can be edited in two places, sooner or later there will be two versions of it. A rep updates a customer's phone number in the CRM, the office changes it in the ERP, and the overnight sync keeps only one. That is why the first thing we ask for is not server access but a meeting to decide which system is the reference in each case.
Usually yes, with extra care. We can work with files the program drops into a folder, read its database or use the vendor's exports. These approaches are more brittle and need watching at every upgrade. Sometimes the cheapest option in the medium term is moving to a newer version.
Not always. If you invoice from a commercial package such as a3ERP, Sage or Holded, adapting it is the vendor's job; ask them about their timetable first. Development is needed when invoices come from an in-house program or sector software that has not been updated.
Hardly ever. Syncing every few minutes suits most processes and copes better with outages. We keep real time for what genuinely needs it, such as stock of a best-selling product.
That is the most common cause of breakage. We monitor responses from external systems and vendor announcements, and adapt the integration under the maintenance agreement. Expired digital certificates and passwords changed without warning are the other two classic culprits.
Yes. A typical set-up has a new hire in the HR system create the Entra ID account, add it to the right Teams and SharePoint groups and assign a licence, with a leaver disabling everything on the same day.
Tell us which programs you use and where someone is copying data between them. We will say what can be connected and what needs sorting out first.
Your request is with us
Expect an answer within one working day. A reported fault that has halted your team is handled first.
No match found. Try another spelling, or go with the closest provincial capital: every job is done remotely, so the location makes no difference to what we deliver anywhere in Spain.