Connecting 1C:Accounting to ILFF
See also: Delivery widget for the cart · ILFF API · All modules and integrations
Download the ILFF extension for 1C:Accounting
Build r4 of 22 November 2026.
What the extension does and who it is for
The ILFF extension for 1C:Enterprise Accounting (BP) prepares accounting documents from ILFF data and sends expected supplies from BP to ILFF:
- ILFF service acts are loaded into BP as service receipts;
- accepted ILFF supplies become goods receipts for the quantity the warehouse actually accepted;
- a BP goods receipt is sent to ILFF as an expected supply, so the warehouse knows what is on its way;
- a completed ILFF shipment becomes transfers of goods to a marketplace on commission.
All BP documents are created unposted: the accountant checks and posts them. Loading the same item again returns the document already created; no second copy appears.
The extension is for companies that store goods at the ILFF fulfilment warehouse and keep their books in 1C:Accounting.
Requirements
| Item | Requirement |
|---|---|
| Application | 1C:Enterprise Accounting, edition 3.0. Tested on version 3.0.210.11 |
| Platform | 1C:Enterprise 8.3. Tested on version 8.3.27.2214 |
| Network | The 1C server connects to ILFF over HTTPS: ff.ilcompany.ru, port 8443 |
| Installation | A 1C specialist with BP administrator rights |
If you use a different BP or platform version, install the extension on a copy of the database first and test it there.
What to prepare
- API key — take it from your ILFF client account, section Интеграция (Integration).
- Sample service receipt — an existing receipt with one ILFF service line. The organisation, contract, service item and accounts are taken from it.
- Sample transfer for sale — a saved sale with the operation type "Transfer for sale", if you will create transfers to a marketplace.
Limitations
- BP documents are not posted automatically.
- Marketplace sales reports are not loaded by this extension.
- In a receipt for an accepted supply, the price is the item's purchase price in BP.
- In a transfer to a marketplace, the price follows the price type of the sample transfer — the item's sales price in BP; prices from ILFF orders are not used. The transfer is posted at cost, and actual sales are recorded with the commission agent's report.
- If there is no price, the document is created with price 0 and a warning.
- If the product unit in BP is not pieces or its factor is not 1, the quantity is transferred without conversion, with a warning: check it before posting.
- The API does not report whether a supply has already been posted in ILFF.
Step 1. Installation (for the 1C specialist)
Download the extension archive from this page. It contains the extension file ILFF_БП.cfe, guides for the accountant and the administrator, installation and rollback steps (INSTALL.md) and manifest.json with checksums. Check the SHA-256 of the .cfe file against manifest.json; if it does not match, do not install the file.
- Back up the database. If ILFF_BP is already installed, save that extension separately: it is your rollback point.
- Load
ILFF_БП.cfethrough the standard BP extension management. When updating, only the ILFF_BP extension is replaced; leave other extensions untouched. Open a new session. - Assign the ILFFБух_Настройка role to the employee who sets up the connection.
- Assign the ILFFБух_Пользователь role to the accountants who work with ILFF documents. Keep their usual BP rights to receipts and transfers. After roles change, the user must sign in again.
- On first connection BP will request permissions for the secure storage and for the API address. Grant them to this extension only.
Step 2. Connection
Open the ILFF section, the Акты услуг ILFF (ILFF service acts) form, the Настройки (Settings) page. Only a user with the setup role sees it.
- Адрес API (API address) — leave it as is: the ILFF address is already filled in.
- Новый ключ API (New API key) — paste the key from the Интеграция (Integration) section of your ILFF client account. Leave Логин публикации (publication login) and Новый пароль публикации (new publication password) empty.
- Поступление-образец (Sample receipt) — select an existing receipt with one ILFF service line.
- Click Записать настройки (Save settings). The Ключ API line will show "Ключ задан" (key set); the key itself is not shown in the form again.
If the key was reissued for the same client, tick Это тот же клиент — сохранить сопоставления (same client — keep mappings) before saving: existing document and product links are kept. Do not tick it for a different client or a different API address.
Step 3. Service acts
- Open Акты услуг ILFF, set the period and, if needed, the act number.
- Click Получить акты (Get acts) and select the act you need.
- Click Загрузить выбранный акт (Load selected act), then Открыть поступление (Open receipt).
- Check the organisation, contract, services, amount, VAT and accounts. Post the document.
The contractor in the act must match the sample's counterparty by INN and KPP, and the VAT rate must match the sample's rate.
Step 4. Accepted supply → goods receipt
- Open Поставки ILFF (ILFF supplies), the Приёмка из ILFF (Acceptance from ILFF) page. Set a period or a supply number and click Получить поставки (Get supplies).
- Select an accepted supply and click Показать товары (Show goods). Declared and accepted quantities are shown separately; the accepted quantity goes to BP.
- Map ILFF products to BP items in the Номенклатура БП column and the supplier to a BP counterparty in the Контрагент БП column. If ILFF has no supplier for the supply, select the counterparty manually. Click Сохранить сопоставления (Save mappings).
- Enter Дата поступления БП (BP receipt date); it is not filled in automatically. Click Создать поступление (Create receipt), check quantity, price, VAT and accounts, then post.
Products with an accepted quantity of 0 are not added to the document. To switch to another supply, save your changes or click Сбросить выбор поставки (Reset supply selection).
Step 5. BP receipt → expected ILFF supply
- In Поставки ILFF, open the Отправка в ILFF (Send to ILFF) page and select a saved BP receipt.
- Choose Вид поставки ILFF (supply type: for the marketplace warehouse, for customer orders, or mixed) and, optionally, the expected date.
- Click Подготовить отправку (Prepare sending) and check the goods and quantities in the preview. Prices and VAT are not sent to ILFF.
- Click Отправить поставку (Send supply). A supply with the status "New" appears in ILFF: the expected quantity equals the quantity sent, the accepted quantity is 0. The warehouse records the acceptance itself.
Sending the same receipt again returns the same supply.
If an error occurred while sending and it is unclear whether the supply arrived, do not send the receipt again and do not change it. Contact your 1C administrator: they will check the supply in ILFF following the administrator guide in the archive and confirm its number with the Подтвердить номер после сверки (Confirm number after reconciliation) command. Until then, sending again is blocked to prevent duplicates.
Step 6. ILFF shipment → transfer to a marketplace
- In Поставки ILFF, open the Передача маркетплейсу (Transfer to marketplace) page and enter the number of a completed ILFF shipment.
- Select the transfer date, Образец передачи на реализацию (sample transfer for sale), Комиссионер (the marketplace as commission agent) and Договор с комиссионером (contract with the commission agent).
- Click Подготовить передачу (Prepare transfer). Check the items, quantities and the Поставщик БП (BP supplier) column; if needed, choose a supplier and prepare the transfer again.
- Click Создать передачи (Create transfers) and open the documents to check them.
A separate unposted transfer is created for each supplier. If no supplier is selected, a separate draft is created with a warning.
Rollback
Stop the exchange. If some sending attempts had an unclear result, reconcile them first following the administrator guide. Then load the saved copy of the previous extension. Do not delete the extension to roll back: document links and duplicate protection would be lost with it.
Support
If the error persists, call ILFF at +7 (495) 868-16-88 or write to your ILFF manager. Give the document number, the time of the attempt and the error text.
For your 1C specialist: extension file · checksums.