A changing population.
A BenSelect census for MetLife benefits. Thousands of elections. One complex self-bill.
The census changes monthly. This saved handoff contains 9,791 benefit records and 55 fields.
Broader platform experience. This case begins in Selerix BenSelect, with MetLife as the benefits vendor.
Power Query often froze on these complex bills. Alteryx let us run billing workflows in the background and work on multiple bills at once.
Coverage, rates, age bands, payroll limits—different rules feeding one summary.
Our platform access was limited. I surfaced affected employees and plain-language error labels; the client owned source corrections.
The total has a reason.
Missing details can prevent correct billing. An Errors tab explains the gap instead of leaving the client guessing. Unresolved items stay visible for review.
Why is the bill lower?
Find clarity.
Solve together.
From questioned totals
to trusted expertise.
I became the account’s billing subject matter expert. Clear errors strengthened confidence in Lockton and supported client retention.
Reported outcome. No retention percentage or audited savings claim.
I led automation across complex self-bills and simpler list bills for multiple clients and providers. A week of manual work became a fraction of the effort.
Reported experience; no audited savings total or precise post-automation duration is presented.
Explore more of my workThis is not a fresh query run or native Excel acceptance. The handoff’s LTD mapping review remains open.
The separate contingency preserves vendor formulas and formatting. Desktop Excel acceptance is still pending.
The bill tells the total.
The exceptions tell the rest of the story.
A real billing automation story.
SCROLL TO FOLLOW THE WORKFLOW ↓A BenSelect census for MetLife benefits. Thousands of elections. One complex self-bill.
The census changes monthly. This saved handoff contains 9,791 benefit records and 55 fields.
Broader platform experience. This case begins in Selerix BenSelect, with MetLife as the benefits vendor.
Billing and error handling run together. Multiple workflows move in the background.
Power Query often froze on these complex bills. Alteryx let us run billing workflows in the background and work on multiple bills at once.
Coverage, rates, age bands, payroll limits—different rules feeding one summary.
The automation flags missing details and duplicates. Every exception has a cause—and an owner.
Our platform access was limited. I surfaced affected employees and plain-language error labels; the client owned source corrections.
The total has a reason.
Missing details can prevent correct billing. An Errors tab explains the gap instead of leaving the client guessing. Unresolved items stay visible for review.
From defending a total to explaining the cause. Less rework. Stronger client relationships.
Why is the bill lower?
Find clarity.
Solve together.
From questioned totals
to trusted expertise.
I became the account’s billing subject matter expert. Clear errors strengthened confidence in Lockton and supported client retention.
Reported outcome. No retention percentage or audited savings claim.
I led automation across complex self-bills and simpler list bills for multiple clients and providers. A week of manual work became a fraction of the effort.
Reported experience; no audited savings total or precise post-automation duration is presented.
Explore more of my workThe vendor’s format stays intact. Exceptions arrive with a clear reason.
This is not a fresh query run or native Excel acceptance. The handoff’s LTD mapping review remains open.
The separate contingency preserves vendor formulas and formatting. Desktop Excel acceptance is still pending.
The bill tells the total.
The exceptions tell the rest of the story.
Every client has a different mix. I work across their vendors, administration platforms, and BI systems to turn complex data into useful answers.
Encrypted-data illustration · No real records or live connections. Platform and vendor combinations vary by client.
Scope access to the people and systems doing the work.
Use protected channels and treat sensitive data deliberately.
Preserve source data and make processing and exceptions traceable.
Less repetition.
More room for the client.
Find the discrepancy.
Bring the evidence.
I used Power BI to dynamically reference census and billing across client folders. Original files stayed intact. Patterns became visible.
Reference in place.
Preserve the originals.
Compare expected coverage with billed participants and periods.
Baseline holds the prior month’s cost per person constant. Review signal, not a validated bill. Dollar axis is cropped to show changes.
Select the review question to locate the difference in the charts. The view stays right here.
A signal becomes a better conversation.
Difference to the Sep comparison.
A reason to investigate.
Reconcile terminated coverage and effective dates against the vendor list.
Bring the enrollment evidence and request a billing correction if confirmed.
Reference in place.
Preserve the originals.
Baseline holds the prior month’s cost per person constant. Review signal, not a validated bill. Dollar axis is cropped to show changes.
Compare the premium with enrollment, then bring the next step. A review signal is not a confirmed billing error.
Leadership adopted the dashboard to see across the practice as the automations ran.
REPORTED EXPERIENCEAn analyst who builds the system, finds the signal, and brings the next step.

Analyst. Builder. Designer.
One person. Many possibilities.A distinctive website. A smarter workflow. Software that earns its place.
The person behind the projects.