Business Central, SII and Verifactu: how to connect Dynamics 365 with the Verifacti APIs
There is no official Verifacti plugin for Microsoft Dynamics 365 Business Central: it connects through the API. Business Central exports each posted invoice and your development or your partner sends it as JSON to the SII API or, if the company is not in the SII, to the Verifactu API; the Spanish Tax Agency (AEAT) response comes back by webhook. For B2B e-invoicing (RD 238/2026), which arrives on 6 October 2027 for businesses with turnover over €8M (date published in the BOE), Verifacti is preparing the E-invoicing API (coming soon).
Which APIs you need for Business Central
First, the ones a large company needs: the SII API and the E-invoicing API (coming soon). Then the Verifactu API, for group companies outside the SII. Underneath them all, the NIF management API: integrated once to register the companies, manage the representation form and receive webhooks. Which obligation each company has is set by the rules, not by Verifacti.
How to connect Business Central with the API
Flow: invoice posted in Business Central → export or event → your middleware or development → Verifacti API → AEAT → webhook to your system.
- Create your free account and register the companies' NIFs with the NIF management API.
- Sign the representation form of each NIF.
- Map the fields of the posted sales invoice to the API JSON.
- Send each invoice with
POST /sii/createor, in batches, withPOST /sii/create_bulk. - Get the AEAT response by webhook and store it with the invoice.
Does your group have several companies, or does a consultancy maintain your Business Central? See large companies and IT consultancies.
Example: sending an invoice to the SII
A full invoice (F1) with POST /sii/create, as in the SII API documentation and validated against its rules. Your development builds this JSON from the Business Central invoice. To retry without duplicates, add the Idempotency-Key header.
{
"ejercicio": "2026",
"periodo": "11",
"serie": "A",
"numero": "1",
"fecha_expedicion": "19-11-2026",
"tipo_factura": "F1",
"clave_regimen": [
"01"
],
"descripcion": "Factura normal",
"nombre": "Nombre cliente",
"nif": "A15022510",
"desglose": {
"no_exenta": {
"tipo_no_exenta": "S1",
"detalle_iva": [
{
"tipo_impositivo": "21",
"base_imponible": "200",
"cuota_repercutida": "42"
}
]
}
},
"importe_total": "242"
}The AEAT response arrives by webhook, with the NIF management API. More cases in the SII examples.
Special cases in Business Central
| Case | What to do | Read more |
|---|---|---|
| Several companies | One NIF per company in the NIF management API, each with its own API key | NIF management API |
| Credit notes and corrective invoices | In the SII, tipo_factura R1–R5 with tipo_rectificativa S (replacement) or I (differences) | SII keys |
| Simplified invoices and tickets | F2; in the SII, same-day ones can go in an F4 summary entry if they meet art. 63.4 of the VAT Regulation | SII keys |
| Transactions with IGIC or IPSI | Regime key 08 in the SII | SII keys · in Verifactu, IGIC invoice |
| Correcting a record the AEAT already has | PUT /sii/modify or POST /sii/cancel; if it ended Incorrecto, fix it and send it again with POST /sii/create | SII API documentation |
| Retries | Idempotency-Key header: the same submission is not duplicated for 24 hours | SII API documentation |
| Companies outside the SII | They send to the Verifactu API with the same pattern | Verifactu API |
Dates
The first row only applies if you build the connector to sell it: then you sell invoicing software. For those who invoice, the Verifactu dates are published in the BOE and the postponement to October 2028 is announced with no rule published. The SII has been in force since 2017, and B2B e-invoicing has dates published in the BOE (RD 238/2026).
| Who | Date | Status | Rule |
|---|---|---|---|
| Producers and resellers of invoicing software RDL 15/2025 did not change this date. | Since 29 Jul 2025 | In force | RD 1007/2023 · Orden HAC/1177/2024 |
| SII: large companies (over €6M), REDEME and VAT groups Since 1 January 2025, also holders of hydrocarbon tax warehouses (RIVA, art. 71.3). | Since 1 Jul 2017 | In force | RD 596/2016 |
| B2B e-invoicing: turnover over €8M | 6 Oct 2027 | Published in the BOE, future date | RD 238/2026 · Orden HAC/1028/2026 |
| B2B e-invoicing: all other businesses and professionals Invoice statuses optional until 6 October 2029 for individuals and pass-through entities up to €8M. | 6 Oct 2028 | Published in the BOE, future date | RD 238/2026 · Orden HAC/1028/2026 |
| Corporate Income Tax payers | 1 Jan 2027 | Published in the BOE, future date | RDL 15/2025 |
| Everyone else, including the self-employed | 1 Jul 2027 | Published in the BOE, future date | RDL 15/2025 |
| Postponement of the pending obligations The note does not specify the scope for businesses invoicing over €8M. | Oct 2028 | Announced, no rule published | Nota de Hacienda, 5 oct 2026 |
This is not advice: each taxpayer determines what applies to them with their adviser.
More detail in Verifactu dates, SII deadlines and e-invoicing dates.
Pricing
The SII has custom pricing based on your invoice volume: ask for a quote via contact. The Verifactu API has a public tariff. The E-invoicing API has no price yet.
Custom pricing
See pricing- SII API: custom pricing based on your invoice volume.
- Verifactu API: from €14.99 per month for the first NIF active in production, VAT excluded.
- Free account and test environment at no cost.
Developer resources
For your AI: llms.txt and the OpenAPI specification.
Questions about Business Central and Verifacti
More questions about the SIIIs there a Verifacti plugin for Business Central?
How will B2B e-invoicing fit into Business Central without changing ERP?
Can I send the SII of several group companies?
Do I need a digital certificate to send to the AEAT?
How much does it cost?
Other integrations
Connect Business Central in the test environment
Create your free account: it includes the SII test environment. Support activates your SII test NIF.