During statement-level regression testing I noticed that any policy carrying a premium tax—examples 01N6000098 and 600000000000809—now shows the wrong death benefit on the client statement. The PDF is pulling DEATH BENEFIT VALUE, yet it should reference TOTAL DEATH BENE VAL on Valm D. I need someone experienced with our policy management system’s data layer, statement generation logic (SQL extracts, mapping tables, Jasper / Crystal templates—whatever tool you prefer to work in), and general insurance data structures to: • Trace the field mapping used when the statement compiles. • Update or override it so the statement fetches TOTAL DEATH BENE VAL for any policy where a premium tax flag exists. • Regression-test at least the two sample policies plus one control case with no premium tax. • Supply a brief change log and proof PDFs. Acceptance is simple: the corrected statements must match the values held in Valm D and pass my side-by-side check against the admin screen. Everything sits in our lower test environment, with Git access and database read permissions ready. Let me know how quickly you can jump in and what you’ll need from me to get started.