Types

The person who acted. Null when retrieve-IQ acted on its own, as for a nightly fetch.

When it happened.

The id of this record. Not a Node id: node does not accept it.

The details as structured data. The shape depends on the event.

The event in one sentence.

The city.

The county, where the county publishes it.

The street address.

A suite or unit, where there is one.

The ZIP code.

The two-letter state code.

When it was created.

When it stops working. Null for a key with no last day.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

When it was last used, to the minute. Null until it has been.

What it is for, as named when it was created.

riq_ and the next eight characters of the secret, to tell keys apart.

When it was revoked. Null while it stands.

What the key may do, within what the firm itself may do.

Whether it works.

The key.

The secret, shown once and never stored. Put it where your system will read it now.

The value as first certified for the year. Null when no assessment is held for it.

The year of the assessed value under appeal.

When it was recorded.

The last day to file. Null where the unit sets it from an event whose date is not on record; deadlineReason says why.

Why deadlineOn is null, in words. Null when there is a date.

rule, when the date came from the unit's filing window; user, when a person entered it.

When it was decided. Null until it is.

The value the board set. Null until decided.

When it was filed. Null until it is.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

A note for whoever reads the appeal next.

The person who recorded it.

The parcel under appeal.

The year the bill on that value falls due.

The value the appeal asks for. Null when none was recorded.

When the unit's rules say the window closes, whatever date the appeal holds (updateAppeal with deadlineFromRule puts it back); null where the rules give no exact date.

The tax saved, as entered from the corrected bill. Null means not yet known, never zero.

Where the appeal stands.

The assessed value minus the decided value; negative when the board raised it. Null until decided, or without an assessment.

Moves on every change to the appeal. updateAppeal, updateAppealStatus and recordAppealOutcome take the version their caller read as expectedVersion, and are refused with CONFLICT when it has moved.

The provision, as the source numbers it.

The requirement's stable key within its unit.

The first assessment year it governs.

The last assessment year it governs; null while it still does.

Earlier versions of it, newest first. Empty for one that never changed.

The unit that holds the requirement.

When this version was written.

The requirement in a sentence or two.

Where it comes from.

A link to the source itself, where one exists.

What part of the filing it is about.

When a person last confirmed it; null means nobody has.

Who confirmed it.

How many times it has changed, counting from 1.

The closing rule as recorded. Null when none is recorded, or the unit sets the date each year.

The last day to file, YYYY-MM-DD. Null when the rule does not yield a date; never guessed.

The opening rule as recorded. Null when none is recorded, or the unit sets the date each year.

The first day to file, YYYY-MM-DD. Null when the rule does not yield a date.

exact, or no_earlier_than or no_later_than when one side of a later-of or earlier-of rule is an event whose date is not on record: a bound, not the deadline.

Why closesOnDate is null, in plain words.

The unit whose rule answered: the unit itself, its parent, or the state.

Where the closing rule came from: the statute or the unit's own notice.

When a person last confirmed the closing rule. Null means not yet verified.

Open appeals left out for want of an assessed value, a requested value or a billed year to take a rate from.

Decided appeals the achieved share was learned from.

The estimate. Null with no decided appeals to learn from, or nothing to sum.

Appeals at OPEN or FILED.

Achieved reduction over requested reduction, across decided appeals.

The year the value was set, which an appeal contests.

When the unit certified the value, where known.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

The assessed value of the buildings and other improvements.

The assessed value of the land.

The year the bill on this value falls due: the same year in most states, the year after in some (Cook County, Illinois).

Zero today for every assessment: a value read again replaces the figure on the same revision. Higher revisions are reserved for a correction recorded as one.

Land plus improvements.

When the nightly fetch accepted it.

Why, in words for the customer.

The page's records, each with the cursor that continues from it.

Whether more follows, and the cursor to continue from.

Bills matching the filter, across every page.

Pass this as after to continue from this record.

The record.

The installments of the bill stored, in order. Empty unless the outcome is STORED.

What happened, in a sentence the person reads.

Whether a bill was stored, kept as evidence only, or already on file.

How many units of that level send a bill.

The kind of unit: county, city, town, township, school_district and so on.

The bill after the review. Null when none of the installments named was visible.

The installment ids the review could not act on. Empty when it acted on every one.

When it was created.

The person who created it.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

Where it is used, as named when it was created.

When a calendar app last read it. Null until one has.

When it was revoked. Null while it is in force.

The feed.

Subscribe to this in Outlook, Google Calendar or Apple Calendar. It is not shown again.

Attempts in the last 24 hours.

Of those, how many failed.

The county.

When the county last answered, with a bill or with NOT_FOUND.

When a fetch was last attempted there.

How the newest attempt ended.

When a bill was last fetched there.

Parcels of the portfolio in the county.

How many attempts in a row have failed, counting back from the newest. Zero when the county answered last.

What is owed to this unit, and how complete that figure is.

The unit that bills, which need not be the unit that assesses the parcel.

Distinct parcels this unit bills. A parcel billed by three units counts once in each.

Every unit with a county FIPS code, for a county map: the county-level units, Alaska's census areas and the regions that stand for counties where the county does not govern (Connecticut, Massachusetts, Rhode Island).

The county-level units only, which is the headline figure: counties, parishes, independent cities and Alaska's boroughs.

By state, in code order.

Every registered unit in the country.

The named units, of any level; a code the registry does not hold is left out. At most 500 at a time.

At ASSESSMENT_ONLY.

At CLOSED.

At COVERED.

At NO_PORTAL.

At NOT_SURVEYED.

At OTHER.

At PORTAL_FOUND.

At READER_READY.

At RETIRED.

All of them.

Whether the unit sets assessed values.

Whether the unit sends a property tax bill of its own.

A county, parish, independent city or one of Alaska's boroughs: the units the headline figure counts.

The five-digit county FIPS code, for a county or its equivalent.

The kind of unit: county, city, town, township, school_district and so on.

As the unit names itself.

Every site recorded for the unit, the one that decided the status first.

The two-letter state code.

Whether the unit's bills can be fetched.

The code of the unit, as Jurisdiction.unitCode has it.

The software behind the site that decided the status.

When a person acknowledged this date; null until then, and again once the date moves.

The person who acknowledged it.

The assessment year the date belongs to.

What is at stake: the balance still owed, for a payment date. Null when the balance is unknown, and for an appeal date; never read a null as zero. The dates are read with PARCEL_READ; the balance is bill data.

When this date was worked out.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

For a payment date: the unit the bill is owed to. For an appeal date: the unit that assesses the parcel and hears the appeal, or, for the unit's own window, the unit itself.

What the date is.

The date. Null when the rule could not be evaluated; unevaluableReason says why.

True for a payment date whose installment the county publishes no payment figure for and the customer's own records show paid in full: the date stays, marked, since the county has not confirmed it. Bill data, as exposure is.

The parcel the date belongs to. Null for a date that belongs to the unit rather than to a parcel: the unit's own appeal window, which stands whichever parcels it assesses.

For an appeal date: exact, or no_earlier_than or no_later_than when one side of a later-of or earlier-of rule is an event whose date is not on record. A bound, not the deadline.

For an appeal date: the unit whose rule answered (the unit, its parent, or the state).

BILL for a payment date read off a bill; JURISDICTION_RULE for an appeal window from the assessing unit's rules.

The date or reason this one replaced, when it moved; null for a date that never changed.

For a payment date: the account the bill belongs to. Null for an appeal date, which belongs to the parcel however many units bill it.

Why there is no date, in words.

The date it had before; null when it had none.

Why it had no date before, when it had none.

When the dates were last generated. Null before the first time: the portfolio has no dates yet.

A change saved since generatedAt (a bill, a correction, a payment, a parcel, a night's fetch, or a rule or notice date the appeal windows are worked out from) is not in the dates yet. They are regenerated when someone who may read bills next opens them; a reader who may not reads them as they stand.

Its size in bytes, where known.

GET this path, with the same Authorization and X-Engagement-ID headers, to read the bytes. HTML from a county is served in a sandbox.

Every reading of the document.

When the file was removed, seven years after it arrived, whether a person uploaded it or it was read from a county site. Null while it is kept. What was read from it stays, and so does the record that it was removed.

The name it was fetched or uploaded under.

Whether a bill was read from this document, by the product or entered by hand. A tax bill without one is evidence a person may enter by hand (enterBill).

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

What the document is.

What the file is, as recognised from its bytes when it arrived; null for a document kept from before that was recorded.

Its page count, for a PDF.

The parcel the document belongs to.

When it arrived.

How it arrived: portal for a page read from the unit's site, upload for a file a person added. email and sftp are reserved.

The county page it was fetched from. Null for an upload.

The person who uploaded it; null for a document read from the unit's site.

When the link stops opening: five minutes after it was made.

Where the document opens, on this API's host. It holds the link's secret.

When the link stops taking the bytes: fifteen minutes after it was made.

The largest file this environment takes.

The HTTP method to send them with: PUT.

Where to send the bytes, on this API's host. It holds the link's secret, so it is shown once.

The firm that works on it.

Whether authorisedOn, authorisationRef and grantedBy are all on record. False means the engagement was approved before approvals were recorded.

Where the written approval is kept: a reference, never the document.

The day the client gave its written approval; null on an engagement approved before approvals were recorded.

The client whose portfolio it is.

The first day the engagement is in force.

The last day the engagement is in force. Null for one with no end date.

The value to send in the X-Engagement-ID header. Not the same as id.

Who at the client gave the approval, as written on it.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

Whether the engagement is in force today: not revoked, begun and not yet ended. One that has lapsed or been revoked is still listed, so the client is not mistaken for a deleted one, but a request under it is refused with FORBIDDEN.

When it was revoked; null while it stands. A revoked engagement is not live whatever its dates say.

Why it was revoked, as recorded when it was.

What the firm may do for this client. A key may do what both its own scopes and the engagement's allow.

Where on that page: [left, top, right, bottom] as fractions of the page's width and height, from its top-left corner.

Null when the reading is exact: a county's own text read by its reader, or a person's entry. A number in [0, 1] only from a model.

The element of the county's HTML page it was read from.

Which figure it is, as a path: "totalBilled", "installments.amountDue", "lineItems.amount".

Which one, for a figure that repeats: an installment's number, a charge's place from 1.

The page it was printed on, from 1, for a PDF.

The figure as printed, or as the person entered it.

When the reading was made.

The person, for a reading a person made; null for one the product made.

A short code for the program that read the document; null for a reading a person made.

Why the reading could not be believed, when it could not.

The figures it took, each with where it was printed.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

The size of each page it read, for a PDF, so each figure can be shown where it was printed.

When a person confirmed the reading.

The person who confirmed it.

How far the reading has got.

Its place among the document's readings, oldest first.

Where the files went: an SFTP host, an S3 bucket or a folder.

The feed, as named in its setup.

When it finished. Null while it runs.

The id of this record. Not a Node id: node does not accept it.

What happened, in words, when something did.

How it ended.

When the night started.

Bills retrieve-IQ is checking before you act on them (TaxBill.retrieveIqCheck). They are not in the queue.

Waiting bills with an installment flagged for the client, which makes the bill DISPUTED.

Of this week's pages, how many could not be read: nothing was taken from them, and each needs a look.

Waiting bills at NEEDS_REVIEW.

Bill pages and files received in the last seven days.

Waiting bills an ERROR check stands against.

What an appeal filed here for that assessment year needs beyond its dates: the form, the agent's authorization, what the application says, where it goes. Empty when nothing is recorded.

The appeal filing window for an assessment year, from the unit's own rules, then its parent's, then the state's.

Whether this unit sets assessed values and hears appeals.

How the unit makes its bill available.

Whether this unit sends a property tax bill of its own.

The five-digit county FIPS code, for a county or its equivalent.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

How many installments the unit splits its annual bill into.

The office that collects the tax, as the unit names it: "Treasurer-tax collector".

What the unit is: state, county, independent_city, city, town, township, village, borough, parish, school_district, special_district or region. A state holds statewide defaults and neither assesses nor bills.

As the unit names itself: "Los Angeles County".

How many parcels of the portfolio this unit assesses or bills, which is what ParcelFilter.jurisdictionIds returns for it. Not the number of parcels in the unit.

Every kind of dated rule for an assessment year, in the order a filing season runs, each with the evidence behind it. A kind nobody recorded is listed as NOT_RECORDED, never left out.

The two-letter state code.

A stable code for the unit: US-CA-FIPS-06007 for a county with a Census code, US-CA-STATE for a state, a code of the state's own scheme for a unit below the county.

The assessment year it was worked out for.

YYYY-MM-DD, after the weekend rule; null unless status is DATED or BOUND.

Which dated rule it is.

exact, or no_earlier_than / no_later_than for a BOUND date.

Why there is no date, in plain words.

The unit whose row answered.

The stored rule that answered; null when none is recorded.

Every stored rule of this kind the unit, its parent and its state hold, the one that answered among them.

Whether there is a date, and if not, why not.

The date the rule itself names, when the weekend rule moved it (a Saturday, Sunday or federal holiday); null when nothing moved.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

The name on the roll.

The last four digits of the tax identification number on file, or null when none is. The whole number is never returned.

What is owed on the bills of the entity's parcels, counted as amountOutstanding counts: unknown and withheld installments set aside and said.

The newest assessment of each of the entity's active parcels, summed: the same rule as PortfolioSummary.totalAssessedValue, so the entities add up to it. "0.00" when none is assessed.

The newest assessment year behind that figure. Null when none of its parcels is assessed.

The owner of record.

Every parcel filed to the entity, whatever its status: what the parcel list filtered by the entity shows.

As it stands now, with the last four digits of its number.

How many installments the figure covers. Zero means no bills are held, which is not the same as owing nothing.

Of the installments with no published payment, how many the customer's own records show paid in full. Said beside the figure, never added into it: the county has not confirmed them.

Installments left out because the county publishes no payment figure for them.

The sum over the installments whose payment figure the county reports.

Installments left out because a check stands against their bill: pending review, neither settled nor unknown.

The last record's cursor: pass it as after for the next page.

Whether another page follows this one.

Whether a page precedes this one.

The first record's cursor.

Its height in points.

Its width in points.

The parcel's activity trail, newest first.

What is still owed on this parcel, and how complete that figure is.

Every appeal recorded on the parcel, newest year first.

The assessments on record, newest year first.

The parcel's bills, newest year first.

The newest assessment on record. Null until one is held.

The parcel's payment and appeal dates: one per installment, and the appeal window of the newest year that has a bill. A parcel with no bill yet has no appeal dates.

Every document held for this parcel, newest first.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

The unit that assesses the parcel and hears its appeals. The units that bill it are on taxAccounts.

The owner of record the parcel is held under.

The soonest payment date that costs money if ignored: a penalty date already passed with a balance known to be owed, otherwise the earliest penalty or due date from today on. A passed date whose payment the county does not publish is not returned. Null when nothing is owed or coming.

As the county writes it: the APN in California.

The property's street address.

Where the parcel stands in the portfolio.

The units that bill this property and the numbers they know it by: active first, then oldest first. Empty for a parcel whose billing units are not yet known.

The county's use code for the property, where it publishes one.

The parcel offered.

Why it was offered, in words.

In [0, 1], to order the candidates; it decides nothing.

The page's records, each with the cursor that continues from it.

Whether more follows, and the cursor to continue from.

Parcels matching the filter, across every page.

Pass this as after to continue from this record.

The record.

Parcels added.

True when nothing was written.

Rows whose parcel was already held; nothing changed for them.

The owner of record the parcels were held under. Null on a dry run.

Rows that were not imported, with the reason for each.

Which row: zero-based, into the rows given.

Why it was rejected, in words.

Rows that named an observation already on record; nothing was written for them.

True when nothing was written.

Rows recorded; on a dry run, the rows that would be.

Rows that could not be recorded, by index in the input, with the reason.

When the row's number matched no parcel exactly, or more than one: the parcels it may mean, strongest first, for a person to choose by sending the row again with parcelId.

Its place in the rows sent, from 0.

Why it was refused, in words.

Positive for a payment or a refund; signed for an adjustment.

The day the money moved.

The entry, for telling one from another. Not a Node id.

A payment, a refund or an adjustment.

A note recorded with it.

When it was recorded.

The person who recorded it, or who sent the list it came in with.

A check number, a confirmation, a ledger line.

Whether a person recorded it or a list brought it in.

When the site was first recorded.

The site's host name.

Supported and waiting only for a final live check.

Why it cannot be fetched from, when it cannot.

Its standing.

Where bills are looked up. Null when there is no site.

The software the site runs, by name.

When a bill was last fetched from it in a live check.

An estimate of what the open appeals could save.

The newest assessment year behind that figure. Null when nothing is assessed.

The same, by state.

Distinct units that bill a parcel in the portfolio: the number of rows countiesInPortfolio returns. A Pennsylvania parcel counts three.

Parcels in the portfolio.

The total of the newest assessed values.

The installment, with its payment records.

False when the same observation was already on record.

Which group it belongs to.

The column headers, in order.

What it contains.

The formats it can be produced in; requestReport refuses any other.

The value to request it by.

Its name, as the app shows it.

The scopes the report reads with, needed beside REPORT_READ to request it: a key or an engagement without one of them is refused, and a report already queued fails if its access loses one before it runs.

The size of the file in bytes, once done.

GET this path, with the same Authorization and X-Engagement-ID headers, to save the file. Only while DONE; null otherwise.

Why it failed, in a sentence: the access it was requested under ended or does not cover the report, or it could not be produced and should be requested again. Quote the job id when you ask retrieve-IQ about it.

Which parcels the report covers, in words: a county, an owner or an appeal by its name where you may read it.

When it finished, done or failed. Null before that.

The file format asked for.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

Which report.

The report's name.

When it was requested.

Who requested it.

How many rows the report holds, once done.

Where the report is.

The provision it cited then.

When this version was written.

The requirement as it read then.

Where it came from then.

A link to that source, where one existed.

When the next version replaced it.

When a person had last confirmed it; null meant nobody had.

Who had confirmed it.

Which version it was, counting from 1.

The bill after the resolution, no longer withheld if this was the last check standing.

The check, now resolved.

The words of whoever reported it, or retrieve-IQ's.

Why retrieve-IQ is checking it.

When retrieve-IQ began checking it.

The assessment year it is about.

When it was filed.

Where they saw the right value, if they said.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

The unit whose rule the report is about.

What the person said is wrong.

The person who filed it.

What the people who maintain the rules found.

When it was answered; null while it is open.

The version of the rule row the report was filed against; null when no row was recorded.

The rule or requirement as the product showed it at filing: expression, date, status, source, version.

Where it stands.

What it is about.

What they said it should be, if they said.

Whether this is the row that answers for the year asked about.

The first assessment year the row governs.

The last assessment year it governs; null while it still does.

The rule as written (07-02, 11-30+1y, assessment_notice + 30d, 4th tuesday of may, later_of(a, b)). Null means confirmed to be set locally each year.

Earlier versions of this row, newest first. Empty for a row that never changed.

The unit that holds the row: the unit itself, its parent, or the state.

Which dated rule it is.

A note on the rule from the people who maintain the rules.

When this version was written.

Where the rule came from, as the dataset names it.

A link to the source itself, where one exists.

When a person last confirmed the row against its source; null means nobody has.

Who confirmed it.

How many times the row has changed, counting from 1.

What happens to a date on a weekend or a holiday.

The last assessment year it governed then; null meant it still did.

The rule as it was written then; null meant set locally each year.

Its note then.

When this version was written.

Where the rule came from then.

A link to that source, where one existed.

When the next version replaced it.

When a person had last confirmed it against its source; null meant nobody had.

Who had confirmed it.

Which version it was, counting from 1.

What it did with a date on a weekend or a holiday.

Documents whose filename matches. Empty, not an error, for a key without BILL_READ.

Units whose name matches and that the portfolio holds parcels in.

Parcels whose number or address matches.

The units that send a bill of their own, by level, most first. In Connecticut these are towns and cities, not counties.

Every unit in the state.

The county-level units only: counties, parishes, independent cities and Alaska's boroughs.

The state's name.

The two-letter code.

The total of their newest assessed values.

Parcels in the state.

The two-letter state code.

The unit's own identifier for the property: the APN in California, block and lot in New Jersey, the control number in Pennsylvania, the SBL in New York.

When the account was recorded.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

The unit that bills the property under this account.

How the account came to be known: parcel (created with the parcel, for the unit that assesses it), import, api, fetch (a county record named the other units that bill the property), reference (the registry of taxing units), or a value beginning backfill for accounts recorded before origins were kept.

The parcel the account is on.

Whether the unit still bills the property under this account.

Set when the nightly fetch accepted this bill without a person, with the reason. Null when a person accepted it or it is not accepted.

What is still owed on the bill, and how complete that figure is. Null while the bill is withheld, as totalBilled is.

The annual total as the county stated it: the figure the charges and the installments are checked against. Null where the county printed none, and while withheld.

The year of the assessed value the bill is based on.

The county's own bill number. Null where the county publishes none.

Which roll the bill is on.

The county's charges for the year, which belong to the bill and not to one installment. They add up to chargesTotal.

The charges summed: what the year is made of. Null while withheld.

The bill's installments, first first.

The installments summed: what is owed and when, as the county split the year, which may carry penalty a county folded into an installment (penaltyIncluded). Null while withheld.

Tells the bills of one parcel apart, each revision its own. Opaque and stable across requests; not an id that node or bill accepts.

What the customer's own records say was paid on the whole bill: the sum over its installments. Null when no installment has anything on record.

The parcel the bill is for.

The year the bill falls due.

Penalty a county folded into an installment's amount (penaltyBasis INCLUDED_IN_AMOUNT_DUE), summed over the installments. Already inside installmentsTotal and the balance, and never added again. Null when no installment carries one.

Set while retrieve-IQ is checking this bill before the customer acts on it. Null otherwise.

Zero for the bill as the unit first issued it. When the unit re-issues it with other charges (on a page that lists none, another total), or a person corrects a reading, the new figures are the next revision, waiting for review under a key of its own; the revision they replace is kept as evidence, SUPERSEDED or REJECTED, and counted nowhere. A change that leaves the charges as they were (a payment posted, interest grown, a date printed) updates the same revision.

The county page or uploaded file the bill was read from.

The bill's review status, taken from its installments: the one most in need of attention speaks for the bill. Never a payment status: amountOutstanding and paidPerRecords say what is known of payment.

The account the bill was sent under: which unit sent it, and the number it knows the property by.

The sum of the installments, the same figure as installmentsTotal. Null, never "0.00", while the bill is withheld: the installments still show their figures, this does not add them up.

Every check run against this bill, across its installments: those still standing first, then warnings, then the ones a person or a later run settled.

Moves whenever anything about this bill changes: a decision, a figure, a date, a charge, its stated total. Every review mutation takes the version its caller read as expectedVersion, and is refused with CONFLICT when it has moved. Not the revision.

True while an unresolved ERROR check stands against the bill. A withheld bill's figures are shown on its installments for the reviewer and left out of every total until a person resolves the check or rejects the bill.

The codes of the checks that stand, comma separated, while withheld. Null otherwise.

What the county asks for this installment.

What is left to pay. Null when the payment figure or the penalty convention is unknown; never read a null as zero.

What the county reports paid. Null when the county publishes no payment figure (Los Angeles and Orange do not), which is not the same as zero.

The last day to pay before a penalty is added, which is the date the county warns taxpayers about.

The date the installment falls due by statute (November 1 and February 1 in California). Not the last day to pay.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

As the county labels it: "1st", "2nd", "Annual".

Its position on the bill, 1 for the first. Null where the bill does not number it.

What the customer's own records say was paid on this installment: payments less refunds, adjustments signed. Null when nothing is on record, which is not a paid figure of zero. Shown beside amountPaid, the county's figure, never in its place.

Whether the county publishes a payment figure for this installment.

The customer's own payment records for this installment, oldest first.

The penalty the county adds after delinquentAfter, where it publishes one.

Whether amountDue already includes the penalty or the penalty is added to it. Null where the county does not say.

The installment's review status. Never a payment status: amountPaid and paymentKnown carry the county's word, paidPerRecords the customer's own records.

True for every installment of a withheld bill (TaxBill.withheld).

That agency's phone number, where the county prints it.

The amount of the line for the year.

What kind of charge it is. Null where the county does not say; never guessed.

The line as the county prints it.

The id of this record. Not a Node id: node does not accept it.

The agency the charge is levied for, where the county names it.

The rate the county prints for the line, where it prints one.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

agent_firm, a firm that works for taxpayers under engagements, or taxpayer, an organisation that holds property of its own.

The organisation's name.

False when the parcel was already held; nothing changed.

The parcel, as held now.

The person's email address.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

The person's name, or the key's name for a service user.

The firm the person belongs to, never the client being acted for.

When a later run of the check passed. The check stays as history.

Which check it is, as a stable code: apn_mismatch, year_over_year_jump and so on.

When the check first made the finding.

What the check expected to find.

Everything that happened to this check, oldest first: found, changed, resolved (who and why), reopened, cleared, found again.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.

The installment the check ran against.

The finding, in words.

What it found.

The words of the resolution that stands now; null when none stands. Every resolution's words stay in history.

When a person accepted the discrepancy; null while no resolution stands.

The person who accepted it.

The version of the checks that made the finding; null for a finding made before versions were recorded.

How much the finding matters.

When it happened.

The person, for RESOLVED; null for everything else.

What the check expected to find at that moment.

What happened.

Their words, for RESOLVED.

What it found at that moment.

Pieced together from the check and the activity trail when the history began, not written as it happened: its figures are the check's as they stood then.

The version of the checks that ran; null where it was not recorded.

The check's severity at that moment.

The city.

The street address.

A suite or unit, where there is one.

The ZIP code.

The two-letter state code. The county's state when omitted.

Replaces the reading's charges when given; left out, they carry over.

The installments to change, each by its id.

The year of the assessed value the bill is based on.

The county's own number for the bill, when it prints one.

Which kind of bill it is.

The charges it lists for the year.

Its installments, as it prints them.

What the bill asks for it.

The date after which the county adds a penalty, when the bill prints one.

When it is due.

Its number on the bill, from 1.

Bills sent by any of these units. Narrower than ParcelFilter.jurisdictionIds: filtering by a school district returns that district's bills, not the county's and the township's for the same parcel.

Bills whose parcel number, street address, city or county bill number contains this text.

WAITING when omitted.

Only bills an ERROR check stands against.

What the bill charges for it.

What kind of charge it is, if you know.

The charge as the bill names it: "General levy", "Flood control".

What the county asks for it.

Null when the county publishes no payment figure.

The date after which the county adds a penalty, when the bill prints one.

When it is due.

The installment, as the bill lists it.

Parcels whose current total assessed value is at least this.

True: parcels with an appeal at OPEN or FILED; false: parcels without one.

Parcels assessed by, or billed by, any of these units.

Parcels held under any of these owners of record.

Parcels whose number or address contains this text.

Parcels in any of these states, by two-letter code.

Parcels at this status.

True to check the rows and write nothing.

An existing owner of record, by id. Either this or legalEntityName.

An owner of record by name, found or created. Either this or legalEntityId.

The rows, at most 500.

The city.

The county by name, as people write it.

As the county writes it.

The street address.

The county's two-letter state. California when left out.

The ZIP code.

The county by name, as people write it: "Los Angeles", with or without "County", "Orleans Parish", "Richmond city".

The id of the unit that assesses the parcel, from jurisdictions.

The owner of record to hold it under, from legalEntities.

As the county writes it.

The street address, if known.

The county's two-letter state, when the county is named. California when left out.

The county's use code, if known.

Which way.

What to order by.

True to check every row and write nothing.

The payments, one a row.

How much: positive for a payment or a refund, signed for an adjustment.

The assessment year of the bill paid.

The county by name. Needed only when the portfolio holds that parcel number in more than one county.

Which installment of that bill, from 1.

PAYMENT when left out.

The day the money moved.

A person's choice of parcel for a row whose number did not match one exactly, usually from the candidates a check offered. The import's trail records the row, the number it gave, the parcel chosen and how the two numbers relate.

As the county writes it.

A check number, a confirmation, a ledger line.

The county's two-letter state; California when left out.

Only these appeals and the parcels they are on: the evidence pack for one appeal is APPEAL_EVIDENCE_PACK with one id here. Each must be an appeal you can read; at most 200.

True: parcels with an appeal at OPEN or FILED; false: parcels without one.

Parcels assessed by, or billed by, any of these units.

Parcels held under any of these owners of record.

Parcels whose number or address contains this text.

Parcels in any of these states, by two-letter code.

Parcels at this status: a ParcelStatus value, such as ACTIVE.

The assessment year the rule was shown for.

Where you saw the right value: an http or https link.

The unit whose rule is wrong (a Jurisdiction id).

What is wrong, up to 2,000 characters.

For a REQUIREMENT: its code, as appealRequirements gives it.

What is wrong: one kind of dated rule, or a requirement.

What it should say, if you know: up to 500 characters.

Its exact size in bytes.

Its name, with its extension: .pdf, .csv or .xlsx.

What the document is, as it will be filed on the parcel.

The parcel the document belongs to.

It works.

Its last day has passed.

A person ended it. The record stays.

Mark it filed, with the date.

Reopen a withdrawn appeal.

Withdraw it.

Filing for the owner.

Who hears the appeal and where it is filed.

What the application must state.

When a filing counts as on time.

The application.

Filing periods the dated rules do not cover, such as a supplemental assessment's.

How it is signed.

Decided; the outcome is recorded. Final.

Filed with the board, awaiting a decision.

Recorded, not yet filed.

Withdrawn before a decision. It can be reopened.

Sent by email. Reserved: no unit is recorded with it yet.

Mailed on paper. Reserved: no unit is recorded with it yet.

No bill: the unit publishes none online, or sends none of its own.

Published on the unit's own website, where it is fetched every night.

Delivered as a file feed. Reserved: no unit is recorded with it yet.

Supplied by the firm as a file. Reserved: no unit is recorded with it yet.

The same bill is already on file; nothing new was stored.

Kept as the person entered it, and not a bill: a check found something wrong (the message says what).

A bill waiting in the inbox for review.

Bills a person accepted or rejected, the newest arrival first, so a decision can be found again.

Bills still waiting on a decision (NEEDS_REVIEW or DISPUTED), the oldest arrival first. The default.

Never returned.

Flagged for the client, with a note.

Reserved: every bill arrives at NEEDS_REVIEW today.

Waiting for a person's decision: where every fetched, uploaded or corrected reading lands.

Never returned.

Rejected by a reviewer as a wrong reading of the bill. Final, and left out of every total and date: a later fetch does not reopen it.

A revision the county replaced with a newer one, kept as evidence. Left out of every total and date.

Accepted by a reviewer.

A bill for value that escaped assessment in an earlier year.

A bill to redeem earlier years' unpaid taxes.

The annual bill on real property.

A bill for a change in value part way through the year, after a sale or new construction.

A bill on property that is not land or buildings, such as equipment, fixtures or a boat.

Tax on the assessed value at the general rate.

A flat charge from a district or agency, not based on value.

A fee added to the bill.

Penalties and costs added for late payment.

A charge for a local improvement, levied on the parcels that benefit from it.

Tax to repay bonds the voters approved.

The unit sends no bill of its own.

The unit's site does not allow automated access, so its bills cannot be fetched. The reason is recorded.

Bills are fetched from the unit's own site every night.

Not surveyed yet.

The unit publishes no bill online.

A site that publishes a balance but no bill document, or an image-only bill.

The unit publishes bills online; support for its site is not built yet.

The unit's site is supported and waits for a final live check.

The unit's site was retired.

The last day an appeal of the year can be filed.

The first day an appeal of the year can be filed.

The last day to pay an installment before a penalty is added.

The date an installment falls due.

A decision on an appeal.

A notice of assessed value.

A letter or other correspondence about the parcel.

A payment receipt.

A tax bill, as the county published it or as it was uploaded.

Read and confirmed by a person. Reserved: not produced today.

Read; its figures are on the bill.

Could not be read; the document needs a look.

Read, but what it says could not be matched to a parcel. Reserved: not produced today.

Being read. Reserved: not produced today.

Waiting to be read. Reserved: not produced today.

The files were produced but could not be delivered.

The files could not be produced.

The files were produced and delivered, but some parcels could not be fetched that night.

Still running.

The client's fetch finished without an error, and the files were produced and delivered.

The night's fetch failed before any file was produced.

The county's site refused the request.

The attempt failed for another reason.

The county answered and had no bill for the parcel.

The county answered with a page that could not be read.

A bill was fetched.

The county's site did not answer in time.

Lowest, earliest or A first.

Highest, latest or Z first.

The current assessment's total value.

The name of the unit that assesses the parcel.

The next payment date.

The parcel number, as text.

Held and tracked. The status every parcel starts in.

Sold or otherwise no longer held; kept for its history.

Exempt from property tax.

Held, with an assessment still to come.

A signed correction of an earlier entry, the way a wrong entry is reversed.

Money paid to the unit.

Money the unit paid back.

It came in with a list of payments (importPayments).

A person recorded it, one at a time (recordPayment).

The penalty is added on top of the amount due once the date passes.

The amount due already includes the penalty.

The unit sends no bill of its own.

Known, and not yet checked.

Bills are fetched from it.

A balance is fetched from it; the site publishes no bill document.

Bills are fetched from it as images, which are read on request.

The unit publishes no bill online.

The site was retired.

Automated access is not possible; reason says why.

Figures for the books.

Appeals and their outcomes.

Dates, bills and what stands against them.

What is held and what it is worth.

Comma-separated text, one header row.

A PDF for reading and printing.

An Excel workbook.

The appeal evidence pack alone: the pack as a PDF and a CSV, with the documents it lists beside them, one folder per appeal, and an index of what is there and what is not.

Ready: downloadUrl fetches the file.

The file has been removed. Request the report again.

Could not be produced; error says why.

Waiting to be produced.

Being produced.

For each appeal: what was asked against what and where it stands, the certified value and its revisions, the original documents and how each was read and reviewed, every reading of the year’s bills, the corrections, the checks and who accepted each, and the trail with the person and the firm, as the records hold them. A trail too long to carry whole ends with a line saying where it was cut and how much is not in the pack.

Every appeal on record: the certified value, what was asked, what was decided, the reduction realised against the reduction requested, and the tax saved where known.

Every parcel's newest two assessment years side by side: the change, the change as a percentage, and a flag at 10% or more.

Every installment we hold, which unit billed it, where its page came from, how it was read and by whom it was reviewed, and how many checks stand against it.

Every payment and appeal date in the next 120 days with the balance at stake, or why the balance is not known, the undated windows last with their reason. The jurisdiction column is the unit the date belongs to: the one that sent the bill for a payment, the one that hears the appeal for a window.

Next year's installments per parcel and billing unit, projected from the newest assessed value at the effective rate the last billed year paid to that unit, split the way that year was split.

A check on the reading failed (the figures do not add up, the parcel differs, a total moved tenfold).

This county's reader is paused after a wrong bill in retrieve-IQ's hand-checked sample.

Someone reported this automatically accepted bill as wrong.

A $0 bill, which is never accepted automatically.

The last day of the regular appeal filing window.

The first day of the regular appeal filing window.

The valuation date the assessment is made as of.

The last day to ask the assessor for an informal review.

When the assessor mails the notice of value.

They checked and the rule stands; resolution says why.

The rule was corrected.

Waiting for the people who maintain the rules.

The day the appeal window closes.

The day the appeal window opens.

The valuation date.

The last day to ask for an informal review.

When the notice of value is mailed.

A filing requirement, named by its code.

The rule counts from an event (a notice mailed, a roll published) whose date is not on record yet.

One side of a later-of or earlier-of rule is an event whose date is not on record, so the date is a floor or a ceiling, not the deadline.

The rule gives this date.

No rule of this kind is recorded for the unit, its parent or its state.

The date is set locally each year, and this year has not been recorded.

A rule is recorded but cannot be worked out, or names a day that is not on the calendar.

Manage the firm itself. Held by people in the app, never by a key.

Record appeals and update them.

Read tax bills, the checks run against them, the documents behind them and the nightly fetch status.

Accept, flag and reject bills, resolve their checks, and take a decision back.

Read parcels, their assessments, the units that assess and bill them, deadlines and calendar feeds.

Add and import parcels.

Request and download reports, and read the portfolio summary.

Withholds the bill: it cannot be accepted until a person resolves the check or a later run clears it.

For information; nothing to do.

Worth a look; the bill can still be accepted.

The unit still bills the property under this number.

It no longer does; the bills already held stay.

The site blocks automated visitors, even a full browser.

The site asks every visitor to prove they are a person before it shows a bill.

The site challenges visitors from data centres.

The site requires an account.

The site was offline when checked.

The site charges per lookup.

The site's published rules for automated visitors do not allow it.

The unit's own terms do not allow automated access.

A later run of the standing check found other figures.

A later run passed.

The check first made the finding.

The check made the finding again after it had passed.

A later run found other figures than the ones accepted, so the resolution no longer covers them.

A person accepted the discrepancy.

A date on a Saturday, Sunday or federal holiday moves to the next business day. State holidays are not counted, so a date can show one business day early, the safe direction.

The date stands whatever day it falls on.

The id: opaque, stable, and what node, nodes and every argument that takes an id accept.