Ledgr/Documentation/Banking

Banking & reconciliation

Import the statement, accept the matches Ledgr suggests, and turn the ones that repeat every month into rules.

Plan.

Banking & reconciliation is included from Starter upwards.

Add a bank account

  1. Banking → Add account
  2. Choose the bank

    FNB, Standard Bank, ABSA, Nedbank, Capitec, Investec, TymeBank, Discovery Bank or African Bank.

  3. Name it the way you think of it

    "FNB Business Cheque" beats "Account 1" when you are matching six months later.

  4. Set the type and currency

    Current, savings or credit card. Credit cards are handled as liability accounts, so a purchase increases what you owe rather than reducing cash.

Import a statement

  1. Download the statement from your bank

    CSV or OFX. Every one of the nine supported banks offers at least one of these from its business banking portal.

  2. Banking → Import, then pick the account and the file
  3. Map the columns

    Tell Ledgr which column is the date, which is the description and which is the amount — and whether debits are negative or in their own column. The mapping is remembered per account, so this is a first-time-only step.

  4. Review the preview and import

    Duplicate lines already in the system are detected and skipped, so re-importing an overlapping date range is safe.

Reconcile

Imported lines land in the unreconciled list, each with a suggested match and a confidence score. Three things you can do with a line:

  • Accept the suggestion — the transaction is matched to that invoice, bill or expense and the document settles
  • Choose a different match — search for the right document and match it manually
  • Categorise it directly — for spend with no document behind it, like bank charges

Tick several rows and accept them in one action when the suggestions are obviously right. The reconciliation ring on the account shows how much is still outstanding.

Reconcile weekly, not at year end.

A week of transactions is recognisable. Nine months of them is archaeology, and the suggestions get worse the further you are from the event.

Bank rules

A rule is a description pattern plus what to do when it matches. The debit order that arrives every month with the same reference should be a rule after the second time you code it by hand.

  1. Banking → Rules → New rule
  2. Set the pattern

    Match on text in the description, optionally narrowed to an amount range or a single account.

  3. Set the action

    The category to post to, and whether to apply it automatically or only suggest it.

  4. Let it work backwards

    Apply the new rule to existing unreconciled lines to clear the backlog it would have caught.

Ledgr also proposes rules of its own, based on corrections you have made more than once — they appear in the suggestions panel for you to accept or dismiss.

The cash position

The banner at the top of the module holds every account with a sparkline of its recent movement and a consolidated total across all of them. Underneath, the monthly inflow and outflow chart shows whether the trend is the right way up. This is the same figure the dashboard's Total Cash KPI reports.

Common problems

What you seeWhat to do
Import rejects the fileConfirm it is the CSV or OFX export, not a PDF statement. Re-download from the bank rather than saving from a viewer.
Amounts import with the wrong signRe-check the column mapping — some banks use one signed column and others use separate debit and credit columns.
No suggestion on an obvious paymentThe amount probably differs from the invoice total because of a gateway fee. Match it manually and record the fee as a bank charge.
Duplicate transactionsOnly if the description and amount differ slightly between exports. Delete the duplicates and re-import the cleaner file.