BriteCore adds AI tool to convert legacy reports into SQL Editor

BriteCore’s June 23 release, listed as BriteCore_release_2606_2_2, added an AI-assisted migration tool that converts legacy BriteData reports into SQL Editor reports and compares the results before the move is completed. Administrators can verify the deployment by matching the version number in the release notes with the version shown inside the instance through the help icon, and BriteCore says release dates can still shift if final validation turns up problems.

The report migration tool, tracked as BC-22696, lands after two earlier steps in the same reporting overhaul. On March 12, BriteCore said report creation remained disabled while it kept building a translation path from BriteData to SQL Editor. On June 7, it added SQL validation at save time so syntax errors, bad table or column references, and unresolved parameter tokens could be caught before a scheduled job failed. BriteCore describes SQL Editor as part of a broader self-service reporting initiative designed to reduce dependence on BriteCore support or engineering teams, and it says the editor exposes logical views rather than writable raw tables.

The June 23 release also tightened several day-to-day reporting tasks. BriteCore redesigned the report notes page with an always-visible date-range filter and a dedicated New Note dialog, which should cut down on the back-and-forth needed to find and add comments in a busy reporting workflow. Excel exports can now carry configurable totals on a per-sheet basis, a small but practical change for carriers and MGAs that still live in spreadsheet rollups after the report run finishes.

Billing and payments picked up a similar round of incremental changes. BriteCore added state-based convenience-fee settings for Stripe payments, including per-card-type fee formulas and disclosure messages, and says the disclosures appear consistently across payment surfaces so carriers can align behavior in states that ban convenience fees while charging them where allowed. The release also added deep links that prefill the secure payment page with policy number and ZIP code, a change aimed at reducing friction for email, text-message, and QR-code payment reminders.

BriteCore first introduced state-based convenience-fee configuration and debit-card fee control on May 22, and the June 23 update extends that work rather than replacing it. That pattern is the real story here: BriteCore is shipping practical workflow changes in reporting, billing, payments, and admin usability, then layering AI on top of a migration problem that carriers actually face.