Vertafore Sagitta and BenefitPoint: what an acquirer inherits

Abe Harbid, 26 October 2026

Besides AMS360 and QQCatalyst, Vertafore’s list of agency management products names Sagitta, BenefitPoint and WorkSmart [1]. Sagitta is described as an enterprise system for large, complex agencies and brokerages, and BenefitPoint as management software for benefits businesses [1][2][3]. The two hold different data, so an acquirer should treat them as separate cases.

What is distinctive about these two systems

Sagitta’s page says it centralizes client, policy, accounting and reporting data, and lists "multi-office and multi-divisional support" as an enterprise need [2]. It describes accounting with interdivisional postings, flexible invoicing and detailed payables [2], and the agencies it names are enterprise-level independent agencies and brokerages, including those serving niche markets and specialty lines [2]. The page offers user-defined quick-entry fields, grid displays and accounting workflows as customization [2]. A heavily customized system means the agency’s own field names, which is the main thing to plan for.

BenefitPoint is different in kind. Vertafore’s page says it centralizes client, policy and benefits plan data, serves benefits specialists, account managers, CSRs and agency principals, and cites 2.4 million active accounts and 3.25 million current plans across its users [3]. The page also frames commission tracking as a challenge for agencies running P&C systems for benefits business [3]. WorkSmart is listed beside them with no description on the products page, so we say nothing about it [1].

What the agency can export from Sagitta

Sagitta’s help site documents report export in detail. The Exporting a Report page says the Export option on the print options bar offers Immediate, Overnight and Batch, and that the system creates an XML file in the path set on the Import/Export Personalization page [4]. CSV is offered as an alternative for users with older versions of Excel, but the system must be personalized for it first [4]. Report Builder exports to Excel have their own personalization, set with program ID RB.100 [5].

The help page lists limits that matter for an acquirer. The XML export leaves out the cover page and Grand Totals, keeps only rows and column data, and shows code descriptions that can be deleted [4]. CSV columns do not adjust automatically, division and department numbers with leading zeros show a circumflex, and Excel cells have a 1,024-character limit [4]. If an agency exports and no file appears, the likely cause is missing personalization, since the help page says it must be set up first [4].

Because totals are dropped, ask for the totals separately in a PDF or Screen output and use them as a control. The engine compares row counts and premium sums against the control the seller supplies.

What the agency can export from BenefitPoint

We found no vendor page describing exports from BenefitPoint. Its product page covers carrier statement uploads, file management and AI-based mapping of statement data into the system, and says nothing about taking data out [3]. So the honest request is generic: plan data, group and member counts where the agency holds them, policy and renewal dates, commission and revenue records, and the carrier statements the agency uploaded. The exact export depends on the reports the agency has built.

What breaks when you map them to your standard

• Divisions and departments. Sagitta’s multi-divisional model [2] means one policy can belong to a division, a department and an office. A single "agency" field cannot hold all three. Leading zeros in division numbers [4] also turn into text noise unless the mapping treats them as text.
• Customized fields. User-defined fields [2] mean the same concept sits in different columns at different Sagitta agencies. A stored mapping from one Sagitta agency may match the column names of another only in part, and the engine shows which columns carried over.
• Dropped totals. XML exports omit Grand Totals [4], so there is no built-in check that the file is complete.
• Plans versus policies. BenefitPoint holds plans [3]. A platform standard built for P&C policies has no field for plan, tier or enrolled lives. Those columns are reported as unmapped rather than forced into premium and coverage fields.
• Specialty lines. Sagitta serves specialty lines [2]. Line codes that do not exist on a platform’s list are flagged with the premium they cover.

Commission statements next to the export

Sagitta’s page does not describe a commissions feature as such. It describes a Reconciliation Agent, labelled an Early Adopter program for agency users, that "automatically matches carrier statements to agency transactions" for revenue, commissions and payables [2]. We quote only the description and not the performance figures the page also gives.

BenefitPoint’s page is more direct. It says the platform allows electronic carrier statement uploads, helps identify missing and underpaid amounts and spots short-pay issues, and presents revenue tracking as something P&C systems miss for benefits business [3]. What the statements themselves hold depends on the carrier and the agency.

What our engine builds

For Sagitta, the engine maps each report layout and keeps the mapping, including the agency’s custom columns, so a later Sagitta agency reuses the matches that carry over and is asked only about the ones that do not. It keeps division and department fields as text, flags a file with no control total and compares sums against the one supplied.

For BenefitPoint exports, it maps plans and policies to the parts of your standard they fit, lists what has no field, and matches the statements the agency receives to the mapped records. Both appear on the dashboard by agency and producer beside the rest. Your team receives an import file in your layout and an error report, and loads it. See commission reconciliation.

Questions

See the full systems list for the benefits-focused AgencyBloc, or start a diagnostic on a real export.

Sagitta, BenefitPoint, WorkSmart and Vertafore are trademarks of their owners. Loadbearing Software is not affiliated with, endorsed by or a partner of any of them.