Contact Info
Why map business processes in a Spanish company before choosing software?
Mapping processes first shows a Spanish company where invoices, approvals and payments really wait, which matters when invoice records must reach the tax agency within a short window under SII. I chart sales, purchasing and the close, settle what the gestoría receives and on what rhythm, and assign owners to remittance, confirming and sign-off steps. Software is chosen afterward. I work remotely and independently.
Last reviewed by Vikas Saroj
In many Spanish companies, invoices used to be sorted out at the end of the month or the quarter. Supplier bills waited in a tray, the gestoría collected a folder, and the books caught up later. For companies in the SII regime that rhythm no longer fits, because invoice records have to reach the tax agency shortly after issue or registration. The process has to change before any system can keep up.
As an independent process consultant, I work remotely with Spanish SMEs, exporters and subsidiaries of foreign groups to map how sales, purchasing, payments and the close really run, find where they wait or repeat, and design a future process with clear owners. Once the process is agreed, it becomes the brief for your current program, a new ERP or simply a better routine.
Vendors and integrators pay me nothing, so no product shapes the recommendations. The engagement runs in English; Any Spanish, Catalan or Basque wording is drafted or proofread on your side, by staff or a Spanish partner, and tax interpretation stays with your asesor fiscal.
The deliverables describe how your company should work, so they remain valid whatever software you choose later.
Short online sessions with the people who take orders, receive goods, record invoices and prepare payments, drawn as swimlane maps that show each wait, re-keyed figure and spreadsheet along the way.
A procure-to-pay design where invoices are registered promptly on arrival and approved in a parallel step, so reporting deadlines your asesor fiscal confirms are not hostage to a slow approver.
A written agreement of what moves between your company and the gestoría: documents, reconciliations, payroll inputs and questions, with owners and a monthly rhythm both sides can follow.
Order to cash mapped through to SEPA direct debit remittances, returned debits, transfers and any remaining promissory notes, with a rule for who acts on each return and how fast.
Payment proposals, confirming lines with your bank and transfers organized so preparation, approval and release sit with different people, and changed bank details are verified before money moves.
Short procedures per role, a named owner per process and a review routine, so the design survives staff turnover and a growing number of entities or regions.
Follow documents through the company
Agree pacing, owners and limits
Make it the daily routine
Plenty of Spanish companies built their back office around a monthly or quarterly rhythm. Sales invoices were checked at month-end, supplier invoices piled up until someone approved them, and the gestoría received a folder or a shared drive full of documents to book and file. That rhythm worked when the tax calendar was quarterly.
For companies within the SII regime, invoice records go to the tax agency within a short window after issue or registration. Whether your company is in scope, and how the window is counted, is for your asesor fiscal to confirm. What I look at is the process: if a supplier invoice waits for weeks in a manager's inbox before anyone records it, the problem is not the software. It is the order of the steps.
So the first workshops follow real documents. A recent sales order and its invoice, a supplier invoice and its payment, a direct debit remittance and its returns. I map who touches each one, in which system, and where it waits. A frequent finding is that registration, approval and payment are tangled into a single step that only one person can perform.
Where that is the case, untangling them is the core of the redesign, and it is pure process work. I describe the underlying workshop method under business process consulting.
A common design for Spanish procure to pay separates two things that many companies treat as one: recording that an invoice exists, and agreeing that it should be paid.
This order keeps reporting on time without forcing managers to approve under pressure. It also gives finance a clear view of liabilities that are recorded but not yet approved, which helps cash planning.
The same pacing applies to sales. Invoices should be issued from one controlled series per channel or entity, and corrections handled through corrective invoices rather than edits. Under newer invoicing software rules, records of issued invoices are expected to stay intact, so the process needs a clear route for every correction. Your asesor fiscal confirms which rules apply; I make sure each correction has an owner and a defined path.
Turning this design into formal requirement lines is the job of my Spanish ERP business analyst work.
Spanish companies collect and pay in ways that shape the process. On the collection side, SEPA direct debit remittances are common for recurring customers, alongside transfers and, in some sectors, promissory notes. On the payment side, many companies use confirming lines with their bank so suppliers can be paid early through the bank while the company pays at maturity.
In the order-to-cash map I make sure each path has an owner and a rule:
In procure to pay I separate preparation, approval and release of payments, including what is sent to the confirming line. Changed supplier bank details are confirmed through a known contact before any payment. Release sits with people authorized by the company's powers of attorney, and your legal advisor confirms who holds them.
Approval limits by amount and area complete the design. Where approvals are the main source of delay, my approval workflows page covers the options in more depth.
Outsourcing tax filings, payroll or both to a gestoría is a long-standing Spanish arrangement. The handoff is often informal: documents sent when someone remembers, questions answered by phone, reconciliations done twice. Mapping the close and the payroll cycle turns it into something explicit.
I agree with you and the gestoría:
Payroll inputs carry personal data, so the maps show where each item travels and who sees it. Your data protection advisor reviews that under GDPR and Spanish data protection law; I raise the questions and leave the legal view to them.
Companies selling to public bodies have one more path: invoices sent through the public administration's electronic invoice portals, with their own codes and status checks. I map that as a separate variant of order to cash, owned by someone who checks status until the invoice is accepted. Regional differences, such as Canary Islands tax or Basque systems, are marked as variants on the same map.
Spanish groups often run several companies, sometimes across tax territories, sometimes with Latin American subsidiaries reporting to Madrid or Barcelona. I build one map per end-to-end process with clearly marked local variants, so the shared core stays standard and the differences are deliberate rather than accidental. Intercompany recharges and the group close get their own map, with the steps each entity finishes before consolidation.
What you take away: maps of today and of the target, a problem log sorted by impact, the sign-off matrix, the written gestoría arrangement, job-level instructions and a requirement list. All of it stays with you in editable form.
Only now does software return to the table. Sometimes the agreed process fits your current program with better setup. Sometimes it justifies a new platform, and then my Spanish ERP selection service and the Spain ERP consultant page take over. Steps the maps flag as repetitive move on to my Spanish business automation work.
Everything I offer companies in this market is summarized on the Spain overview. Work runs remotely, with sessions placed in the hours where Spanish and Indian working days overlap.
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.
No. Whether SII applies, and how deadlines are counted, is for your asesor fiscal to confirm. Once they have, I design the process so invoices are issued and registered at a pace that fits, with owners for each step and a route for corrections, rejections and late documents.
Usually only a little. The aim is to agree what your team prepares, what the gestoría does and how questions flow between you. A clearer handoff reduces chasing on both sides. Their professional responsibilities and methods remain theirs; the map just makes the shared steps predictable.
Yes, that is the best time. The maps and requirement list become the brief for any system decision, so vendors are measured against how your company works rather than against their demo. Sometimes the agreed process shows that the current program can stay with better setup.
The engagement runs in English, so the reference text of every procedure is English. Spanish, Catalan or Basque editions are then drafted by your staff or a Spanish partner from an agreed term list, which keeps vocabulary consistent. Changes are made to the master first and then reflected in each language.
The company's powers of attorney and internal decisions set who may commit and pay on its behalf, and your legal advisor confirms them. My part is the daily process: who prepares a payment run or confirming file, who checks it, who releases it and how absences are covered.
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
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.