Drop a month's mixed PDFs and get a filing plan — each recognized document routed to its
{Property} {ycode}/{YYYY}/{MM.YYYY} folder in Omni Deliveries — plus the missing-docs board:
which properties still lack a statement or rec for each closed month, with the reason on every row.
Nothing is filed until you approve the exact plan on screen.
Aura keeps these sessions connected by itself and re-checks them before every run. This box only appears when one of them needs a person.
Recognized names: the statement convention (07-31-2026_584_ALTON-PARK_PNC_SD.pdf, plus the two earlier spellings) and rec PDFs (MM.YYYY {Property} Bank Rec {name}.pdf). Anything else lands in a visible unrecognized bucket — never guessed into a folder. A statement PDF that misses on name gets one content read (its account's last 4) — set the period below so a tie-broken file has a month to file under.
Property × closed month × document. Present is a filed, correctly-named document; missing only ever means "due and not there" — before the 1st business day of the following month a gap is not due yet, an errored folder listing is unknown (never "missing"), and every excluded property/account carries its reason. Judged from the last finished crawl, never a live walk.
Reads a tree's folder and file names through the logged-in SharePoint session — read-only, checkpointed per folder, resumable if it dies mid-walk. The board judges the Omni Deliveries crawl; the Accounting Active crawl is approved discovery of the client's real tree (it looks, it never touches).