Bank statement rows can store transaction date, value date, description, reference, amount, credit direction, cheque number and the bank account they belong to.
Bank reconciliation currently starts from imported bank-statement data. Lynka does not claim a live bank feed where one is not connected.
Reconciliation matches can point to a customer invoice payment, supplier bill payment or expense and keep the amount matched.
Matching evidence can include confidence score, description similarity, date difference and amount difference, so a suggestion can be reviewed rather than appearing as an unexplained yes or no.
Reconciliation rules can have a name, type, configuration, priority and active state.
Rules can help the system evaluate repeat patterns while Finance keeps control of which rules are active and in what order they are considered.
Reconciliation exceptions can keep the transaction, exception type, severity, candidate matches, assignee, due date, status and resolution notes.
That is more useful than forcing a weak match just to make the unmatched count disappear.
Match records support unmatching with the user, time and reason retained.
A separate reconciliation audit log records previous and new state around reconciliation actions, giving Finance a trail when a decision is later changed.
The Bank Reconciliation Readiness report focuses on unmatched transactions and unresolved exceptions.
It gives the close process a direct answer to “what is still unresolved in the bank work?” without pretending that the report itself performs the reconciliation.
Bank accounts can store the linked chart-of-accounts account, currency, opening balance and last reconciled date and balance.
That keeps the bank statement activity, reconciliation work and ledger account connected around the same bank account record.
Reconciliation matches can store the rule information used, confidence, description similarity, date difference and amount difference. Those signals can help Finance understand why a bank transaction was associated with a recorded receipt, supplier payment or expense.
A candidate is not the same thing as a forced match. Exceptions can stay open with severity, assignment, due date and resolution notes when the bank row needs human review.
Matches can record who matched the transaction and when. They can also record who later unmatched it, when that happened and the reason.
That is safer than deleting the bank row or financial record just to fix a reconciliation decision because the original business transaction and the reconciliation history remain separate.
Reconciliation is where the bank and the books have to agree transaction by transaction. Lynka keeps imported statement rows beside the customer receipts, supplier payments and expenses they may represent.
Reconciliation currently uses imported bank-statement data. Lynka does not present this as an automatic live bank feed.
