This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
client_settings [2018/12/13 15:51] – lisa.maloney | client_settings [2024/09/10 10:52] (current) – tina.robles | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | __**Admin: | + | **Reporting - Admin** |
- | Client Settings can be configured in the Admin -> Client Setup -> Client Settings menu option. | + | {{: |
- | {{: | ||
- | ----- | ||
- | There are 7 different areas to manage the Client Settings. | + | __**Client Settings**__ |
+ | |||
+ | |||
+ | Client Settings can be configured in the Admin -> Client Setup -> Client Settings menu option. | ||
+ | |||
+ | There are 8 different areas to manage the Client Settings. | ||
- | {{:pasted:20181205-193450.png}} | + | {{:pasted:20240826-180633.png}} |
----- | ----- | ||
Line 15: | Line 18: | ||
In this section, manage the Client Description, | In this section, manage the Client Description, | ||
- | {{:pasted:20181205-193856.png}} | + | {{:pasted:20240826-180858.png}} |
__Minimum Password Crack Time__ | __Minimum Password Crack Time__ | ||
Line 35: | Line 38: | ||
Each match we make over a part of a password is given a score for how easy to guess it is, and we then put together all matches we have made in a way which gives the lowest possible possible score for the password. | Each match we make over a part of a password is given a score for how easy to guess it is, and we then put together all matches we have made in a way which gives the lowest possible possible score for the password. | ||
- | The time-to-crack is calculated using the hashing algorithm our passwords are protected by, the score for the password returned from the analysis above, and being attacked by a hypothetical password cracking server which cost ~$20,000 in 2017. | + | The time-to-crack is calculated using the hashing algorithm our passwords are protected by, the score for the password returned from the analysis above, and being attacked by a hypothetical password cracking server which cost ~$20,000 in 2019. |
The speed of a server which can be bought for ~$20k is something which will obviously change over time, and we will continue to keep the values used for the calculation valid over time. | The speed of a server which can be bought for ~$20k is something which will obviously change over time, and we will continue to keep the values used for the calculation valid over time. | ||
Line 61: | Line 64: | ||
**Contract** | **Contract** | ||
- | {{:pasted:20181205-193940.png}} | + | {{:pasted:20240826-181041.png}} |
__Enable and Enforce Lumpsum Product Allocation__: | __Enable and Enforce Lumpsum Product Allocation__: | ||
- | __Enable Forecast Feature__: when checked, | + | ----- |
+ | **Accrual** | ||
+ | |||
+ | The Accrual tab has the option to accrue into the future. | ||
+ | |||
+ | {{:pasted: | ||
+ | |||
+ | When checked, | ||
---- | ---- | ||
+ | **Reporting** | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ---- | ||
+ | **Deduction** | ||
+ | |||
+ | {{: | ||
+ | |||
+ | These are settings you can update to increase auto matching from claim to deduction. | ||
+ | |||
+ | |||
+ | ----- | ||
**Claim** | **Claim** | ||
+ | |||
+ | {{: | ||
This tab contains the claim-related settings like Price Generation, Price Tiers, Default UOM, etc. | This tab contains the claim-related settings like Price Generation, Price Tiers, Default UOM, etc. | ||
Line 76: | Line 101: | ||
Enable Sale Data Price Generation - check this box to use sales data for price generation. | Enable Sale Data Price Generation - check this box to use sales data for price generation. | ||
- | {{:pasted:20181213-153435.png}} | + | {{:pasted:20240827-132603.png}} |
- | * **Look-back Period and Period Type**: The price generation process will use the mostt recent period to find pricing for that company and product. | + | * **Look-back Period and Period Type**: The price generation process will use the most recent period to find pricing for that company and product. |
- | * **Look-back | + | * ** Price Generation |
- | + | ||
- | {{: | + | |
Line 88: | Line 111: | ||
This section allows the 4 different Price Tiers to be Configured. | This section allows the 4 different Price Tiers to be Configured. | ||
- | In the screenshot below, the order used is: Price List by Company, Price List by Product, Default, and Sales Data. | + | {{:pasted:20240827-132703.png}} |
- | + | ||
- | {{:pasted:20160817-113005.png}} | + | |
To change the order, select a value and drag it to the desired location. | To change the order, select a value and drag it to the desired location. | ||
- | To add a tier, select it from the dropdown | + | To add a tier, select it from the dropdown. |
- | To delete an option, select the value in the dropdown and click the delete | + | To delete an option, select the value in the dropdown and click the X icon. {{:pasted:20240827-132742.png}} |
__Other Claim Options__ | __Other Claim Options__ | ||
- | {{:pasted:20181213-154829.png}} | + | {{:pasted:20240827-132807.png}} |
- | **Location Claimant Enforce Eligible Distributor: | + | **Location Claimant Enforce Eligible Distributor: |
**Zero Rate Auto Reject: | **Zero Rate Auto Reject: | ||
Line 113: | Line 134: | ||
**Contacts** | **Contacts** | ||
- | Add Contacts here. Just click Add Contact to add a new row and then click Save. First Name and Last Name are required fields. | + | Add Contacts here. Just click Add Contact to add a new row and then click Save. First Name and Last Name are required fields. |
- | {{:pasted:20150914-174938.png}} | + | {{:pasted:20240827-133027.png}} |
- | + | ||
- | {{: | + | |
----- | ----- | ||
**Fiscal Calendar** | **Fiscal Calendar** | ||
- | Add new Fiscal Calendar Months, Quarters and Weeks. | + | Add new Fiscal Calendar Months, Quarters and Weeks. |
- | {{:pasted:20150914-180112.png}} | + | {{:pasted:20240827-133104.png}} |
+ | |||
+ | Fiscal Calendar entries are validated on save to ensure there are no gaps or overlaps in the date ranges, as | ||
+ | well as no skipped years, quarters, months, and weeks. | ||
- | {{: | ||
----- | ----- | ||
**Tolerance** | **Tolerance** | ||
Tolerances can be added and managed in Client Settings by users who have access. | Tolerances can be added and managed in Client Settings by users who have access. | ||
+ | |||
+ | {{: | ||
+ | |||
**Note: all tolerances are at the claim level - not invoice level.** | **Note: all tolerances are at the claim level - not invoice level.** | ||
- | ----- | + | |
+ | Since tolerances are at the claim level, they cannot be applied at the lump sum level. This is because the tolerance amount is added to the lump sum amount, allowing additional claims to be submitted and paid for the overspent event, provided the overspent amount is within the tolerance limit. | ||
+ | |||
+ | **Example**: | ||
__No Tolerances: | __No Tolerances: | ||
Line 138: | Line 165: | ||
If the Enable Tolerance box is unchecked, no tolerances will be applied. | If the Enable Tolerance box is unchecked, no tolerances will be applied. | ||
- | {{:pasted:20161207-104331.png}} | + | {{:pasted:20240827-133258.png}} |
If the Max Claim Tolerance amount is $0.00, no tolerances will be applied. | If the Max Claim Tolerance amount is $0.00, no tolerances will be applied. | ||
- | {{:pasted:20161207-104412.png}} | + | {{:pasted:20240827-133232.png}} |
- | ----- | + | |
__Tolerances: | __Tolerances: | ||
- | {{:pasted:20161207-104047.png}} | + | {{:pasted:20240827-133247.png}} |
__Line Item Tolerance: | __Line Item Tolerance: | ||
Line 162: | Line 189: | ||
Add: To add a new tolerance reason, click the New button. | Add: To add a new tolerance reason, click the New button. | ||
- | {{:pasted:20161207-105144.png}} | + | {{:pasted:20240827-133419.png}} |
Select a Reason Code from the dropdown, add the tolerance amount and select an action type. Each Reason Code can only be added once. | Select a Reason Code from the dropdown, add the tolerance amount and select an action type. Each Reason Code can only be added once. | ||
Line 170: | Line 197: | ||
Delete: to remove a tolerance reason, check the box for the row and click the Delete button. | Delete: to remove a tolerance reason, check the box for the row and click the Delete button. | ||
- | {{:pasted:20161207-105421.png}} | + | {{:pasted:20240827-133437.png}} |
Click Save after making changes! | Click Save after making changes! | ||
+ | |||
+ | {{: | ||
+ | |||
----- | ----- | ||
__Action Types__ | __Action Types__ | ||
Line 187: | Line 217: | ||
**Payment Calendar** | **Payment Calendar** | ||
- | This section is used to set up Payment Calendars for selection | + | This section is used to set up Payment Calendars for use when running the AutoPay process for Growth |
- | + | {{:pasted:20240827-133529.png}} | |
- | Click the Add Payment Calendar button at the bottom of the screen to add a new payment description. | + | |
- | + | ||
- | {{:pasted:20170419-095144.png}} | + | |
- | + | ||
- | Enter the description. | + | |
- | {{: | + | Click the Add button on the bottom left hand side of the screen to add a new payment calendar description. (i.e. Monthly, Quarterly, Annually) |
- | To add the Payment Dates, select a description by clicking the row which will highlight blue. Then click the Add Payment Date button at the bottom of the screen. | + | {{: |
- | {{: | + | Add the Payment Calendar Description into the text field and hit ENTER on your keyboard. |
- | Enter in the date or select a date using the calendar. | + | {{: |
- | {{: | + | This will add that calendar description in a pick list on the left side of the screen. |
- | If you need to delete a calendar date, select the date by clicking the row. Then click the Remove Payment Date at the bottom of the screen. | ||
- | {{: | + | Once the date is entered, either manually or using the calendar icon, click SAVE in the bottom right hand corner of the screen. If you have different time periods you would set up multiple calendars (i.e. Monthly, Quarterly, Annually). |
- | Remember to click Save after making any changes. | + | {{: |
- | The Executed column is non-editable and will be automatically updated when the process runs. | ||
- | {{: | ||
----- | ----- | ||