Managing bank transactions manually can be time-consuming for finance and accounting teams, especially when businesses process large volumes of customer payments, vendor transactions, bank charges, and other cash movements.
Payment Reconciliation in Microsoft Dynamics 365 Business Central helps finance teams import bank transactions, match payments with open customer or vendor entries, review exceptions, and post the relevant transactions efficiently.
At Leaping Frog Solutions, we help businesses use Microsoft Dynamics 365 Business Central to streamline finance and accounting processes, improve transaction visibility, and reduce repetitive manual work.
This guide explains the Payment Reconciliation Journal process in Business Central, from setup and bank statement import to automatic matching, manual application, posting, and final bank reconciliation.
What Is Payment Reconciliation in Business Central?
Payment Reconciliation in Business Central is the process of importing bank transactions and applying them to related open entries, such as customer invoices, vendor entries, credit memos, and other applicable ledger entries.
Business Central can use automatic application rules to suggest matches based on information such as payment text, related-party information, document numbers, and amounts. Users can review and change the suggested applications before posting.
Why Is Payment Reconciliation Important?
A structured payment reconciliation process can help businesses:
- Match bank transactions with open ledger entries
- Reduce repetitive manual application work
- Identify unmatched or exceptional transactions
- Improve payment posting accuracy
- Maintain more accurate bank records
- Support regular bank reconciliation
- Improve visibility into customer and vendor payments
Payment Reconciliation vs. Bank Account Reconciliation
These two processes are related but serve different purposes.
Payment Reconciliation Journal
The Payment Reconciliation Journal is primarily used to process payments represented by bank transactions and apply them to related open entries. Bank transactions can be imported from a file or feed, automatically matched, reviewed, and posted.
Bank Account Reconciliation
Bank Account Reconciliation compares the company's bank account ledger in Business Central with the external bank statement to identify and resolve differences.
Microsoft recommends regular bank reconciliation to ensure the company's cash records accurately reflect the bank's transactions.
In simple terms:
Payment Reconciliation → Apply and post payments
Bank Account Reconciliation → Verify bank balances and transactions
Prerequisites for Payment Reconciliation
Before starting the reconciliation process, make sure the following are configured.
| Requirement |
Purpose |
| Bank Account |
Bank account must be set up correctly in Business Central |
| Bank Statement Import |
Required if statements are imported electronically |
| Payment Application Rules |
Helps Business Central determine automatic payment matches |
| Open Customer/Vendor Entries |
Provides transactions against which payments can be applied |
| User Permissions |
User must have appropriate finance or accounting permissions |
| Bank Feed |
Optional method for receiving bank transactions |
| Bank Charges G/L Account |
Useful for transactions such as bank fees and charges |
Payment Application Rules can be configured to control how Business Central automatically matches bank transaction information with open entries.
Step-by-Step Payment Reconciliation Process in Business Central
The typical process can be summarized as:
Open Payment Reconciliation Journal → Create Journal → Import Bank Transactions → Apply Automatically → Review and Apply Manually → Resolve Differences → Post → Reconcile Bank Account
Step 1 — Open the Payment Reconciliation Journal
Use the Tell Me search to find:
Payment Reconciliation Journals
Alternatively, depending on your Business Central configuration, access the journal through the relevant Cash Management area.
Microsoft's current workflow uses Payment Reconciliation Journals to import bank transactions and apply payments.
Step 2 — Create a New Payment Reconciliation Journal
Select New Journal and choose the bank account for which payments need to be reconciled.
Verify the relevant bank account information before continuing.
Important information may include:
- Bank Account No.
- Statement No.
- Statement Date
- Statement Ending Balance
The Payment Reconciliation Journal is associated with a specific bank account.
Step 3 — Import Bank Transactions
Once the journal is created, import the relevant bank transactions.
Depending on your setup, Business Central can receive bank transactions through an electronic bank statement file or bank feed.
Select:
Import Bank Transactions
Then choose the appropriate file and import it.
After import, Business Central populates the journal with bank transaction lines.
Review the imported transactions to confirm that:
- The correct bank account was selected
- The expected transactions were imported
- Dates are correct
- Amounts are correct
- Transaction descriptions or references are available
Microsoft documents bank statement/file or feed import as part of the Payment Reconciliation Journal workflow.
Step 4 — Apply Payments Automatically
After importing the transactions, use:
Actions → Apply Automatically
Business Central uses the configured Payment Application Rules to suggest applications between bank transaction lines and open entries.
Matching can consider information such as:
- Related-party information
- Transaction text
- Document number
- External document number
- Amount
- Payment tolerance
The quality of the suggested application is shown through the Match Confidence field.
Understanding Match Confidence
| Match Confidence |
Meaning |
Recommended Action |
| High |
Strong match based on available criteria |
Review and accept |
|
Medium
|
Reasonable match requiring validation |
Review carefully |
| Low |
Limited matching information |
Verify manually |
| No Match |
No suitable application was suggested |
Apply manually |
The exact application rules and results can vary based on the configuration of your Business Central environment.
Step 5 — Review and Apply Unmatched Payments
Not every bank transaction will be matched automatically.
For unmatched transactions, select the relevant journal line and choose:
Apply Manually
The Payment Application page lets users review open entries and manually apply the payment to the appropriate transaction.
Common Reasons for Manual Application
Manual review may be required when:
- Payment references are missing
- Document numbers do not match
- A customer makes a partial payment
- A payment covers multiple invoices
- Bank charges have been deducted
- The transaction relates to a new or unrecognized entry
When applying a payment, verify the Applied Amount and any remaining amount before confirming the application.
Step 6 — Post Bank Charges and Other G/L Transactions
Some bank transactions do not relate to customer or vendor invoices.
Examples include:
- Bank charges
- Interest income
- Interest expenses
- Service fees
- Other direct bank transactions
Where applicable, these transactions can be mapped to the relevant G/L Account rather than a customer or vendor entry.
Business Central supports mapping and posting bank transactions to G/L accounts as part of the payment reconciliation process.
Step 7 — Review Differences Before Posting
Before posting the Payment Reconciliation Journal, review all unmatched applications and differences.
Check:
- Imported transaction amounts
- Applied amounts
- Remaining amounts
- Payment dates
- Customer/vendor applications
- G/L account postings
- Currency differences
- Duplicate transactions
Business Central provides review functionality for applications that require attention, including lines with differences.
Common Difference Scenarios
| Issue |
Possible Cause |
Action |
| Remaining amount |
Payment is not fully applied |
Review and apply the remaining amount |
| Difference on line |
Partial payment, discount, fee, or tolerance |
Review the transaction and applicable adjustment |
| Duplicate match |
Incorrect application |
Remove and reapply the payment |
| Missing transaction |
Bank transaction has no corresponding entry |
Investigate and post appropriately |
| Currency difference |
Foreign currency transaction or exchange-rate variation |
Review the applicable currency adjustment |
Do not post until the reconciliation has been reviewed and the required differences have been resolved according to your organization's accounting procedures.
Step 8 — Post the Payment Reconciliation Journal
After reviewing and validating the applications, post the Payment Reconciliation Journal.
The posting process updates the relevant accounting records based on the applications and transactions in the journal.
Depending on the transaction, posting can result in:
- Customer or vendor entries being applied
- Bank account ledger entries being created
- G/L entries being posted
- Reconciled payment information being recorded
Business Central allows users to review automatic applications and modify them before posting.
Step 9 — Verify the Bank Account Balance
After posting, verify the resulting bank account information.
Navigation:
Cash Management → Bank Accounts
Open the relevant bank account and review the balance and ledger entries.
Compare the Business Central balance with the corresponding bank statement.
Regular bank reconciliation helps identify missing transactions, posting errors, and other differences between the company's records and the bank's records.
Bank Account Reconciliation in Business Central
Payment reconciliation and bank account reconciliation work together but should not be treated as exactly the same process.
For formal bank reconciliation:
Navigation:
Cash Management → Bank Account Reconciliations
Create a new reconciliation and enter the relevant:
- Bank Account No.
- Statement No.
- Statement Date
- Statement Ending Balance
Import or enter bank statement information, compare it with the bank ledger entries, investigate differences, and complete the reconciliation.
Business Central also provides a Test Report that can be used to review a reconciliation before posting.
Common Payment Reconciliation Problems and Solutions
| Problem |
Possible Cause |
Recommended Action |
| Bank statement cannot be imported |
Incorrect import configuration or unsupported file structure |
Review the bank account import setup and file format |
| No automatic matches found |
Missing references or no suitable open entries |
Review open entries and payment application rules |
| Low Match Confidence |
Insufficient matching information |
Review the transaction and apply manually if required |
| Remaining amount is not zero |
Payment is partially or incorrectly applied |
Review applications and remaining amounts |
| Duplicate transactions appear |
Bank transaction was imported more than once |
Check the journal and posted transactions before re-importing |
| Bank balance does not match |
Missing, outstanding, or incorrectly posted transactions |
Run the reconciliation and investigate differences |
| Payment applied to the wrong invoice |
Incorrect automatic or manual application |
Review and reapply the payment correctly |
Key Reports and Pages for Payment Reconciliation
The following pages and reports can help finance teams review payment and bank reconciliation activities:
| Page/ Report |
Purpose |
| Payment Reconciliation Journal |
Import, apply, review, and post payment transactions |
| Bank Account Statement |
Review bank account transactions for a selected period |
| Bank Account Reconciliation |
Compare Business Central bank ledger entries with the bank statement |
| Customer Ledger Entries |
Review customer payments and open entries |
| Vendor Ledger Entries |
Review vendor payments and open entries |
| Trial Balance |
Review G/L balances after posting |
| Aged Accounts Receivable |
Review outstanding customer balances |
| Aged Accounts Payable |
Review outstanding vendor balances |
End-to-End Payment Reconciliation Process
StepActionResult
1Open Payment Reconciliation JournalsJournal page opened
2Create a new journalBank account selected
3Import bank transactionsBank lines loaded
4Apply payments automaticallyMatching suggestions generated
5Review and apply unmatched linesPayments correctly applied
6Review differencesExceptions resolved
7Post the journalAccounting entries updated
8Verify bank balanceBank records compared with Business Central
H2: Best Practices for Payment Reconciliation in Business Central
H3: Maintain Accurate Payment References
Consistent document numbers, transaction references, and customer/vendor information can improve automatic matching.
H3: Configure Payment Application Rules
Payment Application Rules determine the criteria Business Central uses when suggesting automatic applications. Review and adjust these rules based on your organization's transaction patterns.
H3: Review Automatic Applications Before Posting
Automatic matching can reduce manual work, but finance users should review applications—particularly those with lower match confidence or differences—before posting.
H3: Reconcile Bank Accounts Regularly
Regular reconciliation helps identify missing transactions and bookkeeping differences before they become larger month-end issues.
H3: Investigate Exceptions Instead of Forcing Matches
If a transaction cannot be confidently matched, investigate the source rather than applying it to an incorrect account simply to clear the journal.
H2: Frequently Asked Questions About Payment Reconciliation in Business Central
H3: What is Payment Reconciliation in Business Central?
Payment Reconciliation in Business Central is the process of importing bank transactions and applying them to related open customer, vendor, or other applicable ledger entries.
H3: What is a Payment Reconciliation Journal?
A Payment Reconciliation Journal is used to process bank transactions, apply payments to open entries, review automatic applications, and post the resulting transactions.
H3: Can Business Central automatically match bank payments?
Yes. Business Central provides automatic application functionality that uses configured Payment Application Rules to suggest matches between bank transactions and open entries.
H3: What is Match Confidence in Business Central?
Match Confidence indicates the quality of an automatically suggested payment application. It can help users determine which applications require additional review before posting.
H3: Can unmatched payments be applied manually?
Yes. Users can open the Payment Application page and manually apply a payment to the appropriate open entry when automatic matching does not produce the required result.
H3: What is the difference between payment reconciliation and bank reconciliation?
Payment reconciliation focuses on applying bank payments to relevant accounting entries, while bank reconciliation compares Business Central's bank ledger with the external bank statement to verify the bank balance and identify differences.
H3: How can Payment Reconciliation reduce accounting effort?
By importing bank transactions and using automatic application rules to suggest matches, Business Central can reduce repetitive manual payment application and help finance teams focus on exceptions and validation.
H2: Final Takeaway
Payment reconciliation doesn't have to be a repetitive manual accounting task.
With Microsoft Dynamics 365 Business Central, finance teams can import bank transactions, automatically apply payments where appropriate, manually resolve exceptions, and complete bank reconciliation within a structured process.
The basic workflow is:
Import Bank Transactions → Apply Automatically → Review Matches → Apply Exceptions → Resolve Differences → Post → Reconcile Bank Account
When supported by accurate payment references, well-configured application rules, and regular bank reconciliation, the process can help businesses improve payment accuracy, accounting efficiency, cash visibility, and financial control.
At Leaping Frog Solutions, we help businesses streamline finance and accounting processes with Microsoft Dynamics 365 Business Central, from implementation and configuration to process optimization.