Payment application proposals FAQ

  • 20/01/2026
  • 7 minutes to read

If you are having trouble working with payment application proposals, this FAQ addresses common issues and provides solutions.

Why are no payment application proposals shown?

Symptoms

  • The Proposals field shows zero.
  • Status is Unsolved or Related Party Matched.
  • The Payment Application Review page does not display any proposals.

Possible causes

  • The automatic matching engine did not find matching ledger entries.
  • Matching settings are not enabled in Banking Import Setup.
  • The expected ledger entry is closed or already applied.
  • The matching criteria do not correspond to any open ledger entry.

Solution

Verify that matching is configured correctly:

  1. Open Banking Import Setup.
  2. Expand the Matching FastTab.
  3. Confirm that the matching options for the entry types you need are enabled:
    • Cust. Ledger Entries Matching
    • Vendor Ledger Entries Matching
    • Bank Ledger Entries Matching
    • Empl. Ledger Entries Matching
  4. If needed, enable additional strategies:
    • Search Rule Matching
    • Related Party Rule Matching
    • Bank Trans. Code Rule Matching
  5. Return to the bank reconciliation and invoke matching again.

If matching is configured correctly, check that the ledger entry exists and is open:

  1. Open the corresponding ledger entries page.
  2. Search for the expected entry.
  3. Confirm that Open is Yes.

If the entry is in a different currency than the bank account, ensure that application between currencies is allowed in Sales & Receivables Setup or Purchases & Payables Setup.

If matching still fails, apply the entry manually:

  1. Open Payment Application Review.
  2. Choose Show Ledger Entries.
  3. Locate the correct entry.
  4. Select it and choose Apply Ledger Entry.

If no suitable entry exists, complete reconciliation manually or create the required entry.

Note

If proposals are consistently missing for the same transaction pattern, consider creating a search rule or payment reference rule.

Why is the difference not zero after applying a proposal?

Symptoms

A proposal was applied successfully and the Difference field shows a nonzero amount but the Status is set to Difference.

Possible causes

  • The payment is partial.
  • A rounding difference occurred.
  • Bank charges are included in the transaction.
  • A payment discount was not applied.
  • A payment tolerance was not applied.
  • The wrong proposal was selected.

Solution

If the payment is partial, the difference is expected. Adjust the Applied Amount to match the payment amount. The ledger entry remains open with a reduced Remaining Amount.

If the difference is very small, review the Rounding field. Minor multi‑currency rounding differences are expected and posted to the rounding account.

If the difference is caused by bank charges:

  1. Review charge details in the Reconciliation Line Charges FactBox.
  2. Handle charges separately by creating a charge line or posting them to a bank charges expense account.

If the difference equals a potential payment discount:

  1. Review the Pmt. Discount Date.
  2. Verify whether the payment is within the discount period.
  3. If necessary, select Accepted Pmt. Disc. Tolerance.
  4. Review the Applied Pmt. Discount amount.

If the difference is within tolerance limits:

  1. Confirm the Max. Payment Tolerance value.
  2. Ensure payment tolerance is enabled in General Ledger Setup.
  3. Apply the proposal.

If none of these causes applies, unapply the proposal and review alternative proposals.

Why can I not apply a proposal? (Already Applied error)

Symptoms

  • Applying a proposal produces the error The Payment Application Proposal is already applied in another context.
  • The Already Applied field shows Yes.
  • The proposal row may be highlighted in blue.

Possible cause

The referenced ledger entry is already applied in another journal, reconciliation, or payment suggestion.

Solution

Determine where the entry is already applied:

  1. When you open Payment Application Review, a notification appears.
  2. Use the notification action to open the location where the entry is applied.
  3. Review whether the existing application is correct.

If the existing application is incorrect:

  1. Open the journal, reconciliation, or payment suggestion where it is applied.
  2. Unapply the entry or delete the application.
  3. Return to the current statement line and refresh Payment Application Review.
  4. The Already Applied field should now show No.
  5. Apply the proposal.

If the existing application is correct, do not apply it again. Review whether the statement line needs a different entry or manual reconciliation.

Why is the applied amount shown in a different currency?

Symptoms

  • The Applied Amount displays an unexpected currency.
  • Currency codes differ between the proposal and the bank account.

Possible cause

This is expected multi‑currency behavior. The proposal shows the ledger entry currency, while the bank account has its own currency.

Solution

Understand how the system handles multi‑currency application:

  • The Currency Code field shows the entry's currency.
  • The Appln. Currency field shows the bank account currency.
  • Applied Amount is expressed in the entry currency.
  • Appln. Applied Amount is expressed in the bank account currency.

If needed, verify exchange rates in Currency Exchange Rates, especially if the values do not match the expected calculation.

If application between currencies is disallowed, update the Appln. between Currencies field in Sales & Receivables Setup or Purchases & Payables Setup.

Rounding differences appear in Rounding and are posted to the rounding account.

If all values are correct, apply the proposal normally.

Note

The system manages all conversions and rounding automatically.

Introducing payment application proposals
Reviewing payment application proposals
The Payment Application Proposal page
Applying payment proposals