EMS / API Release Notes

Policy Company

• PUT /policy/company/agency-bill

  • Required Fields:

    • PolicyId

    • WritingCompanyCode

  • Optional Fields:

    • ParentCompanyCode

    • CompanyType

  • Value: This endpoint allows users to change the company on Agency Bill policies through EMS. This endpoint supports both billed and unbilled policies and allows the writing company (plus the parent company, where applicable) to be updated. For billed policies, this endpoint completes the required invoice correction and billing updates as part of the company change. This enhancement allows users to make Agency Bill company changes via EMS rather than manually completing the change in AMS360.

Apply Money

• POST /receipts/apply-money

  • Required Fields:

    • ApplyFromInvoiceId

    • ApplyToInvoiceId

    • AmountApplied

    • ApplyDate

  • Value: This endpoint allows users to apply money from an existing on-account invoice to a billing invoice for the same customer. Users can apply all or part of the on-account amount to a single invoice and can also reverse a prior application, when needed. This endpoint creates the required Adjusting Journal Entry and returns the remaining on-account credit and destination invoice balance once the application has been completed.

Submissions

• POST /submission-groups/search

  • Required Fields:

    • CustomerId

  • Value: This endpoint allows users to retrieve Submission Groups that are associated with a customer. The response includes the Submission Group ID, Group Number, and Group Date, which can be used to identify an existing Submission Group when working with submissions. Results are returned only for the specified customer.

• POST /submission

  • Required Fields:

    • SubmissionGroupId

    • SubmissionNumber

    • EffectiveDate

    • ExpirationDate

  • Value: This endpoint allows users to create a new Submission within an existing Submission Group. This endpoint uses the same applicable information and validation as creating a Policy shell while also creating the record as a Submission. This enhancement allows users to create the initial Submission through EMS for an existing Customer or Prospect while continuing to work with the Submission in AMS360.

No updates to existing endpoints are part of this service pack release.

DEFECT SUITE	SALESFORCE NO.	DESCRIPTION OF FIX
DS15160	4685289	An issue was resolved where a blank space could be accepted as a Broker Code when creating a policy through EMS. This could cause the policy to incorrectly appear as if a broker had been assigned. Broker Code validation has been updated to prevent space-filled values from being accepted, thus ensuring that policies are created only with valid broker information.

Submission Group

• POST /submission-group

  • Required Fields:

    • CustomerId

  • Optional Fields:

    • GroupNumber

    • GroupDate

  • Value: This endpoint allows users to create a new Submission Group for a Customer or a Prospect. If a group number or group date is not provided, the system generates a default value consistent with AMS360. These newly created Submission Group IDs, customer IDs, group numbers, and group dates are returned for use in subsequent submission workflows. Submission Groups cannot be created for customers who have been classified as Suspects.

Transaction Premium

• POST /policy/transaction-premiums

  • Required Fields:

    • PolicyId

    • EffectiveDate

    • LineOfBusiness

    • WritingCompanyCode

    • Premium

    • IncludePremium

    • HowBilled

  • Optional Fields:

    • PlanType

    • Description

    • WrittenPremium

    • FullTermPremium

    • EstimatedRevenue

    • Reconciled

  • Value: This endpoint allows users to create a new transaction premium for a policy. The premium is validated by using existing AMS360 policy, line of business, company, billing, and premium rules before it is created. The resulting transaction premium is immediately available for downstream invoice processing, and the new Transaction Premium ID is returned in the response.

• PUT /policy/transaction-premiums

  • Required Fields:

    • PolicyId

    • EffectiveDate

    • PolicyTransactionPremiumId

  • Optional Fields:

    • LineOfBusiness

    • Premium

    • Description

    • HowBilled

    • IncludePremium

    • PlanType

    • WritingCompanyCode

    • WrittenPremium

    • FullTermPremium

    • EstimatedRevenue

    • Reconciled

  • Value: This endpoint allows users to update an existing transaction premium for a policy. Only values provided in the request are updated, whereas values not provided retain their existing information. Certain transaction premium fields are restricted once the premium has been billed, while supported fields will remain available for maintenance, according to existing AMS360 rules.

Company Payable Statement

• POST /account-current/statements

  • Required Fields:

    • CompanyId,

    • GeneralLedgerDivisionCode

    • ThroughDate

  • Optional Fields:

    • StatementDescription

    • StatementDate

    • InvoiceId, CustomerId

    • DefaultPayAmounts

    • IncludeUnpaidInsurance

    • IncludePaidInFullInsurance

    • IncludeBeginningBalanceInvoices

  • Value: This endpoint allows users to create a new Company Payable Statement by using eligible invoices for a specified company and division. Users can create this statement by using all eligible invoices, or with a single selected invoice, with options to control which eligible invoice types are included and whether pay amounts are populated. The statement is created in "In-Progress" status by default, or in "Ready to Pay" when pay amounts have been defaulted, and the newly created Statement ID and statement totals are returned.

• PUT /account-current/statements

  • Required Fields:

    • StatementId

  • Optional Fields:

    • StatementDescription

    • StatementDate

    • Status

    • Updates (DetailId, PayAmount)

  • Value: This endpoint allows users to update an existing Company Payable Statement before it is posted. Users can update the statement description, statement date, status, and Pay Amount values for statement details, and statement totals are then recalculated once Pay Amounts have been changed. Updates are applied together to maintain the integrity of the statement, and supported status changes allow users to move between "In-Progress" and "Ready to Pay" elements as part of the existing AMS360 workflow.

Adjusting Journal Entry

• POST /adjusting-journal-entries

  • Required Fields:

    • Division

    • JournalDate

    • JournalMemo

  • Value: This endpoint allows users to create and immediately post an Adjusting Journal Entry in AMS360. Users can create balanced accounting adjustments across Insured Accounts Receivable, Broker Accounts Receivable, Finance Accounts Receivable, Direct Bill Deposit, and other General Ledger accounts, with applicable business unit and subledger information. This endpoint validates the journal entry plus the user’s applicable security prior to posting, and it returns the General Journal ID, reference number, posting status, posting date, division, and posted debit and credit totals.

No updates to existing endpoints are part of this service pack release.

DEFECT SUITE	SALESFORCE NO.	DESCRIPTION OF FIX
DE77552		PUT /customer Previously, certain customer lookup fields could not be cleared through the PUT /customer endpoint, even though the request returned a successful response. This has been corrected so that Notation, Acquisition, Business Origin, Referral Name, Referral Location, and Marital Status can be cleared by passing an empty string or white-space; passing null or omitting the field continues to preserve the existing value. This endpoint now also returns a "404 Not Found" message when the specified customer does not exist, whereas the "403 Forbidden" message remains reserved for customers the caller does not have permission to update.
DE77884		POST /activities/attachment Previously, adding an existing attachment to one or more activities could result in Activity Update notifications not being delivered, because the notification referenced the attachment instead of the associated activity. This has been corrected so that each affected activity is properly identified when a notification is generated. Activity Update notifications are now generated for each activity included in the request, which allows configured notification subscribers to receive the expected updates.
DE77885		POST /activities/customers Previously, creating activities for multiple customers via the POST /activities/customers endpoint did not generate Activity notifications for configured subscribers. This has been corrected so that an Activity Insert notification is generated for each successfully created customer activity. Notifications now identify the corresponding activity and the customer, thus allowing configured subscribers to receive the expected notifications.
DE78037		POST /activity Previously, creating a customer activity using CustomerId instead of EntityId could generate an Activity notification without the associated customer Entity ID. This has been corrected so that, when CustomerId is provided for a customer activity, the corresponding Entity ID is included in the generated notification. Activity notifications now contain the customer information needed by configured subscribers, regardless of whether CustomerId or EntityId is used in the request.

No new endpoints are part of this service pack release.

Customer

• GET/ Customer

  • Updates to the endpoint:

    • This endpoint has been updated to include the CsrCode and ExecCode fields in the customer response. These fields provide employee codes for the customer’s primary CSR and account executive while continuing to return existing customer information available through the endpoint.

    • Value: This update will allow EMS API users to retrieve the primary CSR and account executive employee codes as part of the customer response, thus providing additional customer personnel information for integrations such as ePay and other API consumers.

DEFECT SUITE	SALESFORCE NO.	DESCRIPTION OF FIX
DS14978	4646713	An issue was resolved where Outbound Notification Service (ONS) notifications were not being consistently generated when activities were created through the EMS API. The notification processing has been updated to ensure that activity changes are now handled reliably, which will improve the consistency of ONS notifications for EMS API activity updates.
DE77551		An issue was resolved where Commercial Supplemental Names returned by the POST /policies/applicant/search endpoint did not include a complete mailing address. The endpoint has been updated to return Address Line 2, City, State, and ZIP Code, whenever that information is available. This fix will ensure that Commercial Supplemental Names will include all mailing address details in the response.
DE77347		An issue was resolved where the GET /config-options endpoint could return a 500 error when an OptionAttribute did not exist. This endpoint has been updated to handle these requests appropriately and will now return a clear response if the requested OptionAttribute is not found.

Invoice Search

• POST /invoices/all-customers/search

  • Required Fields:

    • CustId

  • Value: This endpoint allows users to retrieve invoice information for standard customers, master customers, and sub-customers. It will allow users to support multi-entity customer structures by returning invoices associated with the requested customer relationship. This endpoint also provides invoice status and ownership context so users can determine the correct customer to use for payment processing. These results support filtering, sorting, and pagination.

Account Current Statement Details

• POST /account-current/statements/details/search

  • Required Fields:

    • StatementIds

  • Value: This endpoint allows users to retrieve detailed line-level information for one or more Account Current statements. This includes statement header details, policy information, commission amounts, payable balances, payment amounts, and related invoice information. This endpoint will allow users to review statement details through EMS without having to use workarounds or multiple searches to gather the same information.

Account Current Statement Payment

• POST /account-current/ /statements/payment

  • Required Fields:

    • StatementId

    • BankCode

    • CheckDate

    • CheckType

  • Value: This endpoint allows users to post a payment against an existing Account Current Statement via EMS. When the statement is eligible for payment, the payment is processed and the statement status is updated accordingly. This endpoint also returns payment details, including the cash disbursement identifier, payment status, check number, and posted date to support reconciliation and payment tracking.

Company Addresses

• GET /companies/addresses

  • Updates to the endpoint:

    • Added an optional IsPayee query-string parameter.

    • When IsPayee is true, the endpoint returns only payee addresses.

    • When IsPayee is false, the endpoint returns only non-payee addresses.

    • When IsPayee is omitted, the endpoint returns all addresses.

    • The IsPayee field is now included in the response payload.

  • Value: This update will allow users to retrieve company address information based on whether or not the address is a payee address. This endpoint supports workflows that need to identify the correct pay-to entity and address when working with company and payee information. When the IsPayee filter is not provided, the endpoint will continue to return all addresses to maintain backward compatibility.

DEFECT SUITE	SALESFORCE NO.	DESCRIPTION OF FIX
DS14311	4545488	An issue was resolved where certain policy notifications were failing to deliver when a field value contained an unprintable character. The system now removes unsupported characters from notification data before the message is created, thereby preventing malformed notification messages from being generated. This fix allows valid policy notifications to be delivered successfully and reduces undelivered notifications that were previously caused by invalid characters.
DS14432	4563286	An issue was resolved where users without Download Setup permission could not see available mailboxes when filtering in Assign Customers/Policies. The mailbox filter has been updated so that users who possess the appropriate Download access can view and filter by available mailboxes, without requiring Download Setup permission. This fix allows users to complete the customer and policy assignment workflow while maintaining existing access controls for download transactions.

Policy Commercial Locations

• POST /policy/commercial-locations/search

  • Required Fields:

    • PolicyId

    • TransactionEffectiveDate

  • Value: This will allow users to retrieve a sorted and paginated list of commercial policy location records for a given policy and transaction-effective date. This endpoint applies only to commercial policies, and it supports integration with AMS360 commercial policy data through EMS. This new endpoint reduces the need to retrieve this information through WSAPI, OData, or via manual processes.

• POST /policy/commercial-buildings/search

  • Required Fields:

    • PolicyId

    • TransactionEffectiveDate

  • Value: This will allow users to retrieve a sorted and paginated list of commercial building records for a given policy and transaction-effective date. This endpoint applies only to commercial policies, and it supports integration with AMS360 commercial building data through EMS. This new endpoint reduces the need to retrieve commercial building information through WSAPI, OData, or via manual processes while providing access through standard EMS search functionality.

Policy Commercial Supplemental Names

• POST /policy/commercial-supplemental-names/search

  • Required Fields:

    • PolicyId

    • EndEffectiveDate

  • Value: This will allow users to retrieve a sorted and paginated list of commercial supplemental name records for a given policy and end-effective date. This endpoint returns the most recent commercial supplemental name record for each named insured, on or before the provided end effective date. This new endpoint supports integration with AMS360 Business Auto data through EMS and reduces dependency on WSAPI, OData, or via manual processes.

Company Payees

• POST /company/payees/search

  • Required Fields:

    • CompanyId

  • Value: This endpoint allows users to retrieve a paginated list of company payees. Results include eligible Insurance, Brokerage, and Fee company payees and are sorted with the default payee first, followed by payee name (in ascending order). This endpoint is read-only and does not create or modify company, payee, or statement data

Account Current Statement

• POST /account-current/statements/search

  • Required Fields:

    • divisionCode

  • Value: This endpoint allows users to retrieve a paginated list of Account Current statement header records. Results include statements that match the requested division as well as any optional company, date range, or status filters. This endpoint is read-only and returns header-level statement data only; statement detail, invoice lines, payment execution, and payee resolution are out of scope.

Activity Customer Search

• POST/activity/customer/search

  • Updates to the endpoint:

    • This endpoint has been updated to include activityId and employeeCode in each activity result.

    • This endpoint has also been updated to include attachmentId, whenever an attachment is returned with the activity.

  • Value: This updated endpoint will allow users to identify customer activities and retrieve associated attachments without making additional calls to other activity endpoints. Existing request fields, pagination, sorting, and response behavior remain unchanged.

Policy Claims

• Get /Policy/claims

  • Updates to the endpoint:

    • Added claimDescription to the response model.

  • Value: This updated endpoint will allow users to retrieve the claim description when returning policy claim information. This additional field provides more context for each claim and supports partner workflows such as routing, file naming, and downstream claim processing, all without requiring additional look-ups. Existing request, pagination, filtering, and sorting behavior remain unchanged.

Here is are the three defects that were fixed with this deployment:

DEFECT SUITE	SALESFORCE NO.	DESCRIPTION OF FIX
DS13522	4379031	An issue was resolved where the /customer/profile-answer endpoint returned an error when attempting to clear a profile answer defined as a list. This endpoint now supports list answer formats and allows blank answers to be saved when the profile question is not required. This fix allows users to clear non-required profile answers through EMS without having to manually remove them in AMS360.
DS14363	4551925	An issue was resolved where customers could be assigned to an inactive or deleted employee when multiple employees shared the same ShortName. The system now uses only active employees when resolving the employee assignment during Global Change and API workflows. This fix ensures that customers are assigned to the correct active employee while also preventing assignments from being made to deleted employees.
DS14579	4587204	An issue was resolved in the PUT /customer API endpoint where updating a customer could unintentionally change the customer’s master type when multi-entity settings were not included in the request. In some cases, master and sub-customer relationships were incorrectly converted to standard customers, which resulted in inconsistent customer hierarchy data. This endpoint has been updated to preserve existing master type information when multi-entity settings are not provided, thereby preventing unintended changes during customer updates. In addition, affected records can be identified and corrected through the use of validation logic that restores the appropriate master or sub-customer designation based on existing customer relationship data.
DS14718	4610281	An issue was resolved where concurrent customer creation requests via the EMS Customer endpoint could result in duplicate customer numbers being assigned to different customer records. Under certain conditions, multiple requests processed at the same time could reference the same available customer number before the sequence was updated. The customer number generation process has been updated to ensure that each request receives a unique customer number, even during high-volume concurrent processing. This change eliminates the possibility of duplicate customer numbers being created and improves the reliability and consistency of customer record creation within EMS.

There were NO new endpoints created for this release.

Bank Access Authorization for Service Employees in Bank Center

Service employees

• Updates to the endpoint:

  • You can now add Bank Access to service employees via the bank center. This update allows service employees to have access to EMS endpoints that require bank authorization.

Here is are the three defects that were fixed with this deployment:

DEFECT SUITE	SALESFORCE NO.	DESCRIPTION OF FIX
DE73208		An issue was identified where the POST /invoices/void EMS endpoint did not correctly generate General Ledger postings when voiding an invoice created through the BenefitPoint integration. Instead of fully reversing the original transaction, the system created both debit and credit entries on each affected account, effectively reposting and voiding them simultaneously. This resulted in incorrect financial data that could not be corrected without direct database intervention. This issue was resolved by updating the posting logic to properly filter transaction rows during void processing. The system now ensures that only the appropriate reversal entries are created, thus fully offsetting the original invoice postings. As a result, General Ledger balances correctly net to zero (0) following a void, thereby restoring accurate and reliable financial reporting.
DS14004	4489484	An issue was identified where policy purge operations failed when processing large volumes of records, even though the same policies could often be successfully purged when processed individually, or in small batches. Users experienced high rejection rates with inconsistent and unclear error messages, including dependency failures and asynchronous operation errors; these issues made it difficult to determine the root cause and complete purge activities. This issue was resolved by correcting how purge-related processes handle database operations and dependencies during bulk execution. Updates were made to ensure that purge actions are now executed sequentially and properly complete each step before initiating the next one, which prevents conflicts caused by overlapping operations. As a result, bulk purge processes now complete successfully with significantly reduced rejection rates, providing more reliable and consistent behavior for users who are managing large policy datasets.
DS14478	4568921	An issue was identified where commission percentages did not consistently calculate or display when posting Direct Bill Entry statements through the API. When both gross amounts and agency commission amounts were provided, the system did not reliably compute the commission percentage; this resulted in missing or blank values in the user interface. This created confusion for agencies that expected standard percentage calculations based on submitted amounts. This issue was resolved by restoring and correcting the commission percentage calculation logic during the Direct Bill Entry detail-creation process. Additional safeguards were added to ensure proper handling of null values without unintentionally clearing calculated percentages. As a result, commission percentages are now accurately calculated and displayed when using the POST /direct-bill-entry/detail endpoint, providing consistent and expected behavior for users.

Business Auto

• GET /business-auto/covered-auto-symbols

  • Required Fields:

    • PolicyId

    • LineOfBusinessId

    • EffectiveDate

  • Value: This endpoint will allow users to retrieve the Covered Auto Symbols for a specified Business Auto policy, line of business, and transaction-effective date. The endpoint returns the Covered Auto Symbols data for the selected record so that users can access this information for downstream business processes and integrations. Only active Covered Auto Symbols are returned, and deleted rows are excluded.

• POST /business-auto/coverages/search

  • Required Fields:

    • PolicyId

    • EndEffectiveDate

    • LineOfBusinessId

  • Value: This endpoint allows API consumers to retrieve, in a single request, Business Auto coverage data for a specific policy, transaction-effective date, and line of business. It provides the coverage details needed to support integration and related business processes while returning only active coverage records and excluding deleted entries. The response is structured to support consistent access to Business Auto coverage information, based on the selected policy context.

• POST /business-auto/hired-borrowed/search

  • Required Fields:

    • PolicyId

    • EndEffectiveDate

    • LineOfBusinessId

  • Value: This endpoint allows API consumers to retrieve Business Auto Hired/Borrowed Auto data for a specific policy, transaction-effective date, and line of business. It supports the use of optional filters and returns a sorted, paginated list of matching records so that users can more efficiently access the data they need for integrations and downstream processes. Only active Hired/Borrowed Auto records are returned, and deleted records are excluded.

• POST /business-auto/non-owned/search

  • Required Fields:

    • PolicyId

    • LineOfBusinessId

    • EffectiveDate

  • Value: This endpoint allows API consumers to retrieve Non-Owned Auto data for a specific Business Auto policy, transaction-effective date, and line of business. It supports filtering, sorting, and pagination so that users can more efficiently access the records they need for integrations and related business workflows. Only active Non-Owned Auto records are returned, and deleted rows are excluded.

• POST /business-auto/drive-other-car/search

  • Required Fields:

    • PolicyId

    • EffectiveDate

    • LineOfBusinessId

  • Value: This endpoint allows API consumers to retrieve Drive Other Car data for a specific Business Auto policy, transaction-effective date, and line of business. It supports filtering, sorting, and pagination so that users can more efficiently access the records they need for integrations and downstream processing. Only active Drive Other Car records are returned, and deleted records are excluded.

• POST /business-auto/factors/search

  • Required Fields:

    • PolicyId

    • LineOfBusinessId

    • EffectiveDate

  • Value: This endpoint allows API consumers to retrieve Business Auto factor data for a specific policy, transaction-effective date, and line of business. It provides access to factor values used in rating and premium calculations for Business Auto coverages so that the information can be used in integrations and related business processes. Only active factor records are returned, and deleted records are excluded.

• POST /business-auto/driver-information/search

  • Required Fields:

    • PolicyId

    • LineOfBusinessId

    • EndEffectiveDate

  • Value: This endpoint allows AMS360 EMS API users to retrieve Business Auto driver information for a specific policy, transaction-effective date, and line of business. It supports filtering, sorting, and pagination so that internal products, agencies, and partners can more efficiently access the driver data they need for integrations and related business workflows. The endpoint returns the matching driver records for the selected policy context, while enforcing policy security access.

• POST /business-auto/garage-locations/search

  • Required Fields:

    • PolicyId

    • LineOfBusinessId

    • EndEffectiveDate

  • Value: This endpoint allows users to retrieve Business Auto garage locations associated with a specific policy, transaction-effective date, and line of business. These results return all garage location records tied to the requested transaction, thereby ensuring accurate and time-relevant data for policy servicing and integration needs. Users can optionally filter results by state to narrow the data set. This endpoint supports internal Vertafore systems, external agencies, and partners in efficiently accessing and integrating Business Auto garage location data.

• POST /business-auto/vehicles/search

  • Required Fields:

    • PolicyId

    • LineOfBusinessId

    • EndEffectiveDate

  • Value: This endpoint allows API consumers to retrieve Business Auto vehicle information for a specific policy, transaction-effective date, and line of business. It supports optional filtering by garage location and returns a sorted, paginated list of matching vehicle records so that users can efficiently access detailed vehicle data for integrations and downstream processes. The response includes comprehensive vehicle and rating information associated with the selected policy context, while enforcing policy-level security access. Only active vehicle records are returned, and deleted records are excluded.

• POST /business-auto/vehicles/coverages/search

  • Required Fields:

    • PolicyId

    • LineOfBusinessId

    • EndEffectiveDate

  • Value: This endpoint allows API consumers to retrieve Business Auto vehicle coverage information for a specific policy, transaction-effective date, and line of business. It supports optional filtering by vehicle and returns a sorted, paginated list of matching coverage records so that users can efficiently access coverage details for integrations and downstream processes. The response includes vehicle-level coverage data associated with the selected policy context, while enforcing policy-level security access. Only active vehicle coverage records are returned, and deleted records are excluded.

• GET /business-auto/general-information

  • Required Fields:

    • PolicyId

    • LineOfBusinessId

    • EffectiveDate

  • Value: This endpoint allows API consumers to retrieve Business Auto general information and remarks for a specific policy, line of business, and effective date. It returns the general information record along with any associated remarks and underwriting question responses for the selected policy context, which therefore allows users to access this information for integrations and downstream business processes. This endpoint returns a single record for the requested policy context, while enforcing policy-level security access.

• POST /business-auto/additional-interests/search

  • Required Fields:

    • PolicyId

    • LineOfBusinessId

    • EndEffectiveDate

  • Value: This endpoint allows API consumers to retrieve Business Auto additional interest information for a specific policy, transaction-effective date, and line of business. It supports optional filtering by interest type and state and returns a sorted, paginated list of matching records so that users can more efficiently access the additional interest details they need for integrations and downstream business processes. The response includes the additional interest information associated with the selected policy context, including vehicle attachment details (when applicable), while enforcing policy-level security access. Only active additional interest records are returned, and deleted records are excluded.

• POST /business-auto/forms/search

  • Required Fields:

    • PolicyId

    • LineOfBusinessId

    • EndEffectiveDate

  • Value: This endpoint allows API consumers to retrieve Business Auto form information for a specific policy, transaction-effective date, and line of business. It supports optional filtering by form number and form name, and it returns a sorted, paginated list of matching form records so that users can more efficiently access form details for integrations and downstream business processes. The response includes form information associated with the selected policy context, while enforcing policy-level security access. Only active form records are returned, and deleted records are excluded.

Business Units Levels

GET /business-units/levels

• Updates to the endpoint:

  • This endpoint has been updated to support additional business-unit-level searches for Division, Branch, Department, and Group. Users can now provide GLCode and ShortName as optional search parameters when retrieving business-unit-level information.

  • Validation has been added so that, if the GLCode or ShortName is invalid, the endpoint returns an empty list. This endpoint will also return an empty list when GLCode and ShortName do not belong to the same business-unit level.

  • The response continues to return the existing fields, including GLCode, name, short name, status, and isHidden. These updates improve support for notification subscribers who require more complete business-unit-level data for ONS V3 processing.

Policies Search

POST /policies/search

• Updates to the endpoint:

  • This endpoint has been updated to return additional policy fields that are needed to better support ONS V3 notifications. These added fields include: TypeOfBusiness, IsContinuous, RenewalReportStatus, BillMethod, IsNewPolicy, FullTermPremium, IsFinanced, CompanyType, IsMultiEntity, ChangedBy, ChangedByName, and ChangedDate.

  • RenewalReportStatus reflects the value that is reported as PolicyStatus in ONS v1 policy notifications. ChangedByName returns the employee ShortName associated to the ChangedBy value.

  • These updates provide a more complete policy data set for notification subscribers and reduce the need to rely on incomplete or older endpoint responses.

Companies

GET /companies

• Updates to the endpoint:

  • This endpoint has been updated to return additional optional company fields required for ONS V3 support. These added fields include: CompanyType, IsActive, ParentCompanyCode, ParentCompanyShortName, ShortName, ChangedBy, ChangedByName, and ChangedDate.

  • The request continues to support the primary key for Company Code, and the updated response now provides a more complete set of company details for downstream consumers. ChangedByName returns the employee ShortName associated to the ChangedBy value.

  • These updates improve the consistency of company data returned through EMS and better align the endpoint with ONS V3 notification requirements.

Policies Billing Info

GET /policies/billing-info

• Updates to the endpoint:

  • This endpoint has been updated to return additional billing and policy-related fields needed for notification processing and WSAPI alignment. These added fields include: PolicyType, PolicyTypeOfBusiness, WritingCompanyCode, AccountExecCode, AccountRepCode, IsContinuous, RenewalReportStatus, GLDivisionCode, GLDepartmentCode, GLBranchCode, GLGroupCode, IsNewPolicy, FullTermPremium, IsFinanced, CompanyType, IsMultiEntity, and PolicySubType.

  • This updated response is intended to return both name and code information, where needed, so consumers can retrieve more complete billing-related policy details. These changes improve support for notification subscribers and help align EMS billing information with existing downstream expectations.

Broker Search

POST /brokers/search

• Updates to the endpoint:

  • This endpoint has been updated so that BrokerCode can be used as a search field in the request model. This update supports the primary key requirements needed for ONS V3 processing.

  • This response has also been updated to include missing broker fields, including IsActive and Contact. In addition, this endpoint now supports description fields for Status, ARClosedStatus, BJEClosedStatus, S1099Category, and S1099Type so that users can retrieve more meaningful broker information in the response.

  • These updates provide a more complete broker record for notification subscribers and improve the usability of the endpoint for ONS V3 integrations.

Vendors

GET /vendors

• Updates to the endpoint:

  • Thia endpoint has been updated to return additional vendor fields needed for notification and integration use cases. These added fields include: Description, EmployerIdentificationNumber, GLNumber, IsInactive, IsActive, MiddleName, ShortName, ChangedBy, ChangedByName, and ChangedDate.

  • ChangedByName returns the employee ShortName associated to the ChangedBy value. These updates provide a more complete vendor record and improve the consistency of vendor data returned through EMS.

  • This enhanced response helps notification subscribers access the vendor details they need without relying on incomplete endpoint data.

Here is are the three defects that were fixed with this deployment:

DEFECT SUITE	SALESFORCE NO.	DESCRIPTION OF FIX
DS14247	4530654	An issue was resolved where the GET /policy/additional-information endpoint could return a null value for Business Origin when the agency was using a custom Business Origin code. This occurred because the API was relying on a hard-coded value set that did not account for customer-defined codes. This endpoint has been updated to retrieve Business Origin values from the agency’s configured code list, thereby allowing custom Business Origin codes to be returned correctly for reporting and downstream use.
DE70763	4441200	An issue was resolved where policy notifications generated from "Global Change for Personnel" could fail due to a missing customer ID, which caused synchronization issues with downstream systems. This occurred because policy notifications were not consistently triggered, and customer IDs were not always included when processing global personnel changes. This process has been updated to ensure that policy notifications are properly generated, include the required customer ID, and they are reliably sent (even under high-load conditions), which improves consistency and prevents synchronization failures.
DE72772		An issue was resolved where the POST /policy/invoices endpoint could return a successful response, yet failing during invoice posting because of an invalid general ledger number. This occurred when certain transaction fee charge types did not properly populate the general ledger number, thus resulting in a processing error and leaving the invoice in an incomplete state. This endpoint has been updated to correctly handle these charge types and ensure that the general ledger number is properly assigned. This fix allows invoices to post successfully and eliminates downstream accounting inconsistencies.

• PUT /invoice/correction/message

  • Required Fields:

    • InvoiceID

    • InvoiceMessage

  • Value: This will allow for the correction of an existing invoice message. This endpoint controls whether the message prints on invoices and/or statements. The endpoint replaces (overwrites) the existing message content for the specified invoice.

    Note: This endpoint does not support Invoice corrections to DBE invoices.

• PUT /invoice/correction/bill-to

  • Required Fields:

    • InvoiceID

    • BillSource

  • Value: This will update the bill-to on an invoice. The endpoint also retains the values so downstream outputs (invoice print/PDF, AR displays, etc.) reflect the corrected Bill-To details. The endpoint replaces (overwrites) the current Bill-To values for the specified invoice.

    Note: This endpoint does not support Invoice corrections to DBE invoices.

• POST/invoice/correction message

  • Required Fields:

    • InvoiceID

    • InvoiceMessage

  • Value: This will create a new invoice correction message, if one does not already exist.

    Note: This endpoint does not support Invoice corrections to DBE invoices.

• POST/invoice/customer/search

  • Required Field:

    • InvoiceID

  • Value: This will retrieve a list of sub-customers associated with an invoice. This information can be used in conjunction with making invoice corrections to the endpoints listed above.

    Note: This endpoint does not support Invoice corrections to DBE invoices.

Import Deposit and Post Deposit

• POST /import-deposit/create

  • Required Fields:

    • GeneralLedgerDate

    • BankCode

    • TotalAmount

  • Details:

    • PayerName

    • InvoiceNumber

    • CheckNumber

    • CheckAmount

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

• POST /import-deposit

  • Required Fields:

    • ImportDepositId

    • GeneralLedgerDate

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

• POST /import-deposits/search

  • Required Fields:

    • BankCode or BankShortName (if both are provided, they must match)

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

• DELETE /import-deposit

  • Required Field:

    • ImportDepositId

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

Transaction Premium

• GET/ Transaction Premium

  • Required Fields:

    • Policy ID

    • Optional Fields

    • Transaction effective date

  • Value: This will allow users to retrieve a list of all premiums for a transaction and can further filter this list by "effective date." if needed.

Direct Bill Entry

• POST/Direct-Bill-Entry/Detail

  • Updates to the endpoint:

    • Removed the validation and error message for when a commission percentage is greater than 999.99, because it was applied to cases incorrectly where premium was set to 0 [zero].

    • Commission Percentage recalculation logic has also been removed, since it will cause problems if it is recalculated to more than 999.99.

    • The endpoint has been updated so that, when a company plan is inactive system-wide, as long as the plan has been assigned to a company, it is still carried over to the direct bill entry statement. Also, if the policy transaction premium referenced in the request contains an invalid company plan, it is simply ignored when creating a direct bill entry detail line item.

Here is the sole defect that was fixed with this deployment:

DEFECT SUITE	SALESFORCE NO.	DESCRIPTION OF FIX
DS13774	4441573	An issue was resolved where certain policy notifications were being sent without a valid customer ID, which occasionally caused synchronization failures. The system now validates that a policy and its associated customer ID actually exists before sending notifications, thereby preventing invalid messages from being generated. Also, line-of-business notifications have been standardized to always include the customer ID for consistency across versions. Furthermore, "Global Change for Personnel" and "Global Change for Personnel Import" have been updated to send policy notifications, where notifications are triggered only when changes involve primary personnel.

Import and Post Deposit

• Endpoint: POST /import-deposits/search

  • Required Fields: Either BankCode or BankShortName

  • Value: This will allow users to get paginated list of deposit imports

• NOTE: The balance endpoints associated with this work will come out in the following EMS release.

Agency Bill Service Agreement Enhancements

• Endpoint: POST / service-agreements

  • Required Fields: ServiceAgreementNumber, Description, EffectiveDate, ExpirationDate (Expiration date cannot be on or before the effective date), ServiceType, TypeOfBusiness. DivisionCode, DepartmentCode

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

• POST/service-agreements/search

  • Required Fields: PolicyId

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

• PUT/service-agreements

  • Required Fields: ServiceAgreementId

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

• DELETE/service-agreement

  • Required Fields: PolicyId

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

Billing Charges and Credits

• Endpoint: POST/charge-type

  • Required Fields, ChargeDescription, ReportDescription, ShortName, ChargeCategory

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

• POST/charge-types/search

  • Required Fields: N/A

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360. See the table below for a list of three defects that were fixed with the most recent service pack release.

Payment Plans List

• POST/payment-plans/search

  • Required Fields: N/A

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

Service Agreement Type List

• POST/service-agreements/type

  • Required Fields: Code, Description

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

• POST/service-agreements/types/search

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

Add Additional Transactions to Existing Policies/Service Agreements

• POST/ServiceAgreement/Transaction

  • Required Fields: PolicyId, TransactionEffectiveDate, Description,TransactionType

  • Value: Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

Personnel on Policies and Services Agreements

• POST /policy/personnel

  • Required Fields: PolicyID and PersonnelType

  • Value: This will allow users to add personnel to the policy as of EffectiveAsOfDate

• POST /policy/personnel/search

  • Required Fields: PolicyID

  • Value: This will allow users to return a list of personnel for a policy and its one or more active periods.

• POST /service-agreement/personnel/search

  • Required Fields: PolicyID

  • Value: This will allow users to return a list of personnel for a service agreement and its one or more active periods

• PUT /policy/personnel

  • Required Fields: PolicyId, PersonnelType, IsPrimary, Either SourcePersonnelCode or SourcePersonnelShortName, Either TargetPersonnelCode or TargetPersonnelShortName

  • Value: This will allow to replace the source personnel on the policy to the target personnel as of EffectiveAsOfDate

• PUT /service-agreement/personnel

  • Required Fields: PolicyId, PersonnelType , IsPrimary, Either SourcePersonnelCode or SourcePersonnelShortName, Either TargetPersonnelCode or TargetPersonnelShortName

  • Value: This will allow the user to replace the source personnel on the service agreement to the target personnel as of EffectiveAsOfDate.

• DELETE /policy/personnel

  • Required Fields: PolicyId, PersonnelType, Either a PersonnelCode or a PersonnelShortName

  • Value : This will allow to delete the personnel on the policy as of EffectiveAsOfDate

• DELETE / service-agreement/personnel

  • Required Fields: PolicyId, PersonnelType, Either a PersonnelCode or a PersonnelShortName

  • Value: This will allow to delete the personnel on the service agreement as of EffectiveAsOfDate

Create Invoice Correction

• •POST /policy/invoice-correction

  • Required Fields: InvoiceTransactionID, InvoiceCommissionID, Commission Method, PersonnelType*

    • NOTE: Some of these fields are not required when only updating agency commission or personnel commission

  • Value : This will allow to correct a single invoice transaction

    • NOTE: This endpoint is only available to use with AMS360 26R1, but will extend back to 25R2 and 25R1 with the March service pack.

Update Existing Void Invoice Endpoint to Include Service Agreements

• POST/invoices/void

  • Required Fields: Either CollectionId or InvoiceIds

  • Users gain the ability to make updates using EMS instead of having to manually update these in AMS360.

• Use WSAPI endpoint /v3/WSAPIService.svc/SearchByPhoneNumber instead of the following endpoints:

  • GET /Customers/{contactPhone}

  • GET /Customers/{contactPhone}/cache

  • GET /sms/{contactPhone}/cache (Deprecated but still functional)

  • GET /sms/converstaions/{contactPhone}/customers (Deprecated but still functional)

Here are the four defects that were fixed with this deployment:

DEFECT SUITE	SALESFORCE NO.	DESCRIPTION OF FIX
DS13481	4379668	Endpoint: POST/policy Fixed an issue where a Policy appeared multiple times in the Customer Center Register view when it was created through EMS, with trailing spaces in the Policy Number.
DS13845	4459114	Endpoint: PUT auth/config/agency-keys/generate Improvements were made to the agency key generation endpoint to ensure that validation errors were properly returned and displayed, versus a generic “Server Error” message. Additionally, updates were made to improve the way application access and service employees are managed behind the scenes, thus preventing errors during subscription changes and ensuring a more reliable and consistent experience.
DS13790	4436258	Endpoint: POST/policy/line-of-business Fixed an issue where policies created through WSAPI integrations did not require a sort number on the line of business, which caused subsequent attempts to add additional lines of business through EMS to fail, resulting in an error. The system now properly assigns and validates the sort number, which allows additional lines of business to be added without requiring manual correction.
DS13795	4447183	Endpoint: PUT policy/additional-information Fixed an issue that affected the process of updating the Business Origin through the EMS policy. Additional information endpoints could fail with a validation error when custom Business Origin codes were configured. This endpoint now properly supports valid custom codes, thereby allowing updates without requiring manual changes in the UI.