MOA intake path

Upload, review, and approve an MOA

This first build slice stores the uploaded PDF locally for development, creates a mock extraction payload using the handoff contract, and routes the reviewer into approval.

Back to overview

STEP 1

Upload MOA package

live path

The current build uses the configured Neon, Blob, and OCR service modes for the intake workflow.

Development behavior: uploaded files are stored under the local runtime folder until Blob and OCR are wired by your partner.

STEP 2

Review queue

FileStatusUpdatedReview
MOA #1 2016 Regular.pdfapprovedJun 23, 2026, 5:28 PMOpen review
MOA #1 2016 Regular.pdfapprovedJun 23, 2026, 5:19 PMOpen review
MOA #1 2016 Regular.pdfapprovedJun 23, 2026, 5:13 PMOpen review

STEP 3

Review and approve extracted values

The review page uses the handoff payload contract and lets staff choose whether the approved MOA creates a new project or links to an existing project.

Guardrails

  • The extracted account limits must match the MOA table before project creation is allowed.
  • An approved MOA can either create a new project or be linked to an existing project record.
  • The total of all opening accounts must equal the approved originating MOA total NTE or an approved exception.
  • Project creation should snapshot the approved originating MOA values so later amendments and later MOAs do not overwrite the original agreement.
  • Amendments should create new ledger entries and new allocation records instead of editing historical balances.