You’re offline. This is a read only version of the page.
9,146
Hi
I have an issue with the Text-to-Account mapping in Business Central in that is seems that only the first six characters are being used to do the matching.
Scenario: I have a new implementation. They have decided to bring detailed transactions from their existing system into BC for the prior two years (yes I know, that brings a pile of issues - not my choice). Their current system operates everything as journals, so aside from volumes, this is a relatively straight-forward process. To ensure that the vendor credits / payments are applied where possible, I am separating those out and using the Payment Recon Journals to bring them in.
They have lots of Vendor ID's that are similar:
So I added the vendor list mapping into the Text to Mapping table as above.
However, when then importing the transactions, I get this result:
Can anyone shed light into why it is behaving in this way? I would have thought if it allows us to have more than six characters in the mapping table, it would use them.
Cheers
Heather
Hi Heather,
I would have to test it more in a BC payment rec journal, but the matching is all scored by calculations and similar code is used just like Auto Bank Rec. In Auto Bank Rec (from prior tests in NAV 2018), the matching was scored by these calculations:
Match by amount
Bank Statement Description to Document No to see if there is any relation
Bank Statement Description to External Document No. to see if there is any relation
Transaction Dates match
*Bank Statement Description to Bank Ledger Description (1st 4 characters as a minimum length). Then a common substring is searched upon.
That MatchLengthTreshold is 4 in Codeunit 1255 for Match Bank Payments and that is most likely what you are running into. Even if the vendors are mapped it seems to still take into consideration the Match Length Threshold of 4.
Share
Report
All responses (
Answers (
