Overview
Commission map translations take the coverage type or revenue type values in a carrier statement and change them into the corresponding values in AMS+. This allows you to account for any differences between the statement and AMS+. Please note, you only need to add translations if you’re having issues matching commissions to policy records by coverage type or coding revenue types (overrides, etc.) from the carrier.
To add translations, you must belong to a security group with “Visible (Full Commission Processing)” and “Edit (Full Commission Editing)” Commission permissions.
IN THIS ARTICLE
Adding translations
For coverage type
Imported commissions are matched to policy records in AMS+ by policy number or commission number. If the policy/commission numbers on the carrier statement are not unique enough, you can set up AMS+ to look at the coverage type too so it knows which policy gets the money. Learn more about matching criteria in this article.
When matching on coverage type, the coverage type values in the statement must have exact matches in AMS+. Any differences in spelling, capitalization, or even spacing can cause mismatches and red edits to occur. That’s when you add translations.
To add a translation:
- Go to the Commission page and select Settings.
- In the Commission Settings, go to Import Maps > Translations and select “Add New”.
- Choose the carrier of the import file.
- Choose the “Coverage Type” import file criteria.
- Enter the coverage type as it appears in the import file.
- To prevent typos or errors, copy and paste the coverage type values from the commission statement directly into the map translation.
- Select the matching, active coverage type in AMS+.
- Save.
- Repeat these steps for every coverage type in the import file.
For revenue type
If your agency receives commission overrides from carriers, you may be using revenue types to help you track payouts for the overrides. Sometimes the carrier statements have different codes for overrides than what you have set up in AMS+. When this happens, imported commissions aren’t coded correctly, which can skew reports and payment history. That’s when you add translations.
If your agency pays out the same, no matter what, you may not need revenue type. Learn more about revenue types in this article.
To add a translation:
- Go to Commission > Import Maps > Translations and select “Add New”.
- Set the translation type to “Revenue Type”.
- Choose the carrier of the import file and select the revenue type that appears in the import file.
- Please note, if you’re not seeing a particular revenue type in the dropdown list, you may have to add it in Profile & Settings > Settings > Data & Custom Fields > Revenue Type.
- Select the corresponding, active revenue type in AMS+.
- Save.
- Repeat these steps for every coverage type in the import file.
Best practices
Purge and re-import statement
If you import a carrier statement and you find out that you need to add translations, purge the statement. After adding translations, re-import the statement. Everything should link up correctly. Learn how to purge imported statements.
Same carrier, different statements?
If you add translations for one carrier statement, check any other statements that you receive from the same carrier. If you have other statements for other products or lines of business, there’s a chance that they could share the same coverage type values. Check each one and add translations if needed.
Different products, same coverage type?
Some products have different coverage type values in the carrier statement but share the same coverage type value in AMS+. For example, PPODEN, EPODEN, HMODEN would all go to Dental. If this happens, add translations for each one and map them to the shared coverage type.
Review your carrier statements periodically
At least once a year, review your carrier statements for any changes to the coverage type and update your translations accordingly. Keep in mind, the values in both places must match exactly.