AMC Banking 365 BC - Automatch rules

The automatch process in the Payment Reconciliation Journal in AMC Banking has a default set of rules used for matching outgoing payments, incoming payments, and bank transaction fees,
definable for each own bank account.

In most cases, this default set of rules, covers the needs of most companies.
However, there may be situations where adjusting the default AutoMatch rules is beneficial.

This document describes the available options for adjusting the default AutoMatch rules.

General Auto match rules (Bank Account AutoMatch Setup)

General document related rules

Split Lump-sum incomming payments
Lump-sum payments containing invoice references for multiple customers will be split into separate customer reconciliation entries whenever sufficient information is available.

Short description of splitting lump-sum payments:
Payments covering invoices for multiple customers can now be automatically split and matched.

The system identifies the customers from the stated invoice numbers, splits the payment, and matches each part to the relevant customer entries.

Example

A payment 1.250€ is received for:

• Invoice 1001 (Customer A) Amount 250€

• Invoice 1002 (Customer B) Amount 650€

• Invoice 1003 (Customer C) Amount 350€

If the payment amount equals the total of these invoices, the system will automatically split the payment into three separate customer payments and perform the matching accordingly.

Note: Splitting is only performed if all stated invoices are found in Business Central and the payment amount exactly matches the total invoice amount.

If Split Lump-sum incomming payments is activated and no custom auto-match rules exist for the bank account, the current default auto-match rules will automatically be loaded to allow the changes to be saved.

General party related rules

Party match percentage
Specifies the minimum match percentage required between the Party related value and the bank-provided information to qualify as "Related Party Matched"::Partially.
Setting the Party match percentage to 0 disables this function.

Short description of Party match percentage:
Party-related matching now uses a configurable match percentage instead of requiring the full customer name.

Examples

Party Match Percentage = 50% (Default setting)

• Customer name: AMC-Consult A/S

• Payer reference: AMC

• Result: No party-related match is created because the match percentage is below the required threshold.

Party Match Percentage = 20% or below

• Customer name: AMC-Consult A/S

• Payer reference: AMC

• Result: A partial party-related match is created because the configured threshold is met.

Party Match Percentage = 100%

• Customer name: AMC-Consult A/S

• Payer reference: AMC-Consult A/S

• Result: A fully party-related match is created because the configured threshold is met.

Party Match Percentage = 0%

• No partial party-related matching is performed. Only full party-related matches (100%) are considered.

Combining with Omit Words

The Omit Words feature can be used to exclude words, such as 'A/S', before calculating the match percentage. To use this feature, configure the omitted words for the Account Name match field under Party-related Matching.

For example, if A/S is configured as an omitted word:

• Customer name: AMC-Consult A/S

• Comparison value: AMC-Consult

• Payer reference: AMC

The match percentage is then calculated against the cleaned customer name, improving matching accuracy. Representing approximately 27% of comparison value.

Notes:

• Words with fewer than 3 characters are ignored.

• Lower match percentages may increase matching time.
  

If Party match percentage is changed and no custom auto-match rules exist for the bank account, the current default auto-match rules will automatically be loaded to allow the changes to be saved.

Grid overview (Bank Account AutoMatch Setup)

Include
Specifies whether the AutoMatch type is included in the matching process.
If this option is unselected, the corresponding match field names in the Grid Overview (AutoMatch Fields Setup) will automatically be unselected as well.

AutoMatch Type
The AutoMatch Type has four possible options:

1. End-to-End ID Matching
   Use E2E/ULR reference to match against outgoing payments made with AMC Banking Payment Journal.
   
   Example

   A payment batch is created in the AMC Banking Payment Journal containing payments to three vendors:

   Vendor	Invoice	Amount	E2E/ULR Reference
   Contoso Ltd.	INV-1001	EUR 500.00	E2E-000123
   Fabrikam A/S	INV-2005	EUR 750.00	E2E-000124
   Northwind AB	INV-3010	EUR 1,250.00	E2E-000125

   The bank executes all three payments and later returns them in the bank feed.

   When processing the bank feed, the system uses the E2E/ULR Reference to identify each payment:

   Bank feed Amount	E2E/ULR Reference	Matched Payment
   EUR 500.00	E2E-000123	Contoso Ltd.
   EUR 750.00	E2E-000124	Fabrikam A/S
   EUR 1,250.00	E2E-000125	Northwind AB

   Even if all three payments were sent in the same payment batch or have similar descriptions, each payment is matched to the correct vendor because the E2E/ULR Reference is unique for every payment. This makes the matching process more reliable than matching only on amount or payment description.
   
   Note:
   Some banks combine multiple outgoing payments into a single lump-sum transaction and return only one E2E/ULR reference for the payment batch. If the returned E2E/ULR reference belongs to the batch and the bank feed amount matches the total batch amount, the system can still identify the payment batch and automatically split it into individual Payment Reconciliation Lines, allowing each outgoing payment to be matched separately to the correct vendor.
   
   Some banks combine multiple outgoing payments into a single lump-sum transaction without returning an E2E/ULR reference for the payment batch. In this case, if the bank feed amount matches the total amount of a payment batch, the system can still identify the batch and automatically create individual Payment Reconciliation Lines for each outgoing payment, allowing them to be matched separately to the correct vendor.
   

2. Document-Related Matching
   Use Payment reference/Invoice No. etc. to match against Bank references/Posting text/Manual advice text.
   
   Example

   A customer pays an invoice and includes the invoice number as payment information in the bank.

   Customer Ledger Entry

   Customer	Invoice No.	Amount
   Contoso Ltd.	INV-100245	EUR 1,500.00

   The bank statement contains the following transaction:

   Bank feed field	Value
   Amount	EUR 1,500.00
   Bank Reference	DOC:INV-100245
   Posting Text	Contoso, INV-100245
   Manual Advice Text	(Blank)

   If Use Payment reference/Invoice No. etc. is enabled, the matching process searches the Bank Reference, Posting Text, and Manual Advice Text for values that match the payment reference, invoice number, or other document references stored in Business Central.

   In this example, the value INV-100245 is found in the Bank Reference, allowing the customer ledger entry to be matched automatically.

   But this feature is also useful when the bank does not provide the reference in a dedicated field but includes it as part of the transaction text.

   
   Note:
   See also the Omit Words functionality.
   It can be used together with Use Payment Reference/Invoice No. etc. matching to exclude irrelevant words or characters before comparing references, improving match accuracy.
   

3. Text-to-Account Matching
   Use text-to-account mapping text to match against Bank references/Posting text/Manual advice text.
   
   Example

   You have configured the following Text-to-Account Mapping:

   Search Text	Account Type	Account
   PAYPAL	G/L Account	6780 – PayPal Fees
   AMAZON	Vendor	Amazon EU S.à r.l.
   OFFICE DEPOT	Vendor	Office Depot

   The bank statement contains the following transaction:

   Bank feed field	Value
   Amount	EUR 249.95
   Bank Reference	AMAZON MARKETPLACE
   Posting Text	Card Payment AMAZON
   Manual Advice Text	(Blank)

   If Text-to-Account Matching is enabled, the system searches the Bank Reference, Posting Text, and Manual Advice Text for configured mapping texts.

   In this example, the text AMAZON is found in the Posting Text. The system therefore identifies the transaction as belonging to the mapped vendor (Amazon EU S.à r.l.) and creates a match accordingly.

   This feature is useful when bank transactions contain recognizable text instead of invoice numbers or payment references, allowing recurring transactions to be matched automatically.
   

4. Party-Related Matching
   Use party related information as Name/Account No./Bank Account No to match against Bank references/Posting text/Manual advice text.

   
   Party-Related Matching, if included, is always combined with other AutoMatch types, such as End-to-End ID Matching or Document-Related Matching, as payment application rules are divided into two categories — Document-Related Matching and Party-Related Matching — to achieve the highest possible match score.
   
   Example

   A customer has the following information in Business Central:

   Field	Value
   Customer Name	Contoso Ltd.
   Customer No.	C10000
   Bank Account No.	1234567890

   The bank statement contains the following transaction:

   Bank feed field	Value
   Amount	EUR 2,500.00
   Bank Reference	DOC: INV-100245
   Posting Text	Contoso Ltd.
   Manual Advice Text	(Blank)

   The system first performs Document-Related Matching and identifies the invoice number INV-100245.

   It then performs Party-Related Matching by searching the Bank Reference, Posting Text, and Manual Advice Text for the customer's Name, Account No., or Bank Account No. In this example, Contoso Ltd. is found in both the Bank Reference and Posting Text.

   Because both the document reference and the party information point to the same customer, the combined match receives a higher match score than if only one of the matching methods had succeeded.

Description
Short description of the automatch type.

Try Amount Date Match
Specifies whether a Date/Amount match should be attempted.
This means that if no match can be found based on fields such as Document No. etc.,
the matching process will try to match using the transaction date and amount.

Note:
Enabling Try Amount Date Match can increase the time required for the matching process because the system must search additional open ledger entries when no document-based match is found.

(-/+) Day Tolerance
Specifies the number of days before and after the bank feed transaction date within which the system searches for vendor or customer open ledger entries based on their possible cash discount date or due date.

If you enter 0 or leave the field blank, the Match function only searches for vendor or customer open ledger entries whose due date falls exactly on the bank feed transaction date.

Examples

A bank feed transaction contains the following information:

• Transaction date: 15 July 2026

• Amount: EUR 1,250.00

• Reference: No invoice or document number is provided.

Because no document number is available, the system cannot perform a document-based match.

If Try Amount Date Match is enabled, the system instead searches for open customer or vendor ledger entries with:

• The same amount (EUR 1,250.00), and

• A due date (or possible cash discount date) within the configured Day Tolerance.

For example, if (-/+) Day Tolerance is set to 2, the system searches for entries with a due date or possible cash discount date between 13 July 2026 and 17 July 2026.

If a matching open ledger entry for EUR 1,250.00 is found within the specified date range, the system creates a match. Otherwise, no match is created.

This option is only available for automatch type = End-to-End ID Matching or Document-Related Matching, used together with the option Try Amount Date Match.

Ribbon (Action bar)

Delete

Delete the match setup rules and return to default automatch rules.

Default Match Setup

Fetch the default match rules to use them as a basis for editing and customizing according to your own preferences.

Copy from other Bank Account

Copy the match setup from other bank account to current bank account.

Grid overview (AutoMatch fields Setup)

Include
Specifies whether the AutoMatch field, defined in the Match Field Name, is included in the matching process.

Match Field Name
Specifies the name of the field to be matched against.

The available Match Field Names may vary depending on which AutoMatch Type is selected.
See the description field for more details information on the match field.

Description
Specifies a short description of automatch field.

Omit Words
Specifies the number of omit words configured for this automatch field. Omit words are values that will be removed from the field value before matching to improve matching accuracy.

Users can now define prefixes or text strings that should be ignored during matching. For example, by configuring PS-INV as an omitted word, the system will compare:

• PS-INV123456

• 123456

• 0000123456

as equivalent values, significantly improving the success rate of automatic invoice matching.

Ribbon (Action bar)

Setup omit words

Specify values to be omitted from the selected field's BC value before auto matching,
improving match accuracy by ignoring non-essential words.

Help

Open the AMC Banking Knowledge Base for Own Bank Account to view a detailed description of how to set up your own bank account and other related settings.