Codeunit 1251 "Record Match Mgt."

Base Application · Microsoft.Bank.Reconciliation · BC23-30 · source at ea08af5e · facts from BC29

Procedures

• GetLongestCommonSubstring(FirstString: Text; SecondString: Text): Text: Finds and returns the longest common substring between two strings. Performs case-insensitive comparison to identify the longest sequence of characters that appears in both input strings. Used as a foundation for text similarity scoring in payment matching algorithms.
• CalculateStringNearness(FirstString: Text; SecondString: Text; Threshold: Integer; NormalizingFactor: Integer): Integer: Computes a nearness score between strings. Nearness is based on repeatedly finding longest common substrings. Substring matches below Threshold are not considered. Normalizing factor is the max value returned by this procedure.
• CalculateExactStringNearness(ComparingString: Text; BaseString: Text; NormalizingFactor: Integer): Integer: Like CalculateStringNearness, however it doesn’t repeatedly takes substrings, only once. The result is normalized with respect to the length of the BaseString, in contrast with CalculateStringNearness where it was normalized with respect ot the shorter one.
• Trim(InputString: Text): Text: Removes leading and trailing whitespace characters from a string. Provides consistent text normalization for string comparison operations, ensuring that whitespace differences do not affect matching accuracy.

Plus 2 local procedures.

Triggers

OnRun

Called by

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

• Codeunit 1255 “Match Bank Payments” (5 calls: FindBankAccLedgerEntry → CalculateStringNearness, FindBankAccLedgerEntry → Trim, GetStringNearness → CalculateStringNearness, …)
• Codeunit 1250 “Match General Journal Lines” (4 calls: GetAccountMapping → CalculateStringNearness, GetAccountMapping → Trim, GetDescriptionMatchScore → CalculateStringNearness, …)
• Codeunit 1252 “Match Bank Rec. Lines” (4 calls: BankReconciliationLineTextSimilarityScores → CalculateExactStringNearness, BankReconciliationLineTextSimilarityScores → CalculateStringNearness, GetDescriptionMatchScore → CalculateStringNearness, …)
• Codeunit 1217 “Pre-map Incoming Purch. Doc” (3 calls: FindVendorByNameAndAddress → CalculateStringNearness, FindVendorByPhoneNo → CalculateStringNearness, ValidateCompanyInfoByNameAndAddress → CalculateStringNearness)
• Table 1251 “Text-to-Account Mapping” (2 calls: InsertRec → Trim, InsertRecFromBankAccReconciliationLine → Trim)
• Codeunit 7250 “Bank Rec. AI Matching Impl.” (1 call: ComputeStringNearness → CalculateStringNearness)
• Codeunit 7251 “Bank Acc. Rec. Trans. to Acc.” (1 call: GetMostAppropriateGLAccountNos → Trim)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "Record Match Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.