The consolidated recurring-vendor roster across every pulled property. Pick a property to see its vendors and monthly spend, or search a vendor to see every property that pays it.
Staff: if the vendor database is the cause, check that Postgres is running and seeded (npm run db:seed, then db:seed:vendors).
One row per vendor × GL line (the locked deliverable format): Line Item, GL code, Frequency, Expected (median), Rating. Refreshed by every capture-enabled sweep; the "Loaded" stat above is the staleness check.
The full GL chart of accounts, with the funding category + FR-template column each code sorts into (blank = no funding mapping yet). This is the reference the Funding Requests workflow uses to categorize every Open-AP line.
Every property Aura’s database knows about — short code, Yardi code, and address. The shared reference behind the funding, invoice, and bank-rec workflows.
The MayfairNet staff directory, each person linked to the properties they cover — the source behind the Housing Deposit Scanner's manager emails. Refresh by re-running the WF9 directory crawl, then npm run db:seed:contacts.