Bethan Lister

Premium exposure totals not reconciling to CRM

Ticketclosed

Fenmoor Specialty Underwriting: documents logo Fenmoor Specialty Underwriting: documents · Premium exposure totals not reconciling to CRM

Premium Exposure dashboard aggregating incorrectly: submissions with multiple linked claims counted once per claim instead of once per submission. Imogen Hartley identified bug by comparing exported data to CRM records. Fix deployed 19 Aug 2026.

Priority normal

What happened

What this says

Current to 10 Oct 26

Premium Exposure dashboard aggregating incorrectly: submissions with multiple linked claims counted once per claim instead of once per submission. Imogen Hartley identified bug by comparing exported data to CRM records. Fix deployed 19 Aug 2026.

Problem: The Premium Exposure dashboard summary layer was counting submissions with multiple linked claims once per claim rather than deduplicating at submission level, causing month-end reporting totals to exceed CRM figures. This broke Fenmoor's capacity provider validation process.

Handling: Imogen Hartley isolated the bug by exporting sample bordereaux and comparing line-by-line to CRM. Bethan Lister and the data team reproduced it, identified the deduplication error, and deployed a fix to production by 19 Aug 2026. First response was 112 minutes.

AI · claude-haiku-4-5-20251001 · 10 Oct 2026

Details

Updated 9 Oct 26
Prioritynormal
Statusclosed
Categorybug
Channelemail
First response (min)112
Helpdeskmade from

Trail

  1. Imogen Hartley
    created · Imogen Hartley 13 Aug 2026 13:12
    We've spotted an issue in the Premium Exposure dashboard that's breaking our month-end reporting for capacity providers. When we run the query for August underwriting against our bordereaux, the totals don't match what we're pulling from the CRM. The underlying submissions are there and correct, but the sums in the dashboard are running consistently higher across the board. I've had my team check the source data and it's clean on their end. The real question is whether something has shifted in how the brain is aggregating across submissions and linked claims. We need this right because the capacity providers validate against these numbers week to week. Can you take a look?
  2. Bethan Lister
    public_reply · Bethan Lister 13 Aug 2026 15:04
    Just so I've got this right – the premium totals in the dashboard are running higher than what you're seeing in the CRM, and this is specific to August submissions? Can you try exporting the raw data from the brain for one of those submissions and comparing it line-by-line with your CRM? That'll help me see if it's a calculation issue in the dashboard or something in the underlying data. Let me know what you find. Thanks, Bethan
  3. Imogen Hartley
    public_reply · Imogen Hartley 14 Aug 2026 12:12
    Done – I've exported a sample of five August bordereaux and compared them with the CRM. The detail rows are correct; the summary is wrong. The brain is counting some submissions twice. Submissions with multiple linked claims are being aggregated once per claim instead of once per submission. This has to be fixed by end of week or it breaks our month-end reporting. Can you escalate internally? Best, Imogen
  4. Bethan Lister
    public_reply · Bethan Lister 18 Aug 2026 15:47
    I've picked this up with the data team and reproduced it. The summary layer is counting linked claims incorrectly – a submission with multiple open claims is being weighted once per claim rather than deduplicated at submission level. That's the bug. We've got a fix in test and should be live by end of day tomorrow. I'll let you know the moment it's deployed so you can run your August report again. Thanks, Bethan
  5. Imogen Hartley
    public_reply · Imogen Hartley 19 Aug 2026 12:18
    Brilliant, thank you. I'll stand by for the notification and test as soon as it's live. Best, Imogen
  6. Bethan Lister
    status_change · Bethan Lister 19 Aug 2026 14:13
  7. status_change · 23 Aug 2026 23:59
Helpdeskmade from

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations75
People at customers290
BB-Demo staff40
Calls784
Email threads1,169
Support tickets449
Documents477
Deals117
Invoices101
Events49
News items56

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

Ask B

Ask B

B-Brain · read-only