Configuring Document Exchange Between 1C and 1C-Bitrix
"Document exchange" refers to delivering invoices, acceptance certificates, and delivery notes generated in 1C to the website — so the customer can download them from their personal account. Standard CommerceML is not designed for this, so the implementation is always custom.
Architecture: How Documents Are Transferred
Two main approaches:
1. 1C generates a PDF → saves the file → Bitrix retrieves it on a schedule. 1C renders the printed form of the document, saves the PDF to a network folder or FTP. Bitrix scans the folder via cron, linking files to orders by number.
2. Bitrix requests the document from 1C via REST API on demand. The buyer clicks "Download Invoice" → Bitrix sends an HTTP request to the 1C publication → 1C returns the PDF file. The document is not stored permanently on the site.
The second approach is preferable: the document is always the current version from 1C, with no synchronization issues.
Linking Documents to Orders
A shared identifier is required to link a document to an order. In 1C this is the "Customer Order" document number; on the site it is the order's ACCOUNT_NUMBER. When configuring the exchange, verify that the numbers match (not the Bitrix ID, but ACCOUNT_NUMBER).
Storing Documents in the Personal Account
If the file-storage approach is chosen — link to the order via a highload block:
| Field | Description |
|---|---|
UF_ORDER_ID |
Order ID in Bitrix |
UF_DOC_TYPE |
Type: invoice / certificate / delivery note |
UF_DOC_NUMBER |
Document number |
UF_DOC_DATE |
Document date |
UF_FILE |
File (File type) |
Access Permissions
The buyer must only see their own documents. In the personal account component, filter by UF_ORDER_ID with a check that the order belongs to the current user.
Setup Timeline
Implementing document export via 1C REST API — 2–4 days. Via file exchange linked by number — 1–2 days.