Overview

The disputes feature enables a service provider to record the details of a dispute against an invoice and to manage that dispute through to it's natural conclusion. A dispute can be raised against specific cardlines on the invoice, or a 'general' dispute can be raised where the disputed amount is not related to a specific charge but still tracked against the invoice.

What's in this section?


Licensing

This feature is available to subscribers of the following:  Tick the option(s) that apply. If this is available to all users, meaning "Emersion Core", other options should not be ticked. 

  • Emersion Core
  • Optional Modules
  • Upon Request (please contact your Account Manager)

Acceptance Test

Conduct an acceptance test for this feature.link to the acceptance test page for this module. 

What is this?


Features and How To's

This section contains articles on the functionality of this feature. Most features under a module may only have one or two how-to guides. If so link them from the core section below.  Other features have core features and additional add-ons that extend the features capabilities. Remove the Add On section if it does not apply. 

This section is for other articles related to this feature that don't really fit neatly into the Core or Optional features. What is in here may vary from feature to feature.


Prerequisites

Prerequisites section is to inform readers about what knowledge they should have before using this module. 

* Should the audience be educated in a module or other feature(s) before tacking this one? 

* Should they have completed certain training or be competent in a given area of the system?  

* Should they have a solid understanding of some key Emersion objects and concepts, like service types, or package plans?

If so, list them below and remove the line about "no prerequisites needed"

If not, remove the intro line and bullet point. 

Before attempting to use this feature, users should:

  • Provide Emersion with a list of reasons for a dispute. If you have not supplied Emersion with the list of reasons for a dispute, the only option available to users when they create or update a dispute will be Default. Contact our customer service team with your list of reasons and we will configure the system for you. While you are not limited in the number of reasons you can provide, the reasons themselves should be kept to under 50 characters so they look presentable on the screen.

Dependencies

Some modules and features have dependencies. For example, Commissions is dependent on having the Agents module. Processing an payment via credit card is dependent on having a subscription to the Emersion Payments module AND having a payment gateway configured and enabled. These are the things that need to be captured here.  If there are no dependencies, remove the example and leave the last line about having no dependencies. 

There is no dependencies for this feature. It is a standalone feature in Emersion Core.


Access Control

If you are unable to access a given feature and you have checked the permissions and powers, please contact Emersion.


Module Permissions

Module Permissions are not in the most ideal state, as we know. You may need to draw the user's attention to when it related to module permissions and powers. Use a RED WARNING in these cases.

List the module permission(s) needed to enable the base module. Powers related to its features, particularly the optional features, should not be included here as they are documented on their own feature pages. Once that's complete, delete the sentence immediately below the table. If there are no module permissions, delete the table and leave the sentence.

There are no module permissions related to the module.

Powers

Powers are used to control access to features, functions and page sections. These powers are situated under the Invoicing parent power.

If there are no powers, delete the table and leave the sentence below it.

PowerDescription
Disputes AdministratorThe parent power for disputes raised against invoices. Grants full access to all disputes functionality.
Finalise DisputeGrants the user the ability to finalise invoice disputes.
Finalise Dispute - Leave invoice pendingRequires the user to have Finalise Dispute power. This power grants the user the ability to choose to create a pending invoice when the dispute is finalised.
Finalise Dispute - Next invoice methodRequires the user to have Finalise Dispute power. This power grants the ability to finalise choose to place the credit cardlines on the next invoice. The cardlines will remain pending and unallocated to an invoice.
Update Disputed Amount on Raised DisputeGrants the user access to modify the disputed amounts in a dispute.
Update a Raised DisputeGrants the ability to edit a dispute, update the amount to be credited, the cardline and general statuses, and the dispute setting fields.
Raise a General DisputeRaise a general dispute that is not specifically attributed to a cardline.
Raise Cardline DisputeGrants access to raise a dispute against cardlines on an invoice.
View Dispute and Dispute HistoryGrants access to view disputes (read-only)
Withdraw a DisputeGrants the user access to withdraw a dispute.





Feature Events

If this feature includes specific events, list the event type names and IDs here. If the module includes nothing specific, remove the example, leaving the last line in tact.

There are no events related to the feature.

Feature Reports

If the feature includes specific reports, list the report names and IDs here. If the feature includes nothing specific, remove the example, leaving the last line in tact.

The following reports are included in the feature.

  • Disputes Summary Report (id: 1132)
  • Disputes Report (id: 1133)



Related Articles

Click the macro and choose edit.  Add additional labels and save.  To ensure consistency with all other EKB pages, DO NOT change any other settings in the macro. Simply add more labels and save. This will populate a list of related articles based on the labels (tags) it is given.