CoreviaFlowCOREVIAFLOWDIGITAL PROJECT COMPANY Leave a request
EN UA RU

1С/BAS ↔ Google Sheets integration

Reports and stock from 1С/BAS are refreshed in Google Sheets on a schedule, and rows added by the team in a shared sheet come back to 1С/BAS as documents

The accounting is in 1С/BAS, but the team works in Google Sheets: the sales board, the shipment plan, the list of requests from the field. Every week somebody exports numbers from 1С/BAS into a sheet, and every evening somebody types rows from a sheet back into 1С/BAS. The 1С/BAS ↔ Google Sheets pair removes both manual steps: report and stock tables are rewritten from 1С/BAS on a schedule, and rows that people add in agreed sheets become orders, requests or counts in 1С/BAS. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

What moves between the systems

  • 1С/BAS → Google SheetsSales, receivables and payment reports from 1С/BAS are written into a chosen sheet on a schedule, so the morning board the team opens shows yesterday's figures without anyone exporting them.
  • 1С/BAS → Google SheetsStock balances by warehouse go to a sheet shared with sales and the warehouse, and a zero balance is highlighted so nobody promises an item that is gone.
  • 1С/BAS → Google SheetsOrder statuses from 1С/BAS («assembled», «shipped», «paid») are written next to each row on the shipment plan, so the planner does not ask the warehouse.
  • Google Sheets → 1С/BASA row added by a manager on the order sheet (client, items, quantities, delivery) becomes a customer order in 1С/BAS, and the row receives the document number back.
  • Google Sheets → 1С/BASRequests collected through a Google Form into a sheet are written to 1С/BAS as customer requests or new counterparties with a note, so they do not stay in the sheet forever.
  • Google Sheets → 1С/BASA stock count entered on a phone into a counting sheet turns into a stock count document in 1С/BAS the same evening.

What we connect

  • We agree on the sheets: which tables are written by 1С/BAS, which are filled in by people, and which columns are mandatory in each; a sheet is split in two if both happen in it.
  • We create a service account for the exchange and you share the chosen spreadsheets or the folder with its address, the same way you share a file with a colleague; nothing else in your Drive is visible to it.
  • On the 1С/BAS side we use the open exchange interface the platform builds itself, under a separate user with rights to read reports and create the agreed documents.
  • We set the rhythm within Google's per-minute quotas: reports are rewritten on a schedule, new rows are picked up every few minutes, and large tables are written in one batch rather than cell by cell.
  • We test on a copy of the spreadsheet with a dozen rows, compare the created documents with the accountant, and only then switch the exchange to the live file.

Automation scenarios

01

The board that is always a week old

Before the sales board in Google Sheets is updated by hand from 1С/BAS on Fridays, so on Thursday the team argues with numbers from last week.

After the board is rewritten from 1С/BAS every morning, and the meeting starts with today's figures.

02

Requests stuck in a form sheet

Before a Google Form drops requests into a sheet, and someone remembers to move them into 1С/BAS twice a week.

After every new row becomes a customer request in 1С/BAS within minutes, and the manager sees it in the morning list.

03

Warehouse asked the same question ten times

Before the planner keeps the shipment plan in a sheet and messages the warehouse about every order to find out if it is assembled.

After statuses from 1С/BAS appear next to each row of the plan, and the chat goes quiet.

04

Field orders typed twice

Before field managers write orders into a shared sheet from the phone, and the operator retypes them into 1С/BAS in the evening.

After each row becomes a customer order in 1С/BAS, and the document number is written back into the row.

How it works technically

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-25
  • According 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-25
  • The Google Sheets API is an official interface that lets a program read and modify a spreadsheet's data.

    Source: developers.google.com ↗ checked 2026-09-27
  • Spreadsheet IDs are stable, even if the spreadsheet name changes — renaming the file does not break the connection.

    Source: developers.google.com ↗ checked 2026-09-27
  • Sheets API quotas are per minute and refill every minute; Google's own example is a read limit of 300 requests per minute per project.

    Source: developers.google.com ↗ checked 2026-09-27
  • A service account is a special kind of account used by an application rather than a person; access to a specific Google Sheet is granted by sharing the file or folder with the service account's email address.

    Source: developers.google.com ↗ checked 2026-09-27

Limits

The limits come from both systems. Google Sheets does not report a new row by itself, so rows reach 1С/BAS on a schedule of minutes, not instantly. Google counts requests per minute, so a very large report is written in batches, and a sheet with hundreds of thousands of rows is better replaced by a filtered one. A row edited by hand after it became a document is not changed in 1С/BAS backwards: corrections are made in 1С/BAS. 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.

How to start

Three steps from a first message to work on your project.

  1. 01

    Leave a request

    Describe the task in the form — in text or by voice. Budget and timing are optional.

  2. 02

    We review and estimate

    A developer studies the brief, asks about anything unclear and sends an estimate.

  3. 03

    We start

    Once scope and price are agreed, the work begins.

or write to info@coreviaflow.space

Questions

Can the whole team keep editing the sheet as before?
Yes. People keep working in the same file; the exchange only writes into the tables agreed for 1С/BAS and reads the rows in the tables agreed for people. Notes, colours and extra columns stay as they are.
What if someone renames or moves the spreadsheet?
Nothing breaks: the exchange refers to the spreadsheet by its permanent identifier, not by name or folder. Deleting the file or removing access for the service account is the only thing that stops it, and that is reported.
We already have an Apps Script that does part of this. Do we throw it away?
Not necessarily. Scheduled Apps Script runs can stay for what they do well inside the sheet; the exchange with 1С/BAS takes over the part that touches the accounting. We look at the script at the first step and decide together.

Tell us what needs to be connected

Describe the task in text or a voice message. We look at your setup and reply with a plan.