import { Callout } from "zudoku/ui/Callout";

# Payment application fields

This page describes the fields in which 365 business Banking searches for document numbers and references, and how to add your own fields for application.

Not every payer states your invoice number. Some payers state their own order number, which is stored as the **External Document No.** on the entry, others their customer number or a shop reference. With the **Payment Application Fields**, you define which fields 365 business Banking searches for in the payment reference during application.

## What payment application fields are

The **Payment Application Fields** part is on the **Payment Application Settings** page. Each line specifies a field of a table:

| Field | Meaning |
|---|---|
| **Source Table** | *Customer Ledger Entry*, *Vendor Ledger Entry*, *Customer*, *Vendor* or *G/L Entry* |
| **Field No.** | the field of this table; the lookup only shows fields that qualify |
| **Field Name** | filled from the field number |
| **Priority** | order in which the fields of a source table are checked, starting with the lowest number |

**Priority** applies to every matching method that uses these fields, such as document no. matching, related party matching and direct matching. Fields with the same priority are checked in the order of their **Field No.**

## What the fields are used for

| Source table | Used for |
|---|---|
| *Customer Ledger Entry*, *Vendor Ledger Entry* | [Document no. matching](document-no-matching.mdx): The value of the field on the open entry is searched in the payment reference, the transaction ID, the sender customer reference and the end-to-end reference. The *Customer Ledger Entry* fields also make up the index of [direct matching](direct-matching.mdx) and determine the token lengths. |
| *Customer*, *Vendor* | [Related party matching](related-party-matching.mdx): If the value (such as the customer number) is in the payment reference, the payer counts as recognized. Also used for [customer/vendor matching](on-account-matching.mdx) and for the payer of [open sales documents](../payment-application-open-orders.mdx). |
| *G/L Entry* | [G/L entry matching](gl-entry-matching.mdx) |

## Without setup

**After installation**, *Customer Ledger Entry* and *Vendor Ledger Entry* each have three lines: **Document No.**, **External Document No.** and **Payment Reference**, all with **Priority** 1.

If you delete all lines of a source table, the following defaults apply:

| Source table | Without a line |
|---|---|
| *Customer Ledger Entry*, *Vendor Ledger Entry*, *G/L Entry* | **Document No.** and **External Document No.**, not the payment reference |
| *Customer Ledger Entry* for transaction ID direct matching | only **External Document No.** |
| *Customer*, *Vendor* | no search |

The three lines for *Customer Ledger Entry* and *Vendor Ledger Entry* are created only once. A reinstallation or an update does not create lines that you deleted again. Only if no line at all is left, neither for *Customer Ledger Entry* nor for *Vendor Ledger Entry*, does a reinstallation or an update create the standard lines again. Existing lines and changed priorities remain unchanged.

## Set up

1. Choose the **Search** icon, enter **Payment Application Settings** and open the page.
2. In the **Payment Application Fields** part, choose **New Line**.
3. Choose the **Source Table**.
4. In the **Field No.** field, choose the field from the list. **Field Name** is filled in.
5. Enter a **Priority** if needed.

The change applies from the next application run.

![Payment Application Fields with lines for Customer Ledger Entry, Vendor Ledger Entry and Customer (fields No. and GLN)](/assets/images/365-business-banking/pmt-appl-settings-related-party-fields.en-US.png)

### Which fields qualify

Only **text and code fields** that hold a value of their own (field class *Normal*) qualify. The lookup only shows such fields. Any other field is rejected:

> *"The field … cannot be used to identify a payment. Only text and code fields that hold a value of their own qualify; this one is of type … and class …."*

All values are compared like a document number. A date or a number would first be converted to text in your language and number format and would then match by coincidence or not at all. A calculated field (FlowField) would have to be recalculated for every candidate. In addition, a payer cannot state any of these values on a transfer.

Fields from extensions of other publishers are allowed. If such an extension is uninstalled, application skips the line without stopping.

<Callout type="info" title="Min. Length and Max. Length">
The **Min. Length** and **Max. Length** columns are not evaluated and are hidden. 365 business Banking determines the lengths of references from your data: [Direct matching](direct-matching.mdx).
</Callout>

## Examples

| Occasion | Line |
|---|---|
| Payers state their customer number | source table *Customer*, field **No.** |
| Key accounts pay with their GLN | source table *Customer*, field **GLN** |
| The order number of the customer is stored as External Document No. on the entry | source table *Customer Ledger Entry*, field **External Document No.** (already present after installation) |
| Open G/L entries on a clearing account contain the reference in the Document No. | source table *G/L Entry*, field **Document No.** |

## See also

- [Document no. matching](document-no-matching.mdx)
- [Related party matching](related-party-matching.mdx)
- [Payment application settings](../setup/payment-application-settings.mdx)
- [Direct matching for payment service providers](direct-matching.mdx)