Service · Data and analytics

Master data management

Imagine an electrical wholesaler in Zaragoza whose ERP holds a decade of history. The same installer is listed as “Electricidad Pérez”, as “ELEC. PEREZ S.L.” and once more with no NIF at all, typed in during a Friday rush. One circuit breaker lives under two item codes, one per box and one per piece. Every guest checkout on the webshop spawns yet another customer. Reports built on that can never reconcile. We sort the records out and, just as importantly, agree in writing who creates new ones and how, so twelve months from now you are not back where you began.

NIFs
verified with AEAT and VIES
Duplicates
flagged, reviewed, merged
Named owner
per master dataset
Quality score
reported monthly

What falls within the scope of this service

In Spain, master data feeds far more than reports: the annual 347 return, invoices logged under Verifactu, SEPA payment runs and shipping labels all draw on it. So we tackle the fields with tax or cash consequences first.

Pin down the details with one of our engineers

Customers with a reliable NIF

Tax IDs and legal names checked against the AEAT, EU VAT numbers against VIES. A record with no NIF drops transactions from the 347 return; one with a wrong letter repeats the error on every logged invoice.

Territory and tax regime

Customers in the Canary Islands, Ceuta and Melilla flagged as such, since IGIC or IPSI applies there rather than VAT. A mis-assigned postcode ends up as a wrongly issued invoice.

Suppliers and bank details

IBANs reviewed, one authorised person allowed to change them and a log of who changed what and when. It is the field supplier-impersonation fraudsters target first.

Items ready to sell and ship

EAN, sales units, weight and dimensions made consistent so SEUR or GLS rates calculate correctly and Amazon.es or Miravia listings, via Channable or Lengow, point at the right code.

Standardised addresses

Streets, postcodes and provinces written one way only, which cuts returned parcels and lets you group sales by area without workarounds.

Merges with a mapping table

Every retired code is linked to its replacement in a table that is kept, so integrations, historical reports and searches keep working after the clean-up.

Consumers and retention limits

Webshop accounts inactive beyond your retention period are listed for you and your DPO to delete or anonymise. Invoices stay put under their own tax obligation.

How the engagement unfolds, one stage at a time

Measure first, then prioritise by tax impact rather than convenience. The work is done remotely, from exports or through secure access to your ERP.

01

Extract and count

We export all three datasets and count records lacking an NIF, likely duplicates, unverified IBANs and items missing an EAN or a weight.

02

Order of attack

Anything affecting invoices, the 347 return and collections first; stock and shipping next; old history last.

03

Clean in batches

Each batch is prepared as a review sheet that the dataset owner signs off before it is applied, with an ERP backup taken beforehand.

04

Lock it down in the ERP

Mandatory, unique NIF, a lookup by NIF before saving, restricted rights to create records and a monthly quality report.

The riskiest field on a supplier record is the IBAN. The classic scam arrives by email: “we have changed banks, please pay this account from now on”. If anyone in the accounts office can edit that field without a second check, the next SEPA run goes to a stranger. Limiting who may change an IBAN and requiring confirmation through a separate channel takes ten minutes to configure.

Common questions

Size matters less than the level of mess. The initial count takes a few days; the clean-up runs in batches over several weeks so invoicing is never disrupted. You get a concrete timetable after the diagnosis.

Mostly, yes. a3ERP, Sage 200, Holded and Odoo support mandatory fields, validation and, with varying effort, a warning when an NIF already exists. Where the software cannot do it, we set up a weekly report that catches new duplicates before they pile up.

They are tagged with their territory and tax regime so the ERP does not charge them VAT by mistake. The exact tax configuration is best confirmed with your accountant; our job is to make sure the data is on the record and actually used.

Yes. The whole analysis can run on exports, and changes can be handed over as import files for your team to apply. If you would rather we did it, we work in batches and always after a backup.

After the diagnosis you get a fixed quote, or we work at €75 per hour + VAT under a cap agreed in writing.

Sort out your master data

Let us know which reports refuse to reconcile and which lists feel oversized. Our first step is to size the problem properly, before any proposal.

Hours
Monday to Friday, 9:00-18:00 Spanish time (CET), answers within a working day
Meetings
Video calls via Google Meet or Teams

This site only stores the cookies it needs to work and to remember your chosen city. No advertising or tracking cookies are set. See our privacy policy for the details.