Contact Info
Spain
What does an ERP rescue involve for a Spanish company?
An ERP rescue for a Spanish company separates problems with outside deadlines, such as rejected SII records, clashing invoice series and returned remittances, from ordinary project work, and clears them by cause. I then give the gestoría the evidence to close the quarter, write a neutral account of what went wrong, reset the plan with the integrator and frame the next decision. It runs remotely and independently.
Last reviewed by Vikas Saroj
A Spanish ERP project in trouble rarely gets a quiet moment to recover. SII submissions keep their own deadlines, banks return remittance files, the gestoría needs figures for the quarterly returns, and the integrator is still asking for decisions on open design questions. Meanwhile the go-live date has moved, or the go-live happened and the first weeks have been rough.
As an independent ERP rescue consultant I work on the company's side. I split urgent tax and banking problems from the project backlog, steady daily operations, write down what actually happened, agree a new baseline with the integrator, or plan an orderly exit if that is the better route, and put a clear decision in front of management. I deliver it remotely; a visit can be arranged.
Neither vendors nor integrators pay me, and I have nothing to sell after the rescue, which keeps the assessment honest. The engagement runs in English. Messages to staff and customers in Spanish, Catalan or Basque come from your team or the integrator, and tax questions go to your asesor fiscal.
Recovery Scope
External deadlines from the tax agency and banks are handled before internal project questions.
Two lists from day one: items with an outside deadline, such as SII submissions, remittances and returns, and ordinary project work. Each list has its own owner and review rhythm so neither swamps the other.
Rejected and late invoice records grouped by cause, series clashes between old and new systems resolved with your asesor fiscal, and corrective invoices linked properly to their originals.
Direct debit remittances, returned debits and supplier payment runs brought back under control, with mandates and bank accounts cleaned at the source so the same rejections do not return.
Evidence for the gestoría and asesor fiscal to prepare returns for the affected periods, with a clear view of which system holds which documents and how corrections were posted.
A fact-based review followed by a structured session to agree essential, deferred, dropped and disputed work, with named owners on both sides, or a controlled handover if the relationship ends.
A paper for management comparing continuing, narrowing the scope and starting again on another platform, spelling out what carries over, what could go wrong and what drives cost.
How I Work
Outside deadlines before project debates
Tax and bank list owned
Project changes paused
Daily review with key users
Workarounds written down
What happened, in writing
Contract and scope compared
Interviews held one by one
System and data inspected
Shared written account
A plan both sides can keep
Decision paper for management
Reset plan with owners
Retesting before go-live
Clean quarter-end close
The first thing I do in a Spanish rescue is separate two kinds of work that usually sit in one long issue list. The first kind has an outside clock: invoice records the tax agency expects within its submission window, remittances that must reach the bank before due dates, returned debits customers are waiting to see resolved, and documents the gestoría needs for the next return. The second kind is project work: open design questions, reports, enhancements and defects that hurt but do not trigger a deadline.
Mixing the two causes damage in both directions. Urgent tax items wait behind a debate about a sales report, or the integrator's best people are pulled into firefighting and the project stops moving altogether.
So each list gets its own owner and rhythm. The outside-deadline list is reviewed daily with the administration lead and the integrator's support contact, with every item showing a cause, a due date and the person fixing it. The project list is reviewed weekly and frozen except for items that unblock the first list. Workarounds are allowed, but each one is written down with an end date, so temporary fixes do not quietly become the process.
This structure follows the general approach on my ERP recovery page, adapted to the reporting and banking cycle a Spanish company lives with.
Once the outside-deadline list exists, I work through it by cause rather than one item at a time. A handful of root causes can explain a long list of symptoms:
| Symptom | Where I look first | Who decides the fix |
|---|---|---|
| SII records rejected or accepted with errors | Tax IDs, territory and document type mapping | Asesor fiscal for treatment, integrator for configuration |
| Duplicate or overlapping invoice numbers | Series started in the new system before the old one closed | Asesor fiscal, then integrator |
| Corrective invoice cannot reference an original | Invoices issued before the switch not migrated as references | Integrator, checked by finance |
| Remittance file rejected | Mandate data, creditor details and file format per bank | Finance with the integrator |
| Returned debits not reopening invoices | Bank statement matching rules | Integrator, tested by finance |
Fixes go into master data or configuration, not into posted documents, so the next batch of invoices does not fail the same way. If the company has an entity using TicketBAI in the Basque Country, or deals with the Canary Islands, those flows get their own lines, because their tax rules and channels differ from the mainland.
I do not decide how a rejected record or a duplicated number should be regularized. Your asesor fiscal does. My role is to make sure each decision is recorded and carried out consistently in the system.
A troubled go-live usually lands in the middle of a reporting period, and the quarterly returns are where the confusion becomes expensive. The gestoría or asesor fiscal needs to know which documents sit in which system, which have been corrected and whether the ledgers can be trusted for the period.
I prepare that picture with your administration team:
Your advisors use this to prepare and file returns; the treatment and the filing are their decisions. The same pass covers the payroll file from your labor advisor, which often stops importing cleanly when accounts or cost centers change. It is mapped again, imported and reconciled to the payroll summary before the month is closed.
Getting one quarter closed cleanly does more for confidence than any status report. It shows management, the advisors and staff that the numbers can be relied on again, and it gives the rest of the recovery a stable base to build on.
While operations steady, I build the written account of what happened. I compare the contract and the integrator's proposal with the requirements, the plan with the change log, and the test evidence with the issue list. Then I hold separate conversations with management, process owners, key users and the integrator's lead, because people speak more openly one at a time.
The account usually shows shared causes: a scope defined from a demo rather than written requirements, late decisions on the company side, data that was messier than expected, changes accepted without resetting the plan. Presenting it neutrally lets both sides move on from arguing about the past.
The reset session then sorts every open item into essential, deferred, dropped or disputed. Disputed items are settled against the documents rather than by who argues hardest. What comes out is a new baseline in which each item has a named person and a test that proves it done.
Where the facts show the working relationship has run its course, I organize a handover: configuration documentation, ownership of localization modules and custom code, access credentials, open defects and test material, gathered before anyone leaves. Questions about penalties, withheld payments or termination go to your lawyer, who reviews the contract; I supply a factual timeline and a scope comparison. If a new integrator is needed, my ERP selection work in Spain reuses what the rescue produced.
With operations stable and the facts on paper, management can decide calmly. I set out the realistic routes:
Each route lists reusable work, the main risks and the cost drivers, without invented figures. Starting again is seldom the best answer, but I state it plainly when it is.
Whichever route is chosen, the next go-live is earned through fresh end-to-end tests with real SII, remittance and series cases, and a go/no-go meeting on written criteria, as described under ERP go-live support. Sessions run in the Spanish morning and early afternoon. Once things are stable, an ERP audit for Spain confirms what remains. Projects that are not yet in trouble are better served by my implementation oversight, and the Spain hub lists everything else.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
FAQ
I organize the fix. Failing records are grouped by cause, the causes are corrected in master data or configuration by the integrator or your team, and your asesor fiscal decides how already rejected records should be handled. I track every group until it is cleared, so the daily failures stop rather than being resent one by one.
The aim is to give them what they need: a clear cut-off between systems, reconciled ledgers, a list of pending records and every correction documented. Filing and tax treatment remain their responsibility. In a troubled period, organized evidence is usually what makes the difference between a manageable quarter and a chaotic one.
Only if the facts point there. Once open work is reclassified, responsibilities are put in writing and the company answers questions on time, the original integrator is often able to finish. Where trust or capacity has genuinely gone, I assemble a handover pack covering modules, custom code and credentials. Management decides, with a written assessment in hand.
Yes. The operational work goes ahead regardless, because invoices and remittances cannot wait. In parallel I build a neutral record of what was agreed, delivered and changed, which your lawyer can use. Keeping that record factual helps both sides, whether the dispute is settled or the project continues.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Insights
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.
