Support · Guides

Learn BareLedger, one task at a time.

Plain-language guides to running your books: from the first invoice to a filed tax return, plus everything a developer needs to connect their own tools.

73guides & references
4stages before anything posts
17built-in roles
11financial reports
The one pattern to learn

Nothing reaches your books without a second pair of eyes

Journal entries, invoices, bills, expenses, and payments all follow the same four stages. Learn it once and every module makes sense.

How every record moves

  1. 1DraftBeing written. Not in the books yet.
  2. 2SubmittedLocked and handed over for checking.
  3. 3ReviewedA first checker has passed it on.
  4. 4PostedApproved and written to the ledger in one action.

A different person handles each check. Rejecting at any stage sends the record back to Draft with a required comment, and the whole history is kept forever.

Team, roles & approvals

Who can do what, how records get checked, and why nobody can approve their own work.

See all 24 guides

Built-in roles, one rule: nobody checks their own work

AdministratorRuns the organization: team, settings, subscription.Manage
AccountantFull access to every module and to accounting configuration.Full
StaffPrepares and submits journals, invoices, bills, expenses.Prepare
ReviewerFirst checker. Reviews or rejects, never creates.Review
ApproverFinal checker. Approving is what posts to the ledger.Approve
ViewerRead-only across transactions, reports, and audit trail.View
Roles can be combined per person, and per-page overrides fine-tune access without creating new roles.

Sales & customers

From a quote to money in the bank, with the paperwork your customers and auditors expect.

See all 3 guides

The selling journey

  1. OptionalQuotationPrice first, accept or decline.
  2. OptionalSales orderInternal confirmation the sale is on.
  3. InvoiceThe official document. Approved, posted, numbered.
  4. PaymentMoney in, applied to one or more invoices.
  5. ReceiptProof of payment for the customer.
Informal step, never on reports Goes through review and approval Issued automatically once payment posts

Purchases & expenses

Every cost going out, recorded once, approved by someone else, and settled from the right account.

See all 2 guides

The buying journey

  1. Record the billWhat a supplier is charging you, line by line.
  2. Review & approveSomeone else checks it, then it posts.
  3. Pay the supplierFrom a bank, cash, card, or owner-paid account.
  4. SettledBalance updates, payables aging clears.

Expenses are the shortcut for small, already-paid purchases: one record covers both the cost and the payment.

Banking, journals & reports

Keep the ledger balanced, prove it against the bank, and see where the business stands.

See all 4 guides

Bank reconciliation in five steps

  1. 1Bank accountLink each real account to its ledger account.
  2. 2Import statementUpload the bank's file for the period.
  3. 3Open a sessionPick the closing date and balance.
  4. 4MatchAccept suggested matches, add fees or interest.
  5. 5Zero differenceComplete the session. Locked and audit-ready.

Matching rules remember how you classified recurring bank lines, so the next statement is mostly done for you.

Tax & compliance

Statutory returns generated from posted figures, reviewed, finalized, and tracked to filing.

See all 2 guides

From posted books to a filed return

  1. 1See what's dueA calendar of filings for your country and fiscal year.
  2. 2GenerateFigures are pulled straight from posted transactions.
  3. 3ReviewOverride a line if needed. Every override is logged.
  4. 4FinalizeFreeze the return and export it.
  5. 5Mark as filedRecord the date and reference from the authority.

Due dates are indicative. The tax authority's own calendar always prevails.

Developers & API

Everything the app can do, you can do from a script. Same endpoints, your own API key.

See all 21 guides

Anatomy of an API request

GET https://bareledger.app/api/v1/reports/trial-balance
Authorization: Bearer <your API key>
X-Tenant: <organization id>
Accept: application/json
  1. 1One base URL, one version. Everything lives under /api/v1/, the same endpoints the web and mobile apps use.
  2. 2Your API key is the bearer token. Create it under My profile → API keys. It acts as you, with your permissions.
  3. 3Say which organization. The tenant header picks the set of books. Copy the id from Organization settings (masked until you confirm an emailed code); only organizations you are registered in are ever visible.
  4. 4JSON in, JSON out. Predictable pagination, ISO-8601 dates, and a consistent error shape.
Read-only or read & write keys Optional expiry Revoke any time Same rate limits as the app

Ready to try it yourself?

Create your free account in minutes. Every feature is included on every plan, and nothing posts without a second pair of eyes.

Get started free