What is missing, in order.

Being built, and already named in the product.

• Crossing Alerts

  Three rules: at a percentage of the threshold you choose, on the payment that actually crosses, and when a W-9 you hold expires. The rules screen has shipped and the rules are stored and editable; what is still missing is the delivery, so an enabled rule is recorded rather than sent.

  Sold on Core. Marked in development until a message actually arrives.

• Filing Readiness

  A card per tax year: how many returns you owe, the computed deadline, whether you are over the electronic-filing minimum, and the payees blocking you. This has shipped — the deadlines are stored weekend-adjusted and the per-year screen lists the blockers by payee.

  Sold on Firm, and in the first release.

• Workspace settings and invitations

  The roster, roles and invitation acceptance, with the last-owner guard in place. The screens have shipped: a workspace can invite, change a role, accept an invitation by link, and set its own tax treatment.

Decided, not started.

• State thresholds

  WithholdWatch is federal only today, and says so on /how-it-works and here. States do not all follow the federal figure and several have their own filing requirements, so this is a per-state data set with its own citations rather than a flag on an existing row.

  Nothing about state requirements is implied by a green figure in WithholdWatch today.

• Annual billing

  Monthly only at first release. Annual is worth having and is not worth shipping as a control that cannot complete a purchase, so it waits until the billing catalogue is connected.

Open questions, stated as questions.

• The indexed figure for the year after next

  The threshold is indexed from the tax year after the current one and the figure has not been published. WithholdWatch stores that year as unpublished and will not estimate it: the screen reads “Not yet published” and shows no numeral and no accent. When the IRS publishes, it becomes one row in the ledger and nothing else changes.

  This is the honest version of a feature. There is nothing to build until there is a number.

• Third-party networks: the gray zone

  Whether a payment through a third-party settlement organisation is yours to report is genuinely unsettled at small volumes, because the network’s own threshold has both a dollar test and a transaction-count test and most small-business payees clear neither. WithholdWatch excludes them by default, following Reg. 1.6041-1(a)(1)(iv): the settlement organisation reports the transaction on a 1099-K and the payor files nothing, so counting it here as well would double-count the same money. What is missing is a per-payee override with a recorded reason, rather than one switch for the whole workspace.

• TIN matching

  Checking a name and number against the IRS records would turn a self-reported W-9 status into a verified one. It also requires holding the full taxpayer number, which WithholdWatch currently refuses to store. That trade is the whole design of the product and it will not be made quietly.

  If it ever ships it will be opt-in, per payee, and said plainly on this page first.

• Filing itself

  WithholdWatch tells you what you owe and who is blocking it. It does not transmit returns, and doing so needs the number it refuses to hold. The likelier shape is an export that a filing service accepts, not a filing engine.