Connect a KROS Fakturácia account

Torevo Invoices does not use a shared Torevo account in KROS. Each merchant connects their own company in the KROS Fakturácia web application and remains responsible for its licence, accounting configuration and document correctness.

Which KROS package you need

Snapshot verified on 19 July 2026 against the KROS Fakturácia price list and KROS e-shop connection guide:

KROS package	Public monthly price	API prepojenie	Suitable for Torevo
Free	€0	not listed	no
Basic (Základ)	€5.90	optional €4.90 add-on	yes, after activating the add-on
Standard (Štandard)	€11.00	optional €4.90 add-on	yes, after activating the add-on
KROS Firma	€14.90	included	yes

KROS labels these as monthly prices for a 12-month payment period, excluding VAT. For basic Torevo invoicing, Základ plus API prepojenie is the lowest currently documented technical requirement. Torevo V1 does not require KROS Firma or KROS Sklad; choose them only for their additional KROS features. Prices and terms can change, so reconfirm them with KROS before purchase.

What to prepare

Prepare:

• a company created in the KROS Fakturácia web application,
• a purchased package with the active API prepojenie feature,
• complete company, invoice and VAT details,
• a numbering sequence intended for Shopify documents,
• a user allowed to create the API token and webhook,
• your accountant’s decision on dates, taxes, rounding and payments.

Create the API token

1. Sign in to the correct company in KROS Fakturácia.
2. Open Company settings → API connections.
3. Create a dedicated API connection with a clear name, for example Torevo – store.myshopify.com.
4. Do not create another connection for the same store by default; name each environment and legal entity unambiguously.
5. Generate the token only when you can store it safely. Copy it to a password manager and then into Torevo.
6. Never send the token by email or to support.

According to the KROS OpenAPI guide, KROS shows the token only when it is created. Resetting it invalidates the previous token, so replace it in Torevo immediately and run the connection check after rotation.

Create the provider account in Torevo

In Torevo Invoices → Providers → KROS, add an account and name it so the legal entity and environment are clear. Enter the API token. Torevo encrypts it and does not display it after storage.

Run Test connection. Continue only when the check confirms the expected company and available configuration. If you manage multiple companies, create a separate provider account for each and never copy tokens between them without checking company identity.

Callback and webhook secret

Torevo displays the account-specific HTTPS callback URL. Add it to the API connection in KROS and configure a webhook authorisation key. Store the same secret in Torevo.

KROS describes its callback URL and authorisation key as optional API settings, but both are required for Torevo’s authenticated asynchronous flow. If inbound payment changes from KROS are part of your workflow, also enable Notifikácie o úhradách do API on the same connection. That switch does not replace the callback URL.

Before the first document, verify:

• the URL belongs to the correct Shopify shop and provider account,
• it uses HTTPS and is not a local or temporary URL,
• the authorisation key matches on both sides,
• the first synthetic event does not report a signature error,
• old callback URLs are no longer active after a change.

Webhook events may repeat or arrive late. Torevo verifies and deduplicates them; disabling signature verification is not a supported workaround.

What KROS owns and what Torevo owns

Area	Source of truth
Supplier company data, VAT regime and available numbering sequences	KROS Fakturácia
Order, lines, discounts, shipping, currency and Shopify transactions	Shopify
Provider account, trigger, conditions, date and payment policy	Torevo Invoices
Number and final content of the accepted document	KROS Fakturácia
Submission, callback, PDF, reconciliation and decision-audit state	Torevo Invoices

A change in one system does not mean an accounting document in the other system should be rewritten. Correct issued documents through an accountant-approved process.

Numbering sequence and document dates

Select a dedicated or accountant-approved numbering sequence. Confirm its format, next number, period and year-boundary behaviour. Do not change it while documents are pending without a controlled transition.

Configure a supported date policy and verify issue, supply and due dates on a test order. The application does not make accounting decisions for the merchant.

PDF report and payment account

Choose a report available to the connected company. The current connector interface supports KROS reports identified as 17, 19 and 101, with 19 as the default. Always confirm availability and appearance in the specific company.

Optionally configure a payment account ID if your accounting flow needs one. Do not infer it from a display name. On the first invoice, inspect the supplier, customer, lines, taxes, totals, currency, due date, numbering and payment details in the PDF.

Accounting and automation decisions

Before document creation, confirm with the accountant:

• B2C and B2B customer identity,
• VAT status and supported rates,
• discounts, shipping and rounding treatment,
• supported currencies and countries,
• Shopify payment-gateway mappings,
• conditions for invoices, payments, refunds and credit notes,
• statutory retention and document access.

Keep automatic credit notes disabled until every live scenario is separately certified. An unknown combination must fail to manual review.

Required test before automation

Use a synthetic test order without real personal data. Create an invoice manually, receive its callback, open the PDF, register a supported payment and verify safe reconciliation. Repeat for B2B, discounts, shipping, tax and every currency you use.

Enable automation only after the merchant and accountant approve the internal checklist. Start with a narrow condition and monitor the first live documents.

Rotation or disconnection

If token exposure is suspected, reset it in KROS, update Torevo and verify the connection. Coordinate webhook-secret rotation on both sides so callbacks are not left unverifiable.

Disconnecting stops new operations. It does not delete statutory documents from KROS or change the merchant’s retention duties. Before uninstalling, export the required audit and confirm every pending operation.