Blotter · Manifesto

Nobody was checking. So we built something that does.

Why Blotter exists

This product started with a folder of PDFs. A handful of rental properties, three different property managers, and years of monthly statements that had been opened, skimmed for the draw amount, and filed. The properties made money. The statements arrived on time. Everything looked fine, the way things look fine when nobody is looking.

The statement nobody read

Then one unit sat vacant for a few months, and the statements kept coming. One of them showed $3,578.43 in charges against that unit, a unit collecting no rent. Repairs, services, line after line, all presumably real work by real vendors. Maybe every dollar of it was legitimate. That was exactly the problem: there was no way to know, because nobody had ever asked, and the document that could answer the question was sitting in a folder, unread, like all the others.

That is the strange arrangement every owner with a property manager lives inside. You hire someone to handle your money. Every month they write down what they did with it, grade their own homework, and send you the grade. Your accountant does not check it; they are paid to file what you give them, not to audit your manager. You do not check it; that is why you hired a manager. The PM does not check it; they wrote it. The most important financial document in the relationship has exactly zero readers.

The answer key was printed on the document

Here is what made the problem solvable. An owner statement is not a press release; it is a ledger, and a ledger carries its own answer key. The beginning balance, plus every dollar in, minus every dollar out, must equal the ending balance. To the cent. No permission needed, no portal login, no benefit of the doubt: the document can be tested against itself.

So we built an engine that reads the statement the way an auditor would. Extract every line. Run the arithmetic. Check the fees against the contract. Flag charges against units that earn nothing. Match every expense to the invoice behind it. The first time we ran it across the founding portfolio: ten of eleven statements reconciled to the cent, the eleventh printed no balances at all (so the engine said "unverifiable" instead of pretending), and the vacant-unit charges came back flagged, with the exact lines cited and a question drafted.

What we believe

The books should do themselves. Your property manager already produces the financial record every month. Bookkeeping that asks you to re-type or re-categorize what the statement already says is a chore invented by software. Statements flow in; the picture assembles itself.

A number you cannot verify is a rumor. Every figure on your dashboard traces to a statement line, every statement passes its own arithmetic or says loudly that it did not, and every charge meets its invoice. A pretty chart on top of unaudited data is decoration.

Questions, never accusations. Most property managers are honest, and most flagged charges have ordinary explanations. The product never accuses; it cites evidence and drafts a polite question. The first audit in our corpus that mattered most was answered by the PM in a day, reasonably. That is the system working.

Your data works for you and no one else. Statements are your business. Benchmarks are aggregate, anonymized, and published only when no one can be singled out. Nothing you upload is ever turned against you, or quietly become someone else’s product. The details are on Security.

Where it goes

The audit was the beginning, not the point. Once every statement is read, proven, and filed, you have something owners almost never have: one financial picture of the entire portfolio that is actually true. Lender-ready when you refinance. Schedule E and the CPA package at tax time. A digest each month that says "all clear" and means it, because something checked.

The folder of unread PDFs turned out to be the most valuable thing in the filing cabinet. Yours is too.