Apply cash
Match bank payments
Suggest customer matches for bank lines in the Payment Reconciliation Journal after Apply Automatically, accept them, remember payers and post as usual.
updated: applies-to: 1.2.0.0
Match the customer receipts on your bank statement to open invoices before you post. Bitta Collections adds a Customer Matches menu to the native Payment Reconciliation Journal. It works after the native Apply Automatically, on the lines that are still unapplied, and you post the journal as usual.
Applies to: Bitta Collections 1.2 on Business Central online, version 28 or later.
Before you start
- You need the BAA COLL EDIT permission set (the Collector set), plus the Business Central permissions for payment reconciliation journals.
- Suggest Customer Matches needs a seat of the Bitta Collections license. Accepting and rejecting suggestions work without a seat.
- Import the bank statement into a payment reconciliation journal as you do today, for example from a bank feed or a file.
Run Apply Automatically first
- Search for Payment Reconciliation Journals and open the journal of the bank account.
- Choose Apply Automatically, the native action.
Bitta Collections also helps the native matcher here. When a line's text names an open invoice by its document number or external document number, the native matcher gets that invoice as a candidate. Disputed invoices are moved down in the native ranking, never hidden. Nothing is written by this step.
Suggest customer matches
- Select the lines that are still unapplied or have a difference. Only the selected lines are used; with no lines selected, the current line is used. You can select all lines.
- Choose Customer Matches > Suggest Customer Matches. A message tells you how many suggestions were created.
- Select a line and read the Customer Match FactBox: confidence, method, amounts and the explanation.
Only customer receipts get suggestions: lines with a positive amount that is not fully applied, whose account type is Customer or that have no account yet. Lines posted to a G/L account, vendor, bank account or another account type are skipped and are not counted in the message.
The customer comes from the line, if it has one. Otherwise it is found from a document number in the text, a text-to-account mapping or the payer name. When no customer is found, the message says so. Fill in the payer name, choose Remember Payer, or apply the line manually.
The same rules as for unapplied payments find the documents: document references, exact amount, a combination of up to 5 invoices, then oldest first. See how the rules match.
Accept suggestions
| Action | What it does |
|---|---|
| Accept Best Match | Applies the line to the documents of its best suggestion, as native applied entries |
| Accept All High | Applies every line that has a proposed High rule suggestion. You see the count and total first |
| Match Suggestions | Opens Payment Match Suggestions for this journal, where you accept or reject each suggestion |
Accepting writes native applied payment entries for the line, as a native application does. The journal line then shows the application, and you can still change it natively. The Customer Match FactBox then shows what was accepted: the amount, the documents and the customer. When you are done, post the journal with the native posting action.
If an accepted suggestion leaves an invoice partly open, the Short Payment dialog asks whether to open a dispute. The dispute opens after you post the journal, when the collections job runs next.
To undo an accepted suggestion, use the native Remove Applications on the journal. Reject works only on suggestions that were not accepted yet.
After Remove Applications, the FactBox says that the line has no application now. Choose Suggest Customer Matches again: the FactBox then shows the new suggestion, and the earlier suggestion gets the status Withdrawn, so it no longer counts as accepted. Match Suggestions also marks such suggestions Withdrawn when it opens. A suggestion whose documents are still applied to the line stays Accepted. Withdrawn suggestions are left out of the Cash Application Register and of the accepted counts.
NOTE
Accept All High never takes an AI suggestion. A person reviews AI suggestions one by one.
Remember a payer
When a customer always pays under a name that Business Central doesn't recognize, link the name to the customer once.
- Apply the line to the customer, by a suggestion or manually.
- Choose Customer Matches > Remember Payer.
This creates a native Text-to-Account Mapping for the payer name, and a message confirms that payments from that payer will be matched to the customer from now on. Native matching and the suggestions both use the mapping next time. If the text is already mapped to another account, change it on the Text-to-Account Mapping page.
NOTE
The native matcher finds a Remember Payer mapping only when the payer name is in the line's Transaction Text. Local-currency bank lines match only local-currency invoices; the setting Appln. between Currencies is not used.
AI ranking (preview)
When the rules find no clear match, Rank possible matches can ask Azure OpenAI to rank the open documents of a line. It is off by default, and a person keeps or discards each proposal. See AI features (preview).
What's next
Read remittance advice from a mailbox or a file: Remittances.