Security change on December 1, 2026: TLS 1.2 will become the minimum standard for 365 business Print Agent. Details and system requirements
365 business development
Incoming Payments and Bank Reconciliation

Payment code mapping (obsolete)

The obsolete payment code mapping in 365 business Banking assigns transactions to accounts by ZKA code and SEPA purpose code. Use reconciliation rules instead.

Obsolete

Payment code mapping has been deprecated since version 18.1 and will be removed in a later version of 365 business Banking. It remains functional until then. Reconciliation rules cover its entire functionality and additionally provide posting text, dimensions and further criteria. Therefore, create new mappings only as reconciliation rules.

With a SEPA payment, the bank transmits codes besides the payment reference that describe the kind of transaction:

  • ZKA Code: The business transaction code of the German banks, see ZKA codes.
  • SEPA Purpose Code: The purpose of a SEPA payment, for example SALA for salary, see SEPA purpose codes.

How the mapping works

On the Payment Code Mappings page, you define in each line which account belongs to which codes:

FieldMeaning
ZKA Code, ZKA Code DescriptionBusiness transaction code and its description
SEPA Purpose Code, SEPA Purpose Code DescriptionSEPA purpose code and its description
DescriptionYour description of the mapping
To Account Type, To Account No.The account the line is applied to. Mappings without a To Account No. are ignored.

Payment Code Mappings page with two lines for ZKA codes 402 and 403, To Account Type G/L Account and To Account No. 6885

During Apply Automatically, 365 business Banking looks for a mapping for every line that has bank transaction details, in this order:

  1. ZKA code and SEPA purpose code both match.
  2. Only the ZKA code matches (for a mapping without a SEPA purpose code).
  3. Only the SEPA purpose code matches (for a mapping without a ZKA code).

The first stage that finds a mapping applies. If several lines match on one stage, the first one is used. The mapping found is rated like a text-to-account mapping and therefore competes with open entries and reconciliation rules. If it applies a line, the match confidence is High - Payment Code-to-Account Mapping.

Like reconciliation rules, payment code mapping is part of the licensed feature set: without a valid license, it is not applied during application. In automatic application, it runs directly after the reconciliation rules, see How automatic application works.

Switch to reconciliation rules

  1. Open a Payment Reconciliation Journal with a line that is applied through a payment code mapping, and choose Reconciliation Rules. The new rule is prefilled with, among other things, the line's mapping text, ZKA code, SEPA purpose code, counterparty IBAN and bank account.
  2. Clear Mapping Text and Counterparty IBAN so that the rule, like the payment code mapping, applies by the codes alone. Clear Bank Account No. if the rule is to apply to all bank accounts. Enter the Bal. Account Type and Bal. Account No. of the payment code mapping.
  3. If the rule should apply for all SEPA purpose codes, clear SEPA Purpose Code. This corresponds to stage 2 above. For stage 3, clear the ZKA Code accordingly.
  4. Delete the line on the Payment Code Mappings page as soon as the rule applies. Otherwise, both mappings compete with each other.

For how reconciliation rules are checked and rated, see Reconciliation rules.

See also

Last modified on