Daily activity report
Daily activity answers “what happened financially today?” — while today is still happening. It is the operational view: a day's profit, income, and expenses, how they compare to yesterday, how they accumulated hour by hour, and the individual transactions behind them.
The other three reports are the ones you send to someone. This is the one you actually look at — the reason real-time reporting is worth having at all.
What it answers
A monthly profit & loss tells you a month later that something went wrong. A daily view tells you the morning it starts. Refunds spiking, commission flat while volume climbs, an expense account moving that should not be — these are same-day questions, and they need same-day numbers.
Because the figures are refreshed as transactions arrive rather than assembled by a nightly job, there is nothing to wait for. A transaction posted through the API a minute ago is in this report now. You will find it in the app as Daily Activity, on any ledger.
The three tiles
The day opens with Profit, Income, and Expenses, each carrying a comparison against the previous day so you see movement rather than just a number. A figure on its own rarely tells you anything; the same figure next to yesterday's usually does.
Cumulative profit, hour by hour
Below the tiles, profit accumulates across the day as a running total. A daily total tells you where you ended up; the curve tells you when things happened. A step at 9am and a slow climb through the afternoon are different days with the same total, and the difference is usually the thing you wanted to know.
Breakdown and transactions
The income and expense sides break down into the same trees the other reports use, mirroring your chart of accounts, with bar and pie views when proportion matters more than amount.
Underneath sits the part that makes the report useful rather than merely informative: the transactions posted that day, listed and filterable by account, account template, or category. So the path from “expenses are up” to “these eleven transactions did it” is two clicks, not a database query.
Every transaction carries the description and metadata your code sent when it posted, which is what makes a row traceable back to the event in your product that caused it. That is worth designing for — see Transactions.
Which day is today
Days are your days. The backend stores every instant in UTC, and the calendar boundary is applied when the report is read, in your timezone. A team in New York and a team in Tokyo each see the same ledger rolled up by their own calendar day — neither is looking at a converted copy of the other's numbers.
Navigate with previous, next, and today. The selected day lives in the URL, so a particular day is shareable.
Limitations
- Figures come from a continuously refreshed rollup of your entries, not a re-sum of the whole ledger on every request. A posting appears within about a minute rather than instantly.
- App only. There is no daily report endpoint in the public API. Transaction listing supports
sinceandtillbounds if you need a day's raw activity programmatically. - One day at a time. For a range, use the profit & loss, which shares the same underlying computation.
- No alerting. Ledfra does not watch these numbers for you or notify you when one moves — there are no webhooks or event subscriptions today.
- Income and expenses only. This is a performance view; for position as of a day, use the balance sheet.
Where to go next
- Profit & loss — the same view across a chosen period.
- Balance sheet — what you own and owe as of a given day.
- Trial balance — the account-by-account proof behind all of it.
- Quickstart — get a ledger posting real activity so these reports have something to show.
- What is Ledfra? — the ledger these figures come from.