Account matching in Continia Banking
Account matching is a key part of the reconciliation process in Continia Banking. It ensures that imported bank statement lines are identified, categorized, and applied correctly to customer, vendor, employee, and bank account ledger entries. Continia Banking expands the matching features available in Business Central with additional rules, matching logic, and tools that help you complete reconciliation accurately and with fewer manual steps.
This section describes the concepts and matching rules that support account identification, document matching, and proposal creation during reconciliation. It also explains additional features that help you manage special cases, such as posting multiple applications as one entry or applying statement lines manually.
In this section:
Introducing reconciliation with Continia Banking
Learn how Continia Banking supports the reconciliation process in Business Central. This article explains how imported bank transactions are matched to your books, how unmatched entries are presented for review, and how Continia adds matching rules on top of Business Central’s standard functionality. See Introducing reconciliation with Continia Banking.
The basics of account identification in Continia Banking
Account identification matches details such as BBAN, IBAN, names, and addresses to ensure that transactions are applied to the correct accounts. This article describes how the system identifies accounts, what happens when information is incomplete, and how the reconciliation status indicates when an account was identified but an application could not be created. See The basics of account identification in Continia Banking.
Matching statement amount to account balance
This feature helps create payment application proposals when the statement amount matches the total open balance of a customer, vendor, or employee account. The article explains how the system checks for a full balance match and how it uses that match to suggest applications when no document number is available. See Matching statement amount to account balance.
Transaction type identification
Continia Banking uses transaction code rules to categorize incoming transactions. This article describes how standardized ISO Transaction Codes and proprietary codes are used to identify transaction types such as payments, fees, and other activities, helping the system apply the correct matching and posting logic. See Transaction type identification.
Document number matching
Document number matching identifies invoice numbers, payment references, and other document identifiers in bank statement files. This article describes how Continia Banking detects document numbers and uses them to create accurate and consistent payment application proposals. See Document number matching.
Posting multiple applications as one sum entry
When a single statement line applies to several invoices, the system normally posts one entry per application. This article explains how the sum posting feature allows these applications to be posted as one ledger entry, reducing the number of posted entries for the same account and improving clarity in the ledger. See Posting multiple applications as one sum entry.
Matching bank account ledger entries by posting date and amount
This matching rule identifies exact matches between bank statement lines and bank account ledger entries based on posting date and amount. The article explains how date tolerances work and how the system creates application proposals using this method under the right conditions. See Matching bank account ledger entries by posting date and amount.
Manual application
Manual application gives you full control when a statement line cannot be matched automatically. This section explains when to use manual application, how it integrates with the Payment Application Review workflow, and the types of scenarios where manual selection of ledger entries is necessary. See Introducing manual application.