Setting Up Marketplace Seller Payouts on 1C-Bitrix

Payout problems for marketplace sellers are familiar to aggregator owners: manual transfers take hours, calculation errors lead to conflicts, and tax authorities require documentation. Our team of certified 1C-Bitrix specialists with over 5 years of experience configures marketplace seller payouts on 1C-Bitrix — including balance accounting, manual requests, and automatic transfers via API. Over this time, we have implemented systems for 30+ marketplaces: from electronics online stores to service aggregators. Average client savings: up to 2 million RUB per year through automation.

Manual payouts are 5 times slower than automatic ones, but they are essential at the start. Automation via Tinkoff or YooMoney saves up to 70% of manager time. Our engineers ensure correct integration and compliance with 152-FZ requirements. Contact us for a consultation — we'll discuss your project details.

How seller balance accounting works — configuring seller payouts

Balance is compiled from financial transactions recorded at each event:

• • upon confirming sub-order payment: amount = subtotal - commission

  Table mp_finance_log:

  Field	Type	Description
  ID	int, AI
  VENDOR_ID	int	FK to seller
  TYPE	varchar	sale / commission / payout / refund
  AMOUNT	decimal(10,2)	Positive = income
  REFERENCE_ID	int	ID of sub-order or payout request
  STATUS	varchar	pending / confirmed / cancelled
  CREATED_AT	datetime

  Current balance = SUM(AMOUNT) WHERE VENDOR_ID = X AND STATUS = 'confirmed'. Source: 1C-Bitrix documentation — financial accounting

  Why manual payouts are inefficient

  Manual payouts take up to 10 minutes per operation: check request, verify balance, execute transfer via bank client. With 50 payouts per day, that's almost a full workday. Errors in entering details are a common cause of delays and reputational risks. For a large marketplace with 5000+ monthly transactions, automation savings exceed 1 million RUB — confirmed by our experience.

  Comparison of approaches:

  Criterion	Manual payouts	Automatic payouts
  Time per payout	~10 min	1–2 sec
  Manager costs	High	Zero
  Errors	Possible (human factor)	Minimal
  Implementation threshold	Low (1–2 weeks)	Medium (+1–2 weeks for API)

  Automatic payouts are 10 times faster and virtually eliminate errors.

  Manual payouts: step-by-step process

  The seller clicks "Request payout" in the personal account, specifying an amount (not exceeding available balance). A record is created in mp_payout_requests with status pending. The manager sees the request in the admin panel and, after actually transferring funds, confirms it — the status changes to completed, and the balance decreases.

  Minimum payout threshold and frequency (e.g., no more than once a week) are configured in b_option via the admin panel.

  How to set up automatic payouts via API

  Step-by-step automation plan

  1. Select a payment gateway. Suitable options: Tinkoff, YooMoney, CloudPayments, QIWI B2B. Each has its own security and speed requirements.
  2. Encrypt payment details. Store seller payment data in a separate table with AES-256 (152-FZ requirement).
  3. Develop a payout agent. Write a Bitrix agent that runs on a schedule (e.g., every Friday at 10:00). The agent collects requests with status pending, sends a request to the gateway API, and upon success changes status to completed and debits the balance.
  4. Logging and notifications. Record each payout in the financial log, send notifications to the seller and manager.
  5. Generate documents. Upon payout completion, generate a PDF service acceptance certificate (via tcpdf) and attach it to the operation.

  Typical automation mistakes

  • Ignoring payment gateway limits (e.g., maximum transfer amount or daily limit).
  • Lack of API error handling: on failure, the payout may hang in status pending and the balance won't decrease. Implement callback notifications.
  • Complexity with refunds: on order cancellation, correctly restore the seller's balance and cancel the payout if not yet executed.

  Why tax documents matter

  During payouts, the platform must generate service acceptance certificates (for commission) and sales reports. PDF generation via tcpdf or template is standard. Documents are attached to the payout and available for download by the seller and admin. This is an FTS and 54-FZ requirement.

  What's included in the work

  • Designing the financial transaction scheme (infoblocks, HL-blocks)
  • Developing the balance accounting and request module
  • Integrating with a payment gateway (Tinkoff, YooMoney, CloudPayments, QIWI B2B)
  • Generating PDF documents
  • Testing and documentation
  • Training managers and sellers

  Timeline

  • Balance accounting and manual payouts: 1–2 weeks
  • Automatic payouts via API: +1–2 weeks
  • Financial document generation: 3–5 days

  Final timeline depends on integration complexity and catalog volume. We'll assess your project in one day — contact us for a consultation.

  Get a ready-made module with documentation and support. Order payout configuration — and your sellers will receive money on time.