Customer statement payment references FAQ

Why can't I see the Payment Reference Template field on the Standard Statement request page?

Make sure that:

• Customer Statement Payment Reference is enabled in Continia Feature Management.
• Cust. Stmt. Reference Matching is enabled in Banking Import Setup.

After enabling the settings, reopen the Standard Statement report.

Why isn't a payment matched even though the customer used the payment reference?

Make sure that:

• Cust. Stmt. Reference Matching is enabled.
• The relevant Payment Reference Rule is active.
• The rule extracts the correct value from the transaction text.
• The imported reference matches the stored reference.
• The statement has not been reprinted, which generates a new reference.

Use the Test action on the Payment Reference Rule to verify the extracted value.

Why is the wrong customer ledger entry proposed?

This can happen if the payment reference is not unique or if the matching rule is configured incorrectly.

Review the reference in Customer Statement References and verify that the associated Payment Reference Template generates unique values.

Why does the matched reference not produce the expected result?

If you're using a Transformation Rule, it may be modifying the extracted reference before matching.

Use the Test action on the Payment Reference Rule to review the transformed value and adjust or remove the transformation rule if necessary.

Why did customer statement references disappear after I reprinted a statement?

This is expected behavior. When a statement is reprinted for the same customer and statement number, existing references are replaced with newly generated references.

Why was a payment reference found, but no application proposal was created?

Application proposals are created only for open customer ledger entries.

If an entry has already been applied or closed, it is ignored even if its payment reference is found during matching.