Checks, invoices, leases, receipts, statements, certificates, and job records all enter through one document system. Zeno reads them once, routes them to the right module, suggests the work they imply, and keeps the original evidence beside every result.
A central document record carries classification, extraction, entity matches, suggestions, status, provenance, sharing, and the path back to what it created. Modules do not invent disconnected upload and parsing systems.
Zeno classifies a rent check differently from a vendor bill or statement, then routes it without losing the common lifecycle underneath. Low-confidence cases stay visible for review.
Payer, date, amount, reference, and likely entity appear beside the original page. A reviewer corrects judgment calls in context and decides when the document becomes operational and financial work.
Once approved, the document creates or supports the real payment, bill, lease, or transaction. That record lives in the operational module and on the ledger, with the source still one click away.
Direct captures from the public Parkview Property Management sandbox on August 22, 2026. Sample names and financial data are synthetic; the product interface has not been recreated.
Classification and extraction matter only when they lead safely into the real domain workflow.
Receive a file by upload, email, watched folder, connected source, or agent draft.
Run OCR once and preserve text for every downstream consumer.
Identify type and module while leaving uncertainty in review.
Match entities, detect duplicates, and apply relevant rules and knowledge.
Show the source beside the proposed operational or accounting record.
Retain the original, parsed data, links, provenance, and audit history.
Reclassification and reparsing update one record instead of creating disconnected copies.
Extracted facts remain reviewable wherever judgment or financial consequence exists.
Documents can be searched, shared with expiring links, exported, restored, or removed.
