Finding rows in long lists
Some lists grow with your business. Counterparties, accounts and transactions can run to millions of rows. These lists never load every row into your browser. You see one page at a time, and the system does the searching, sorting and counting for you.
Short lists, such as structures or operating entities, still load whole. You search, sort and export them in your browser, exactly as before.
Two kinds of long list
| Kind | Examples | How you move through it |
|---|---|---|
| Worklist | Counterparties, accounts, debit orders, standing orders, direct debits, direct credits, the suspense worklist, a bank account’s statements, matches and expected items, your open tasks and a record’s tasks, the post list, the approval queue, documents awaiting signature, an operating entity’s submissions, commands, batches, the month’s charges, usage that could not be charged | Page by page, with Previous and Next. |
| History | Account transactions, an account’s cash transactions and bank deposits, ledger entries, a record’s events, a card’s holds and authorisations, the journal and account movements reports, the simulator outbox, your closed tasks, correspondence, email and SMS history, notes, alerts and files | Newest first. Select Load older for earlier rows. |
The count is the whole list
The count beside the list title covers every row that matches your filters. It is not the number of rows on the page.
Woodgrove Bank holds 10,100 counterparties. Alex filters the list to active companies. The count shows 123, and the first page shows them sorted by name.
When the page shows fewer rows than the list holds, the count reads “100 of 12,345”.
An operating entity holds 180 direct debit instructions. Its direct debits panel used to stop at 50. The count now shows 180, and Next reaches every one of them. The status, external account and triage filters on that panel apply on the server, so the count always matches what the filter selects.
A record’s accounts
The Accounts panel on an operating entity, an organisational unit or a cost centre is the accounts page, fixed to that record. It has the same filters, columns, totals and paging. You cannot widen it to another record’s accounts.
An operating entity holds 250 accounts, and another entity holds 50. The entity’s Accounts panel counts 250. Every row on its first page belongs to that entity, and the balance totals cover its 250 accounts only.
A unit’s panel includes the accounts its child units service. A cost centre’s panel lists the open accounts on the centre today. Only the operating entity’s panel offers Export.
Subtotals
Some worklists show subtotal rows at the foot: one row per group, with its count and its totals. The groups cover every matching row, not the page. The rows themselves keep their sort order.
An operating entity holds 350 open suspense cases, 120 of them older than 30 days. The suspense worklist counts 350. Its Age band subtotals show 230 in “0–30 days” and 120 in “31+ days”. Each case falls in a band of its own purpose, so two purposes with different bands each count their cases by their own bands.
Searching
- Type in the search box at the top right of the list.
- Type at least three characters. Fewer than three does nothing, and the box tells you so.
- Wait a moment. The list reloads with every matching row, from the whole list.
The search box’s placeholder names what it searches. On counterparties, that is the name and the number. Search ignores capitals.
Sorting
Select a column heading to sort by it. Select it again to reverse the order. Only some columns sort on a long list: the ones the system can sort across every row. On counterparties, those are the counterparty and the registration date.
Paging stops ten thousand rows deep
A worklist pages forward to its ten-thousandth row and no further. Past that point, the list says Narrow the filter or search to see further, and Next is greyed out. The count still shows the full number.
Nobody pages through ten thousand rows to find one. Search or filter instead.
Scrolling a history
A history shows its newest rows first. Scroll down, or select Load older, to add the next older rows to the bottom of the list. The rows you already loaded stay where they are.
If something is posted while you scroll, the list does not shift under you. A bar at the top says how many new postings there are. Select Refresh to start again from the newest row.
Totals
A total at the foot of a long list covers every matching row, not the page you can see. Amounts in different currencies are never added together; each currency shows its own total.
Alex runs the journal entries report for September. The month holds 250 rows, and the first page shows 100 of them. The debit total at the foot reads 9,876,543.21, the whole month’s figure. It stays the same as Alex loads older rows. The journal report states its totals in the operating entity’s accounting currency.
On a history, the total belongs to the moment the first page was read. A posting that arrives later waits for Refresh, so the total and the rows always agree.
Exporting
Export CSV on a long list downloads every row that matches your filters and search. It is not limited to the page you can see, and the ten-thousand-row paging limit does not apply.
Alex exports an account holding 250 transactions. The file holds a header line and 250 rows, newest first, in the order the list shows them. A history file also carries the balance after each entry, one column per balance.
Each list has its own export permission, separate from viewing it. A clerk can view transactions without being able to download them. Without the permission, the Export CSV button is not shown, and the system refuses a direct request.
Every export is recorded in the exporter’s user history, under Settings → Access control → Users. The line reads “Exported 250 rows from accounts.export-transactions”. If the download breaks part-way, the line ends “, incomplete”.
A report’s export keeps the report’s own limits. The journal entries report covers at most 366 days, and so does its file.
Short lists still offer Excel, CSV and JSON exports of the rows on screen.
What your organisation configures
Nothing about paging is configured. The page size and the ten-thousand-row limit are the same for every organisation. Who may export each list is a permission your administrator grants. The filters each list offers, such as counterparty types, come from your organisation’s own settings.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.