# How to map source records to Vertafore AMS360 destination

**URL:** <https://community.synatic.com/t/how-to-map-source-records-to-vertafore-ams360-destination/240>\
**Category:** Mapper\
**Tags:** helper-functions\
**Created:** [June 1, 2022, 1:55pm UTC](https://community.synatic.com/t/how-to-map-source-records-to-vertafore-ams360-destination/240 "2022-06-01T13:55:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![navessa](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.synatic.com/navessa/32/58_2.png) [@navessa](https://community.synatic.com/u/navessa)\
**Post date:** [June 1, 2022, 1:55pm UTC](https://community.synatic.com/t/how-to-map-source-records-to-vertafore-ams360-destination/240/1 "2022-06-01T13:55:51Z")

</div>

To **map source records to Vertafore AMS360 destination** , you need to **add the nested objects to the fields** in your Super Mapper. Illustrated below is the Super Mapper with highlighted fields that are nested which are going to AMS360 (SOAP Service destination step).

 ![image](https://canada1.discourse-cdn.com/flex032/uploads/synatic/original/1X/d4a8a8ddc7a8c896f009af4e0869093e4f8967ba.png)

The below link assists with what Vertafore AMS360 nested objects to use when mapping fields to AMS360:

> [API Documentation](https://link.vertafore.com/VERTAFORE/documentation/AMS360/content?apiSlug=AMS360:WSAPI:22f503&resourceSlug=R659cd175)