Automated Bank Reconciliation

Pegasus Opera for Pegasus Opera SQL SE & Opera 3

Upload a bank statement PDF or connect via Open Banking. Crakd extracts every transaction, matches them against your Opera cashbook, posts what's missing and reconciles - penny exact, every time. It learns as you go, so common transactions stop needing attention after the first few statements.

Book a Demo ▶ Full Walkthrough
2-minute overview

Full Step-by-Step Walkthrough

A detailed look at every step - from uploading your bank statement through to a fully reconciled cashbook in Opera.

Simple Pricing

Platform required. Add Bank Reconciliation on top.

Required

Platform + Dashboards

Real-time dashboards, user access, Crakd Gateway

£199 /mo
Starter from £199 (5 users) Growth from £299 (10 users) Scale from £399 (20 users)
ADD-ON
Bank Reconciliation

Auto Bank Rec

Statement scanning, auto-matching, posting to Opera

£195 /mo
Unlimited bank accounts Unlimited statements 12-month minimum term
Platform + Bank Rec from
£394 /mo

All prices exclude VAT. See full pricing for bundles and discounts.

Frequently Asked Questions

Any bank that produces a PDF statement. Extraction is AI-based, not template-based, so there is no fixed list of supported layouts. High-street banks, challenger banks and business accounts all work. Statements can arrive by email (picked up automatically) or be uploaded manually. You can also connect via Open Banking and skip PDFs entirely.
Each statement line is matched in a fixed order: recurring entries (standing orders, direct debits) first, then bank transfers, then learned aliases from previous statements, then fuzzy name matching against your Opera customers and suppliers. If a line is genuinely ambiguous it is left unmatched for you to assign rather than guessed at.
Yes. Every confirmed match is saved as an alias, so the same bank description matches instantly next time. Normalised description patterns are also remembered with their coding, so recurring nominal-type lines come pre-suggested. Common transactions stop needing attention after the first few statements.
Every balance comparison is to the penny - no tolerance thresholds anywhere. Each transaction gets a unique fingerprint checked against the cashbook before posting, so re-importing a completed statement is a proven no-op. The reconciliation cannot complete unless the difference between the statement and Opera is exactly zero.
Yes, and the two don't fight. If you complete a reconciliation in Opera Cashbook, the app detects it on the next scan and drops the statement from its list automatically. The app never requires you to abandon Opera's native tools.
No. Scanning, extraction and matching are entirely read-only. Opera is only written to when you explicitly click Import or complete a reconciliation, and every write follows Opera's own posting rules, sequences and counters.
On different banks, yes, freely. On the same bank, the first user holds control and anyone else sees a live read-only view. When they finish, control transfers automatically. If a session goes stale, a Take Over button appears.
The app detects the divergence automatically. A single Recover button re-aligns the app to Opera in one step - stale flags cleared, statements whose postings were lost returned to the queue, PDFs restored from the durable store. Opera itself is never modified during recovery.
Opera SQL SE is fully supported, including all posting and reconciliation. Opera 3 companies can be connected and are currently served in preview mode. The Opera version is selected per company in Settings.

See it in action

Book a 15-minute live walkthrough. We'll run through the full process using a sample bank statement.

Book a Demo