Impact
Reclass Agent Audits 126,000 Journal Entries a Month, So a Person Reads 25 per Property
Community managers code every journal entry at their property, roughly a thousand a month each, tagging the property, the unit, the vendor, and the general ledger account. They are not accountants.
Deployment Log
The Starting Point
Community managers code every journal entry at their property, roughly a thousand a month each, tagging the property, the unit, the vendor, and the general ledger account. They are not accountants. At month end a finance team of forty reviews all of it and reclassifies the small share that is wrong.
Finding twenty bad entries in a thousand is needle work, and it sits directly on the critical path to closing the books. Every other close task waits behind it. The rules that decide what is correct are not in any system. They live in a chart of accounts, a budget memo, and a set of guidelines that only this company uses.
What We Built
At each property’s close date, an agent reads that month’s entries and proposes reclassifications, using their chart of accounts, their budget memo, and their written guidelines as the source of truth. The accountant sees twenty or thirty proposals instead of a thousand entries, and approves or rejects each one.
A rejection requires a reason, and that reason goes back into the agent’s context, so next month it makes the same mistake less often. The accountant moves from search to audit. The agent never posts anything on its own.
What Changed
| Before | After | Basis | |
|---|---|---|---|
| Entries a human reads | ~1,000 per property | 20 to 30 proposals | Observed |
| Review time per property | 2 to 3 hours, monthly | Approval only | Observed |
| Across 126 communities | 250 to 380 hours a month | — | Projected |
What We Are Watching
The learning loop is the open question. Whether rejection reasons make the agent measurably better by the third close, or whether the guidelines themselves need rewriting first. We will know in ninety days.
Frequently Asked Questions
A reclass, or reclassification, moves a journal entry that was coded to the wrong property, unit, vendor or general ledger account to the right one. At this operator, community managers code about a thousand entries a month each, and finance reclassifies the small share that is wrong at month end.
At each property's close date, the agent reads that month's entries and proposes reclassifications using the operator's own chart of accounts, budget memo and written guidelines. An accountant approves or rejects each proposal, and the agent never posts anything on its own.
An accountant now reads 20 to 30 proposals per property instead of about 1,000 entries, replacing 2 to 3 hours of monthly review per property with approvals. Across 126 communities, that is a projected 250 to 380 hours a month.
Every rejection needs a reason, and that reason goes back into the agent's context so it repeats the mistake less often. Whether that makes it measurably better by the third close is the open question, with an answer expected within ninety days.
Deployment Log
Build notes from Venn's forward deployed engineers, published as they ship. Each entry is a glimpse inside the process and covers what was built, the impact, and what they're watching.
