Matching is manual
Thousands of small transactions ticked off against statements by hand.
Use case
Close the monthwithout the chase.
Transactions matched against statements automatically, exceptions routed to the person who can resolve them, and an audit trail that assembles itself — so close is a review, not a rebuild.
- Works with your bank feeds
- Exception-first
- Audit trail by default
Reconciliation
- Transaction
- Match
- Exception
- Review
What gets in the way
Why close always takes longer than planned.
Exceptions have no owner
A break is found, then sits in a spreadsheet until somebody claims it.
The trail is rebuilt later
Evidence of what was matched and why is assembled after the fact, for the auditor.
The same breaks recur
Nothing feeds back, so next month brings the same exceptions again.
How Dockly One helps
From the transaction to a trail that stands on its own.
- TransactionBank, card and ledger
- MatchBy rule and by pattern
- ExceptionRaised with a reason
- ReviewRouted to an owner
- ReconcileAgreed and closed
- Audit trailKept as it happens
Dockly products working together
One platform, four products, no integration project.
Key capabilities
Everything a close needs to run on exceptions.
Rule-based matching
One-to-one, one-to-many and tolerance matching on rules you can read.
Pattern learning
Recurring matches recognised from history, with the reasoning shown.
Exception ownership
Every break has an owner, an age and a next action from the moment it appears.
Statement reconciliation
Bank, card and supplier statements agreed against the ledger in one place.
Close dashboard
What is matched, what is open and what is blocking, live through the period.
Continuous audit trail
Evidence recorded as the work happens, not reassembled for the auditor.
Ready to make closea review, not a rebuild?
See how Dockly One reconciles your transactions.
Request access- Works with your bank feeds
- Exception-first
- Audit trail by default