Docs/Security
SecurityRead-only accessPublic guide

Security and read-only bank access

LeedBooks is designed to review bank activity and prepare bookkeeping work without giving it permission to move money.

Read-only bank access

LeedBooks uses bank connections to read transaction activity for bookkeeping.

Read-only access means the system can review transactions and balances needed for bookkeeping, but it should not have permission to move money out of your bank account.

Bookkeeping access is not payment access

LeedBooks needs transaction data to do bookkeeping. It does not need permission to send money from your bank.

01
Read

Import transaction activity from connected business accounts.

02
Review

Prepare categories, rules, transfers, reports, and cleanup suggestions.

03
Approve

Ask for approval before sensitive bookkeeping changes are committed.

What LeedBooks can do

LeedBooks can use connected account data to help with bookkeeping.

It can help:

  • Import transactions
  • Suggest categories
  • Identify likely transfers
  • Prepare review queue items
  • Learn rules and aliases
  • Build reports from posted activity
  • Flag cleanup work
  • Surface tax-readiness tasks

What LeedBooks cannot do

LeedBooks is not a bank transfer tool.

It should not:

  • Move money from your bank account
  • Send payments to vendors
  • Withdraw funds
  • Change bank credentials
  • Replace your legal or tax advisor
  • Commit sensitive bookkeeping changes without review

If something looks like payment authorization, stop and contact support.

Approval protection

The approval loop is part of the safety model.

The AI can prepare work and explain the reason, but important bookkeeping actions should still be reviewed.

This matters for:

  • Category changes
  • Broad rules
  • Transfer matching
  • Duplicate cleanup
  • Vendor aliases
  • Payee tax status
  • Month-end close decisions

Safe account habits

Use a few simple habits:

  • Connect only business accounts.
  • Remove accounts that should not be in the books.
  • Use strong passwords for your login.
  • Keep admin access limited.
  • Review broad rules before approving them.
  • Ask the AI to explain unclear suggestions.
  • Contact support if something feels off.

When to contact support

Contact support if:

  • An account was connected by mistake.
  • A bank connection looks stale.
  • A transaction appears in the wrong account.
  • You see activity that does not belong to the business.
  • A suggested rule feels too broad.
  • You are unsure whether a transaction is a transfer.
Next step

Connect bank accounts safely

Learn which accounts to connect and how to avoid pulling the wrong activity into the books.

Read bank connection guide
Previous
Referrals
Next
You are at the end