# Check application: why a line is (not) applied

In 365 business Banking, the Check Application and Check Quick Apply actions show every candidate checked for a line, with its reason, in the application log.

A common question about automatic application is why a line was not applied although the invoice number is in the payment reference. **Check Application** answers this question. Business Central runs automatic application for exactly one line as a test, undoes it completely afterwards, and shows which candidates there were, which candidate would have been selected and why the others were rejected. **Check Quick Apply** provides the same function for Quick Apply.

## Standard functionality in Business Central

In the standard, the **Payment Application** page shows the candidates of a line and, for applied lines, the match details. The standard does not show why an entry did not qualify.

For more information from Microsoft, see [Review or apply payments after automatic application](https://learn.microsoft.com/en-us/dynamics365/business-central/receivables-how-review-apply-payments-auto-application).

## What 365 business Banking adds

365 business Banking adds the **Check Application** and **Check Quick Apply** actions in the payment reconciliation journal and the **Application Log** page. The log explains every step of 365 business Banking (related party, document reference, date tolerance, direct matching, reconciliation rules, mappings, payment groups, sales documents, remittance advice, on account) and the standard matching.

## Step by step

1. Open the payment reconciliation journal and select **one** line.
2. Choose **Apply Automatically** > **Check Application**. To check the result [Quick Apply](apply.mdx#quick-apply) would produce for the line, choose **Apply Automatically** > **Check Quick Apply**.

   ![The Payment Reconciliation Journal with the Apply Automatically split button open: Apply Automatically, Apply Selected Automatically, Quick Apply, Check Application and Check Quick Apply](/assets/images/365-business-banking/bank-reconciliation/zahlungsabstimmung-splitbutton-schnellausgleich-pruefen.en-US.png)

3. The **Application Log** page opens. Read the **Summary** at the top first, then the **Candidates**.

   ![The Application Log for a line without an application: summary "Would be applied to 103181 for 1,383.02. We found a match for the Document No. in the Transaction Text.", result Would Apply to One Entry with Match Confidence High](/assets/images/365-business-banking/bank-reconciliation/ausgleichsprotokoll-ausgleich-pruefen.en-US.png)

The line is not changed in the process. If it already has an application, the application is temporarily removed for the explanation and restored afterwards. For this reason, the previously selected candidate appears in the candidate list, and the summary states the reason for the match. The whole trial run is then rolled back completely. An application, including an accepted one, remains unchanged. Unsaved changes in the journal are saved first.

![The Application Log for a line that is already applied: "Would be applied to 108196 for -2,499.00. We found a match for the External Document No. in the Transaction Text. One further candidate was considered and rejected.", result Would Apply to One Entry with vendor 20000 and Match Confidence Medium](/assets/images/365-business-banking/bank-reconciliation/ausgleich-pruefen-protokoll-ausgeglichene-zeile.en-US.png)

![The Payment Reconciliation Journal after Check Application: the checked line keeps its application with Match Confidence Low, Applied Amount and Document No.](/assets/images/365-business-banking/bank-reconciliation/ausgleich-pruefen-ausgleich-bleibt-erhalten.en-US.png)

![Click video: select a line in the Payment Reconciliation Journal, choose Apply Automatically > Check Application and read the summary, the result and the rejected candidates with their reason in the Application Log](/assets/images/365-business-banking/videos/check-application.en-US.gif)

## Application log

| Area | Content |
|---|---|
| **Summary** | one sentence with the result automatic application would produce for the line, and a second sentence with the reason, such as *"Would be applied to … for …. We found a match for the … in the …."* or *"No application would be made. …"* |
| **Bank Transaction** | **Transaction Date**, **Transaction Amount**, **Payer or Payee**, **Payer or Payee Account**, **Transaction ID**, **Transaction Text**: the information the matching evaluates |
| **Result** | **Result**, **Would Apply To**, **Would Apply To Account Type**, **Would Apply To Account No.**, **Applications** (more than one for a collective payment, payment group or allocation across sales documents), **Would Apply Amount**, **Difference**, **Match Confidence**, **Candidates Considered**, **Candidates Rejected**, **Error** |
| **Candidates** | one row per candidate checked (see below), or a sentence stating why no candidates are listed |
| **Origin** | **Bank Account No.**, **Statement No.**, **Statement Line No.**, **Split from Line No.** (for split lines), **Explained At**, **Explained By**, **Took** |

### Result

| Value | Meaning |
|---|---|
| *Would Apply to One Entry* | The line would be assigned one candidate. |
| *Would Apply to Several Entries* | collective payment, payment group or allocation across sales documents |
| *Would Not Apply* | No candidate was sufficient for an automatic application. |
| *Skipped* | The line was not passed to the matching, for example because it is [pending](pending-entries.mdx). |
| *Could Not Be Explained* | An error occurred during the trial run. The **Error** field states it. |

### Candidates

| Column | Meaning |
|---|---|
| **Candidate** | the item that was evaluated: an open entry, a reconciliation rule, a mapping, or a collective payment made up of several entries |
| **Outcome** | *Would Apply*, *Rejected* or *Considered*. Rejected candidates are the normal case, not errors. |
| **Reason** | why the candidate would have been selected or not |
| **Amount**, **Difference** | open amount of the candidate and difference from the transaction amount |
| **Found By** | the part of the matching that found the candidate. If the result is not what you expected, review the related setup. |
| **Score**, **Match Confidence** | quality on the standard scale (the higher, the better) and the confidence band |
| **Related Party Matched** | *Fully*, *Partially*, *No* or *Not Considered* |

With **Personalize**, you can show further columns: **Document No. Matched**, **Amount Matched**, **Direct Debit Collection Matched**, **Account Type**, **Account No.**, **Document No.**, **Posting Date**, **Due Date**.

The following table maps the values of **Found By** to the setup to review:

| Found By | Setup |
|---|---|
| *Standard Matching*, *Amount and Date* | payment application rules, [date tolerance](date-tolerance.mdx), tolerance on the bank account; for G/L entries as candidates, also [G/L entry matching](gl-entry-matching.mdx) |
| *Related Party* | [Related party matching](related-party-matching.mdx) |
| *Document Reference* | [Document no. matching](document-no-matching.mdx), [payment application fields](payment-application-fields.mdx), [context words](../setup/context-words.mdx) |
| *Transaction ID*, *Purpose Reference* | [Direct matching](direct-matching.mdx) |
| *Reconciliation Rule* | [Reconciliation rules](../bank-reconciliation-rules.mdx) |
| *Payment Code Mapping* | [Payment code mapping](../payment-code-mapping.mdx) |
| *Text-to-Account Mapping* | text-to-account mapping (standard) |
| *Payment Group* | [Payment groups](../payment-groups.mdx) |
| *Sales Document* | [Application with open sales documents](../payment-application-open-orders.mdx) |
| *Remittance Advice* | [Application in payment reconciliation](../remittance-advice/payment-reconciliation.mdx) |
| *On-Account* | [Customer/vendor matching](on-account-matching.mdx) |

## Typical reasons

| Reason (excerpt) | Meaning |
|---|---|
| *"Open entry … has … remaining, and this transaction is for …."* | The amount does not fit, not even with tolerance. |
| *"The payer is named …, which is too far from … to treat the two as the same business partner."* | The name does not meet the 50 % rule: [Related party matching](related-party-matching.mdx). |
| *"The payment purpose contains …, which is the end of document number …. That is too little of the number to count as a reference to it."* | The partial number covers less than 70 %: [Document no. matching](document-no-matching.mdx). |
| *"The payment purpose contains …, the end of document number …, but no word such as invoice, RE or RG that would say a document number is meant."* | A short partial number without a context word: [Context words](../setup/context-words.mdx). |
| *"The payment purpose could refer to document …, but nothing in the transaction names the customer or vendor it belongs to."* | Weak match without a recognized payer. |
| *"Open entry … was posted on …, which is outside the period this transaction may be applied to."* | The entry is more recent than the payment: [Date tolerance](date-tolerance.mdx). |
| *"The account … the money came from belongs to more than one business partner."* | The IBAN is stored for several customers or vendors. |
| *"A matching open entry was found, so the payment was not put on account."* | On-account matching only applies if there is no other candidate. |
| *"Several candidates fit equally well, so none of them would be applied without being looked at."* | Several candidates have the same rating. Apply the line manually. |
| *"This line is reserved as a pending entry, so the automatic application leaves it alone."* | The line is pending: [Pending bank entries](pending-entries.mdx). |
| *"Reconciliation rule … could not set the field …, so it was left unchanged: …"* | A field from the **Additional Fields** of the reconciliation rule could not be applied to this line, for example because its value is no longer valid. The rule still applies; only this field is skipped. The reason is at the end of the message: [Reconciliation rules](../bank-reconciliation-rules.mdx). |

## Check Quick Apply

**Check Quick Apply** runs [Quick Apply](apply.mdx#quick-apply) for the selected line as a test. The same **Application Log** shows which candidates the Quick Apply functions found, which candidate would be applied and why the others were rejected. Nothing is applied and nothing is changed.

Among the candidates is a note on how Quick Apply works: *"Quick Apply only uses the transaction number, a document reference in the payment purpose, reconciliation rules, payment code and text mappings and on-account matching. Open entries are not weighed the way Apply Automatically weighs them."* If Quick Apply finds no match but **Check Application** does, the cause is this limited scope.

Lines that Quick Apply skips receive the result *Skipped* with one of the following reasons:

| Reason | Meaning |
|---|---|
| *"The application of this line was accepted or made by hand, so Quick Apply leaves it alone."* | The line has the match confidence *Accepted* or *Manual*. |
| *"This line has no amount, so Quick Apply leaves it alone."* | The **Transaction Amount** is 0. |
| *"This line is reserved as a pending entry, so Quick Apply leaves it alone."* | The line is [pending](pending-entries.mdx). |

![The Application Log of Check Quick Apply: "No application would be made.", result Would Not Apply, one candidate considered and rejected](/assets/images/365-business-banking/bank-reconciliation/ausgleichsprotokoll-schnellausgleich-pruefen.en-US.png)

## Limits

- **Exactly one line.** The log lists every candidate the line was evaluated against. For several lines, it would no longer be readable. With several lines selected, Business Central reports: *"Select one journal line. The application is checked for a single line at a time, …"*
- **No saving.** The log is only available while the page is open. If you need it later, for example for support, export it with **Open in Excel**.
- **Snapshot.** If you change a reconciliation rule or an open entry afterwards, the explanation is no longer current. **Explained At** shows when the explanation was created.
- **Shortened with many candidates.** If direct matching narrows the candidates to one entry, the log lists at most 20 of the displaced entries.

## See also

- [How automatic application works](../concepts/how-matching-works.mdx)
- [Apply bank transactions](apply.mdx)
- [Payment application settings](../setup/payment-application-settings.mdx)
- [Extended reconciliation log (feature)](../features/details/extended-reconciliation-log.md)