HawkSoft data after an acquisition: what to ask the agency for

Abe Harbid, 26 October 2026

HawkSoft, Inc. calls HawkSoft an agency management system created by independent agents that powers thousands of agencies [1]. The data an acquirer receives is usually a report exported to CSV, plus the agency’s commission settings, which are written in terms of agent positions rather than producers [2][3]. Those positions are the main mapping problem.

What is distinctive about HawkSoft agencies

HawkSoft is run as an independent company and says so on its own pages [1]. Its reporting emphasis is on the agency’s own numbers: the vendor’s page lists reports such as monthly close ratio by producer, policies per client, commissions by carrier and retention, and tracks leads through a sales funnel [4]. A HawkSoft blog on report types describes two auto-generated dashboards, Agency Intelligence and Sales and Retention, plus fully customizable Advanced Reports, and adds that "your reports will only ever be as accurate as the data inside HawkSoft" [5].

For an acquirer, that last sentence is the useful one. An agency that has kept clean client and policy records will export clean files. An agency that has not will export what it has, and the report will not repair it.

What the agency can export

HawkSoft’s import and export page is the clearest statement of formats. On the import side it lists ACORD XML, ACORD Level 3 (AL3) and Tagged File Format (CMSMTF) for creating client files, adding policies or updating policies from a third-party source, and spreadsheets in CSV, XLS or XLSX for carrier commission data [2]. On the export side, it describes a list import/export for commercial lines: a policy’s current list is exported as a CSV template, edited by the insured and imported back [2]. The data it names there is drivers and vehicles for large commercial fleets, scheduled and unscheduled items for agricultural property and inland marine, and certificate holders [2].

The commission blog adds that Quick Reports can be filtered, summarized, shared and exported [3]. The pages we read do not describe a single full-book export. The practical route is to have the agency run reports for clients, policies and commissions and export each to CSV, so ask for those three, with the date each was run.

What breaks when you map it to your standard

• Agent 1, 2 and 3. HawkSoft’s commission article describes commissions in terms of Agent 1, 2 and 3 positions, with the option for Agent 2 and Agent 3 to be paid a percentage of the earlier agent’s commission [3]. Your roster has producers with codes. A policy with three agent columns has to become one primary producer and a split, or several split rows, depending on your standard.
• New, Renew and Rewrite. Rules in the article carry separate amounts for New, Renew and Rewrite terms and can be scoped by carrier, agent, line of business and application type [3]. A flat rate per policy loses that. If your standard has a single new and a single renewal rate, a Rewrite needs a rule for which it counts as.
• Policy overrides. The article says individual policies can have commission overrides, and that rules calculate in list order [3]. Two policies from the same carrier and line can therefore carry different rates, and neither is wrong.
• Commercial lists. Fleet and schedule lists [2] are child records of a policy. Most platform standards have no place for them in the policy import, so the engine reports them as unmapped instead of dropping them.
• Leads beside clients. The vendor’s page describes lead tracking that shows where clients sit in the sales funnel [4]. If lead rows appear in a client export, mapping them as clients inflates the book.

Commission statements next to the export

HawkSoft’s article on commission management in HawkSoft 6 describes how carrier statements are handled. Carrier statements can arrive as carrier downloads that auto-match where possible, as spreadsheets through a Commission Importer, or as manual entry, and PDFs are best converted to CSV or entered by hand [3]. All statements appear in a Reconcile Statements tab, where staff match unmatched transactions, adjust or void entries and complete a reconciliation under a reporting date [3]. Payout to agents is a separate step, from an Agent Payout tab, with per-agent statements in CSV or PDF [3].

Two points matter to an acquirer. Reconciliation is separate from payout, so a statement can be reconciled long before an agent is paid [3]. And the agency reports show commission the carriers paid the agency, separate from commission the agency paid its agents [3]. Your reconciliation should compare the first with the carrier statement and the second with your comp plan, which are different checks.

What our engine builds for a HawkSoft agency

The engine reads each CSV or spreadsheet the agency exports and keeps a mapping for that layout. For the agent columns it asks once how positions become producers and splits, then stores the answer with the layout so the next HawkSoft agency sending the same columns does not repeat it. It flags policies with no Agent 1, codes that are not on your roster, duplicate clients and carriers with no matching code.

Carrier statements are matched line by line against the book in the mapped file. Lines with no policy, and policies with no line in a statement where one is expected, are listed by carrier. The agency then appears on the dashboard beside the rest. You receive an import file in your layout and an error report, and your team does the load.

Questions

See how EZLynx and NowCerts, the other systems small independents use, differ, or return to the list of systems. A diagnostic runs on a real HawkSoft export.

HawkSoft is a trademark of its owner. Loadbearing Software is not affiliated with, endorsed by or a partner of HawkSoft, Inc. or any other company named here.