Bring bank activity and your books into one controlled workflow. Cyntrova suggests likely relationships, explains the evidence and keeps uncertain transactions visible for your team to resolve.
Start with supported statement data or imports, preserve the source and define the period being reviewed. Cyntrova keeps the bank activity distinct from the accounting records it may relate to.
BANK STATEMENTSOURCE ATTACHED
Statement activitySelected account · Review period
IMPORTActivity stays separate until reviewed.Available feeds and import formats depend on current product support.
RECONCILIATION SCOPE
One account. One period. One review queue.
Statement activity
Candidate book records
Opening and closing context
02 / MATCH SUGGESTIONS, WITH REASONS
Know why it may belong.
A useful suggestion does more than put two records side by side. It shows the signals that support the relationship—and leaves the decision with an authorised reviewer.
AI suggests. Your team confirms.
c.Bank reconciliationAI suggests. You confirm.
ILLUSTRATIVE WORKFLOW
SUGGESTED MATCH96% MATCH
BANK ACTIVITY₹47,200
Aarav Supplies
05 Sep 2026 · Reference 1042
↔
BOOKSPAY-0084
Aarav Supplies
₹47,200 · Payment record
Amount agreesCounterparty alignsDate proximity
Waiting for your review
03 / EVIDENCE BEFORE CONFIDENCE
A reason you can inspect. Not a score you must trust.
Amount, counterparty, date and reference context can support a proposed relationship. The interface should make those reasons visible so the reviewer can accept, reject or investigate the suggestion.
01Amount
See whether the values agree or whether a tolerance needs attention.
02Counterparty
Compare names, references and the business relationship behind the records.
03Date & reference
Use timing and source references as supporting context—not silent proof.
04Human decision
Confirm only after the relationship makes sense in the books.
04 / EXCEPTIONS STAY VISIBLE
Focus the team on what remains.
Not every bank line has one obvious counterpart. Low-confidence or incomplete relationships stay in a review queue, with the source and the reason for attention still visible.
Confirming a relationship between existing records should not silently create a missing payment or journal. When accounting action is needed, it remains a separate, deliberate step through the established accounting workflow.
01Review the proposed relationshipSource and candidate record stay side by side.
02Confirm or return to exceptionsThe reviewer decides whether the evidence is sufficient.
03Keep accounting authority explicitNo silent posting hidden behind a match suggestion.
06 / CONNECTED TO THE ACCOUNTING CORE
The close should end in explainable books.
Reconciliation is strongest when the source activity, matched records, unresolved differences and final review remain connected to the accounting context they support.
Keep the imported statement context available for review.
02
Suggestion explained
Preserve the signals that supported the proposed relationship.
03
Decision attributable
Record who confirmed, rejected or resolved the item.
04
Exceptions carried forward
Unresolved differences remain visible instead of disappearing into the close.
BANK RECONCILIATION, EXPLAINED
Clear decisions. Clear boundaries.
Are suggested matches automatically approved?+
No. A suggested match is presented for review. An authorised person confirms the relationship or returns the item to the exception queue.
Does confirming a match create a payment or journal?+
Not silently. Matching existing records and creating missing accounting entries are separate decisions. Any required posting should follow Cyntrova’s established accounting controls.
What happens when no confident match is found?+
The transaction stays unmatched or moves into an exception queue with the available source context, so the team can investigate it.
Which bank feeds and statement formats are supported?+
Availability can depend on the current integration, bank and account type. Confirm support for your bank and preferred import format during a walkthrough.
A CONTROLLED CLOSE
Reconcile faster. Keep the judgement.
Bring suggestions, evidence, exceptions and accounting context into one reviewable workflow.
