Skip to content
English
  • There are no suggestions because the search field is empty.

Exceptions Page

This page displays errors when they exist for the cycle.

This page displays errors when they exist for the cycle. The cycle cannot be closed when there are errors and will need to be corrected and the cycle ran again. The Policies mentioned in errors will not be reflected in the Results or Summary of the Cycle. If one Agent in the hierarchy of a Policy has an error, it will prevent commissions for all the Agents in the Policy. If there are no errors the Exception tab will be grayed out. The list of errors in the exception page can be exported.

Exception page in an open cycle

Exception Examples:

Paid thru date does not match payment month for policy Test123.

This exception occurs for Policies that allow advances when the PTD on the transaction does not equal one month from the Effective Date of the Policy. So, if the Effective Date of the Policy is 1/1/2024, if the Effective date does not equal 2/1/2024 it will generate this error. Correcting the effective date of the Policy and re-running the cycle will correct the issue.

Policy Test123, Agent (EE1204 Elvis Esterine) does not have plan rates

This exception can happen for a variety of reasons for why the system cannot find matching commission rates. Look for these factors:

  • Contract (or Alternate Contract in settings) for the Agent has Commission Rates for the Product in the Policy.
  • Commission Rates cover the Effective or Submitted Date of the Policy
  • Commission Rates cover the month of the Policy

To fix the issue, update the Contract or Commission Rate and re-run the cycle.

Warning: Policy Test123 for issuer Ambetter has a negative transaction for month 1

This Warnings is displayed when there is a negative month one Transaction processed in the first cycle, but not if it is canceled out by a matching positive amount month one Transaction. So, if there is only one month-one Transaction for -$100 you would see a warning. If there were two Transactions, one for -$100 and one for $100, then there would not be a warning. The warning is to alert the admin in case they feel they need to follow up to find out where a missing positive Transaction is to go with a negative Transaction. The negative month one warning does not occur on Policies with Pay Code As Earned or Converted. It can also be an indication for a Policy transferred from a previous system that the Pay Code in the Policy should be As Earned or Converted.