Architecture and consulting

Billing workflows with traceable ledger entries

Billing workflows connect ledger events, document generation and review controls without exposing client account data.

Built for: SMT Research, Vancouver
Service line: Architecture and consulting
Window: Jun to Sep 2026

The headline numberLedgerAppend-only event historyTechnical capability. Client deposits, balances and billing outcomes are confidential.

01Key numbers

What we measured

LedgerAppend-only event historyTechnical capability. Client deposits, balances and billing outcomes are confidential.

02The situation

What was true before

Billing workflows connect ledger events, document generation and review controls without exposing client account data.

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.

Explicit event types

Store event magnitude separately from its type so the meaning of a ledger entry is unambiguous.

Connect to the actual user workflow

Verify the path users take to generate documents before attaching ledger updates to it.

Sales and Forecasting

How the projection is built

Backlog, remaining to bill on open ordersA

−Marked finished, nothing left to billB

=What the engine spreads across monthsC

+Eligible pipeline, not signedD

=ProjectedC + D

What this number does not vouch for

DatesReview missing or outdated scheduling information.

MappingReview records without a confirmed source-system match.

ValidationResolve flagged records before accepting the projection.

Depiction · A revenue forecast that prints its own arithmetic. Every row carries the method that placed its dollar, so a controller can defend the total line by line.The panel on the right is the part most forecasts omit: the amounts the engine will not vouch for, published beside the number rather than discovered in an audit.

Surfaces built

Walkthroughs use demonstration data. Client records remain confidential.

Ledger event recordsImage withheld
Document generation workflowImage withheld
Reconciliation reviewImage 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.

Ledger event records
Document generation workflow
Reconciliation review

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.6 · Construction billing
docs/research/01-salesforce-platform.md §4 · The hard rule on done

Keep reading

Two more

All case studies

Architecture and consulting
3Systems connectedA technical integration count. Client financial results are confidential.
A forecast with an explanation behind every row
Forecasting combines operational and accounting records through a shared key, with a documented method on each forecast row.
Custom development
28Configuration recordsProvince and tax-class rules stored in custom metadata.
Tax rules maintained as configuration
Tax calculation rules need a shared configuration source that works with both formulas and Apex.

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.