AMS360 data after an acquisition: what the export gives you

Abe Harbid, 26 October 2026

AMS360 is Vertafore’s agency management system, and Vertafore’s page says it fits a small independent agency or a large multi-location firm [1]. An agency on it will most likely hand you report exports in CSV or Excel form, and possibly a custom export if it bought a license for one [2][3]. The hard parts for the acquirer are the accounting terms, the producer fields and the direct bill statements.

What is distinctive about AMS360 data

The vendor page describes client and policy data across the policy lifecycle, with carriers sending new policies, endorsements, claims and renewals directly into the system [1]. It also describes billing and invoicing, payment tracking, account reconciliation and a general ledger, and says commission splits are calculated automatically and shown on statements [1]. The users it names are agents, brokers, CSRs and agency principals [1].

The distinctive feature for an acquirer is how much of the commission side lives in the accounting. An AMS360 agency does not just store a commission rate on a policy. It keeps statements, ledger postings and a commissions payable account for each producer. Vertafore’s help pages describe a report that gives access to the billing and non-billing activity affecting a producer or broker’s commissions payable account, with a reconciliation to the general ledger [4]; it also lists non-billing items such as checks, receipts, journal entries and employee draws that feed the balance [4]. Moving that into a platform’s standard means deciding which of those layers you want.

What the agency can export

Vertafore’s help site is specific about export routes, which is unusual. The page on printing, previewing and exporting a report says File, then Create CSV, exports a report, and that if the option is disabled the report cannot be exported [2]. In the report viewer, the Export Report icon offers Crystal Reports, Adobe Acrobat PDF, Microsoft Excel, Microsoft Excel Data Only, Microsoft Word and Rich Text Format [2]. For an acquirer, "Excel Data Only" and CSV are the two worth asking for, since the others carry formatting that has to be stripped.

A second route is the Custom Data Exporter. Its help page says it exports to Excel, XML, TXT and CSV, that it is an add-on that needs the custom license, and that it ships with eight standard data sets: Active Customers with No Active Policies, Birthday Data, Certificate Information, Commercial Contacts, Company Personnel, Customer Policy Information, Customer Policy Profile and Personal Dependents [3]. The agency can also build its own data sets [3]. If the seller has the license, the Customer Policy Information data set is the likeliest starting point for policies. If it does not, you will be working from reports.

Vertafore’s pages we read do not state a single full-database export for AMS360, so we do not assume one. Ask the agency which of these it has used.

What breaks when you map it to your standard

• Producer and executive naming. The direct bill statement grid in the help pages uses columns called Exec Name, Exec Amt and Exec Comm next to Agcy Comm [5]. Your standard calls this person a producer. A mapping has to say that the executive on the policy is the producer, and what to do when a policy has several.
• Company fields that mean different things. The same grid shows WriteCo and ChgCo, and the customer grid shows Writing Co [5]. Reports that carry several company columns need a decision about which one is the carrier of record in your standard.
• Transaction rows instead of policy rows. The statement grids are lists of transactions with a type, an effective date and amounts [5]. Mapped naively, one policy becomes several rows, and premium double counts.
• Reports as snapshots. A report is a view built for a purpose. The CSV from a production report will not have the fields the CSV from a customer report has, and the two cannot always be joined.

Commission statements next to the export

The help page for reconciling a direct bill commission statement says AMS360 builds a statement of eligible, uncleared direct bill transactions, compares premiums, non-premiums and commissions against amounts already received, and lets staff record what the carrier actually paid [5]. It names Company Statement Totals and Agency Statement Totals and says they should agree before posting [5]. Its totals are grouped by line category: property and casualty, life and health, financial services and other [5].

Paying producers is a separate step. The page on creating a Pay Commission Statement says statements are generated in the Broker Center only for brokers defined as Gross Brokers, and that a statement lists the invoices collected for commission payment [6]. An agency that pays some people on a gross basis and others on a net basis will show both patterns in its files.

What our engine builds for an AMS360 agency

The engine maps each AMS360 report layout the agency sends and stores the mapping under that layout. A CSV from one report and a CSV from another get separate mappings, and the same layout from a later agency reuses the first. It keeps transaction rows apart from policy rows, joins them where a policy number allows it, and lists the ones that do not join.

It checks producer codes against your roster, flags unknown carrier codes with the premium behind them, and reads the carrier commission statements against the mapped book. Variances are listed by carrier. The dashboard then shows the agency beside the others. Your team receives an import file in your layout and an error report and runs the import itself. Details of the statement side are on the commission reconciliation page.

Questions

Compare it with QQCatalyst, Vertafore’s system for smaller agencies, or go back to the systems list. To test a real export, ask for the diagnostic.

AMS360, Vertafore and other names are trademarks of their owners. Loadbearing Software is not affiliated with, endorsed by or a partner of any of them.