Agency Management System
Policy Balance Hub for Vertafore AMS360
CSV import with a prebuilt AMS360 migration kit
Policy Balance Hub does not connect to Vertafore AMS360 over an API. It ships a prebuilt migration kit instead: two import recipes that already know AMS360's Custom Data Exporter column names, so moving your customers and policies across is a two-file upload rather than a mapping exercise.
Plan availability: Importing and reconciling work on every paid plan. Reconciliation, aging and commission reports are on Professional and up.
What the integration does
- A prebuilt AMS360 migration kit maps the Custom Data Exporter's customer and policy data sets — the column names are already filled in
- The policy import auto-creates any customer or carrier it has not seen, so the two files can be uploaded in order and link themselves up
- Adjust any mapping in the wizard when your data set differs, and save it as your own recipe
- Reconcile carrier statements against the imported book, detecting missing deposits and underpayments
- Record each policy's billing type (agency-bill or direct-bill), and invoice agency-billed premium separately
- Export reconciled data as CSV/Excel for AMS360 reporting and audits
Why agencies use it
- Get your AMS360 book into Policy Balance Hub without hand-mapping every column
- Eliminate manual matching of AMS360 policies to carrier statements
- Track commissions across multiple carriers in one place with an immutable audit trail
What it does not do
Stated up front rather than discovered later.
- There is no live API connection to AMS360. The kit reads files you export from the Custom Data Exporter.
- Nothing is written back to AMS360 — it stays your system of record for policy management.
- The kit covers customers and policies only. There is no producer import, and commission history is better brought across through statement uploads than through a migration file.
- AMS360 does not publish a fixed export schema, so the kit's column names are the commonly-seen ones. When yours differ, the mapping step adjusts per file.
Frequently asked questions
- What AMS360 exports do I need?
- The customer data set and the policy data set, both from the Custom Data Exporter, as CSV. The prebuilt kit already lists the columns each one needs. Upload the customer file first, then the policy file — policies link themselves to the customers created in the first pass.
- Does Policy Balance Hub write back to AMS360?
- No. There is no API connection in either direction. Your AMS360 instance remains the source of truth for policy management, and reconciled commission data leaves Policy Balance Hub as CSV/Excel for posting to your accounting system.
- Our export column names are different. Does the kit still help?
- Yes. AMS360 data sets are user-configured, so the kit's value is the entity wiring and a correct starting mapping rather than an exact schema. Where your columns differ, change them in the mapping step and save the result as your agency's own recipe.
Ready to stop drowning in spreadsheets?
See how Policy Balance Hub can automate premium reconciliation for your agency. Start the trial in minutes — or request a personalized walkthrough.
14-day free trial (up to 100 policies, 3 users). No credit card required.