Migrating rules from Payment Management

• 14/10/2025
• 8 minutter at læse

You can rely on Continia Banking to handle most reconciliation tasks automatically, so you often don’t need to recreate rules from Payment Management (PM). For example, you don’t need search rules for accounts with unusual characters or formatting (for example, Lauritzen Kontormøbler A/S).

Use the table below to determine which rules require manual migration:

Search rules

If you used reconciliation rules in Payment Management (Customer, Vendor, Employee, or Bank Account), create corresponding Search Rules in Banking.

Action:

1. Search () for and select Search Rules.
2. On the action bar, click New.
3. Assign a Code and add a Description.
4. Select a Search Field Template.
   • DESCTRANSACTEXT - searches the description of the bank statement line (called Search In Description in Payment Management).
   • DETAILTEXT - searches the statement line details related to the bank statement line (called Notification in Payment Management).
   • DESCTRANSACDETAILS - searches both the description and the details (equivalent to enabling both settings in Payment Management).
5. Adjust filters as needed.

For detailed instruction about creating rules in Continia Banking, see Setting up search rules in Continia Banking.

Direct debit return rules

To migrate Reversal Rules from Payment Management, create Direct Debit Return Rules in Continia Banking.

Action:

• Follow the instructions of this article: Adding a direct debit return rule. Keep in mind that:
  • For all customers – leave Customer No. blank.
  • For specific customers – create one rule per customer.
  • For single return reasons – select the code in Return Reason Code.
  • For multiple reasons – use Add additional Return Reasons.

Payment reference rules

If you used payment reference search rules in Payment Management (PM), you need to create payment reference rules in Continia Banking. These rules define how payment references are matched during reconciliation.

For more information, see Setting up a payment reference rule

Action:

Create a payment reference rule

1. Search () for and select Payment Reference Rules.
2. On the action bar, click New.
3. Assign a Code and optionally add a Description.
4. Select the Payment Reference Search Field Template:
   • DESCTRANSACTEXT – searches in the description (matches PM’s Description).
   • DETAILTEXT – searches in notification text (matches PM’s Notification).
5. Set the Validation Code Pattern to define the reference format (use default patterns or a custom regex).
6. Enable Direct Match if the original Search Principle in PM was Exact.
7. Specify Reference Start Position and Reference Length if needed.
8. Select the Table (Bank Account Ledger Entry) and Field (CTS-CB End To End Id or CTS-CB Payment Information Id).
9. Test the rule with a sample reference to verify correct matching.

Use default rules as templates

Where possible, copy existing default Payment Reference Rules using the Copy Payment Reference Rule action to reduce setup effort.

Configure bank-specific references

If different bank accounts use different Payment ID Masks:

1. Create a rule for each bank account.
2. Add the bank account to the Bank Account No. field in the Rule Filter FastTab.

Handle document type in references

To handle document type references:

1. Enable Match Document Type in the Payment Reference Rule.
2. Specify Document Type Start Position and Length in the reference.
3. Use Related Document Types to map indicators to document types.
4. Test with a sample reference to verify correct setup.

Handle check digit in references

1. Enable Check Digit in the rule.
2. Configure:
   • Check Digit Calculation Start Position
   • Check Digit Calculation Length
   • Check Digit Position
   • Check Digit Algorithm
3. Complete remaining fields as guided on the page.
4. Test with a sample reference to ensure validation works.

Migrate payment identification search rules

Recreate Payment Identification Search Rules from PM as Payment Reference Rules:

1. Create a new rule with Code/Description.
2. Select the appropriate Search Field Template.
3. Define Validation Code Pattern for prefixes or formats.
4. Set Table/Field mapping (Bank Account Ledger Entry → CTS-CB End To End Id or CTS-CB Payment Information Id).
5. Enable Direct Match if required.
6. Set Bank Account No. in the filter if applicable.
7. Test with a sample reference to verify setup.

Split rules

Split Rules are new in Banking and allow you to automatically split charges or foreign payment fees into multiple lines during import. For more information, see Introducing split rules.

Multiple bank statements

If you imported multiple statements per reconciliation in Payment Management, enable the Multiple Bank Statements setting in Continia Banking.

Action:

1. Open the Bank Account Card.
2. Go to the Reconciliation Import Setup section and enable Multiple Bank Statements.

For more information, see Importing multiple bank statements in Continia Banking.

Job queue imports

If you used job queues in Payment Management, enable them on the Reconciliation Import Setup page in Continia Banking. Continia Banking will configure the necessary job queues automatically.

If you import both CAMT.053 and CAMT.054, create separate setups for each transaction type.

Action:

1. Search () for and select Reconciliation Import Setup.
2. Select the Job Queue Import Action.

Additional considerations

While Continia Banking includes many improvements over Payment Management, a few familiar features are not (yet) available. These capabilities are planned for future updates or have alternative approaches in Banking:

• Manual merge of bank statement lines.
• Automatic merge of bank statement lines using merge rules.
• Tolerance days for matching by posting date and amount (coming in the next service pack).
• Payment reference on customer statement reports.
• Printing of payment reference on sales documents
• Search rules with account type Bank Account (Bank Account Reconciliation Rules are not yet supported).