pitch.reconciliations.finance
The tie-out is the artifact.
Bank, subledger, intercompany, and suspense: the account reconciliation designed as a typed call that returns with its evidence attached — every item named, owned, and dated, closed on evidence a stranger could find. Inside the close suite. Nothing here is live yet, and this deck says so plainly.
↓ scroll · arrow keys
You already know how to tie out an account. You have done it every month,
usually correctly, often late at night. The problem is that none of it
stays. The tie-out for operating cash is a PDF in a shared drive named
Bank Rec MAR (final)(2).pdf, and the only person who can connect it to
the account it supports is the person who saved it. One recurring
reconciliation is done correctly every month by exactly one person, from a
method that was never written down. Evidence that cannot be found is
evidence that does not exist — which the auditor's request list will
demonstrate, months later, when the work gets done twice at the worst
possible hourly rate.
Now the agent arrives. An agent can run the mechanical middle of a close, and the reconciliation is the most mechanical middle there is: two sides, a difference, a set of items that explain it. But an agent that closes items on assertion is the old failure at machine speed. What the close needs from software is not confidence. It is an artifact: a tie-out that is dated, sourced, attached to the account, and readable by someone who has never seen this close before.
Four instrument classes, named the way the register at the apex already names them: bank (ledger against statement), subledger (control account against its detail), intercompany (both sides of the mirror, with elimination support), and suspense (aged items named, owned, and dated until cleared). One designed shape:
// the contract as designed — nothing at this domain is callable today
POST /reconciliations
{
"class": "bank", // bank | subledger | intercompany | suspense
"account": "1010 · Operating cash",
"period": "2026-06",
"sides": { "ledger": "...", "statement": "..." }
}
// designed response: the tie-out artifact — or no artifact, and no charge
{
"reconciliation": {
"state": "tied_out", // tied_out | open — never closed by assertion
"items": [
{ "name": "deposit in transit", "owner": "named", "due": "dated", "evidence": "attached" }
],
"artifact": { "tieOut": "dated, sourced, attached to the account" }
}
}
The rules are the close suite's, applied at instrument grain. An item
without its evidence stays open no matter who says it is fine. The tie-out
is attached to the account it supports, not to a person's folder. The
artifact is the deliverable: an account that cannot be tied out produces
no artifact — an honest open state with its items — and meters nothing.
Everything on this slide is design intent. No reconciliation SKU exists, no call is servable, and the register at the apex says "Nothing at this domain is live." The contract ships as a servable surface only behind the family's publish gates, with its price posted on the family card in the same commit.
Agents can't sign the opinion. They can tie out the account. That is the vertical's ratified declarative shape applied to this door's own boundary. The reconciliation is not a reserved act — nobody forbids an agent, or a controller, from tying out an account. The opinion is reserved: expressing assurance on financial statements belongs to a licensed firm under the state accountancy acts, signing a tax return to a credentialed preparer, representation before a taxing authority to a Circular 230 practitioner, investment advice to the advisers regime. A call that reaches any of the four is designed to return a typed BLOCKED with a cure that names the act, the reason, the party who may lawfully perform it, and the route. The platform performs none of the four, and neither does any pool.
Where a reconciliation surfaces work that needs a credentialed reviewer, the route is typed — and today it is also honestly refused, because the accounting supply face has not opened:
gigs.accountants serves its RESERVED register leaf (curl-verified 2026-07-30): "Credentialed accounting professionals staffing routed books and close work. Nothing at this domain is live." The credentialed route this deck names is typed and refused, not staffed.
gigs.tax serves today — the tax cell's live supply door, recruiting CPAs against the estate's sign-off vocabulary. (The record's Enrolled Agent parity is a queued root-surface conflict; the live page is CPA-only.) Serving is a liveness fact about the sibling pattern this route graduates into, not a claim that close work routes there.
| instrument | returns | meter | price |
|---|---|---|---|
| Bank reconciliation | tie-out artifact, dated and sourced | no record, no charge | Price posts with the SKU |
| Subledger reconciliation | control-to-detail tie-out with items | no record, no charge | Price posts with the SKU |
| Intercompany reconciliation | both-sides tie-out, elimination support | no record, no charge | Price posts with the SKU |
| Suspense clearance | aged items named, owned, and dated | no record, no charge | Price posts with the SKU |
Flat per record, fixed at post, posted on the family's one rate card, and released on the record produced. No fee varies with the day-count achieved, for the same reason no fee in this family varies with the direction of a Decision: a fee that rewards closing fast is a machine for closing wrong. No seats, no minimums, no percentage of anything. Until a SKU posts, every price cell above reads exactly what the vertical's publish gates require it to read.
The fourth ProofPredicate was written for data products. Whether a close work product — a tie-out — is a served record is an open owner question in the vertical's canon, recommended for ratification rather than minting a fifth predicate. Until it is ruled, the meter promise here is design intent, and no SKU ships against it.
substrate — apis.finance
the controller who owns the close
the whole close, calendar grain
the controller as a person
the working surface over the close
the agent running a close
reconciliations as typed calls
the builder embedding the family
one key, posted prices, the money kernel
A brand here is one ICP and one motion, chosen explicitly. The flagship addresses the human who owns the calendar; this door addresses the close whose reconciliations are run by an agent — same hero, different grain, different caller on the wire. And the filing is worn openly rather than smoothed over: the vertical's owner ruling files this name among the work-product aliases that 301 into the flagship once the flagship ships. The flagship has not shipped, the apex already posts a door-grain identity ("Reserved for reconciliations as typed calls"), and this record proposes the instrument-grain door as a graduation, on the estate's own precedent. Ratify or reverse; the register stays honest either way.
monthend.finance, the flagship, serves its RESERVED register leaf (curl-verified 2026-07-30): "Nothing at this domain is live." The ruling that would 301 this name into the flagship has not triggered.
controllers.finance serves its RESERVED register leaf (curl-verified 2026-07-30): "The controller's working surface over the close: the calendar, the checklist, the evidence, the sign-off. Nothing at this domain is live."
apis.finance serves today: "Agents can't lend. They can call it." — the family hub with the Mandate specimen, the key funnel, llms.txt, and the rate-card frame any close-suite SKU would post on. One key is designed to open every live door in the family.
The apex serves the family register's own leaf (curl-verified 2026-07-30): "reconciliations.finance · RESERVED · apis.finance family register — Reserved for reconciliations as typed calls. Account reconciliation with evidence attached: bank, subledger, intercompany, and suspense, inside the close suite. Nothing at this domain is live." The identity this deck argues is already posted at the apex, in the estate's one honest word.
Until the close-suite ruling lands, no close-suite copy may claim a capability, and this deck claims none: every capability slide above is design intent, and both suite domains remain holding leaves.
The graduation this record proposes — work-product door at instrument grain rather than 301 alias — is a filing decision the owner has not made. It is recorded in this file's frontmatter reconciliation note and queued; the deck's green Claims stay curl-true under either outcome.
The register at reconciliations.finance already says what this door is reserved for, and keys@apis.finance — the register's own door line — is where you hear when it opens.
If this was forwarded to you: reconciliations.finance is the reserved instrument door of an accounting close suite — the account reconciliation designed as a typed call that returns a tie-out artifact with its evidence attached, or returns no artifact and charges nothing. Nothing at the domain is live; the deck above states every capability as design intent and carries the evidence for every liveness fact it posts. The live front door of the family is apis.finance. To hear when this one opens, write to keys@apis.finance.