Slovak e-Invoicing and TDD Reporting
Guide to integrating the B2Brouter API and complying with the Slovak e-invoicing and reporting obligation from your own system.
From 2027-01-01, each VAT payer registered in Slovakia must issue structured e-invoices for its domestic B2B supplies and send them through the Peppol network. The access point must also report the data of each invoice to the Financial Administration (Finančná správa, FS) as a Tax Data Document (TDD). B2Brouter does this for you: you send your invoice data through the REST API, and B2Brouter generates the Peppol BIS 3 invoice, delivers it to the buyer, and generates and sends the TDD.
| What B2Brouter does for you | Details |
|---|---|
| Peppol access point | Delivers your invoices to the buyer’s access point (C2 → C3) and receives your invoices (C3 → C2) |
| Peppol registration | Publishes your company as a Peppol participant 0245:<DIČ> |
| Document generation | You send JSON, B2Brouter generates the Peppol BIS Billing 3.0 invoice or credit note |
| TDD reporting | Generates the TDD of each reportable invoice and sends it to the access point of the FS (C5) |
| FS answer | Receives the Message Level Status (MLS) of the FS and updates the state of the TDD |
| Legal archive | Stores the invoices, the TDDs and the MLS answers for the legally required 10 years |
The path to your first invoice: create your account with the IČ DPH → check the sk Tax Report Setting → enable Peppol → create a contact → issue the invoice → follow the TDD.
Regulatory context: Act 385/2025 Coll. amends the Slovak VAT Act (222/2004 Coll.). From 2027-01-01, a VAT payer issues e-invoices (EN 16931) for domestic supplies to businesses and legal persons established in Slovakia, and sends them through a certified delivery service (a Peppol access point). The supplier and the customer report the invoice data to the Financial Administration within five days, through the delivery service. Every domestic taxable person and legal person must be able to receive e-invoices. From 2030-07-01, the final rules apply: per-transaction reporting of domestic and cross-border supplies, and the end of the control statement.
Who is this guide for?
Section titled “Who is this guide for?”eDocExchange: companies that connect their ERP or accounting software to B2Brouter. You create the account once (web UI or API), then you issue invoices and follow their lifecycle through the API.
eDocSync: software vendors that offer Slovak compliance to their own customers. You create the accounts of your customers through the API, issue their invoices and follow the lifecycle. Your customers do not need a B2Brouter login.
The Slovak functions are the same in both models.
Before you start
Section titled “Before you start”Environments
Section titled “Environments”| Environment | B2Brouter API | Use |
|---|---|---|
| Production | https://api.b2brouter.net | Real invoices and real TDDs |
| Sandbox | https://api.b2brouter.net with a test_ API key | Tests of the full flow, with a simulated Peppol network and a simulated FS |
API credentials
Section titled “API credentials”Authentication uses a static API key in the X-B2B-API-Key HTTP header. Generate it in the B2Brouter UI under Developers → API Keys. Also set X-B2B-API-Version in every request.
New to the API? Start with the API introduction: environments, API key and first request.
Slovak identifiers
Section titled “Slovak identifiers”A Slovak company has three identifiers. Each one has its own place in B2Brouter:
| Identifier | Format | Scheme | Where it goes | What it activates |
|---|---|---|---|---|
| IČ DPH (VAT number) | SK + 10 digits | tin_scheme: 9950 | TIN of the account and of the contacts | TDD reporting (automatic) |
| DIČ (tax number) | 10 digits | "0245" | Peppol identifier (pin_scheme, pin_value) | Peppol participant 0245:<DIČ> |
| IČO (company number) | 8 digits | cin_scheme: "0158" | CIN (company number) of the account | Nothing by itself |
- The 10 digits of the IČ DPH are the DIČ:
SK2022222222has the DIČ2022222222. - The IČO is always a company number (
cin_scheme), never a TIN. - Slovak Peppol identifies every participant with the DIČ (
0245). The IČ DPH (9950) is not a valid Peppol identifier in Slovakia.
Create your company account
Section titled “Create your company account”Create the account with POST /accounts. For Slovak TDD reporting, the account needs:
| Field | Value |
|---|---|
country | "sk" |
tin_scheme, tin_value | 9950, SK<DIČ> |
cin_scheme, cin_value | "0158", the IČO (optional) |
address, city, postalcode | the address of the company |
curl --request POST \ --url https://api.b2brouter.net/accounts \ --header 'X-B2B-API-Key: {YOUR_API_KEY}' \ --header 'X-B2B-API-Version: {YOUR_API_VERSION}' \ --header 'Content-Type: application/json' \ --data '{ "account": { "name": "Príklad s.r.o.", "country": "sk", "currency": "EUR", "tin_scheme": 9950, "tin_value": "SK3000000003", "cin_scheme": "0158", "cin_value": "30000009", "address": "Testovacia 1", "city": "Bratislava", "postalcode": "81101", "email": "billing@example.sk" } }'The sk Tax Report Setting
Section titled “The sk Tax Report Setting”B2Brouter creates the sk Tax Report Setting itself when an account in Slovakia has an IČ DPH (9950): when you create the account, or when you add the IČ DPH later. You do not create it.
To see it, use GET /accounts/{ACCOUNT_ID}/tax_report_settings:
{ "tax_report_settings": [ { "code": "sk", "start_date": "2027-01-01T00:00:00.000Z", "auto_generate": true, "auto_send": false, "enabled": true, "locked": false, "created_at": "2026-11-09T10:42:19.726Z", "updated_at": "2026-11-09T10:42:19.726Z" } ], "meta": { "total_count": 1, "offset": 0, "limit": 25 }}- The reporting starts on 2027-01-01. Supplies before that date have no TDD.
- B2Brouter manages this setting.
POST,PUTandDELETEon/accounts/{ACCOUNT_ID}/tax_report_settings/skreturn HTTP 409. - An account gets no
sksetting when it is not in Slovakia, when it has no IČ DPH, or when it is an organisational unit (office). An office reports through its parent account.
Enable Peppol
Section titled “Enable Peppol”Enable Peppol with a standard Peppol transport. For a Slovak account:
pin_schememust be"0245", andpin_valueis the DIČ (the 10 digits of the IČ DPH). B2Brouter refuses another scheme with HTTP 422.- Invoice and Credit Note are always enabled, because every Slovak receiving participant must accept both. Self-billing stays disabled.
curl --request POST \ --url https://api.b2brouter.net/accounts/{ACCOUNT_ID}/transports \ --header 'X-B2B-API-Key: {YOUR_API_KEY}' \ --header 'X-B2B-API-Version: {YOUR_API_VERSION}' \ --header 'Content-Type: application/json' \ --data '{ "transport": { "code": "peppol", "enabled": true, "reception": true, "standard_documents": true, "invoice": true, "credit_note": true, "self_billing": false, "application_response": true, "pin_scheme": "0245", "pin_value": "3000000003" } }'POST Transport - API Reference
B2Brouter publishes your company as the Peppol participant 0245:<DIČ> in the B2Brouter SMP. The Slovak central SMP is not active yet. When it is, B2Brouter publishes there.
Create a contact
Section titled “Create a contact”A Slovak B2B buyer is a normal contact. These fields decide the routing and the TDD:
| Field | Value | Purpose |
|---|---|---|
country | "sk" | A TDD is generated only for a buyer in Slovakia |
tin_scheme, tin_value | 9950, SK<DIČ> | Tax ID of the buyer (BT-48). A TDD is generated only for a buyer with a tax ID |
pin_scheme, pin_value | "0245", <DIČ> | Peppol identifier of the buyer (BT-49) |
city, postalcode | required | BT-52, BT-53 |
transport_type_code | "peppol" | Delivery through Peppol |
document_type_code | "xml.ubl.invoice.bis3" | Peppol BIS Billing 3.0 |
curl --request POST \ --url https://api.b2brouter.net/accounts/{ACCOUNT_ID}/contacts \ --header 'X-B2B-API-Key: {YOUR_API_KEY}' \ --header 'X-B2B-API-Version: {YOUR_API_VERSION}' \ --header 'Content-Type: application/json' \ --data '{ "contact": { "name": "Odberateľ a.s.", "address": "Hlavná 10", "city": "Košice", "postalcode": "04001", "country": "sk", "currency": "EUR", "tin_scheme": 9950, "tin_value": "SK3000000014", "pin_scheme": "0245", "pin_value": "3000000014", "transport_type_code": "peppol", "document_type_code": "xml.ubl.invoice.bis3" } }'Buyers outside Slovakia: an invoice to a buyer outside Slovakia has no TDD. B2Brouter delivers it through Peppol with the buyer’s own scheme, as for any other country.
Issue invoices
Section titled “Issue invoices”Create the invoice with the standard Invoice API, POST /accounts/{ACCOUNT_ID}/invoices. Use send_after_import: true to create and send it in one step.
curl --request POST \ --url https://api.b2brouter.net/accounts/{ACCOUNT_ID}/invoices \ --header 'X-B2B-API-Key: {YOUR_API_KEY}' \ --header 'X-B2B-API-Version: {YOUR_API_VERSION}' \ --header 'Content-Type: application/json' \ --data '{ "send_after_import": true, "invoice": { "type": "IssuedInvoice", "contact_id": {CONTACT_ID}, "number": "FA2027-0001", "date": "2027-01-15", "tax_point_date": "2027-01-15", "due_date": "2027-02-14", "currency": "EUR", "invoice_lines_attributes": [ { "quantity": 10.0, "description": "Consulting services", "price": 150.0, "taxes_attributes": [ { "name": "DPH", "percent": 23.0, "category": "S" } ] } ] } }'Slovak invoice rules
Section titled “Slovak invoice rules”- Supply date: give the date of the supply (
tax_point_date, BT-7). B2Brouter uses it to decide whether the invoice has a TDD. Without it, B2Brouter uses the delivery date, then the end of the invoicing period, then the invoice date. - VAT rates: 23 %, 19 % and 5 %.
- Document types with a TDD:
380,381,383,388and393. - No TDD: type
384, self-billing (389,261), simplified invoices, proformas, and invoices with only exempt lines. - Corrections: you cannot change an invoice after you send it. To correct it, issue a credit note (
381) or a new invoice (380) withamended_number.
The TDD comes after the send: B2Brouter generates the TDD only after the Peppol send of the invoice succeeds. The response of
POST /invoicestherefore has an emptytax_report_ids. Read the invoice again later to get the ID.
Invoice lifecycle
Section titled “Invoice lifecycle”The invoice follows the standard Peppol lifecycle:
| State | Meaning |
|---|---|
new | Created, not sent |
sending | B2Brouter (C2) sends it through Peppol |
sent | The buyer’s access point (C3) has it |
registered | The buyer’s access point (C3) confirmed the delivery |
refused | The buyer (C4) refused it |
error | B2Brouter could not deliver it. Read the error, correct the cause and send again |
Use webhooks to follow the state changes, or read the invoice with GET /invoices/{INVOICE_ID}.
TDD reporting
Section titled “TDD reporting”When B2Brouter generates a TDD
Section titled “When B2Brouter generates a TDD”B2Brouter generates the TDD of an issued invoice when all these conditions are true:
- The account is in Slovakia, has an IČ DPH (
9950) and has theskTax Report Setting. - The buyer is in Slovakia and has a tax ID.
- The supply is from 2027-01-01.
- The invoice type has a TDD (see Slovak invoice rules).
- The Peppol send of the invoice succeeded.
The TDD reports the invoice that B2Brouter delivered through Peppol. You do not send any TDD data: B2Brouter takes it from the invoice.
Follow the TDD
Section titled “Follow the TDD”- Read the invoice with
GET /invoices/{INVOICE_ID}. The fieldtax_report_idscontains the ID of the TDD. - Read the TDD with
GET /tax_reports/{TAX_REPORT_ID}. ItstypeisSkTdd.
| State | Meaning |
|---|---|
new | B2Brouter generated the TDD and has not sent it yet |
sending | B2Brouter sends the TDD to the access point of the FS (C5) |
sent | The access point of the FS has the TDD. The FS has not answered yet |
registered | The FS accepted the TDD |
refused | The FS refused the TDD. See errors |
error | B2Brouter could not send the TDD. See errors |
GET /tax_reports/{TAX_REPORT_ID}/downloadreturns the TDD XML.- The TaxReport webhook fires on
registered,refusedanderror. - B2Brouter creates, sends and finishes every TDD.
POST,PATCHandDELETEof anskTaxReport return HTTP 409.
The FS answer (MLS)
Section titled “The FS answer (MLS)”The FS answers each TDD with a Peppol Message Level Status (MLS): a UBL ApplicationResponse in the OpenPeppol MLS format (urn:peppol:edec:mls:1.0). B2Brouter receives it and updates the state of the TDD.
MLS ResponseCode | TDD state |
|---|---|
AP (accepted) | registered |
RE (rejected) | refused |
To get the MLS, use GET /tax_reports/{TAX_REPORT_ID}/download_response:
- It returns the MLS of the current send of the TDD.
- It returns HTTP 404 while the FS has not answered.
- For a TDD in
error, it returns HTTP 422 with the send error.
A refused MLS has an overall description and one line for each broken rule, with the rule and its text, and a status reason code such as BV (business rule violation):
<cac:DocumentResponse> <cac:Response> <cbc:ResponseCode>RE</cbc:ResponseCode> <cbc:Description>Rejected due to validation errors</cbc:Description> </cac:Response> <cac:DocumentReference> <cbc:ID>…</cbc:ID> </cac:DocumentReference> <cac:LineResponse> <cac:LineReference><cbc:LineID>NA</cbc:LineID></cac:LineReference> <cac:Response> <cbc:Description>[ibr-tdd-01] – The cbc:CustomizationID (TDT-001) element MUST have the value 'urn:peppol:taxdata:sk-1'.</cbc:Description> <cac:Status><cbc:StatusReasonCode>BV</cbc:StatusReasonCode></cac:Status> </cac:Response> </cac:LineResponse></cac:DocumentResponse>The TaxReport also shows the reason in errors:
"errors": [ { "code": "ibr-tdd-01", "description": "BV: The cbc:CustomizationID (TDT-001) element MUST have the value 'urn:peppol:taxdata:sk-1'." }]errorsshows only the result of the current send. A new send clears it.- Subject to change: the text of
description. Usecodeto identify the rule. - Subject to change: today
errorshas one item. Later versions can add one item for each reason. - Subject to change:
DocumentReference/IDidentifies the Peppol message that carried the TDD.
If the FS refuses the TDD
Section titled “If the FS refuses the TDD”The FS refuses a TDD when the invoice data breaks a rule. Read errors, correct the data, and issue a corrective invoice: a credit note (381), or a new invoice (380) with amended_number.
Receiving invoices
Section titled “Receiving invoices”Testing in the Sandbox
Section titled “Testing in the Sandbox”The Sandbox runs the full issue flow with a simulated Peppol network and a simulated FS. Use a test_ API key. Your Sandbox is a copy of your production company.
What is different in the Sandbox:
- No 2027 limit: any supply date generates a TDD, so you can test now.
- Peppol transport: the company of the Sandbox gets an active transport
0245:<DIČ>when B2Brouter creates the Sandbox. - Automatic send: the TDD goes from
newtosendingat once, and the simulated FS answers after a short delay. - Test buyers: the result depends on the buyer.
Buyer (pin_scheme:pin_value) | Name | Invoice state | TDD state |
|---|---|---|---|
0245:2099999902 | Test SK — Registered | registered | registered |
0245:2099999803 | Test SK — Refused | registered | refused |
0245:2099999704 | Test SK — Invoice refused | refused | registered |
0245:2099999605 | Test SK — TDD error | registered | error |
| Any other SK buyer | sent | registered |
- The TIN of each test buyer is
9950withSK+ the same 10 digits, for exampleSK2099999902. - New Sandboxes of a Slovak company include these four contacts. If your Sandbox existed before, create the contacts yourself with the identifiers in the table.
- The test buyer “Refused” always gives the rule
ibr-tdd-01. The real FS can refuse for other rules. - The test buyer “TDD error” always gives the error code
SK_C5_UNREACHABLE, and it fails on every send. Subject to change: production can use other codes. - In the Sandbox, the MLS
DocumentReference/IDis the UUID of the TDD.
See also Sandbox for the general Sandbox rules.
Limitations
Section titled “Limitations”These cases are not available yet:
- A TDD that replaces (
R) or cancels (D) an earlier one. - A buyer without an IČ DPH.
- A buyer that is not on Peppol.
- The automatic checks of the Slovak invoice particulars (§ 74 of the VAT Act).
- Self-billing invoices.