Skip to content

Analytics

Chart of accounts analytics

Your spend split by ledger account: which kinds of charge weigh the most, and how they move month after month.

Updated on August 14, 2026

Where the allocations come from

Every processed purchase invoice line carries a ledger account. This page aggregates those allocations over the chosen period. An invoice received but not yet checked does not appear: until someone confirms the allocation, the expense belongs to no account.

Note

The chart of accounts itself — creating accounts, importing, labels — is managed in the Accounting section. Here, we only read it.

The indicators

How dense your account allocation is, in three figures.

  • Total allocated — the sum of lines attached to an account over the period.
  • Accounts used — how many accounts in your chart were actually used. A rich but barely used chart points to accounts worth removing, or to allocation habits that are too coarse.
  • Lines — the number of allocations, useful to judge whether a total rests on many small expenses or a few large invoices.

Spend by account

The ranking of the busiest accounts, with the amount, the number of lines and each one's share of the total. Beyond the main accounts, the rest is grouped under “Other accounts” to keep the ranking readable.

The two charts

Evolution over time, then a snapshot of the period.

  • Monthly allocations

    A month-by-month stack of the top five accounts, the rest grouped. It brings out the seasonality of a charge — a line that swells every quarter end, for instance.

  • Distribution by account

    Each account's share across the whole period, with no time dimension.

The page is worth what your allocation is worth

If most of your spend lands on one catch-all account, the analysis will say so plainly: one account dwarfing the others. That is a useful signal. Refining allocation at entry — or correcting invoices already processed — is enough to make the page usable from the next visit.

Note

Atlas suggests an allocation when it reads an invoice; it stays a suggestion to validate, and it is the validated version that feeds this analysis.