Setting up document exchange between 1C and 1C-Bitrix
A customer paid for an order, but the invoice doesn't appear in their personal account — a familiar situation. Managers manually search for the PDF in 1C, send it via email, spending up to 15 minutes per order. With 100 orders a day, that's 25 hours per month of pure routine. Customers wait, managers get stressed, and the business loses loyalty. Standard CommerceML (Wikipedia) transfers only XML structures, not binary files, so exporting invoices or certificates to the personal account without custom development is impossible. We, certified 1C-Bitrix specialists with five years of experience, configure an integration that fully automates the process. Over 50+ projects, we've ironed out typical mistakes: for example, linking by order ID instead of ACCOUNT_NUMBER, which caused document loss. We guarantee that every customer will see their documents immediately after payment.
Automation yields direct savings: clients reduce order processing costs by 40% and document sending time by 80%. This is not just convenience but financial gain — reduced manager workload and faster turnover. Contact us — we will analyze your process free of charge and propose an optimal exchange scheme.
Document Transfer Options from 1C to Bitrix
Two main approaches:
1. 1C generates PDF → saves file → Bitrix fetches on schedule. 1C creates a print form, saves the PDF to a network folder or FTP. Bitrix scans the folder via cron, links files to orders by ACCOUNT_NUMBER. This option is cheap but does not guarantee relevance: the document on the site may become outdated.
2. Bitrix requests a document from 1C via REST API on demand. The customer clicks "Download invoice" → Bitrix makes an HTTP request to the 1C web service → 1C returns the PDF. The document is not stored on the site permanently. This is more reliable: the user always gets the latest version from 1C.
| Criteria | File exchange | REST API |
|---|---|---|
| Relevance | No (copy at export time) | Yes (always from 1C) |
| Implementation Complexity | Low | Medium |
| Schedule dependency | Yes (cron) | No (event-driven) |
| Site load | Low (files already ready) | Medium (real-time PDF generation) |
| Setup time | 1–2 days | 2–4 days |
Why Proper Order Linking Matters
To link a document to an order, we need a common identifier. In 1C, this is the "Customer order" document number; on the site, it's the order's ACCOUNT_NUMBER. A typical mistake: using the Bitrix order ID, which does not match the number in 1C. During exchange setup, we always verify that numbers are identical. Otherwise, the document won't attach, and the customer won't see it.
How Documents Are Stored in the Personal Account
If we choose the file storage approach on the site, linking to the order is done via a highload-block:
| Field | Description |
|---|---|
UF_ORDER_ID |
Order ID in Bitrix |
UF_DOC_TYPE |
Type: invoice / certificate / waybill |
UF_DOC_NUMBER |
Document number |
UF_DOC_DATE |
Document date |
UF_FILE |
File (type File) |
How to Set Up Document Access Rights
The customer should see only their own documents. In the personal account component, we filter by UF_ORDER_ID with a check that the order belongs to the current user. We use CSaleOrder::GetByID and standard authorization methods.
Step-by-Step Exchange Setup (REST API)
- Create a web service in 1C to issue PDF by ACCOUNT_NUMBER.
- On the Bitrix site, register a REST route and a component for the "Download invoice" button.
- Develop a highload-block for caching links (optional).
- Set up access rights — verify the order owner.
- Test on a real order: create an order in 1C, check display in the personal account.
- Train managers and hand over documentation.
Example REST request implementation
```php // Bitrix: sending a request to 1C $httpClient = new \Bitrix\Main\Web\HttpClient(); $response = $httpClient->get('https://1c.local/order/doc?number='.$accountNumber); if ($response->getStatus() == 200) { $fileContent = $response->getResult(); // save or output the file } ```What's Included in the Setup?
- Development of the personal account component for displaying documents.
- Creation of a highload-block for storing file links.
- Configuration of a REST route or agent for file exchange.
- Integration with 1C: modification of print forms if needed.
- Testing on real orders and training for managers.
- Provision of documentation and warranty support.
How Long Does Setup Take?
Implementing document export via 1C REST API — 2–4 days. Via file exchange with number linking — 1–2 days. Timelines may increase if 1C print forms need modification or non-standard linking. Setup cost is discussed individually, but on average the project pays off in 1–2 months.
Our experience: over 50 projects integrating 1C and Bitrix, 5 years on the market, warranty on all work. We reduce document sending time by 80% — it's easy to calculate the savings. Contact us — get a consultation and demo access to a ready-made solution. Order document exchange setup and automate the routine.