Skip to content

Vchasno.Kasa Receipts Import

The same job as the Checkbox import, for the other fiscal service: the service pulls receipts from Vchasno.Kasa and turns them into documents.

Where to find it: Modules → Vchasno.Kasa → Maintenances → Vchasno.Kasa Receipts Import

A worked example

Vchasno.Kasa receipts import

The window is equally short: a period, "Execute" and "Scheduled". The scheduled run, like its neighbour's, looks at the last two days.

The run report is the part worth reading

The service does not answer "done" but with a summary:

  • Imported — how many receipts became documents;
  • Skipped — how many were already in the system, plus receipts without lines and receipts with a global discount: those are not imported and are named by receipt number in the warnings (global discounts are not supported);
  • Errors and Warnings — listed out (the first ten, the rest folded into a counter).

That is why it should not be run blind: if reference data is missing you see it immediately, rather than a week later in a revenue report.

When the invoice comes out as a draft

The normal outcome is a posted invoice. But when a receipt line cannot be matched to an item card, the invoice is still created — unposted. The reasoning is simple: better a document someone opens and fixes than a silently lost sale.

The invoice also stays unposted when an approval rule applies to invoices: posting waits for approval, just as for an invoice entered by hand.

Any other refusal while saving (the till customer's currency, a rate, a payment method and so on) leaves that receipt out: the errors list "Receipt … is not imported: …" with the reason, and the next run tries it again. Every receipt is saved in its own transaction, so the rest are imported.

Typical situations

"No Vchasno.Kasa receipts were imported". Check the period and that the till is connected in the right mode. Read the warnings too: the till user needs a default client and a location — without them the service skips that till and names the user to complete.

An invoice row has an empty VAT rate. Look at the VAT mapping on the account: for a receipt tax group missing from the mapping (or when the receipt names no group) the row's VAT code stays empty — nothing is substituted and no warning is given. Add a mapping row for that group.

The invoice exists but is not posted. Most often that is the unmatched-line case — open it, fix the row and post. If every item was found, posting is waiting for an approval rule.

The service refuses, naming a register: it is shared from another company, and only that company runs this maintenance. Vchasno.Kasa accounts, invoices, fiscal receipts or registers written by posting are shared into this company from another one — the company owning the till imports its receipts. The refusal comes before the first request to Vchasno.Kasa.

Where to look next