Events

Every action in a Book — posting a transaction, editing an account, adding a comment, attaching a file — generates an Event. Events record who performed the action (a person, a bot, or a bank connection), what changed, and when. Together they form a complete, tamper-proof audit trail that is essential for collaboration and trust. For a deeper look at the model, see Core Concepts — Events.

Events are not just a log to look at. They are the mechanism that powers automations across Bkper — bots, AI agents, and integrations all listen for Events and react to them in real time.

The Activities panel

The Activities panel is where you view Events in your Book. Click the Activities button in the top-right corner to open it.

The panel shows a chronological feed of every action taken on the Book — transactions created, accounts edited, collaborators added, comments posted, and more. You can review exactly what each team member or automation has been doing.

Reading an Event

Each entry in the Activities panel shows:

• Who acted — The user’s avatar and name, or the agent’s logo and name for bots, apps, and bank connections. This makes it immediately clear whether a human or an automation performed the action.
• What changed — The entity affected (a transaction, account, group, or other object) and the nature of the change (created, updated, deleted, posted, checked, etc.).
• When it happened — A timestamp for every action, so you can reconstruct exactly what occurred and in what order.

Filtering Events

Select any transaction in the list and the Activities panel instantly filters to show only the Events relevant to that specific record — every edit, state change, comment, and attachment across its entire lifecycle.

This is useful for auditing a specific transaction: you can see who created it, who posted it, whether a bot modified it, and who ultimately checked it.

Humans and agents

Bkper treats human users and automated agents the same way — both generate Events, and both are clearly identified in the Activities panel. When a bot calculates taxes on a checked transaction, or a bank connection imports a statement, or an AI agent processes a document, each action appears as an Event with the agent’s distinct logo and name.

This means you always know what acted and why, whether the action was manual or automated. There is no hidden behavior — every automation is transparent and auditable.

Agent responses

When a bot or app reacts to an Event, its response is recorded directly on the Event that triggered it. Click the response at the bottom of an Event entry to see what the automation did — for example, the tax amount it calculated, the currency conversion it applied, or the subledger entry it created.

If an automation encounters an error, the error is also recorded on the Event, so you can review and troubleshoot without guessing what went wrong.

How Events power Bkper

Events are the foundation of Bkper’s automation model. Rather than running on a schedule, automations in Bkper are event-driven — they react the moment something happens:

• Bots listen for specific Event types and respond automatically. When you check a transaction, a Tax Bot can calculate and post the tax entry, an Exchange Bot can convert the amount to another currency, or a Subledger Bot can mirror the transaction in a related Book — all within seconds.

• AI Agents use Events to understand context and take action. The Bkper Agent can parse documents, extract transaction data, and record entries — each action generating its own Events for full traceability.

• Bank connections import transactions from your bank and each import appears as Events, so you can trace every imported record back to its source.

• Reports and analysis — because Events capture every change with precise timestamps, they provide the data needed for compliance, auditing, and operational reporting.

The event-driven model means automations compose naturally: one bot’s action generates a new Event that another bot can react to. A posted transaction can trigger a tax calculation, which triggers a currency conversion, which triggers a subledger entry — each step fully visible in the Activities panel.

For developers building custom automations, see the Events reference and Event Handlers guide.