1С/BAS ↔ Microsoft Excel integration

Reports, price lists and stock from 1С/BAS land in Excel workbooks by themselves, and rows filled in by managers in Excel come back to 1С/BAS as documents

Half the company lives in 1С/BAS, the other half in Excel: the accountant exports a sales report on Monday, the sales lead re-sorts it into their own workbook, and managers keep order forms and stock counts in spreadsheets that later have to be typed into 1С/BAS by hand. Every export is a manual step, every copy of the file is a version nobody can trust. The 1С/BAS ↔ Excel pair connects the accounting to the workbooks people already use in OneDrive or SharePoint: the report tables are refreshed on a schedule, and rows that managers add in Excel become documents in 1С/BAS. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

Request an integration System page: 1С/BAS →System page: Microsoft Excel →

What moves between the systems

1С/BAS → Microsoft ExcelSales, receivables or stock reports from 1С/BAS are written into a named table in a workbook on OneDrive or SharePoint on a schedule, so the report the director opens is always today's.
1С/BAS → Microsoft ExcelThe current price list by the chosen price type is kept on a separate sheet: managers send clients the same numbers the accounting has.
1С/BAS → Microsoft ExcelStock balances by warehouse go to a sheet the warehouse and sales teams share, so nobody promises an item that ran out yesterday.
Microsoft Excel → 1С/BASRows a manager fills in an order form sheet (client, items, quantities) become customer orders in 1С/BAS, with the counterparty found by code or created anew.
Microsoft Excel → 1С/BASAn inventory count entered in Excel on a tablet in the warehouse turns into a stock count document in 1С/BAS instead of being re-typed in the evening.
Microsoft Excel → 1С/BASCorrected prices approved in a price sheet go back to 1С/BAS as a price-setting document, so the workbook and the accounting agree on the new numbers.

What we connect

We list the workbooks that matter: which reports the director needs, which sheets managers fill in, and where the files live in OneDrive or SharePoint; local files on a laptop are moved there first.
In each workbook we turn the working ranges into named tables with fixed column headers: the exchange writes and reads tables, not random cells, so a moved column does not break anything.
The Microsoft 365 administrator registers the exchange as an application with access only to the chosen folder, so it cannot see other documents of the company.
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 and the rules: reports refresh on a schedule, filled-in rows are picked up every few minutes, and a row with an unknown item or client is marked in the sheet instead of silently skipped.
We test on copies of the workbooks with a dozen rows, compare the created documents with the accountant, and only then switch to the live files.

Automation scenarios

The Monday report

Before the accountant exports sales to Excel every Monday, the file is mailed around, and by Wednesday three people have three different versions.

After one workbook on SharePoint is refreshed from 1С/BAS every morning, and everyone opens the same table.

Orders from a spreadsheet

Before the field manager writes orders into their own sheet, sends it in the evening, and the operator types thirty rows into 1С/BAS.

After each row on the order sheet becomes a customer order in 1С/BAS within minutes, and the row gets the document number back.

Old price list in the manager's mailbox

Before prices changed in 1С/BAS, but the manager keeps sending the Excel price list from last month.

After the price sheet is rewritten from 1С/BAS on a schedule, and the manager sends a file that matches the accounting.

Counting stock twice

Before the warehouse counts stock into Excel on a tablet, then the same numbers are typed into 1С/BAS the next day.

After the count sheet turns into a stock count document in 1С/BAS, and differences are visible the same evening.

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
Microsoft's own interface lets an application read and change Excel workbooks that are stored in OneDrive or SharePoint — the same files people open in Excel on their desktop.
Source: learn.microsoft.com ↗ checked 2026-09-28
Microsoft describes Excel as a data store inside Microsoft 365: whatever is in a workbook is available to any application connected to Microsoft 365, and such applications can use Excel to keep their data.
Source: learn.microsoft.com ↗ checked 2026-09-28
The connection works with the parts of a workbook people actually use — tables, ranges of cells and charts — and can create, read, update and delete them.
Source: learn.microsoft.com ↗ checked 2026-09-28
When an application makes more than one or two changes to a workbook, Microsoft recommends opening a working session with it; in a persistent session every change is saved into the workbook itself, and this is the most efficient way to work.
Source: learn.microsoft.com ↗ checked 2026-09-28

Limits

The limits come from both systems. The exchange works with workbooks stored in OneDrive or SharePoint, not with files on someone's desktop; a workbook that is being edited at the moment of writing receives the update a little later. Excel does not report changes by itself, so filled-in rows reach 1С/BAS on a schedule of minutes, not instantly. Formulas, merged cells and manual formatting outside the named tables are left alone, but data must be inside those tables. 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.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Our files are on a shared network drive, not in the cloud. Will it work?

Not as is. The connection reads and writes workbooks stored in OneDrive or SharePoint inside Microsoft 365. At the first step we move the working files there; for people it looks the same, the file simply opens from a different folder.

Will the exchange overwrite what people typed into the report?

Only inside the table that comes from 1С/BAS. Columns and sheets people add for their own notes stay untouched; we agree at the start which tables are written by the exchange and which by people.

What happens to a row with a typo in the item name?

The row is not turned into a document. The exchange marks it in the sheet with a note on what did not match, the manager corrects the cell, and on the next pass the row goes through.