Skip to main content

Bulk operations and export

When you need to process or export several financial operations at once, row selection and list export help. This article describes what is actually available today in the Finances section, and what is done one operation at a time.

Access

Working with the "Finances" section (including selection, posting and export) is available to the administrator and the head. A client sees their own operations in view mode. The section is not displayed for managers and warehouse workers.

What the list interface offers​

In the Finances section, above the operations table, there is:

  • Row selection — checkboxes on the left and the "Select all" / "Clear selection" button (rows of the current page are selected).
  • A summary of the selection — a counter of the selected rows, toggles by direction (In/Out), document type (Bills/Payments) and currency, plus the Amount and the Remaining for the selected operations. This helps to check the total quickly before taking action. Remaining is the unpaid part of the selected bills.
Different currencies are not added up in the summary

The total is shown in a single currency — the one selected with the currency toggle (for example, RUB or EUR). Operations in other currencies are not included in that sum: switch the currency to see the total for it. The direction, document type and currency toggles appear only when the selection contains more than one value of the corresponding attribute.

  • Export buttons (Excel/CSV) in the table footer.
  • Per-row actions in each row: open, edit, delete, Post / Cancel posting.
There is no separate "Post/Unpost in bulk" button in the selection panel

Selection in the list serves primarily to total up and check the selected operations. Posting and unposting are performed one operation at a time — with the button in the row or from the operation card. To post several operations, filter the list and go through the rows you need.

Exporting the list to Excel/CSV​

The export buttons are located in the table footer and build the file on the browser side from the list rows that are already loaded.

Important specifics:

The current page is exported, not the whole filtered list

The file is assembled from the rows already loaded into the table — that is, from the open page. If 500 operations match the filter while 50 are shown on the page, exactly those 50 go into the file, with no warning.

What to do: look at the caption under the table — "Showing N of M records". If N is smaller than M, increase the page size to a value covering the whole slice, and only then export. Alternatively, narrow the filters so that the result fits on one page.

  • The rows of the page are exported, not only the selected ones. To get the slice you need, apply the filters first (the "Filters" panel), then check that the whole slice fits on the page.
  • The set of export columns is fixed and does not depend on which columns you have hidden or shown on screen. The file contains 18 columns: number, operation type, payment date, creation date, document type, currency, account/cash, amount, document balance, item, counterparty, posted, paid, operation basis, shipment, request, author, comment.
  • For the client role three columns — item, counterparty, author — are not included in the export: the same ones that are hidden from them in the table. The server does not send these fields to a client at all — not to the table, not to the operation card, not to the file.
  • The formats available are Excel (.xlsx) and CSV.

Useful scenarios:

  • Export for the accounting department (including for a subsequent import into 1C).
  • Preparing a payment register for the bank.
  • Reconciliation with a counterparty's acceptance certificates.
If you want to export a specific slice

Filter the list first (by account, period, counterparty, status), then export — the filters will be applied to the file.

Posting and unposting several operations​

Today, in the finance interface, posting and unposting are performed row by row (see What "posting" means).

If you use the API or automation scripts, the system also has server-side bulk operations with the following rules and limits:

  • Bulk posting and bulk unposting — up to 100 operations per call.
  • Bulk export — up to 1000 operations per call.
  • Partial success, not "all or nothing". Each operation is processed separately: some may be posted successfully while others fail. The response returns how many were processed and how many failed, with a reason for each.
  • Execution is synchronous (at request time), without a background task and without a separate progress notification.
  • A rate limit applies to bulk calls — around 200 requests per hour per user; if it is exceeded, the call will be temporarily rejected.
  • Available to roles with finance permissions (administrator, head).
Why "partial success" is a good thing

If a batch worked on an "all or nothing" basis, one incorrect operation would block the posting of all the others. Partial success lets you post the correct documents and deal with the problematic ones separately.

What bulk mode does not offer​

  • Bulk editing of fields is not supported. To change, say, the item or the counterparty on a group of operations, open each one and edit them one at a time (and remember: a posted operation must be unposted first — see Financial operations).
  • Bulk deletion is not supported — deletion is performed one operation at a time through its card, with the same restrictions (a posted or linked operation cannot be deleted).

Typical scenarios​

Closing the month​

  1. In the filter, select the period and the "Not posted" status.
  2. Review the list and check the Amount of the selection — whether all the drafts really need to be posted.
  3. Post the required operations row by row.
  4. Open analytics and verify the figures.

Reconciliation with the bank​

  1. In the Finances section, filter operations by a specific account and period.
  2. Export the list to Excel.
  3. Compare it with the bank statement — find the discrepancies.

What's next​