Policy quote amounts showing incorrect values
Ticketclosed
Clonvara Insurance Services: documents · Policy quote amounts showing incorrect values
Transaction amounts showing wrong values due to decimal formatting bug in CRM import; about 50 records affected; rollback queued.
Priority low
What happened
What this says
Current to 11 Oct 26Transaction amounts showing wrong values due to decimal formatting bug in CRM import; about 50 records affected; rollback queued.
Problem: Policy renewal quotes showing significantly lower amounts in brain than in source CRM; affecting revenue tracking. Handling: Very slow first response (640 minutes). Bethan diagnosed decimal formatting bug in transaction field; escalated to engineering for rollback of approximately 50 affected records. Watch: Financial data corruption is critical.
Details
Updated 9 Oct 26Prioritylow
Statusclosed
Categorydata_quality
Channelweb
First response (min)640
CSAT5
Helpdeskmade from
Trail
created · Cian Farrell 3 Sep 2026 10:10We're seeing some unusual data in our broker activity records, it looks like some transactions are showing the wrong amounts. For example, several policy renewal quotes are showing less than what we actually quoted to the clients. This is throwing off our revenue tracking. Can you check what's happening?- public_reply · Bethan Lister 3 Sep 2026 20:50I've picked this up, Cian. Just so I've got this right, you're seeing transaction amounts that don't match what's in your source system? Can you try something, can you run a search for one of the transactions you know is wrong and tell me what amount you see in the brain versus what you see in your CRM? That'll help me figure out if it's a data sync issue or something else. Thanks, Bethan
- public_reply · Cian Farrell 4 Sep 2026 10:33I checked one example, a policy quote is showing a significantly lower amount in the brain than it shows in the CRM. So it's definitely something on the sync side.
- public_reply · Bethan Lister 8 Sep 2026 10:38I've checked the logs, Cian, and I found the issue. There's a formatting problem with how decimal places are being handled in that particular field when we import from your system. It's rounding amounts inconsistently. I've identified which records are affected and I'm working with the engineering team to roll back those specific records to the correct values. You should see them corrected in the next refresh. Thanks, Bethan
- internal_note · Bethan Lister 8 Sep 2026 10:55Escalated to Kieran, decimal formatting bug in transaction amount field. About fifty records affected in current dataset. Rollback needed before next refresh. Customer notified of timeline.
- status_change · 12 Sep 2026 23:59
Helpdeskmade from