LensReading which lens this session carries.
All contracts

CTR-TAX · version 2

Indirect Tax Engine — Tax determinations

The oldest validation on the register. A contract validated 33 days ago against a source that releases monthly is a contract nobody has really checked.

RatifiedIn contract

What the contract says

These are the terms the connector is generated against. A source that stops matching them is a drift finding, not a silent data change.

Entity
Tax determination · inbound
Primary key
determinationId
Declared volume
1,900 records a day
Freshness commitment
1 d
Owner
F. Aubert · Tax Technology
Vendor
Vertex · high criticality · modeled
Cardinality
One transaction line to one determination. A re-determination supersedes rather than appends.
Write-back rule
None. Tax determination is authoritative at the engine and the platform records the outcome.

Review state

Neither review is performed by the team that wrote the contract.

Security reviewApproved
M. Lindqvist · Jun 18, 2026
Privacy reviewApproved
Dr. Katrin Wehner · Jul 10, 2026

Validation and drift

Drift is only detectable on a contract that has been read against a sample.

Last validatedJul 16, 2026 · 33 d ago
2,000 records read in the sample.
The oldest validation still standing, and old enough that it should be repeated.

The field list

4 fields · 1 key · 0 personal. The validation rule on each row is what admits or rejects a record at the staging boundary.

FieldSourceTargetTypeFlagsDriftValidation
Determination iddetermination.idtaxLine.refstring(30)
keyinternal
In contractUnique.
Tax codedetermination.taxCodetaxLine.codestring(10)
internal
In contractMust resolve against the code table for the jurisdiction.
Ratedetermination.ratetaxLine.ratedecimal(7,4)
internal
In contractBetween 0 and 1.
Jurisdictiondetermination.jurisdictiontaxLine.jurisdictionstring(20)
internal
In contractDeclared jurisdiction only.

What has passed the staging boundary against this contract

1 batch · 2,840 arrived · 2,722 admitted · 118 quarantined · 0 rejected

BatchArrivedInAdmittedQuarantinedRejectedResultGate
STG-0024Aug 17, 14:002,8402,7221180Partly admitted2,722 admitted · 118 quarantined · 0 rejected outright.

Rejects raised against these batches

1 reason covering 118 records. Each one names a field, what was observed and what the contract expected.

Tax code does not resolve for the declared jurisdiction118 records · 19 h oldFix at source
Observed: 6 codes with no entry in the jurisdiction table
Expected: A code in the jurisdiction table
STG-0024 · field taxCode · queue quarantine · F. Aubert

Replay windows

1 window recorded against this contract.

RPL-009Completed
Source correction · Jul 11, 2026 to Jul 17, 2026
A rate table was corrected retroactively for two jurisdictions.
5,620 replayed · 5,473 held at the idempotence key · 0 duplicates created

Write-back routes into this system

No write-back route is designed into this system.

What this contract is, and what it is not

A contract, a validation rule, a freshness commitment and a replay path are real mechanisms and they are what this wave builds. What they are not is a connection. No connector on this estate is attached to a customer instance, so every batch, every replay and every write-back attempt recorded here ran against a modeled extract or a sandbox, and the registry keeps saying modeled.

The last validation read 2,000 records 33 days ago, which is 105% of a single day at the declared volume. A sample proves the shape of what it read and nothing beyond it.