Transaction Matching Capabilities
Account Reconciliation uses AI-powered automatic matching to reconcile GL transactions against bank statement data. The system supports three matching types to handle various business scenarios where transactions are recorded differently between systems.
Supported Matching Types
| Matching Type | Description | Transaction Limit |
|---|---|---|
One-to-One |
Matches a single GL transaction to a single bank transaction |
Unlimited |
One-to-Many |
Matches one GL transaction to multiple bank transactions |
Up to 4 bank transactions |
| Many-to-One | Matches multiple GL transactions to one bank transaction | Up to 4 GL entries |
Note: Many-to-one and one-to-many matching currently support up to 4 transactions on either side. If you need to match more than 4 transactions, create multiple matches or add unmatched line items with explanations.
One-to-One Matching
One-to-one matching pairs a single GL transaction with a single bank statement transaction. This is the most common match type, used when transaction amounts and details correspond directly between systems.
Example:
A GL entry for $1,500.00 dated December 5 matches to a bank statement deposit of $1,500.00 on the same date.
One-to-Many Matching
One-to-many matching automatically groups multiple bank transactions to match a single GL transaction. This handles scenarios where one business transaction appears as multiple entries in the bank statement.
Example:
A GL payment entry of $10,000 matches to four separate bank transactions of $2,500 each processed on the same day.
Common Use Cases:
| Scenario | Description |
|---|---|
Split payments |
One GL invoice payment matches multiple bank transactions due to payment processing limits |
ACH batches |
Single GL disbursement entry matches multiple ACH transactions processed separately by the bank |
Credit card settlements |
One GL sales entry matches multiple settlement transactions from the payment processor |
Many-to-One Matching
Many-to-one matching automatically groups multiple GL transactions to match a single bank statement transaction. This handles scenarios where multiple business activities are recorded separately in the GL but appear as one combined entry in the bank statement.
Example:
Four separate GL expense entries totaling $8,000 match to a single $8,000 bank withdrawal.
Common Use Cases:
| Scenario | Description |
|---|---|
Consolidated deposits |
Multiple individual GL entries for customer payments match to a single consolidated bank deposit |
Batch payments |
Multiple GL disbursement entries match to a single bank withdrawal for a batch payment run |
Aggregated fees |
Several small GL fee entries match to one monthly bank service charge |
All matched transactions maintain complete audit trails showing the matching method used and when the match was created.