Skip to content

Checkbox

A bridge module between the system and the Checkbox fiscal service — the software cash register through which a receipt reaches the tax authority. It keeps no books: the accounting side of a sale lives in the invoice, which also moves the stock, while what is stored here is the receipt itself — what was sold, how it was paid for and with which fiscal details it went to the tax office.

The main thing to grasp up front: a fiscal receipt and an accounting document are two different things, and an import service stands between them. Until it has run, the sales exist in Checkbox and not in the system: no revenue, no goods issued.

The route: from a sale to an accounting document

Checkbox account (login, tills, cashiers)
        ↓
Sale at a Checkbox till (the Checkbox app or device) → the receipt is registered in Checkbox → the tax office
        ↓
Checkbox receipts import (service) → fiscal receipts and invoices: stock, postings, revenue
  1. Checkbox accounts — which account the system signs in with, which tills and cashiers exist there. Without it the receipts go nowhere.
  2. Encrypt Checkbox secrets — a one-off routine for older databases where cashier passwords, PINs and licence keys were stored in the open.
  3. Fiscal receipts — the log of what the till rang up and the tax office registered.
  4. Checkbox receipts import — the service that collects receipts from Checkbox and turns them into accounting documents.

What is worth understanding

A fiscal receipt is not an accounting document. It moves no stock and creates no postings. It is the tax authority's slip: proof that the sale was registered. The accounting trace appears only after the import.

Until the import has run, the reports are empty. This is the commonest misunderstanding: the till traded all day, the receipts are in Checkbox, and there is no revenue in the system. Look at the import service rather than hunting for lost sales.

The receipts log is shared between two services. The same fiscal receipts register is filled by Vchasno.Kasa. The company picks a provider; the system shows the receipts the same way.

Secrets are encrypted by themselves. Cashier passwords and till licence keys are access to fiscalisation on the company's behalf, so the system encrypts them as soon as they are saved in the account. The encryption routine is run only once — in an older database where these fields were stored in plain text.

The ERPJS till does not send receipts to Checkbox. Selling happens at a Checkbox till — their app or device — and ERPJS only collects the receipts already registered there. The ERPJS till (POS) is fiscalised by Vchasno.Kasa; sales of the offline till are fiscalised by neither module.

Where to start in a new database

  1. Checkbox account — the access, tills and cashiers on the service's side.
  2. Ring up a test receipt at the Checkbox till.
  3. Run the import and confirm the receipt appeared in fiscal receipts and produced an accounting document.

Common tasks

You need Where to go
connect the fiscal service Checkbox accounts
find a particular receipt Fiscal receipts
find out why there is no revenue in the system Checkbox receipts import
hide the cashiers' passwords Encrypt Checkbox secrets

Everything in the module

References: Checkbox accounts

Logs: fiscal receipts

Maintenance: Checkbox receipts import · encrypt Checkbox secrets

Where to look next

  • Vchasno.Kasa — the second fiscal service, sharing the same receipts log.
  • POS · Offline — the tills of ERPJS itself: the first one's receipts are fiscalised by Vchasno.Kasa, not Checkbox; the second one's sales are not fiscalised at all.
  • Sales ledger — the invoices receipts turn into.