Custom development

Tax rules maintained as configuration

Tax calculation rules need a shared configuration source that works with both formulas and Apex.

Built for: SMT Research, Vancouver
Service line: Custom development
Window: Jun to Sep 2026
Milestone: Rate table live 2026-08-09

The headline number28Configuration recordsProvince and tax-class rules stored in custom metadata.

01Key numbers

What we measured

28Configuration recordsProvince and tax-class rules stored in custom metadata.

02The situation

What was true before

Tax calculation rules need a shared configuration source that works with both formulas and Apex.

Recognise this in your own org?

Start a diagnostic See the service lines

03What we built

The mechanism

The public case describes the implementation. Client financial data and findings are withheld under NDA.

Custom metadata for formula access

Formula fields can reference custom metadata. Effective dates keep rule changes explicit and reviewable.

Regression checks before release

Compare calculation outputs before and after each deployment. Investigate unexpected differences before rollout.

1Quote accepted

2Create order and lines

3Carry the tax code across

4One location and work order per segment

5Raise intake tasks from config

6Fault path: show the real errorAdded

Depiction · The quote-to-order conversion, as rebuilt. Eleven create and update steps, each with a fault path.It had no fault handling at all, so a failed conversion crashed silently and the salesperson could only report that it did not work. The error screen is why they can now say what went wrong.

Surfaces built

Walkthroughs use demonstration data. Client records remain confidential.

Province and tax-class configurationImage withheld
Effective-date controlsImage withheld
Calculation regression checksImage withheld

The finding

Client financial information is confidential.

Amounts, ratios, financial findings and underlying client records are not published.

04Outcome

What changed, verified

The implementation is described through its workflows and controls.

Province and tax-class configuration
Effective-date controls
Calculation regression checks

How it was verified

Validation compares source records with system outputs. Client records and financial results remain private.

Sources

docs/research/01-salesforce-platform.md §2.1 · Tax engine rebuild
docs/research/01-salesforce-platform.md §1 · Configuration in custom metadata
docs/research/01-salesforce-platform.md §5 · Pull quotes

Keep reading

Two more

All case studies

Custom development
GeocodingAddress-to-coordinate workflowTechnical capability. Client sales distribution is confidential.
Salesforce records on an interactive map
An interactive map connects Salesforce records to locations and gives users a direct path back to the underlying record.
Custom development
5 to 6Systems a field technician checked each morningThe recorded before state. No after count was measured, so we do not publish one.
Five to six systems every morning, and a flow that logged nothing
Field crews were opening five or six systems before starting work, and a logging flow was telling them it had saved data when it had saved nothing.

Next step

Bring us your hardest Salesforce problem

Tell us which Salesforce workflow needs attention. Start with a free fit conversation; we agree scope and fees before paid work begins.