pitch.journalentries.co
The instrument the books are made of.
Journal entries prepared as typed deliverables with their support attached — balanced by construction, every line resolving to the documents behind it, re-performable by any reviewer, posted only on a recorded authorization from a named human at your entity. The second door of a family named for the instruments of the back office, behind the lead: trialbalance.co.
↓ scroll · arrow keys
Everything a company does ends up as the same instrument. The sale, the payroll, the rent, the estimate, the correction of the estimate — whatever happened, the books record it as a journal entry: a date, a memo, lines that debit and credit, and support somewhere that says why. It is the most universal work product in accounting, because it is the one every other work product resolves to.
And the entries that matter most are still made the way they were made thirty years ago. Subledgers write the routine ones; the accruals, the corrections, and the topside entries are prepared by hand — the amount computed in a side spreadsheet, the support in an email thread, the recurring entry cloned from last month with last month's memo still on it, the posting keyed in under one person's login. The entry says what happened. It cannot show why, and the person who could is not always still there.
So the whole system of record inherits the credibility of a folder. When a reviewer samples an entry and asks for what's behind it, the honest answer is too often a memory — and every departure from the accounting team is a small hole in the books' institutional memory that nobody prices until review finds it.
The contract is stated before the code exists, so it can be read and challenged first. The deliverable this door is designed to return: the journal entry as a typed record — balanced by construction (an entry whose debits do not equal its credits is refused at preparation, not caught at review), support-attached (every line resolves to the documents and computations behind it), and re-performable: the same inputs reproduce the same entry for any reviewer at any later date.
// SPECIMEN — illustrative product mechanics, designed shape, not a live response
POST /v1/workers/entries
{
"period": "…",
"entry": {
"date": "…",
"memo": "Accrue services received, not yet invoiced",
"lines": [
{ "account": "6220 · Professional services", "debit": "…" },
{ "account": "2050 · Accrued liabilities", "credit": "…" }
],
"balanced": true,
"support": [
"the statement of work the estimate reads from",
"the computation, versioned, that produced the amount"
]
},
"prepared_by": "journal-entry worker (versioned; agent-prepared)",
"posting": "held — posts only on a recorded authorization from a named party at the entity",
"receipt": { "outcome": "prepared", "reperformable": true }
}
Two rules hold the shape together. Preparation is not posting: agent workers compute, draft, and attach — nothing posts to the entity's books without a recorded authorization from a named party at the entity, carried on the entry as part of its record. And nothing changes silently under a close: workers are versioned, and every entry cites the version that prepared it.
Everything on this slide is design, not product. The worker that produces this deliverable is roadmap in the vertical's own offer register; no call shown here can be made today, and this deck says so rather than demoing around it.
The claim in this door's name is a fact about accounting, not about this product: every other instrument of the back office either is a journal entry, produces one, or totals them. The accrual posts as an entry. The amortization schedule exists to imply one, period after period. The pay run posts as several. The reconciliation's adjustments post as them. The capital call's receipt posts as one. And the trial balance — the artifact the family's lead door is named for — is nothing but the sum of what posted: assemble every entry correctly and the tie-out is a consequence, not an achievement.
That is why this instrument runs at a different cadence from every sibling. The tie-out is monthly; the entries are continuous — they happen whenever the business does something, which is always. The most universal instrument is also the highest-frequency one, and the one where prepared- with-support-attached compounds hardest: fix the atom and everything assembled from atoms inherits the fix.
the controller
the tie-out — the period assembled, proven, and authorized — the family lead
the accountant
entries prepared with their support attached, posted only on recorded authorization
the payroll owner
pay runs prepared and evidenced — their postings are entries
the fund controller
call notices on the notice period the agreement sets — receipts post as entries
the account owner
variances explained — the story of what the period’s entries moved
The instrument ends where the law's reserved acts begin, and the boundary is the design rather than a disclaimer. Preparation is not posting — agent workers compute, draft, and attach; a recorded authorization from a named party at the entity is the only path to a posting, and the entity closes its own books. Preparing an entry is not an act any statute reserves — the reserved acts live nearby, and this door stops exactly at them: nothing here expresses assurance — no audit, no review, no attest opinion in any register; nothing here signs — not a return, not a filing; and where an act does require a credential, the work routes to a credentialed preparer rather than around one — which is what this door's own register leaf already says: "routed to credentialed preparers where the act requires one."
Primary motion is B2H2A: the entity buys, its accountant directs, and agent workers prepare the entries under that direction — with the recorded authorization of a named human as the only path to a posting. Secondary is B2A2B: the entity's own systems raising entries against the same worker as the business runs — the natural fit for the family's highest-frequency instrument. The channel matches the coordinate — the domain IS the shelf position, because a work product named at its own address is findable by the humans who produce it and the machines that will.
The boundary with the siblings is the ICP: the lead door serves the controller who owns the close; this door serves the accountant who carries the entries. One instrument per door, one buyer per instrument.
No motion is proven. The first entity that takes entries as deliverables — one ledger connection, one class of entries, one named authorizer — is the claim that matters, and it posts when it has happened.
The work behind the entries — computation, drafting, support assembly, balance checks — is precisely the work that migrates Human → Agentic → Generative → Code, and unlike the monthly instruments, entries run at the cadence of the business itself: a metered deliverable with continuous demand, no seasonal cliff, and no licensed-supply cost on this brand's books. What never migrates is the authorization — that stays human and named by design, which is the product's trust seam, not its cost center.
Deliverable-metered, posted-card doctrine, releasing in the served-record class: the deliverable exists and is receipted, or nothing meters. The figures publish when a card is live; none is asserted before then.
Entities, entries prepared, postings authorized. Not presentable until the reporting basis resolves; no figure appears in this deck before then.
This record is candid about its own status in the estate — and it carries a double contingency. First: the finance vertical's canon rules that one flagship — monthend.finance — carries the close suite, with the .co instrument names as sections of that one door until a SKU is real, and commits that "if one ever becomes a door of its own it will say so at its own address before it says so here." Second: the pitch-deck program's pack assignment elects trialbalance.co as lead of the instrument family with this door filed behind it — an election that is itself a graduation ahead of the fin ruling, queued for ratification at the lead door's own record. This deck files journalentries.co as the second door of the family, behind the lead. If the one-flagship ruling stands, this record re-files as the journal-entries section of monthend.finance and loses nothing true; if the family election is ratified, the door says so at its own address first, exactly as the fin record requires.
The apex serves today and files itself honestly: "journalentries.co · RESERVED · apis.finance family register — Reserved for journal entries as a work product … Nothing at this domain is live." The live leaf and this record agree on every present-tense fact.
The family lead, trialbalance.co, also serves today — the same RESERVED register-leaf pattern, "Reserved for the trial balance as a work product." Neither door has shipped a product surface.
The fin canon's ruled flagship, monthend.finance, also serves today — the same RESERVED register-leaf pattern, "Reserved for the close, as a product." The filing question is about which name leads, not about any live claim.
Which coordinate this door ultimately answers under — the flagship with the instruments as sections, or the instrument family with the lead door at its head and this one behind it — is an open estate decision. This deck wears it openly, and no green claim above depends on the outcome.
Stated plainly: this deck precedes everything except the coordinate. No product surface has shipped at this door — no catalog, no card, no callable worker. The apex serves the estate's own RESERVED register leaf, filed on purpose, and every amber in this deck is deliberate: the record is built before the product, and says so.
The apis.finance hub serves today, with its own live surface and rate card. The register filing runs one way for now: this leaf files ITSELF under the "apis.finance family register" on its own page and its /llms.txt, while the hub's published family map does not yet list the books doors — a hub-side register seam this deck wears openly, queued in the estate's decision queue.
What journalentries.co serves is a placeholder, not a product. The first product claim this brand can post is a real front door at its own address.
The claim that matters: an external entity's entries, prepared under a scoped program — balanced by construction, support attached, posted on that entity's named human's recorded authorization. It posts when it has happened, with the receipt discipline as the evidence.
This record is the front door today — the door itself is filed RESERVED at journalentries.co, and says so.
If this was forwarded to you: journalentries.co is the second door of a family of domains named for the work products of the finance back office, behind the lead, trialbalance.co. It names the most universal instrument in accounting — the journal entry, which every business event becomes — and is designed so that instrument carries its own evidence: balanced by construction, support attached, re-performable by any reviewer, with agent workers preparing and a named human at the entity authorizing every posting. Nothing is live yet: the door serves an honest RESERVED placeholder, every claim in this deck carries its own state and evidence, and the brand is candidly pre-launch — including about an open filing question it would be easier not to mention. If you carry the entries somewhere: this record is the front door. If you know who does: forward this.