ERPNext Accounting in Spain

A PGC chart and the Spanish tax templates

Spanish bookkeeping follows the Plan General de Contabilidad, with a simplified version for smaller companies. Its account numbering is familiar to every gestoria, so a chart that ignores it creates translation work every quarter. Whether a maintained Spanish chart template exists for your ERPNext version should be checked with Frappe or the partner; my approach is to build or adjust the chart with your advisor and keep management segments in cost centers and accounting dimensions.

Tax templates then need to cover cases a generic setup misses:

• IVA rates: each rate you charge, with item-level overrides for goods at reduced rates.
• Equivalence surcharge: retailers buying from you may be subject to it, so their customer record must add the surcharge line to every sale.
• Withholding: invoices from lawyers, consultants and landlords often carry withholding that reduces the amount paid; ERPNext handles this through deduction lines or withholding categories, which I test on real invoices.
• EU and export sales: intra-community supplies and reverse charge purchases routed through tax categories.
• Other territories: the Canary Islands, Ceuta and Melilla sit outside IVA with their own indirect taxes, so entities or customers there need separate templates.

Your asesor confirms each treatment. I confirm ERPNext applies it consistently and that the reports show what the returns need. General features are on ERPNext Accounting.

Invoice records under the Spanish invoicing software rules

Spain has introduced rules for the software that produces invoices. Broadly, invoice records should be complete, chained so later tampering is detectable, kept with an event log and, under one of the available modes, reported to the tax agency straight after issue. Who is affected, which mode applies and when it all takes effect are questions for your asesor, and the details have shifted before.

ERPNext has a useful starting point here, since posted invoices are locked and corrections happen through cancel-and-amend documents. A locked document, though, is still a long way from satisfying the rules. What I check, with the app publisher or service provider:

• Which component generates the chained records and the code or reference printed on the invoice.
• What the publisher states, in writing, about its position under the rules and the declaration it provides.
• How cancellations, amendments and corrective invoices are handled, each in its own series.
• What happens to records if the server is restored from a backup or the app is upgraded.

Self-hosted, customized ERPNext is not automatically covered by anyone's statement about the rules. If no route can be confirmed for your setup, a Spanish invoicing program issuing invoices beside ERPNext is the safer design; the ERPNext in Spain page describes those architectures.

SII, TicketBAI and what the ledger must hold

Companies within the SII regime send invoice data to the tax agency shortly after issuing or receiving each invoice. In the Basque provinces, TicketBAI applies through each provincial treasury, and Navarre runs its own arrangements. Public sector customers may require Facturae files through the government entry point. Your asesor tells you which apply to each company in your group.

Whatever app or external service handles the submission, the ERPNext ledger needs to hold the right data and the outcome:

• The invoice type and special regime key the submission requires, set by tax category so users do not choose it each time.
• Supplier invoice data entered completely, including the supplier's own invoice number and date, since purchase records are reported too.
• A status field per invoice showing accepted, accepted with errors, rejected or pending, which finance reviews before each period closes.
• Separate configuration for each company when entities sit in different tax territories.

I run a test cycle per company: standard invoices, a corrective invoice, a rejected record and its resubmission, and a supplier invoice. Have Frappe, the app maintainer or the partner confirm the app's status for your exact version shortly before go-live, since tax agency specifications change and community apps are updated on their own schedule.

Returns, the gestoria and Spanish bank files

In Spain the periodic IVA return, the withholding returns and the annual informative returns are usually prepared by an asesor or gestoria, often in their own Spanish software. ERPNext produces a general ledger, tax reports and custom reports, but not necessarily the return layouts your advisor files. I agree with them early whether they work from ERPNext reports, from an export into their package, or from a report built for the purpose, and test it on a full quarter of staging data.

On the banking side:

• Statements: Spanish banks provide statements in a standard domestic layout and often in other formats; I check which one your version imports cleanly, or whether a conversion step or app is needed.
• Direct debit remittances: SEPA collections for customers who pay by direct debit, with mandate data on the customer and returned debits posted back to receivables.
• Supplier payments: transfer batches and, if you use them, bank-managed supplier payment lines, where the bank's file and posting logic must be tested together.

Exporters to Latin America or the United Kingdom need foreign currency accounts and a revaluation routine agreed with the advisor. Groups with sister companies also need intercompany rules, described on the multi-company page.

Upgrades, ownership and when ERPNext is the wrong ledger

A Spanish compliance app is only as good as the speed with which someone updates it. When the tax agency changes a schema, the app must follow, and your ERPNext must be upgraded and retested without breaking reports. That is why I ask, before any configuration, who owns each piece: Frappe Cloud, your own servers or a partner's hosting for the platform; a community maintainer or paid provider for the Spanish app; an internal or contracted developer for custom reports. I document names and response expectations.

Upgrade rules I write into the plan:

• Rehearse every upgrade on a copy of production and rerun a closed quarter's reports.
• Avoid upgrades in the days before a filing deadline your asesor flags.
• Keep custom code in a separate app so core updates stay possible.

ERPNext Accounting is the wrong ledger in Spain when your gestoria keeps the books and will not work from another system, when nobody can own the compliance app, or when entities across several tax territories would multiply the app work beyond what your team can maintain. In those cases ERPNext can still run operations upstream, or a platform with a vendor-maintained Spanish localization, such as Odoo Accounting in Spain, may be simpler. I take no commission from any vendor. More on remote delivery is on the Spain ERP consultant page.