Sales tax rules, checked by code.
Sales tax review was manual and slow. I built a read-only agent that applies coded GST/HST rules to the books and writes a review workbook for each client.
Languages
Tools & platforms
AI & LLM
Skills
rules validated against a reviewer's work
clients tested
The thinking behind it
- 01 · What I noticed
The rules were known, but they lived in reviewers' heads, so every review was a little different.
- 02 · What I decided
Write the rules as code, keep the agent read-only, and check its results against a reviewer's finished work.
- 03 · What I delivered
Ten rules that matched a reviewer's output on four clients.
Old system vs new system
- Export transactions
- Check tax on each line
- Apply rules from memory
- Build the review sheet
- Agent reads the books (read-only)
- Coded rules check every line
- Findings written automatically
- Reviewer gets a ready workbook
Watch it run
Click through the four steps. In step 3, click any box to see what it does.
Turning a reviewer's judgment into rules.
Sales tax rules lived in reviewers' heads. Each one had to be written as a clear, testable rule, then checked against a reviewer's finished work before it could be trusted. Ten rules passed that test on four clients; five more were specified next.
Why it's built this way
Read-only access
The agent can check the books but never change them.
Rules as code
Every check is explicit, so anyone can see why a line was flagged.
Validate against real reviews
Results were compared to a reviewer's finished workbooks on four clients.
What made it work
- 01
Write down what experts know
The hardest part is getting the rule out of someone's head.
- 02
Prove it before people rely on it
Matching expert output builds trust faster than any demo.
- 03
Read-only is a feature
An agent that cannot change data is easier to approve.
Have a similar mess? Tell me the step you hate.