SubsequentIQ · a RecordStone module

Know a lien redeemed before you pay its taxes.

On a New Jersey lien you have to keep paying the property's municipal taxes to protect your position — quarterly, per parcel, at amounts only the municipality's own portal knows. SubsequentIQ makes the lookup, writes the amounts back to the record, raises the check with a date, and compares the portal's holder and status against your own record so a quiet redemption does not stay quiet.

Holder & status review Illustrative
Redeemed · active
Portal shows this certificate redeemed

Your record still has it accruing, and a subsequent payment is scheduled against it. Review task raised; no stage changed.

NJ / masked parcel / 2024 · portal holder — not you
scheduled subsequent · due in 9 days
Holder changed
Portal names a different holder of record

Flagged for a person. Nothing written, no check task raised.

NJ / masked parcel / 2023 · last matched two quarters ago
Duplicate parcel
Two liens on one parcel, both carrying value

Read-only finding. Likely a legitimate multi-year position — it needs a human call, so it becomes a worklist item, not an edit.

NJ / masked parcel / 2022 · multi-certificate group

Why it exists

The clerical part is annoying. The invisible part is expensive.

Subsequent taxes are real capital deployed on top of a lien you already own. Get the number wrong and it costs you a quarter. Not knowing the lien changed hands costs you the whole payment — and the time to unwind it.

Nothing announces a redemption to the holder. The certificate closes at the municipality, the quarterly process runs on unchanged, and the error stays invisible until somebody reconciles.

  • Silent redemption A certificate redeems at the municipality. Your record still says accruing, so the next quarterly run pays subsequent taxes on a position you no longer hold.
  • Holder drift An assignment, a sale, a clerical correction at the municipality. The portal's holder of record and your own record disagree, and a manual process never compares the two.
  • Manual lookup Four portal visits per parcel per year — find it, read it, retype it, remember to raise the check. Exact, repetitive work, and where the transcription errors live.
  • Duplicate positions More than one lien on the same parcel can be a genuine multi-year position or a double count. Told apart by hand, it is usually told apart late.

How a run works

Build · check · write back · compare · reconcile

Five steps, quarterly, against your own book.

The run drives a real browser across the municipal portals, writes the amounts back to the record, and hands every judgement call to a person. Step four is the one that pays for the other four.

  • Municipality names normalised to the right portal, not the nearest match
  • A failed read is reported, never written as a number
  • Every write logged with its prior value, so any run can be reversed
  • Disagreements become review tasks — never automatic stage changes
Quarterly run / sequence
01 · Build the input Active liens pulled from the record; each municipality normalised to its portal name.
02 · Check the portal Each parcel visited on the municipality's own system. No-match, multi-parcel and login-wall outcomes are typed, not guessed.
03 · Write back, raise the check Tax due, utility due, total due, good-through and last-checked land on the lien, with a dated task for the payment.
04 · Compare holder and status Portal versus record. Redeemed-but-active sorted to the top, because that is the one that costs money.
05 · Duplicate-parcel hygiene Read-only. Parcels carrying more than one lien are grouped and classified into a worklist.
InputYour record
SourceThe municipality
OutputAmounts & exceptions

Controls

The restraint is the feature.

This module touches money and stage. Everything below is a deliberate limit, not a roadmap gap.

CTRL / 01

Never moves a stage

A portal disagreement raises a review task. It does not redeem, close or reclassify a lien — a person makes that call, every time.

CTRL / 02

Never writes a guess

If the read fails, or the detail page disagrees with the summary page, the amount is held back and reported as unverified rather than written.

CTRL / 03

Preview on demand

Any run can be executed as a preview first, writing nothing and producing the same file of proposed changes for review before it is authorised.

CTRL / 04

Every write reversible

Each created or updated field is logged to a run manifest alongside its prior value, so a quarter's run can be reviewed or unwound.

CTRL / 05

Attributed and approved

Writes carry who authorised them and why, recorded next to the run itself rather than reconstructed afterwards.

CTRL / 06

The duplicate scan never writes

Read-only by construction. It produces a worklist for a human, and cannot produce an edit.

Coverage

New Jersey today, portal by verified portal.

Coverage is a registry, not a claim. Every municipal mapping carries the date it was last verified, and a municipality that is not mapped is reported as unmapped rather than silently skipped. Another state needs its own adapter — portal discovery, municipality normalisation, lookup-key formats and validation — built and proven before it is offered.

  • 508 municipal portal mappings, each with a verification date
  • 487 on the WIPP platform, 21 on other systems
  • One state. New Jersey. No other state is offered today
  • Scheduled ahead of the Feb 1 · May 1 · Aug 1 · Nov 1 due dates
Portal registry / coverage
Municipal mappings registered 508 — each with a last-verified date
Platforms 487 WIPP · 21 other
States offered One — New Jersey
Cadence Quarterly, ahead of the due date
Unmapped municipality Reported, never skipped in silence
RegistryDated
ScopeStated
GapsVisible

Pricing

Priced per monitored lien, per year.

Not per seat. The cost of delivery scales with liens, not with users — every monitored lien is four portal visits a year whether one person or twenty look at the result. Seat pricing would punish a small team with a large book and subsidise a large team with a small one.

It is also the unit you already think in. You know how many New Jersey liens you hold.

Per monitored lien, per year

One subscription, sold on your RecordStone tenancy. Priced against the size of the book being monitored, with terms for servicers administering several books.

Every subscription includes

  • Quarterly portal refresh across your mapped municipalities
  • Amounts written back to the record, with dated check-cutting tasks
  • Silent-redemption and holder-change alerting
  • Duplicate-parcel worklist, read-only
  • Unmapped-municipality and portal-error reporting
  • Full run manifest with prior values, for review or reversal

Questions

The things people actually ask.

Where the honest answer is "not yet", it says so. A monitoring product that overstates its own coverage is worse than no monitoring product.

Do I need RecordStone to use it?

Yes. SubsequentIQ is a module sold on the RecordStone platform, not a standalone product. It reads and writes your liens where they already live, which is what lets it compare the portal against your own record rather than against a spreadsheet.

Will it change my data without asking?

It writes the tax amounts, dates and portal stage it read, and it raises tasks — that is the fill you are subscribing to, and a scheduled quarterly run performs it. What it will not do is act on a disagreement: it never moves a lien's stage. Any run can be executed as a preview first, and every write is logged with its prior value so it can be reversed.

What happens when a municipality changes its portal?

The affected parcels are reported as portal errors rather than written with wrong numbers, and the mapping is re-verified. Portal drift is expected and handled as maintenance, not as an outage.

Can you cover states other than New Jersey?

Not today. Each state needs its own portal adapter before it can be offered. If you hold paper elsewhere, tell us where and we will tell you honestly what it would take.

How do you handle a parcel the portal will not return?

It is reported, not guessed. No-match parcels, multi-parcel results and login walls each get their own outcome, so you can see exactly what was and was not checked in a given run.

Executive Briefing

Bring us the book. We'll show you what a run surfaces.

Tell us the state and roughly how many liens you hold. We will walk through what SubsequentIQ covers today, what it does not, and what a quarterly run would put in front of your team.