Payment reference rules FAQ
If you are having trouble working with payment reference rules, this FAQ addresses common issues and provides solutions.
Why can't the payment reference rule find the ledger entries?
Symptoms
The payment reference rule does not match any ledger entries, even though the reference appears to be correct.
Possible causes
Check the ledger entry:
- Is it open?
- Is the posting date after your bank statement date? (entries with future posting dates are excluded)
- Does the currency code align with the setup? The Appln. between Currencies setting in the Sales & Receivables Setup and/or Purchases & Payables Setup may restrict which entries are considered.
Solution
- Make sure Payment Reference Rule Matching is enabled on the Banking Import Setup page.
- Verify that the setting for the relevant ledger entry type (Customer, Vendor, Bank Account, Employee, or G/L Entry) is enabled on the Banking Import Setup page.
- Confirm that the payment reference rule itself is enabled.
- Check that the validation pattern matches the reference.
- Ensure any filters on the rule align with the bank account and bank transaction code on the statement lines.
- Verify that all mandatory fields (marked with red asterisks) are filled in.
- Make sure the rule setup is complete (no notification appears on the page).
Use a sample reference and verify it against the rule on the Test FastTab.
Why doesn't my payment reference rule match invoices based on the external document number?
Symptoms
- The rule runs without errors but the entries remain Unresolved after Automatic Matching.
- You see an “Invalid search rule” error after modifying the setup.
- The system doesn’t match even though the External Document Number exists on the invoice.
- Manually filtering by External Document No. finds the correct invoice, but automatic matching does not.
Solution
To resolve this:
- Go to “Validation Code…” and create a new validation using this regex:
^71\/(?!0{18})\d{18}\d$
- Delete any invalid search rules.
- Remove the Sub-family code in the payment reference rule.
- Run Automatic Matching again — it should now correctly find and match the entry based on the External Document Number.
For more information, see Regular expression structure for matching payment references
Why aren't KID numbers matching automatically?
Symptoms
KID numbers on bank statements are not matched to invoices.
Possible causes
- The reference format does not match the system setup.
- Leading zeros or incorrect start position or lenght.
Solution
To solve this:
- Verify that the KID validation pattern follows the recommended format.
- Copy the existing rule instead of modifying it directly. Update the copy with the correct settings.
- Set the reference start position and length:
- For a 10-digit KID number with leading zeros (e.g., 0007432198):
- Start position: 4
- Length: 7
- For a 10-digit KID number with leading zeros (e.g., 0007432198):
- Test the rule by running Automatic Matching.
For more information, see Regular expression structure for matching payment references
Does Continia Banking support payment references across localizations?
Yes. Continia Banking supports payment reference matching across Scandinavian localizations, even if your tenant is set up for a different country. For example, Norwegian KID numbers can be processed in a Danish tenant. If a specific field (such as KID) isn't available in the current localization, Continia Banking uses fallback fields like Payment Reference or Creditor Number. For complex setups, contact your Continia partner or support representative.
Why isn't my default payment reference rule working?
Symptoms
A default rule exists but doesn’t match payment references.
Possible causes
- The rule is disabled.
- Filters (Bank Code, Bank Account No., Statement Type) don’t match your setup.
- The reference format doesn’t match the rule’s validation pattern.
Solution
- Make sure the rule is enabled.
- Verify all filters.
- Use the Test action to confirm the reference matches the rule.
- If needed, copy the default rule and adjust the settings in the custom version. See Default payment reference rules for instructions on how to do this.
Why is my custom rule incomplete?
Symptoms
The rule throws an error or shows incomplete configuration.
Possible causes
- Mandatory fields are not filled (indicated by red asterisks).
- Configuration is incomplete (notification appears).
- Match Document Type is enabled but mappings aren't linked.
- Payment Reference Rule Matching isn't enabled in Banking Import Setup.
Solution
- Fill in all mandatory fields.
- Follow notifications at the top of the page.
- Ensure the following are configured:
- Pmt. Reference Field Template
- Validation Pattern Code
- Match to Table
- Match to Field
- If Check Digit is enabled:
- Algorithm
- Position
- Calc. Start Pos.
- Calc. Length
- If Direct Match is disabled:
- Reference Start Position
- Reference Length
- If Match Document Type is enabled:
- Document Type Start Position and Length
- Link mappings via Related Document Types
- Enable Payment Reference Rule Matching in Banking Import Setup.
Why does my rule not match any transactions?
Possible causes
- Filters are too restrictive.
- Validation pattern does not match the reference.
- Extraction settings are incorrect.
- The rule is disabled.
Solution
- Review and adjust filters.
- Test your rule with sample references.
- Check extraction settings and validation pattern.
- Ensure the rule is enabled.
Why does my rule not recognize the document type?
Possible causes
- Document type indicator is not mapped.
- Mapping exists but is not linked via Related Document Types.
- Extraction settings are incorrect.
Solution
- Create document type mappings in Document Type Mappings.
- Link mappings to the rule using Related Document Types.
- Verify start position and length for document type extraction.
- Test to confirm correct indicator extraction.
Why can't I edit or delete a rule?
Possible causes
- The rule is a system-provided default rule.
Solution
- Use the Copy action to create a custom rule.
- Disable the default rule if it should not be used.