Finance | Project Operations, Human Resources, ...

exclude disputed transactions from customer account statement?

(0) Share

Report

Posted on by David Penna

140

Hi, does anyone know a way to exclude disputed transactions from appearing on the customer account statement?

I have the same question (0)

All responses (11)

Answers (0)

Junaid Idrees on at

Like (0)

Report

Hi D Papa,

Can you please share some details, How exactly you are marking "Disputed transactions" in the system? Do you use any reason code or specific tagging?

For example: Chargeback are usually disputed transactions so When a dispute is made, the merchant has to reverse the transaction and the customer receive the money back or it could be related to defective goods or credit card CVV code issue.

Was this reply helpful? Yes No
David Penna 140 on at

Like (0)

Report

Hi, sorry for not providing more info. I am referring to customer voucher transactions that appear in Accounts Receivable > Transactions or Credit and Collections > Collections lists (invoices, credit notes, interest notes, etc). They are automatically assigned a default Collections Status of Not Disputed, but can be set to Disputed or other available values. In our current system, we are able to dispute transactions which excludes them from a customer's aging balance and disables them from being shown on their account statement.

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hi D Papa,

The transactions that you classify as disputed in the collections/aged balances workspace can be excluded by default from collection letters but not from the account statement of your customer.

You would have to check where the collection status field is tracked and then try to define a filter in the report.

Best regards,

Ludwig

Was this reply helpful? Yes No
David Penna 140 on at

Like (0)

Report

[quote user="Ludwig Reinhard"]
Hi D Papa,

The transactions that you classify as disputed in the collections/aged balances workspace can be excluded by default from collection letters but not from the account statement of your customer.

You would have to check where the collection status field is tracked and then try to define a filter in the report.

Best regards,

Ludwig
[/quote]
Hi Ludwig,

The Status / Collections Status field comes from the Customer Transactions table.

In the Customer Account Statement form, the preset Parameter selections seem to be the only way to choose Transaction options:

There is also a Filter but it only draws from the Customers table and the option to add a Table Join is disabled:

Was this reply helpful? Yes No
Suggested answer

Junaid Idrees on at

Like (0)

Report

Hi D Papa,

Select Cutomer and you will be able to add the join.

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hi D Papa,

As Junaid mentioned, you can add joins.

The thing is that you have to find the correct table and join to filter your records as you want.

This might take a while and require some trial & error testing until you get this right.

Best regards,

Ludwig

Was this reply helpful? Yes No
David Penna 140 on at

Like (0)

Report

Thanks Junaid, I did that and went to Add Table Join. Here are the details for the field I want to access:

In the Add Table Join list, I'm not sure how to bring in the table that contains the Collections Status field, as you can't sort / filter by Table Name, but you can sort / filter by Relation, Table relation description, Relation source & Relation. Should I just be looking to add a Join of the Customer Transactions (CustTrans) table itself, and THEN the particular field I want to access will be available in the Range tab of the Filter?

Was this reply helpful? Yes No
Suggested answer

Junaid Idrees on at

Like (0)

Report

I have already checked "Collection Status" and other "Status" data fields yesterday and unfortunately couldn't find in Customer transactions/Open customer transaction/Collection Journal tables.

As ludwig mentioned, you need to spend some time to find the correct table and make join or might need developer help.

Was this reply helpful? Yes No
David Penna 140 on at

Like (0)

Report

Thanks Junaid & Ludwig. So I was able to find what I believe to be the correct Table (since the available Criteria values match those in the Collections' form) and add it as a Join:

The default Collections Status for ALL transactions is 'Not Disputed' so with the Filter set as above, I assumed it would create a statement with no transactions excluded. Unfortunately NO statement was created at all. I know the statement is working correctly without that criteria because I was able to create one before I added it. Any ideas as to why this isn't working?

Was this reply helpful? Yes No
Suggested answer

Junaid Idrees on at

Like (0)

Report

Hi D Papa,

Glad to know that one part of your issue is resolved but unfortunately not 100 %. I am just thinking loudly since collection history table maintain information about collection letters and customer account statement fetching information from a dataset that might not have "collection history" table part of it (Even after including Join) and that's why system is not showing any result when you include any field from that table.

Was this reply helpful? Yes No