Open documentation navigation
Invoicing workflow

Torevo Invoices with KROS private beta

Prerequisites, safe KROS connection, invoice preparation, payment reconciliation, PDF access and recovery in the Torevo Invoices private beta.

Updated: 18 July 2026
On this page

Torevo Invoices is a provider-neutral Shopify invoicing application. Its first private-beta provider connects eligible Shopify orders with KROS Fakturácia and keeps document state, payment processing, recovery and authenticated PDF access close to the order.

Controlled private beta

The application is not a public KROS or Shopify App Store release yet. Access requires an approved pilot, a compatible KROS account and completion of the live certification checklist.

Torevo is an independent software provider. Use of the KROS name describes compatibility and does not claim an official, certified or partner relationship.

Prerequisites

The pilot merchant needs:

  • a compatible Shopify store and authority to transfer order and invoice data,
  • a supported KROS account, licence and API access,
  • an approved pilot shop on the Torevo allowlist,
  • confirmed invoice numbering, VAT and date policies from the merchant’s accountant,
  • a completed test plan using synthetic customer and order data.

KROS licensing or usage fees are separate from any Shopify-billed Torevo plan.

Connect KROS safely

Open Torevo Invoices → KROS, create a provider account and enter the API token. The token is encrypted and write-only; the app reports whether it exists but never displays it again.

Run the connection check, select an eligible numbering sequence and register the account-specific HTTPS callback URL in KROS. A callback is processed only after its signature passes verification. Replayed events are deduplicated.

Do not paste tokens, callback secrets, invoice PDFs or customer records into a support message.

Configure invoice rules

Review these settings before preparing a document:

  1. document numbering and date policy,
  2. VAT payer status and supported tax treatment,
  3. partner identity source for B2C and B2B orders,
  4. product, discount and shipping-line mapping,
  5. payment profiles for known Shopify gateways,
  6. automatic-creation rules and their kill switches.

Unknown gateways, missing business identity, unsupported currency/tax combinations and total mismatches fail closed to merchant review.

Prepare and submit an invoice

Open an order in Torevo Invoices or use the Shopify Admin order action. The app re-queries Shopify, builds a fresh preview and reconciles products, discounts, shipping, taxes and the final total.

Submission is asynchronous. After KROS accepts a request, Torevo stores the request identifier and waits for the signed callback or safe reconciliation. It never creates another invoice merely because a callback is delayed.

The document moves through explicit states such as prepared, submitted, processing, accepted, PDF pending, ready or needs attention. Raw KROS responses and customer payloads are not shown in the timeline.

Payments and refunds

Configured Shopify transactions can be registered against an accepted invoice. Each provider transaction has an idempotency key, so a repeated webhook or worker retry cannot register the same payment twice.

Partial and multiple payments remain visible as separate operations. An unknown gateway or ambiguous match requires manual review.

Refunds are evaluated for credit-note review. Automatic full, partial and shipping credit notes remain disabled until each scenario has separate live accounting certification. The private beta must not promise automatic credit notes.

PDF access

When the configured KROS report is ready, a background job downloads the PDF into private tenant-scoped storage. Only an authenticated user from the owning Shopify shop can open it through the application.

The app does not expose document storage through a public URL. A missing or malformed PDF remains in a recoverable state and can be retried without creating another invoice.

Reconciliation and recovery

Use reconciliation when a callback is overdue, a provider outcome is unknown or KROS contains a document not yet attached to the local record. A unique verified match can be attached; an ambiguous match stays in needs-attention state.

Never solve an uncertain result by submitting the invoice again. Capture the safe document ID, request ID, timestamp and error code, then use the operations or support screen.

Current private-beta limits

  • No public install link until Shopify review and listing approval.
  • No official, partner or certified KROS claim.
  • No POS, receipt, proforma, advance/final-invoice or historical-import claim.
  • No automatic credit-note claim while certification flags remain disabled.
  • No provider email-delivery claim; PDF access is authenticated inside the app.
  • Currency, tax and accounting combinations are supported only after explicit pilot validation.

Disconnect, uninstall and support

Disconnecting a provider account stops new submissions but preserves the safe references and audit records needed to understand existing documents. Uninstall triggers shop-scoped cleanup and retention workflows; statutory invoice retention remains the merchant’s responsibility in KROS.

For support, send the shop domain, safe document or operation ID, timestamp and visible error code. Never send access tokens, full customer details, invoice attachments or raw Shopify/KROS payloads.