↔
Receipts from 1С/BAS are fiscalised in Checkbox and come back as closed sales
A sale is registered in 1С/BAS, but the fiscal receipt lives in Checkbox. Without a link the cashier enters the same items twice and the accountant reconciles two registers at the end of the day. We connect them so a sale posted in 1С/BAS turns into a Checkbox receipt, and the receipt's fiscal number and status come back to the same 1С/BAS document.
Before the cashier records the sale in 1С/BAS and then repeats the same items in the Checkbox cash register, so a busy hour means queues and mistyped quantities.
After the sale is entered once in 1С/BAS and the receipt is printed from the same data.
Before at closing the accountant compares the 1С/BAS sales list with the Checkbox shift report and hunts for the receipt that is missing on one side.
After every 1С/BAS sale carries its fiscal number, so a sale without a receipt is visible immediately, not at night.
Before a return is written in 1С/BAS, but the return receipt is made in Checkbox separately and sometimes forgotten, which surfaces only in a tax check.
After the return in 1С/BAS creates the return receipt on the same register and stores its number.
Before site payments are fiscalised by Checkbox through a payment service, but the accountant learns about them from a bank statement days later.
After each fiscalised online payment appears in 1С/BAS as a sale with the receipt attached on the same day.
For those who want to check: each point links to the official documentation page it comes from.
The official BAS support portal documents its integration technologies under the title «Технології інтеграції 1С:Підприємства 8.3» — BAS is built on the 1C:Enterprise 8.3 platform.
Source: its.bas-soft.eu ↗ checked 2026-09-25According to the same documentation, the platform automatically builds a REST interface using the OData protocol, through which outside systems can read, change, create and delete data over HTTP.
Source: its.bas-soft.eu ↗ checked 2026-09-25The Checkbox PRRO API runs on a single host, api.checkbox.ua, for both test and live mode — an open RESTful API.
Source: wiki.checkbox.ua ↗ checked 2026-09-25Webhooks are set up with a POST /api/v1/webhook call, the URL is saved separately per cash register, and the request body is signed with HMAC-SHA256, verified via the x-request-signature header.
Source: wiki.checkbox.ua ↗ checked 2026-09-25If the integration server responds with an error (code ≥400) or doesn't answer within 10 seconds, Checkbox retries the webhook for up to 24 hours with an exponential backoff (from 1 second to 30 minutes).
Source: wiki.checkbox.ua ↗ checked 2026-09-25Fiscalisation of LiqPay, WayForPay, Mono Checkout and NovaPay payments in Checkbox doesn't work directly — it goes through the AssetPayments service, which accepts the payment itself and opens the shift / creates the receipt.
Source: wiki.checkbox.ua ↗ checked 2026-09-25The limits come from both systems. A Checkbox test register allows no more than 100 receipts a month, so the test shift is planned to fit, and one cashier may hold no more than three active sessions at a time, which we take into account when several 1С/BAS workstations share a register. Online payments through LiqPay, WayForPay, Mono Checkout and NovaPay are fiscalised by Checkbox through an intermediate service, not directly, so their receipts reach 1С/BAS with that service's timing. 1С/BAS is on the official prohibited software list: we do not take projects for state bodies, critical infrastructure or systems with state data, and with private businesses we discuss the risk openly.
Three steps from a first message to work on your project.
Describe the task in the form — in text or by voice. Budget and timing are optional.
A developer studies the brief, asks about anything unclear and sends an estimate.
Once scope and price are agreed, the work begins.
or write to info@coreviaflow.space
Describe the task in text or a voice message. We look at your setup and reply with a plan.
Four services people come to us for most often. Each page explains what we do, how the work goes and where to start.
Choose the system, set up the pipeline, migrate data, train the team.
Learn more →Accounting, telephony, website, payments and messengers feed the CRM on their own.
Learn more →Orders, requests and answers around the clock, straight into your CRM.
Learn more →Flows between CRM, email, spreadsheets, payments and AI, on your own server.
Learn more →Accounting & ERPUAAlready running your accounting in 1С/BAS? We automate the work around it
See scenarios →Payments & POSUAThe cash register that sends the receipt to the tax office the moment payment goes through
See scenarios →↔
Acts and invoices leave 1С/BAS for signing in Вчасно on their own, and the signed originals come back into the books
See scenarios →↔
Orders from KeyCRM land in 1С/BAS as sales documents, and stock and payments from 1С/BAS come back to the sales team
See scenarios →↔
The fiscal receipt is issued when the parcel is on its way, and the delivery status closes the order without a manager
See scenarios →↔
A won deal in Bitrix24 becomes a sales document in 1С/BAS, and stock, payments and shipments from 1С/BAS come back to the deal
See scenarios →Implementation · Development · Integrations →
1С/BAS ↔ Checkbox — the system names are trademarks of their owners. CoreviaFlow is not affiliated with them unless stated otherwise.
