MarketSync: Configuration and Processing

Last updated: November 17, 2026

Overview

MarketSync is our core Download's feature that processes carrier transactions from IVANS and applies them to your Amplo environment. This article provides information about the configuration and rules that govern MarketSync.

Amplo Setup

The Amplo Setup application is used to configure the MarketSync connection. These settings are managed by Amplo Support when initially installing MarketSync and do not need to be adjusted by your team.

Amplo Connector ECA

MarketSync utilizes an External Client Application that includes App Authorization settings. By default, Amplo sets the following values:

  • Refresh Token Policy (Idle Expiration Time Limit Enforced): Expire refresh token after specific time

  • Refresh Token Validity Period: 8

  • Refresh Token Validity Unit: Day(s)

  • IP Relaxation: Enforce IP Restrictions

Policy Matching Criteria

For carriers and lines of business with a Carrier Decision Mapping of Update, MarketSync checks each Policy Download Detail against existing policies in your organization. For the system to confirm a match, it moves through the strategies and criteria described below. When a match is not found, the system will set the Transaction Status to Reconcile, and the download will route to the Amplo Policy Download Inbox. 

Exact Match

If your organization does not have policy number prefix or suffix removal activated, the system will look for an exact match of the following fields:

  • Line of Business: matching occurs through the IVANS Policy Mapping record, where the policy’s Policy / Coverage Type field must ultimately match the download’s LOB code via the ACORD LOB code. (IVANS Policy Mapping > ACORD LOB Code > Policy Coverage Type. For more information about configuring mappings, click here.

  • Policy number

  • Effective date and expiration date

  • NAIC code

Normalized match

If your organization does have policy number prefix or suffix removal activated or no exact match of the policy number is found, the system will look to match on a normalized policy number with the following requirements:

  • The download’s Policy Number with spaces and and special characters removed must equal the policy’s Policy Number or Calculated Policy Number.

  • Effective Date must match.

  • Expiration Date must match, unless the Transaction Code is PAB or REI.

Renewal transaction codes (RWL, RRQ, AND RWQ)

Renewal Transaction Codes (RWL, RRQ, or RWQ) behave differently. The system will first check for an exact match, and if one is not found, uses the following strategies:

  • The normalized download Policy Number must match the policy’s Policy Number or Calculated Policy Number, and the policy’s Expiration Date must match the download’s Effective Date.

  • The download’s normalized Prior Policy Number must equal the policy’s Policy Number, and the policy’s Expiration Date must equal the download’s Effective Date.

Unmatched new business (NBS) transactions

Unmatched New Business (NBS) transactions will route to the Amplo Policy Download Inbox for review. If needed, users can create an account using the Add Account button visible when clicking into the Customer Account field. If a system policy shell does not already exist, users will need to create one before selecting it in the System Policy field, otherwise, you will encounter an error when clicking Update: “Please select System Policy before queueing a Market Sync update.” 

Ignore Reason Configuration

Amplo Policy Download Inbox allows for the assignment of picklist reasons when choosing to Ignore a transaction. To enable this feature, an Admin can complete the steps below (requires Salesforce Managed Package version 2.12 and higher):

  1. Navigate to Setup.

  2. Using Quick Find, search for Custom Settings.

  3. Click Manage next to Config.

  4. Confirm if Inbox_Ignore_Configuration exists. If not, click New.

  5. Input the following values (other fields should be left blank):

    1. Name: Inbox Ignore Configuration

    2. Key: Inbox_Ignore_Configuration

    3. Type: String

    4. String Setting: select an option below

      1. None: no ignore reason will be required; the transaction is ignored upon clicking Ignore

      2. Picklist: displays a modal upon clicking Ignore that displays the following options:

        1. Duplicate/already handled

        2. Carrier/source issue

        3. Not a valid transaction

        4. Other (requires comment)

      3. Custom: displays a modal with a free text field

  6. Click Save.

Policy Processing Jobs

This section describes the system jobs that occur during the processing of download transactions. The steps are completed in the order laid out below, but not every transaction will go through every step. You can find information about the steps run and their status on the System tab of the Policy Download Detail record.

Step Types

  1. Policy Match: this step runs the match rules to link a PDD with an existing policy record.

  2. Policy Renewal: this step runs when a renewal transaction matches to an expiring policy. It copies the expiring policy into a new-term policy, and then matches the new term policy to the transaction.

  3. Enrichment: this step fills the Policy Download Detail record with data from the matching policy if the PDD fields are blank, including blank Agency, Branch, Department, Account Manager, Primary Producer, and Billing Company.

  4. Carrier LOB Reconciliation: this step reviews the organization’s Carrier Decision Mappings for the Issuing Carrier, Line of Business, and Transaction Code.

    • An Update value will continue processing.

    • Ignore will set the Transaction Status to Ignore, and processing will stop.

    • Reconcile will set the Transaction Status to Reconcile, route the transaction to the Amplo Policy Download Inbox, and processing will stop.

  5. Confirm Match: requires an associated System Policy field value. The step status is set to Processing, and the match is sent to our core engine for processing. A Complete status indicates that the call was accepted by the engine, and Error indicates a failure.

  6. Policy Continuation: job that runs after a Failed transaction is updated from the Inbox after Confirm Match already completed. Resends the corrected data to our core engine.

When updating policies through the Amplo Policy Download Inbox, actions have different impacts on job processing:

  • Update: If no jobs have been run, this action will create one with standard steps. If Confirm Match step already completed, a Policy Continuation step will be created. If the latest run is missing steps, clicking Update will add them, or processing will restart and continue from any errored steps.

  • Ignore: marks open steps as Complete and sets Confirm Match to Pending.

  • Rematch: restarts errored steps from the latest run

Step statuses

Processing steps can have a number of statuses. This section describes their meaning and application.

  • Pending/Ready: step is queued, not started yet

  • In Progress: step is running

  • Waiting: Confirm Match step or Policy Continuation step is preparing to send information to our core engine

  • Complete: step is finished

  • Error: step failed; the reason is the Error Reason