EMS / API Release Notes

• 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.