Integrity by design

Your books, kept honest
and kept safe.

Accounting software holds the truth about a business. Libro puts these controls around it.

One system, three parts.

Libro is the dashboard your team signs in to, the API behind it and the database that holds the books. It can run on a machine in the office or on a cloud server.

  • Scheduled backups. The database is snapshotted and verified on a schedule.
  • Your rules. Password, session and sign-in policies set per role.
Your team’s browsers
Libro · dashboard, API, databaseOffice or cloud server
Scheduled, verified backups

Controls that come in the box.

Every one of these is in the system, on from the first day or one setting away.

A record of every change

Every create, edit and delete is kept as a before-and-after, with who did it and when. The history can't be edited.

Two-factor sign-in

Protect accounts with an authenticator app, and require it for the roles that can post and close.

Password rules you set

Minimum length, character rules, reuse and expiry, set per role. Passwords found in known breach lists are refused.

Sessions that end

Idle sessions time out, and when an admin resets a password, that account is signed out everywhere.

Access by role and by branch

Roles decide what each person can do. Visibility can be limited to their own branch, or only the records they created.

Nothing deleted out from under you

An account that entries point at can't be deleted. Libro says what is still using it instead.

Automatic backups

The database is snapshotted on a schedule, and the snapshots are verified regularly.

Sign-in from where you work

Optionally limit an account to the countries your team works from.

The change trail

Who did what, and when.

Every record carries its own history: created, changed, approved, posted — each with a name and a time, and the before and after of every edit. Nobody can edit the history itself.

A posted voucher's history: the bookkeeper created it and added three journal lines, the finance manager approved it, and the accountant posted it, each with a date and time.

Found a problem?

If you believe you’ve found a security issue, email support@tekhx.com with the details. Please give us a chance to fix it before telling anyone else.

See it on the demo business