AMS360 2025 R2 Release Notes

When creating or updating a direct bill entry statement, an optional notes section has been added to track additional comments.

When creating a receipt in any center, an optional Notes section has been added to track additional comments.

With the Broker or Agency of Record (BOR/AOR) Commission feature, you can now record the start- and end-dates when a policy is transferred to your agency mid-term through a Broker or Agency of Record (BOR/AOR) change. This record of dates helps the system automatically assign both personnel and agency commissions, based on the effective and expiration dates you have entered.

Direct Bill Entry Multiple Division Statement: Add Totals by Division

A multi-division DBE Statement now shows agency commission by division. This feature allows users to quickly journal-entry the DB Receivable between the division to which the check was posted and the divisions where that statement was posted.

Previously, regarding a policy with a broker, the percentage of Agency commissions was paid on the Agency commission amount before Broker commissions were paid out. Now, the Agency has the option to default the Employee commissions that are a percentage of the Agency after the Broker commission is taken out of the Agency commission, and this process can be changed on each policy, as needed.

Security Update When Creating Checks from Payable Statements

New secured items have been added to control access to creating checks for both account-current and commission-payable statements. This update ensures that only approved users can perform these sensitive financial tasks.

Direct Bill Entry: Linking Receipts and Journal Entries

Agencies that operate on an accrual basis can now link receipts and journal entries directly to direct-bill entry statements, which enhances financial reconciliation and visibility. This feature allows receipts and journal entries that have been posted to the direct bill receivable accounts, e.g., general ledger numbers 11241000 or 11242000, to be linked.

Adding, Replacing, or Removing a Broker on a Billed Policy Mid-Term

When adding, replacing, or removing a broker from a billed policy, any date between the policy's effective date and the current date, on an active policy, can be selected for the change. This update helps track the actual date of a broker change that has occurred.

ACORD

The foillowing ACORD forms have been updated:

• ACORD 50RI (2024/08) Rhode Island Insurance Identification Card

• ACORD 50OK (2024/12) Oklahoma Owners Security Verification Form

• ACORD 50AR (2024/08) Arkansas Proof of Insurance Card

• ACORD 50WV (2024/09) West Virginia Certificate of Insurance

• ACORD 50LA (2024/10) Louisiana Auto Insurance Identification Card (set)

• ACORD 50IN (2024/11) Indiana Insurance Identification Card

• ACORD 50ME (2024/11) Maine Motor Vehicle Insurance Identification Card

In the Admin Center - Policy Configuration, there is now a way to select which types of policy transactions automatically have their annualized premium and annualized estimated revenue calculated. We have added three policy transactions for you to select if you wish to have the annual premium calculated automatically.

These selections are "Cancellation and Reinstatements," "Premium Audit Transactions," and "Multi-year Policies." This feature allows agencies to perform some level of forecasting while saving time by automatically calculating the annualized premium field and an annualized Revenue field when endorsements come in.

• Navigate to the Administration Center - Customer/Policy on the left panel-Policy Configuration

• Click on the circle to select the policy transaction(s)

• Click Apply.

Policy Configuration: Global Update of Annualized Calculations

The policy view now has an annualized premium field and an annualized revenue field. These fields are calculated automatically whenever there are policy endorsements. Policy Configuration can be run for the initial calculation of the new Annualized Premium field and the Annualized Revenue field.

Users can now access the AgencyOne certificates page directly from AMS360.

Policy Cancellation: Adding the Requirement for a Cancellation Reason

Users who possess admin credentials can now, via the Administrative Center, require a policy cancellation reason.

New Line of Business: ACORD 834 — Cyber and Privacy Coverage

Commercial Cyber and Privacy Line of Business (LOB) has been added as a Line of Business (LOB) and is now included in the options for LOBs. This LOB has matching sections to ensure that data is fully integrated with ACORD 834.

Revised Alignment for Transactions Premiums/Billing Section

The Transactions Premiums/Billing Section within a Policy has had its column alignment changed from left-aligned to right-aligned. The page now has dollar amounts aligned to the right side, which increases the scanning rate of the data.

Additions to Commercial Supplemental Name Section

This release provides several additions within the Commercial Supplemental Name Section.

Policy Transactions: Adding New "Annualized Premium" and "Annualized Estimated Revenue" Fields per Line of Business

Two fields have been added to the Policy Transaction View and the Policies View grids. This addition will make forecasting easier, since these two fields save time by are calculating automatically.

When you click on a Policy or make a new policy, go to the Transaction Total Section. You will see two new non-editable fields: "Annualized Premium" and "Annualized Estimated Revenue." When you go to the Policy View grid in the Customer Center, you will see the two new columns titled “Annualized Premium” and “Annualized Estimated Revenue”, which will show these amounts based on the policy.

Policy View/Grid: Export All .csv File Updates to Show Annualized Estimated Revenue and Annualized Premium per Policy

fThe following fields have been added in the Customer Center - Policy Grid to show Annualized Estimated Revenue and Annualized Premium per policy. These are exportable to a .csv file. This work saves time from having to open each policy and view the Annualized Estimated Revenue and Annualized Premium fields.

Go to Customer Center. Open the Customer and go to Policy view. You will see the fields on the Policy Grid.

Email Address Format Validation

With this release, when a user tries to save an invalid email address, an AMS360 validation message appears that reads, "Email is invalid."

Whenever a user creates a new customer or edits an existing customer within "Customer Setup" in the email text field, the information is saved when a valid email is entered into either Email or Email 2, and once "Save" or "Save and Close" is clicked. However, when an invalid email is entered into Email or Email 2, and once "Save" or "Save and Close" is clicked, users see the following AMS360 validation message in the banner above the toolbar: “Email is invalid."

It is not necessary to click out of the message; you can go back to the Email field and either take out the email data or fix the email so it is valid.

As with the new email validation process, if a user attempts to save an invalid web address, an AMS360 validation message appears that reads, "Customer Web Address is invalid."

New Fields: "Total Estimated Revenue" and "Total Cost "

“Total Estimated Revenue” and “Customer Total Cost” are new fields, found under the "General Information" group. With their addition to the Summary Heading Field, you will see the “Total Estimated Revenue” and “Customer Total Cost” numbers shown in the Summary banner.

Go to "Customer." Select your Customer and click on "Customer Overview." Click on the cogwheel located in the Summary Section. The Customer Summary Options page will open. Under General Information, you will see “Total Estimated Revenue” and “Customer Total Cost.” Drag and drop them to the Summary Heading Fields and click "Save."

You will see these new fields in the Summary banner. When you hover over them, you will see a tool-tip that reads, “Total Estimated Revenue” or “Customer Total Cost."

NOTE: You can only have seven selections in the Customer Summary field.

When there are lines of business listed on a package policy, these additional lines will now appear in the Policies View. This improvement makes it more convenient and efficient to view the lines of business that are included in a package policy.

The AMS360 Declaration Page has an updated look that is more consistent with other updates that match the rest of the AMS360 look.

Populate Prior Policy from Policy Being Renewed on a Submission

When renewing a policy and selecting a submission, the policy from the renewing policy now shows as the prior policy, whereas before it showed as the submission policy. This change is important to improve the ability to track renewals.

Field Importance: Additional Customer Information Page

Additional Customer Information fields can now be set to "Optional" (default), "Recommended," or "Required." Agency data quality is therefore improved by allowing an admin to select the required fields needed for users to provide data in the Additional Customer Information field within Customer Setup.

Type-of-Business Change Retained with Downloaded Renewals

The Type of Business is now retained when there is a download on an existing policy. Previously, the type of business being changed defaulted back to its original type of business when the policy was renewed via download. Also, changes to the Type of Business selection are retained when the policy is renewed manually.

Read-Only Policy View Side Panel Security

A new security element will provide users with the ability to view the right-side Policy Summary View, even if they do not have access to the policy, but provided they have access to the Customer.

These levels are as follows:

• Feature: Policy

• Group: Policy

• Task: Policy Side View - Policy Summary

• Access: "No Access" is default; "View Only" gives access

"Overflow Pages and Attachments" as Default Option for eForms

For users with admin access, when they open the eForms setup screen, they will now be able to select a default option to choose exactly what their users will see when working with eForms. Admins have the option to select “Form Only” or “Form, Overflow Pages and Attachments.”

This feature reduces the number of clicks a user must perform (perhaps as many as 20 to 30 a day) per eForm, when reprinting a certificate and discovering the Overflow Pages have been omitted inadvertently.

Go to Admin Center. Under “Customer/Policy,” click "eForms Setup." A user will then see the new options to select a default. This view will then be updated for all users at the agency. When the users then go into eForms they will now see a radio button selection based on the setup criteria as established in the admin center.

GLOBAL CHANGE

Global Change for Personnel: Performance Enhancements

We have enhanced the Global Change for Personnel (GCP) process to make it faster and less disruptive to users:

• More Access: Only one customer and one policy are locked at a time, so you can continue working with other data.

• Runs in the Background: Global Change for Personnel now does its processing behind the scenes, making users more productive. A refreshed Global Change for Personnel page makes it easier to track the status of the process in real time.

GLOBAL NAVIGATION

REPORTS — CLASSIC

In the past, AMS360 and its components, including Crystal Reports, were always run as 32-bit applications.

Now, the client installer has been updated so that AMS360 and its components run as 64-bit applications on applicable machines. This new installer is backwards compatible with previous versions of AMS360, so there is no need to reinstall when switching between agencies of different versions. Previous versions of AMS360 will continue to run their 32-bit applications.

This upgrade improves performance and helps better accommodate customers who work with larger databases When you log into your 25R2 agency, you will be prompted to download and install a new client. Download and run the installer. Then you may log into your agency, as usual.

REPORTS — MY AGENCY REPORTS (MAR)

New Business Unit Change Customer: Policy Extract Simple Report

A new, simplified report has been created, in addition to the existing report, that includes fewer columns when running the report. This new report makes it easier for users to export the report without having to wait for complex calculations (e.g., revenue) to complete.

These columns have been removed from the new report:

• Customer Extract

  • Broker Name

  • Customer Revenue (Earned)

  • Customer Revenue (Estimated)

  • Relationship

• Policy Extract

  • Bill Method

  • Policy Revenue (Earned)

  • Policy Revenue (Estimated)

Except for the removed columns, the simple report behaves the same as in the past.

Revenue Recognition for Direct-Bill Report

The new MAR Revenue Recognition Report allows users to view billing activity between any two dates for direct bill policies, including $0.00 commission lines. This feature supports both accurate revenue tracking and auditing of revenue on a larger scale.

Book of Business & Production Analysis Reports: Annualized Estimated Revenue and Annualized Premium-per-policy

The "Book of Business" and "Production Analysis" reports in My Agency Report (MAR) now show annualized estimated revenue and annualized premium-per-policy, changing the annualized estimated revenue and annualized premium to be displayed on a per-line-of-business basis.

These two fields added so users can quickly see the amounts per Line of Business from the report without having to go separately into each policy.

To run the report, go to MAR and select the report, complete the search criteria, and then view the report.

The Direct Bill Entry Receipt Allocation Report can be used to verify which receipts and/or journal entries have been posted to the direct bill receivable GL accounts.

DocuSign Update to Support Auth2 Requirement

AMS360 has updated DocuSign integration to support its new Auth2 login security requirement.

CUSTOMER

Customer Contacts Lifecycle Management

The EMS API now supports full lifecycle management of Customer Contacts (via the API) for the following operations: Create, Retrieve, Update, and Delete.

Users will experience seamless synchronization between AMS360 and external CRM or HR systems, as well as improved integration with BenefitPoint and other Vertafore solutions.

Creating DBE Statements Through EMS API

Users can now create Direct Bill Entry Statements through the EMS API. This capability simplifies automation for billing and reconciliation processes across systems, thus ensuring faster and more accurate accounting workflows.

Comprehensive Endpoints for Homeowner Policy Data

The EMS API now exposes comprehensive endpoints to manage Homeowner policy data, including the following elements:

• Locations

• Endorsements

• Coverage details

• Replacement cost information

• Underwriting

• Additional Interests

• Scheduled Personal Property

New endpoints allow users to create, update, append, search, and delete notes directly through the EMS API for the following elements:

• Cash Receipts

• Direct Bill Entry (DBE) Statements

Endpoints:

• POST /receipt/note: Add a note to a receipt during creation.

• GET /receipt/note: Retrieve note information for a Cash Receipt by CashReceiptDetailId.

• POST /direct-bill-entry/notes/search: Search notes within DBE records.

• POST /direct-bill-entry/note: Create or update notes on a DBE record.

Scheduled Personal Property Enhancements

EMS API users can now manage the following two categories:

• Coverage Summaries

• Scheduled Items

These endpoints expand Personal Lines Rating (PLR) capabilities, thereby improving synchronization and automation across internal Vertafore systems and external agency integrations.

EMS/API Policy Loss History (for PL Rating)

EMS now has a full set of endpoints that work with Policy Loss History information. Internal Vertafore products, external agencies, and Orange partners can retrieve, create, update, and delete Loss History Information on AMS360 Policies via the EMS API.

ACORD

Fixed an error within the ACORD "eForm Tree Item Selection," where it was exhibiting inconsistencies after expanding "Certificate Holders to View." Users now experience proper number ordering.

Fixed an error that caused Certificate Holders to be displayed out of alphabetical order in the eForms Manager.

Changes have been made where descriptions for buildings were not pushing into Line of Business (LOB) premise information. More information here.

Fixed an issue that caused the following error message to appear when processing a Global Change for Personnel Import: "No records are selected for global change for personnel."

Fixed an error that prevented the primary contact listed in the Notification Service Setup from being saved.

Fixed an error that caused "Import Deposits" in the Bank Center to fail when imported.

Fixed an error where a log showed up in the event viewer after a new Receipt/Additional receipt was added and the user went back to the Bank Deposit page.

Fixed an error where, if an employee had access to a bank and that person became inactive, an admin with access to the Bank Security View page is now able to see all banks and grant others access.

Fixed an error where the Change Requests/Comparison feature was pulling incorrect data. When agencies were making endorsements to policies and deleting vehicles/equipment, Change Requests (and the Comparison tool) showed incorrect items being deleted, and also appeared to amend every other item on the list while also reordering the data.

Additional security has been created to further protect the ability to create checks from Account Current, Employee and Broker Commission statements. More information here.

Previously, the Event Viewer was returning errors upon login/logout, which were related to the clientInstaller. After using the Client Installer (Rev. 13, 64-bit), Event Viewer errors occurred while logging in and out of AMS360. This no longer happens.

Prior to this fix, the install redirect screen was showing an incorrect file size. When redirected to the new AMS360 client installer, users saw that the installer's file size was listed as 22MB. This was incorrect, and the file size now reads as 257MB.

Fixed an error that caused the eForms manager to load too slowly.

Fixed multiple errors where invalid NAICS and SIC codes appeared on the Customer Analysis report and under Customer Overview.

Fixed an issue where the writing company code was presented on the policy page instead of the writing company name.

Fixed an error that prevented the proper functioning of Division Consolidation if Branch Codes were out of sync. More information here.

Fixed an error with the Contacts Page when a user tried to send an email with an attachment.

Fixed an error when a commission payable statement was created from the Employee Center, but users instead received an error message no matter which selection was made; this prevented the statement from being created.

Fixed an error where the receipt page crashed after attempting to switch banks into different divisions whenever the "Received From" name showed as a blank in the drop-down menu.

Fixed an issue where a service employee was given access to a customer, yet the customer did not show up.

EMS API

Formerly, the "GET /user-permissions" API returned its authItemPermission value as an integer. Now, this API returns its authItemPermission value in a human-readable string format.

The Trust Transfer grid previously showed incorrect invoice dates. An update to the stored procedure now returns the correct invoice and effective dates.

A new payee failed to be designated as the default one, where the changes were not saved and a modal with an error message was displayed. Following this fix, once a new payee is added to the Payee section and the original payee's Last name is substituted with the just-added one in the Name & Address section, by clicking the Save button the changes are NOT saved and an error message is displayed.

Fixed an error where users were unable to add an address for a company on the page and instead received an error message.

Fixed an error where the Payee and the Company Address was not properly defaulted on the Check Page.

Fixed an error where the EMS call Agency-Commission's error message, "version not compatible" appeared for users, caused by insufficient information on supported AMS360 versions,

Fixed an error where the Policy Additional Interest Type was not updating via the OData call into the user interface (UI).

POST/personal auto/coverages EMS API endpoint allowed any string for option description when it has a set PrCode list

Four-decimal digits instead of two were being returned for the money data type in the following endpoints: POST /personal-auto/coverages/search; POST /homeowners/location/replacement-cost/search

FINANCE CENTER

Fixed an issue where the Direct Bill Deposit section did not clear out other company drop-downs when a specific company was selected for one of the three drop-downs. This occurred in the "Broker, Employee, and Insured Centers for Receipt" page, as well as in the "Insured Centers for Journal Entry" page.

Fixed an issue where users were unable to open form letters, and AMS360 froze when opening the Form Letter Preview.

Fixed an error that occurred once a policy was saved after invoicing, by adding code to attempt to repair the Primary Key once the error was triggered

Fixed an error that occurred when voiding a Direct Bill Entry (DBE) statement due to its large file size. More information here.

DS10928

DS11012

Fixed IVANS and Database issues to allow agencies to quickly assign items to multiple IVANS accounts. More information here.

The default ONS setting has been changed from "Single Retry" to "Blocking" for all AMS360 versions after 24R2.

Fixed an error that caused policies to be displayed twice in the policy drop-down menu within the Outlook Add-In.

Fixed an error that prevented the Outlook Add-In from creating an Activity/Suspense from an incoming email, since the tray would not load.

Fixed an issue where users were unable to edit or replace personnel on service agreements. When choosing to edit or replace personnel on a service agreements, users saw an error error message that read: "A policy must have personnel records identifying the primary personnel and their active and inactive dates. This policy does not have complete personnel records. Please contact AMS360 Customer Support."

Fixed an error where, in certain circumstances, a Commission Template was saved multiple edtimes. When adding a term to a Commission Template in AMS360, if a user quickly clicked the "Save and Close" button multiple times before the UI changed, the rows of that commission template was duplicated. Since a user should only be allowed to click "Save and Close" once, additional attempts to perform this function now have no effect.

Fixed a latency issue within "Create Policy Specific Split," When selecting "Create Policy Specific Split" within a policy, it was taking nearly 13 minutes to load for users who have access to all business units. Now, for users who have access to a single division, it loads within seconds.

Fixed an issue that occurred when adding Coverages to the General Liability Line of Business.

Distribution Jobs: The "Division" drop-down menu in the Business Units section was pre-filled with the wrong value in "edit" mode.

Fixed an issue where the Policy Dec Page redesign assigned an incorrect name to the log-out menu. The Dec Page redesign was putting the login ID as this value, whereas the correct value is the employee's short name.

Fixes an issue where the dollar amounts are now right-aligned instead of left-aligned in the Commercial Cyber and Privacy Line of Business.

Fixed an issue where commas were missing within the Retention column under Coverages for the Commercial Cyber and Privacy Line of Business.

Fixed an issue in the Coverages section, where the Retention column had commas within AMS360, but they were missing when the data was mapped to ACORD 834.

The "Distribution" page opened by displaying an error message, where no records got loaded to the grid and a "New Distribution Job" could not be created.

Fixed an error that caused the Future Invoices report to display an incorrect Agency commission amount whenever a specific Line of Business was selected in the selection criteria.

Fixed an issue that resulted in an error message when clicking the Form Letters button in the Customer List Classic Report.

Fixed an issue where users received the message, "An unexpected error was logged in the event log," when they attempted to run the Security Setup report within Classic Reports. Users also experienced intermittent errors when attempting to open Security Group Setup. Both issues produced the following message: "An unexpected error was logged in the event log," while also registering "System Out of Memory" errors in EV.

Fixed an issue that occurred when a scheduled report was run; the data seemed to be duplicated and came in blank, but then the reports possessed data after running again.

REPORTS — MY AGENCY REPORTS (MAR)

Fixed an issue on the Production Analysis Report where agreements were displayed as "Renewal Group" even when they were "New Business." No matter the transaction type invoiced on a service agreement, the My Agency Reports Production Analysis Report column for New Business/Renewal Group was always reporting the service agreement invoice as "Renewal Group." This has been corrected through the addition of separate transaction types for service agreements, i.e., "New Business Service Agreement" and "Renewal Service Agreement."

Fixed an issue where filtering was not working in the "Detail View" when two or more filters were selected. When users added more than one filter in the Detail view of a report within My Agency Reports, and at least one of those filters had more than one selection, they saw more data than expected. For example, if a user chose A & B criteria for one filter and then C & D criteria for another, the results had either A, B, C, or D, as opposed to a combination of the two categories as was intended (e.g., A+C, A+D, B+C, B+D). Templates that were saved with multiple filters also did not filter correctly, and the Filtered Data Set exported to Excel from within the Detail View incorrectly mirrored this behavior.

Fixed an issue with Business Unit Access and Employee Business Unit Access. More information here.

TRUST TRANSFER

DE58949

DE61219

Fixed an error that involved a Trust Transfer with Subscription Policies. Policies that were invoiced as Subscription policies were being pulled into the Trust Transfer and overstating the commission that should have been transferred.

Fixed an error regarding Trust Transfer Dates where, when creating a trust transfer, followed by saving and closing, and then reopening the Trust Transfer, the dates were being changed to the date previously entered.

WSAPI3.0 CustomerProfileAnswerGet and CustomerProfileAnswerGetList - 500 internal error occurred following an unrelated OData change in 25R2.