ExemptLink
Proposed workflow 05 / Explain the population difference

Your engine. Your GL.
One reviewable bridge.

Compare tax-engine treatment, GL exempt sales and exemption evidence for an agreed period. Give each difference a reason and an owner.

Research-stage concept · illustrative product preview

EXEMPTLINK / MONTHLY RECONCILIATIONCONCEPT PREVIEW
Three populations, one differenceIllustrative GL $16,000, engine $15,100 and sample $16,000 reveal a $900 population difference.Three populations, one differenceDEMO / ILLUSTRATIVE · concept previewGL population$16,000Engine population$15,100Evidence sample$16,000Difference USD 900 / needs reviewSynthetic TX-096 absent from the engine export. No recovered-money claim.
Illustrative mobile scene
GL16,000
Engine15,100
Evidence16,000
Illustrative USD / April 2026

Three populations, one difference

Use a labeled three-row table before the difference note.

Human review required
DEMO — SYNTHETIC DATAFinite sequence · reviewed states
Primary owner

Controller and indirect-tax lead

Inputs

Bounded historical engine, GL and exemption exports with agreed entity/period mappings.

Proposed output

A population bridge, difference register, assigned owner and review status.

The job it owns

Monthly tax-engine versus GL/exemption reconciliation.

Each offer is an independent managed-workflow hypothesis. The initial scope is historical evidence for one US state.

01

Defined cutoffs

Avoid explaining an export-timing difference as an evidence failure.

02

Control totals

Numbers and bar lengths agree with the actual sample populations.

03

No book changes

The proposal produces a review register, with no GL or tax-return write.

The work, step by step

From source to
reviewable output.

01

Align the populations

Agree period, entity, currency, credits, reversals and cutoffs.

02

Trace the difference

Connect each unmatched item to a source row and cause.

03

Assign the review

Record the next action without changing books or returns.

Synthetic product evidence

Three totals.
One explained difference.

The sample’s USD 900 difference is not a tax liability or recovered amount. The 100-sale linkage pilot cannot stand in for a complete monthly GL population.

Open sample report
GL16,000
Engine15,100
Evidence16,000
Illustrative USD / April 2026
STATUS Illustrative / not operatingRESPONSIBILITY

Controller and indirect-tax lead

How value is tested

Measure what your
current workflow misses.

Which reconciliation control already exists, and what incremental review does the pilot add?

Baseline

Existing coverage

Capture current-suite alerts, configured modules and the reviewer’s usual process for the same sample.

Reviewed outcome

Incremental findings

Count tax-lead-confirmed, previously unidentified, remediable gaps. Record false positives, omissions and review effort.

Commitment

A purchase decision

Proceed only with tax-owner sign-off and a signed, funded audit-prep pilot. Stop when the incumbent already closes the job at lower cost.

Read evaluation method
Workflow questions

Know the boundary.

What does the USD 900 example mean?

The fictional engine export omits TX-096. GL and evidence sample totals are USD 16,000; the engine total is USD 15,100. The difference needs review.

Is this included automatically in the first pilot?

No. Each workflow is tested independently. Reconciliation additionally requires properly bounded monthly exports.

Can this workflow change returns or source systems?

No. The starting scope is permissioned historical evidence and human review. The preview does not execute outbound actions or system writes.

A bounded first step

Test this workflow
with your tax owner.

A population bridge, difference register, assigned owner and review status. Start with a scoped conversation before sharing any records.

Discuss monthly reconciliation Proposed pilot · no records required to start