# Bkper for Accountants

Bkper's core implements the same fundamentals as any double-entry bookkeeping or accounting system, with a key differentiating factor.

## A paradigm shift in transaction representation

Instead of working with traditional journal entries:

Bkper is driven by a **transaction flow** — resources move from one Account to another:

Both representations are fundamentally the same, but the shift in paradigm introduces a higher level of abstraction that changes how teams work with financial data:

- The flow representation is closer to reality.
- It is easier to understand for non-accountants.
- It sets a common language among clients, accountants, and developers.
- It enables much more effective financial modeling.
- It enhances control and audit.
- It presents accounting as a **strategic tool**, rather than a tax and compliance burden.

## An event-driven architecture

Instead of relying on databases and batch processes:

Bkper is built as an **event-driven API**, converting a complex, rigid, compliance-driven environment into a consistent and organized ledger.

### What this architecture enables

- Effective [robot process automation](https://bkper.com/docs/guides/automations/apps-and-bots.md)
- Flexible and simple customizations
- Reusable components and services — Bots, Apps, and Templates
- Streamlined and safe [collaboration](https://bkper.com/docs/guides/using-bkper/book-sharing.md)

## Built on Google Cloud Platform

Bkper applies the highest security standards:

- **User management** outsourced to Google Workspace
- **API access** through OAuth2 and SSL
- **Distributed datastore**, [encrypted at rest](https://cloud.google.com/docs/security/encryption/default-encryption)
- **[Point-in-time disaster recovery](https://cloud.google.com/datastore/docs/pitr)** up to 7 days
- **Security infrastructure** outsourced to Google Cloud Platform