Business Central Consultant in Spain

What the Spanish version covers, and what partners add

Microsoft localizes Business Central for Spain directly. The Spanish version has included the national accounting plan, Spanish VAT reporting, SII submission and the Cartera functionality for bills and payment orders. That is a strong base, and it changes the conversation: many Spanish requirements are configuration rather than development.

It is not the whole picture. The invoicing software rules have required updates, and Microsoft and partners have been responding; Basque entities need TicketBAI support, which typically comes from partner apps; Navarre and public sector e-invoicing may involve further components. I build a coverage map from your advisor's list:

• Standard in the Spanish version, confirmed in a sandbox on your target version.
• Partner app, with publisher, licensing, support terms and how it tracks Microsoft's update cycle.
• Manual or external, with the person or service responsible.

The map becomes part of the statement of work, so each obligation has an owner before signing. Your asesor fiscal decides what applies; I make sure the system is shown to meet it. The Business Central page covers the product without the Spanish layer.

VAT posting groups for mainland, islands and special regimes

Business Central applies tax through the combination of VAT business and product posting groups. In Spain that matrix has to cover more cases than most countries: standard and reduced rates, intra-EU acquisitions and supplies, exports, domestic reverse charge, the equivalence surcharge that applies to certain retail customers, and, for companies selling into the Canary Islands, Ceuta or Melilla, sales outside the scope of mainland VAT.

Companies operating in the Canary Islands themselves usually need an entity configured for the islands' indirect tax, with its own returns. I treat that as a separate design question rather than a few extra codes.

My method:

• List every combination of customer or supplier type and item type the business produces.
• Agree the treatment of each with your advisor, in writing.
• Design the matrix and the default posting groups on customers, suppliers and items, so users rarely choose.
• Test each combination with a posted document and check the VAT report and SII record it produces.

Dimensions follow the same discipline: region, channel and cost center defaulted from master data, mandatory where reporting depends on them, and mapped to the parent's structure for subsidiaries. My solution design service explains how I document both.

Cartera, SEPA remittances and payment files

Spanish receivables and payables often move as documents rather than simple open invoices. Business Central's Cartera functionality handles bills and invoices as receivable or payable documents, groups them into bill groups or payment orders, and tracks them through presentation, discount, collection and rejection. For companies that rely on remittances, this is one of the Spanish version's most useful features, and one of the easiest to misconfigure.

I work through the cycle with your treasury contact:

• Which payment methods create documents, and which settle directly.
• How SEPA direct debit remittances are generated and how returned debits reopen receivables with fees.
• How supplier payment orders are approved and exported as SEPA transfers.
• How confirming lines offered by your banks are handled, which may need partner extensions.
• How bank statements are imported and matched.

Each bank is tested with real files before go-live, because acceptance rules differ between banks. Any step left manual is added to the month-end checklist with a named person. The finance automation page shows the wider patterns I use.

Reading the partner's statement of work

Business Central reaches Spanish customers through Microsoft's partner network, and the statement of work you sign with a partner sets the real scope. I am independent of that network: I hold no partner status, have no licenses to sell and accept no introduction fees, so I can read the document entirely from your side.

What I check in Spanish proposals:

• Regional components. Which apps are assumed for TicketBAI, Navarre or public sector invoicing, who publishes them and whether their subscriptions are included.
• Certificates and submissions. Who sets up the digital certificate for SII and other submissions and who monitors errors after go-live.
• Migration lines. Which objects, how much history, who cleanses data and who reconciles balances with the gestoría.
• Training. Which roles, in which language and how many sessions are assumed.
• Acceptance. Whether sign-off depends on your test scripts or the partner's checklist.

You get the document back annotated: open questions in the margin and alternative wording where a line is vague, so negotiation focuses on substance. The method is set out under vendor proposal review; platform-level questions are on Dynamics 365 in Spain.

When Business Central is more than a Spanish company needs

Business Central earns its place in Spanish companies with several entities, a parent that reports in another structure, real treasury complexity or growth that outpaces a small accounting program. It is harder to justify when:

• A single company sells mainly services, invoices modestly and relies on its gestoría for the books; a lighter option such as Zoho Books may be enough if its invoicing compliance is evidenced.
• An online seller or distributor wants stock, web orders and accounting in one package without add-on apps; compare Odoo Accounting in Spain.
• Nobody internally can own the partner relationship, the apps and the update cycle.

Where Business Central fits, the work above protects the investment: a coverage map, an agreed posting matrix, tested bank files and a contract you understand. Sessions are remote, scheduled in the Spanish morning, with written notes afterward. The Spain hub and the ERP consultant in Spain page describe my wider approach.