$103.50 (new record, no prior value)
- Authority
- Not publicly citable. The correction was verified against records that cannot be published. See how corrections are published.
- Affected page
- New Jersey record
Change log
Every correction and every fee change enters through a change package with its own evidence and its own application ledger. This page is generated from those packages, and it is filtered through an allowlist so that internal evidence cannot leak into it. 2 packages are on the record, producing 6 published entries.
Change packages contain material that must never be published: internal database references, order numbers, staff names, and company impact analysis. The generator emits only jurisdiction, transaction, entity type, field, old value, new value, effective date, and an authority citation if and only if that authority resolves to an official public source. Everything else is dropped by an allowlist of 7 fields, not a denylist, and a build test fails if an unrecognised field reaches this page.
Where a correction cannot be publicly cited, the entry still publishes and says so. That is more useful than silence, and it is true.
$103.50 (new record, no prior value)
$103.50 (new record, no prior value)
$1,400.00 (new record, no prior value) · effective 2026-07-01
$1,400.00 (new record, no prior value) · effective 2026-07-01
$700.00 (new record, no prior value) · effective 2026-07-01
$700.00 (new record, no prior value) · effective 2026-07-01
Enacted and not yet in force. These live on the forward calendar, because the useful question about a future change is not "what happened" but "when does the number I am using stop being right".
Corrections from readers enter the same queue as everything else: they are triaged, researched against official sources, and either folded into the record with evidence or closed with a reason. The production site carries a report form on every page that writes into that queue.