Orchard Tax

Prepare & Review Workflow

End-to-end flow from verified source documents to a reviewed draft return.

Workflow

  1. Upload source PDFs for a return.
  2. Classify and extract fields when an extraction API key is configured.
  3. Verify every field before it can feed the engine.
  4. Build ReturnInputs from verified fields and overrides.
  5. Compute a deterministic draft with source refs and rule citations.
  6. Review diagnostics, YoY deltas, and line-level provenance.
  7. Snapshot the reviewed draft before changing return status.

Review contract

Received means the PDF is in the system, but nothing from it can affect a draft yet.

Extracted means the document produced candidate fields and a human still has to confirm them.

Verified means the field values can safely feed the engine, which is the only point at which a line may appear in the draft.

Reviewed means the preparer has checked the draft, resolved diagnostics, and snapshotting is complete.

Why this shape

  • The engine only consumes verified inputs, never raw OCR guesses.
  • Every computed line carries sources and cites, so a reviewer can click straight back to the source page and the rule behind the number.
  • Overrides stay explicit and recorded; they do not rewrite the underlying field history.
  • Year-over-year checks belong in review because they compare the current draft against a prior-year anchor, not against whatever the extractor happened to guess.

On this page