Finocket keeps two separate records of what happened to your workspace, and they answer two different questions. Activity is the readable history of what was done — by your team, by the assistant, by connected apps, and by the outside services Finocket talks to on your behalf. The Audit log is the tamper-evident record of what was changed or deleted in your books, with the previous state kept in full.
Open ActivityEverything that happened, newest firstReading the Activity timeline
Every entry is one sentence in plain language: who, what, and how it went. Nothing on this screen prints an action code, a table name or a raw id at you.
- Entries are grouped by day — Today, Yesterday, then the date — with times shown in IST.
- Anything that failed or was refused carries a Needs attention badge and a red card edge, and the filter row counts them for you.
- The refresh control at the top re-reads the timeline. It is a snapshot, not a live feed — nothing appears until you refresh or reopen the screen.
Who did it — five kinds of actor
Finocket distinguishes a person from an automation from an assistant, and never writes one down as another. The filters group them:
- People & apps — someone on your team working in the app, or a connected app using an API key.
- Assistant — and this is two different things kept apart. “The assistant, on your behalf” is a tool call you asked for. “The assistant, on its own” is an autonomous action. If you only ever read one distinction on this screen, read that one.
- Outside services — a call Finocket made to somebody else's system: the e-invoice IRP, a marketplace, your email or WhatsApp provider.
- Scheduled work Finocket does with no human in the loop is recorded as Finocket, automatically, and appears under Everything.
Why the outside calls sit on the same timeline
“I filed the return” and “the GSP rejected it” are one story. Split across two screens, that is how people end up believing something worked. So an outbound call appears in the same stream as the action that caused it, with the provider named, how long it took, and which attempt it was.
One status is worth learning: was already done. When an IRP answers “already registered”, the document is filed. Finocket shows that as a success, because sending you to chase a problem you do not have is its own kind of failure.
The Audit log is a different record
Reports → Audit log answers “what did this row look like before someone changed it?”. A database trigger snapshots the previous state of a row whenever it is updated or deleted, and writes it somewhere nothing in the app can reach. Tap a line to expand the full before-state as it stood.
- It covers far more than invoices: payments, expenses, journal vouchers, ledgers, fixed assets, cost-centre splits, saved reports, workflow rules and more all carry the trigger.
- Routine edits appear here too — marking an invoice paid, correcting an amount. That is the trail working, not a problem.
- Use Activity for what was done; use the Audit log for what a record used to say.
What these screens will not do
- They will not let anyone edit or delete an entry. Not a teammate, not an admin, not the owner, not support. Both records are readable by your workspace and writable by nothing — there is no delete button because there is no delete permission to hang one on.
- Activity will not name the person. It tells you an action came from someone on your team, not which one. For the per-person split, open Settings → Usage & activity, which separates your own actions from the workspace's.
- It will not search, filter by date, or export. There is no date range, no text search and no CSV on Activity. It is a screen for reading the recent past, not for building a report out of it.
- It will not go back further than the most recent entries. Activity loads roughly the last hundred actions and the last hundred outside calls, and stops. There is no next page.
- It will not backfill. Nothing that happened before this record existed appears in it, and turning a feature on does not reconstruct its past.
- It will not shout if it cannot load. If the read is denied or the data is not there, Activity shows an empty timeline rather than an error. An unexpectedly empty screen on a busy workspace is worth raising with us, not shrugging at.
- The Audit log will not show you the “after”. It keeps the previous state; the current state is on the record itself. And it identifies the actor by a shortened id, not a name.
- Neither is an alarm. Nothing here notifies you. A failed call sits quietly under Needs attention until somebody looks.