One daily run, fully reconciled

1

Each office drops its daily export on a dedicated SFTP account or uploads it in the console. Files are validated as they land; bad rows are set aside and reported by ID, and the rest load.

• —CSV, delimited, fixed-width, XML or Excel
• —Missing or late files raise an alert at 10:00
• —Duplicate files are ignored automatically

2

A versioned mapping profile translates your column names, date formats, document-type codes and APN layout. Nothing county-specific is hard-coded.

• —Dry-run against sample files before go-live
• —Every file records the profile version used
• —Staff approve profile changes before they go live

3

Each document is classified as a notice, a notice flagged for signer review, an exception, or excluded, with the reason stored alongside.

• —Government grantees excluded per §27297.7(c)
• —Missing APNs read from the image, uncertain readings to staff
• —Signer checks recognize trusts, companion deeds and agents

4

Anything that cannot be matched cleanly lands in the queue sorted by days left, with suggested parcels, corrected APN readings or successor parcels ready to accept.

• —Hold for next Assessor file
• —Release valid parcels on multi-APN documents
• —Every action is audited

5

A daily batch collects pending notices into one accessible PDF sized for a #10 double-window envelope, plus a manifest and cover sheet.

• —Approve, download, mark mailed
• —Void and reprint individual notices
• —Returned mail tracked if you choose

Decision Rules

Every outcome has a reason code

Thirteen rules run in a fixed order. The first one that applies sets the outcome, and every intermediate fact is stored with the decision, so staff and auditors can see exactly why a document did or did not get a notice.