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.
SubsequentIQ · a RecordStone module
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.
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 youFlagged for a person. Nothing written, no check task raised.
NJ / masked parcel / 2023 · last matched two quarters agoRead-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 groupWhy it exists
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.
How a run works
Build · check · write back · compare · reconcile
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.
Controls
This module touches money and stage. Everything below is a deliberate limit, not a roadmap gap.
A portal disagreement raises a review task. It does not redeem, close or reclassify a lien — a person makes that call, every time.
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.
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.
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.
Writes carry who authorised them and why, recorded next to the run itself rather than reconstructed afterwards.
Read-only by construction. It produces a worklist for a human, and cannot produce an edit.
Coverage
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.
Pricing
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
Questions
Where the honest answer is "not yet", it says so. A monitoring product that overstates its own coverage is worse than no monitoring product.
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.
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.
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.
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.
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
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.
This page describes RecordStone for informational purposes only. It is not an offer to sell or a solicitation of an offer to buy any security, and it is not investment advice.
Descriptions of platform capabilities are representative and do not guarantee any outcome, result, or level of performance. Interface examples and identifiers are synthetic and illustrative. RecordStone supports the governed operating record; it does not replace the official net asset value process.
SubsequentIQ reports what a municipal portal returned on the date it was checked. It is an operational tool and does not determine lien priority, redemption rights, or statutory deadlines.