Skip to content
Log in

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 youDetails
Peppol access pointDelivers your invoices to the buyer’s access point (C2 → C3) and receives your invoices (C3 → C2)
Peppol registrationPublishes your company as a Peppol participant 0245:<DIČ>
Document generationYou send JSON, B2Brouter generates the Peppol BIS Billing 3.0 invoice or credit note
TDD reportingGenerates the TDD of each reportable invoice and sends it to the access point of the FS (C5)
FS answerReceives the Message Level Status (MLS) of the FS and updates the state of the TDD
Legal archiveStores 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.

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.

EnvironmentB2Brouter APIUse
Productionhttps://api.b2brouter.netReal invoices and real TDDs
Sandboxhttps://api.b2brouter.net with a test_ API keyTests of the full flow, with a simulated Peppol network and a simulated FS

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.

A Slovak company has three identifiers. Each one has its own place in B2Brouter:

IdentifierFormatSchemeWhere it goesWhat it activates
IČ DPH (VAT number)SK + 10 digitstin_scheme: 9950TIN of the account and of the contactsTDD reporting (automatic)
DIČ (tax number)10 digits"0245"Peppol identifier (pin_scheme, pin_value)Peppol participant 0245:<DIČ>
IČO (company number)8 digitscin_scheme: "0158"CIN (company number) of the accountNothing by itself
  • The 10 digits of the IČ DPH are the DIČ: SK2022222222 has 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 the account with POST /accounts. For Slovak TDD reporting, the account needs:

FieldValue
country"sk"
tin_scheme, tin_value9950, SK<DIČ>
cin_scheme, cin_value"0158", the IČO (optional)
address, city, postalcodethe address of the company
Terminal window
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"
}
}'

POST Account - API Reference

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, PUT and DELETE on /accounts/{ACCOUNT_ID}/tax_report_settings/sk return HTTP 409.
  • An account gets no sk setting 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 with a standard Peppol transport. For a Slovak account:

  • pin_scheme must be "0245", and pin_value is 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.
Terminal window
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.

A Slovak B2B buyer is a normal contact. These fields decide the routing and the TDD:

FieldValuePurpose
country"sk"A TDD is generated only for a buyer in Slovakia
tin_scheme, tin_value9950, 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, postalcoderequiredBT-52, BT-53
transport_type_code"peppol"Delivery through Peppol
document_type_code"xml.ubl.invoice.bis3"Peppol BIS Billing 3.0
Terminal window
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"
}
}'

POST Contact - API Reference

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.

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.

Terminal window
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" }
]
}
]
}
}'
  • 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, 388 and 393.
  • 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) with amended_number.

The TDD comes after the send: B2Brouter generates the TDD only after the Peppol send of the invoice succeeds. The response of POST /invoices therefore has an empty tax_report_ids. Read the invoice again later to get the ID.

The invoice follows the standard Peppol lifecycle:

StateMeaning
newCreated, not sent
sendingB2Brouter (C2) sends it through Peppol
sentThe buyer’s access point (C3) has it
registeredThe buyer’s access point (C3) confirmed the delivery
refusedThe buyer (C4) refused it
errorB2Brouter 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}.

B2Brouter generates the TDD of an issued invoice when all these conditions are true:

  1. The account is in Slovakia, has an IČ DPH (9950) and has the sk Tax Report Setting.
  2. The buyer is in Slovakia and has a tax ID.
  3. The supply is from 2027-01-01.
  4. The invoice type has a TDD (see Slovak invoice rules).
  5. 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.

  1. Read the invoice with GET /invoices/{INVOICE_ID}. The field tax_report_ids contains the ID of the TDD.
  2. Read the TDD with GET /tax_reports/{TAX_REPORT_ID}. Its type is SkTdd.
StateMeaning
newB2Brouter generated the TDD and has not sent it yet
sendingB2Brouter sends the TDD to the access point of the FS (C5)
sentThe access point of the FS has the TDD. The FS has not answered yet
registeredThe FS accepted the TDD
refusedThe FS refused the TDD. See errors
errorB2Brouter could not send the TDD. See errors
  • GET /tax_reports/{TAX_REPORT_ID}/download returns the TDD XML.
  • The TaxReport webhook fires on registered, refused and error.
  • B2Brouter creates, sends and finishes every TDD. POST, PATCH and DELETE of an sk TaxReport return HTTP 409.

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 ResponseCodeTDD 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'."
}
]
  • errors shows only the result of the current send. A new send clears it.
  • Subject to change: the text of description. Use code to identify the rule.
  • Subject to change: today errors has one item. Later versions can add one item for each reason.
  • Subject to change: DocumentReference/ID identifies the Peppol message that carried 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.

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 new to sending at once, and the simulated FS answers after a short delay.
  • Test buyers: the result depends on the buyer.
Buyer (pin_scheme:pin_value)NameInvoice stateTDD state
0245:2099999902Test SK — Registeredregisteredregistered
0245:2099999803Test SK — Refusedregisteredrefused
0245:2099999704Test SK — Invoice refusedrefusedregistered
0245:2099999605Test SK — TDD errorregisterederror
Any other SK buyersentregistered
  • The TIN of each test buyer is 9950 with SK + the same 10 digits, for example SK2099999902.
  • 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/ID is the UUID of the TDD.

See also Sandbox for the general Sandbox rules.

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.

Last updated: