USE CASE

Bank reconciliation

Import the statement, match it to the books, and create entries for whatever is missing.

The problem

Reconciliation is usually two windows and a highlighter: the bank statement on one side, the ledger on the other, and an afternoon of ticking lines. Customer payments with no reference and bank charges nobody recorded turn it into a Friday-night job.

How it runs in Sundial

1. Import the bank statement into Finance & Accounting as a file from your bank. Each line becomes a bank transaction.

2. Open the bank reconciliation tool for the account and period. Sundial suggests matches between statement lines and payments, receipts and journal entries already in the books, by amount, date and reference.

3. Confirm the matches. One statement line can be matched to several invoices when a customer pays in bulk.

4. For lines with no match, create the entry in place: a payment entry for a customer receipt that was never recorded, or a journal entry for bank charges and interest.

5. When the closing balance on the statement agrees with the books, the account is reconciled for the period.

What the team sees

Accountants see unreconciled lines by account and age. Credit controllers see customer receipts applied to invoices the same day the statement arrives. The owner sees bank balances that agree with the books.

Sample for Kestrel Workspace: 312 statement lines in October, 296 matched automatically by amount and reference, 16 resolved by hand.

With AI (coming to Sundial)

Sundial is built for an agent to propose matches for the hard lines too, such as a payment with a misspelled name or a combined amount, and leave them for an accountant to confirm. This is roadmap; matching today follows the rules above.

THE NEXT AGE OF ERP

Run the whole business
in one calm system.

Try the demoTalk to us