Dijit.app Dijit.app Documentation

Documentation/ Working with documents/ The document list

The document list

Every document type has a list of its own. The columns change with the type and with how the account is set up, but how the table behaves, loading records, selecting, sorting and keeping the view, is the same everywhere.

The usual columns

ColumnWhat is in it
StatusHow the checks went. This is what tells you which documents need you.
IDThe document's reference. It is what support asks for to find it.
Supplier or ClientThe issuer or the recipient, depending on the document type.
Tax numberThe other party's tax reference.
Document numberThe issuer's own numbering.
AmountsNet, tax and total.
ProjectThe project the document is charged to, if one was set.
SourceHow it came in: manual upload, email, API, copy or moved.
Item statusHow the checks went on the lines.
Consolidation statusOn invoices, where they stand against their delivery notes.
Due dateThe due date worked out for it, and whether it is paid.

The item lists add line columns: code, product, quantity, unit price, discounts, ERP reference, family and raw material.

The three dates

Worth not muddling, because the filters work on one or the other:

DateWhat it is
Document dateThe one printed on the document. This is the one that matters for the accounts.
Upload dateWhen it arrived in Dijit.app.
Processed dateWhen the reading finished.

A March invoice uploaded in June has a document date in March and an upload date in June. Looking for it in the wrong period is the usual reason something "is not there".

Dates are shown in the time zone set on the device. Changing it is covered in Preferences.

How records load

The list does not pull your whole history at once: it brings in a block of records and offers to load more documents to carry on. The header says how many are showing out of the total.

That has a practical consequence for batch actions: you can only select what is loaded. To work on a large set, narrowing it with filters beats loading block after block.

The button that brings in the next block stays in view after the first load, with no need to scroll to the bottom of the table.

Rows of pages being merged

A multi-page PDF uploaded with auto-merge takes up a single row while it is being merged, on a light blue background and with the progress: Merging pages · 3 of 5. That row cannot be opened or ticked, and it does not count towards the totals in the header.

The list refreshes itself every few seconds until it finishes, without moving you or losing what you have ticked. The whole of it, including what happens when pages do not arrive, is in Multi-page PDFs and auto-merge.

Selecting documents

The first column lets you tick documents one by one, or use the header tick box, which covers the records currently loaded. With documents ticked the batch actions come alive: approve, delete, download, merge, assign a project and send.

How the view is kept

The list keeps the page, the scroll position and the filters after any action: approving, merging, sending, assigning a project or deleting. You come back to the very row you were on, not to the top of the list.

Deleting a document from its own row does not even reload the list: the row goes and everything else stays put. That is what makes it possible to work steadily down a long list without losing your place at every step.

The action bar at the top stays put as you scroll down, so the batch actions remain within reach without going back up.

Refreshing and clearing filters

If a document that should be there is not, check in this order: no filter is active, the period you are looking at is the right one, it is not in another list because it was uploaded as the wrong type, and the Source column, to confirm whether it ever arrived.

↑ Back to top

Last reviewed: 29 September 2026 · The Dijit.app team