Does Lynka connect to live bank feeds?
The verified reconciliation workflow uses imported bank statement data; do not assume a live bank feed.
Lynka guide
Bank reconciliation is a matching job, not a bank-feed promise.
Reconciliation compares statement activity with the financial records in the books so differences can be explained before the period is treated as complete.
The basic question is simple: does the movement shown by the bank correspond to a payment, supplier settlement, expense or other transaction in the accounting records?
Lynka reconciliation works from imported bank statement data. It does not currently provide a live bank feed.
01
Start with the bank statement period
Import or enter the statement data for the account and period being reviewed. Confirm opening and closing context according to the company’s process before matching individual lines.
A reconciliation is only as trustworthy as the statement data being compared, so duplicate or incomplete imports should be resolved first.
02
Identify plausible transaction candidates
A statement line can be compared with customer payments, supplier payments and expenses using amount, date and description context. Candidate matching is a way to narrow the search, not proof that two records are the same transaction.
The reviewer remains responsible for deciding whether a proposed match is correct.
03
Treat amount and date differences as evidence
Small date differences can occur because the accounting record and bank posting date are not identical. Amount differences may reflect fees, combined payments, currency effects or a genuine mismatch.
Do not force a match simply to clear the statement. An unexplained difference belongs in exception work.
04
Use reconciliation rules for repeatable patterns
Rules can help recognize recurring description patterns or known transaction behavior. They are useful when a bank uses consistent text for the same type of charge or receipt.
Rules should reduce repetitive searching without hiding exceptions that deserve review.
05
Keep unresolved lines visible
An exception can record why a statement item is not reconciled and what needs to happen next. Unmatched items are not automatically errors; they may represent transactions not yet entered or timing differences.
A visible exception list is better than marking questionable lines reconciled to make the count look complete.
06
Preserve the ability to undo a wrong match
If a reconciliation decision was incorrect, unmatching should be explicit and traceable rather than requiring edits that erase the prior action.
That history helps finance understand why the account changed during review.
07
Review reconciliation readiness before close
A readiness view can summarize matched and unmatched statement activity for the account. Finance can use that alongside other close checks instead of assuming the bank is reconciled because most lines look familiar.
The objective is explainable completeness, not a cosmetic 100 percent indicator.
08
Know what reconciliation does not solve
Bank reconciliation does not replace cash-flow forecasting, treasury management or transaction authorization. It verifies that bank activity and accounting records can be connected and exceptions explained.
For small businesses, doing that consistently is already a substantial control.
Reconciliation review list
- Statement data covers the intended account and period.
- Duplicate statement imports were checked.
- Candidate matches were reviewed, not accepted blindly.
- Amount and date differences are explained.
- Recurring rules are tested before broad use.
- Unmatched lines have an owner or reason.
- Incorrect matches are explicitly undone.
- Readiness is reviewed before period close.