MarketSync: Navigation and Workflows
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 how users navigate and use MarketSync within Amplo.
Amplo Policy Download Inbox
The Amplo Policy Download Inbox has a streamlined layout that makes processing downloads a breeze. Transactions are grouped by policy, allowing you to quickly assess volume at a glance, and the filters section is collapsed by default to provide more space on the page for your work. Main actions are brought to the front, while less frequently used actions are available in a drop down.
Filter Bar and Actions
# policies: shows the number of policies displayed on the page. You can adjust this value in the Policies to load filter.
# transactions: shows the number of transactions applied to the policies
# active filters: shows the number of filters applied to the policy page
Policies to load - select to display up to 50 policies on the page
Saved filter - this list will display saved filters
Show filters - click to expand the filters section
Rematch all - runs the policy matching job again for every transaction in the inbox and matches the policy and account to the Policy Download Detail record (does not automatically reprocess record)
Available filters include: Policy Number, Named Insured, Customer Account, Transaction Code, LOB, Issuing Carrier, Carrier Parent Account, Agency, Branch, Created Start Date, and Created End Date. Once you have added field values, you can click Create New Filter to generate a saved filter view for the future.
Policy Group table
The policy group table displays download transactions grouped by policy, along with available field values.
Named Insured - the named insured from the Policy Download Detail record
Policy Number - the Policy Number from the PDD record
Customer Account - if found, the matching system account record. This field is a lookup against system records and is used to match the download to a system account.
System Policy - if found, the matching system policy record. This field is a lookup against system policy records for a specific account. To return values, a Customer Account record must be selected.
Policy Term - the policy term from the PDD’s Effective Date and Expiration Date fields
Carrier - the carrier from the PDD record
Transaction table
When opening a policy group using the expand arrow, you will see a new table appear. This section describes the information available in the transaction table.
Transaction - displays the Transaction Code, LOB code, and Endorsement Effective Date from the Policy Download Detail record; the value is a hyper-link to the Policy Download Detail record associated with the transaction.
Status - describes the status of the transaction. Values are set automatically or within the Policy Download Detail record. They include:
Insert - indicates that the transaction resulted in new records created in Amplo
Ignore - indicates that a transaction did not result in changes to Amplo records. Transactions can be manually set to Ignore or automatically set to Ignore through Carrier Decision Mappings
Update - indicates that the transaction resulted in the update of existing records in Amplo. This status can be the result of automatic processing based on Carrier Decision Mappings or through manual processing in the Amplo Policy Download Inbox.
Processing - indicates a match has been found for a transaction, and system processes are running to write the policy data
Failed - indicates a record stopped processing due to an error. The error message is found in the Last Error Text field on the Policy Download Detail record.
Held - a legacy status that MarketSync functionality no longer uses
Reconcile - indicates that a match was not found by the system, and the policy routes to the Amplo Policy Download Inbox for manual review. This value can also be set based on Carrier Decision Mappings.
Matching - indicates that a transaction has been received, and the system is running a job to match it. This status is also set when a user clicks Update on a policy in the Amplo Policy Download Inbox.
Enriching - indicates that the system is completing the Policy Download Detail record with system values.
Inbox - set if the Transaction Status field is blank. Only relevant for transactions processed through Legacy Downloads.
Policy Group Actions
Add Account (Customer Account field) - opens a modal to create a customer account from the Inbox
Update - once a transaction in the inbox is manually matched to a system account and policy, clicking Update will apply the data from the download to the matched policy
Rematch - this button runs the policy matcher job again for every transaction in the policy group
Update Details - opens a new window where you are able to view and adjust values for:
Agency - if the download transaction does not contain a value, the system carries it over from the matched System Policy during enrichment. Values input into this field will be written to the policy only if the field is blank; as Agency is required for policy creation, it should only be written for new policies. For Legacy Downloads, this field can be used to set a value for the required Agency field for new business or renewal policies if the download does not contain a value.
Branch - if the download transaction does not contain a value, the system carries it over from the matched System Policy during enrichment. Values input into this field will be written to the policy only if the field is blank; as Branch is required for policy creation, it should only be written for new policies. For Legacy Downloads, this field can be used to set a value for the required Branch field for new business or renewal policies if the download does not contain a value.
Department - if the download transaction does not contain a value, the system carries it over from the matched System Policy during enrichment. Values input into this field will be written to the policy only if the field is blank on the policy.
Profit Center - this value can be set from the Update Details section and will be written to the PDD but not to the policy
Account Manager - if the download transaction does not contain a value, the system carries it over from the matched System Policy during enrichment. If the value is set in the Update Details section, it will be written to the PDD and policy upon clicking Update.
Primary Producer - if the download transaction does not contain a value, the system carries it over from the matched System Policy during enrichment
Agency Coverage Code - this value can be set from the Update Details section and will be written to the PDD but not to the policy
Transaction Actions
Ignore - manually sets the Transaction Status to Ignore; the system will not write values from the Policy Download Detail record to existing records nor create new records. If Inbox Ignore reasons are configured, clicking the button will display a modal to select or provide an Ignore Reason based on your organization's setup.
Picklist values include:
Duplicate/already handled
Carrier/source issues
Not a valid transaction
Other: selecting this option displays a free text field to input a reason.
Open - opens the associated Policy Download Detail record in another tab
Common Workflows
When downloads match to policies according to matching rules, our system will automatically update or insert records in the background as needed based on the transaction type. This section describes common workflows from the Amplo Policy Download Inbox.
Unmatched transactions
The most common scenario for a policy routing to the inbox is that a match did not automatically occur, and so an account or policy needs to be manually associated with the transaction in order to process. Common reasons for not matching include:
missing or inaccurate data used for matching (policy number, NAIC, term dates, and LOB, transaction code)
missing policy record
This section provides detailed workflows for common scenarios to manually process transactions out of the inbox.
All unmatched transaction types in the Amplo Policy Download Inbox currently use the same workflows. Our team is working on functionality to allow for the manual and automatic creation of policies from within the Amplo Policy Download Inbox.
If the transaction does not have a matching Account or Policy, and no Account exists in the system, you will need to create both records prior to matching and applying the transaction.
You can create the Account using the Add Account button in the Customer Account field.
Next, in the Amplo Policy Download Inbox, click the transaction hyperlink or the Open button on the Transaction record.
Review and note key information: Transaction Code, Policy Number, NAIC, Effective Date, Expiration Date, and LOB Code.
Using App Launcher, navigate to the Amplo app and then to the newly created Account record.
In the toolbar on the right side of the page, click the Add PL/CL Policy button (the name will depend on the type of account). If the button does not appear in the toolbar, click the down arrow to view more options.
Complete the creation process, filling in required fields and data necessary for matching. Click Save.
Return to the Amplo Policy Download Inbox, and either search for the policy in the System Policy field, or select Rematch from the Actions menu.
Selecting Rematch will automatically process the record if a match is found. Otherwise, once matched, click Update.
If an Account is matched but has no matching policy, you will want to check if a policy exists and update it if necessary prior to matching and applying the transaction.
In the Amplo Policy Download Inbox, click the transaction hyperlink or the Open button on the Transaction record.
Review and note key information: Transaction Code, Policy Number, NAIC, Effective Date, Expiration Date, and LOB Code.
Using App Launcher, navigate to the Amplo app and then to the appropriate Account record. Click the Policies tab.
Review the list of policies to find the correct one, and click on the Policy/Coverage Type link to open it.
Review the policy details to determine if any necessary matching criteria is incorrect, and update as needed.
Return to the Amplo Policy Download Inbox, and either search for the policy in the System Policy field, or select Rematch from the Actions menu.
Selecting Rematch will automatically process the record if a match is found. Otherwise, once matched, click Update.
If an Account is matched but has no matching policy AND a policy doesn’t exist, you will need to create a policy shell prior to manually matching in the Amplo Policy Download Inbox and applying the transaction.
In the Amplo Policy Download Inbox, click the transaction hyperlink or the Open button on the Transaction record.
Review and note key information: Transaction Code, Policy Number, NAIC, Effective Date, Expiration Date, and LOB Code.
Using App Launcher, navigate to the Amplo app and then to the appropriate Account record.
In the toolbar on the right side of the page, click the Add PL/CL Policy button (the name will depend on the type of account). If the button does not appear in the toolbar, click the down arrow to view more options.
Complete the creation process, filling in required fields and data necessary for matching. Click Save.
Navigate back to the Amplo Policy Download Inbox, and match the transaction to the newly created policy or select Rematch from the Actions menu.
Selecting Rematch will automatically process the record if a match is found. Otherwise, once matched, click Update.
Errored or Failed Transactions
When a transaction fails to process because of an error, the transaction is routed to the Amplo Policy Download Inbox with a Transaction Status of Failed. This section describes common errors and resolution steps.
Before troubleshooting the issue, review the transaction’s Last Error Text.
In the Amplo Policy Download Inbox, click the Transaction hyperlink text or the Open button to open the Policy Download Detail record.
In the PDD record, review and note the value for the Last Error Text field.
Using the information from the Last Error Text field, determine the cause of the error. Often, the error is due to missing required information or a custom automation or validation rule that prevents the creation of a record.
Once you have resolved the underlying issue(s), return to the Amplo Policy Download Inbox.
Note whether the record has been matched to an Account and Policy using the Customer Account and System Policy fields.
Click the Transaction hyperlink or the Open button on the appropriate record to go to the PDD record.
Click the pencil icon for the Transaction Status field.
If the policy was correctly matched to an Account AND Policy, change the status to Processing. No further action should be necessary.
If the policy was not fully matched to an Account AND Policy, change the status to Reconcile to route it to the Inbox. Return to the Amplo Policy Download Inbox to manually match and Update the transaction.