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.

To verify the extracted value, enter sample text in the Test section of the Payment Reference Rule page.

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.

To review the transformed value, enter sample text in the Test section of the Payment Reference Rule page. Adjust or remove the transformation rule if necessary.

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

When a statement is reprinted for the same period, the stored reference and statement number are kept, and only missing entries are added. Existing references aren't replaced with new 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.