pitch.monthend.finance

monthend.finance

The close, as a product.

The month-end close as a record: every item named, owned, and dated; every reconciliation closed on evidence a stranger can find; every variance arriving with its drivers; every statutory clock typed apart from your own targets. Agents can't sign an opinion. They can prepare the close.

↓ scroll · arrow keys

The villain is a practice, not a party

You already know how to close. You have done it every month, usually correctly, often late at night, and almost always from a method that lives in your head and a folder nobody else can navigate. The work is not the problem. The problem is that none of it stays.

The Ritual, the close as a monthly reperformance of undocumented knowledge, wears three masks:

  • The folder of screenshots. The evidence exists. It 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. Evidence that cannot be found is evidence that does not exist, which the request list will demonstrate in about nine months.
  • The person-shaped dependency. One recurring accrual is computed correctly every month by exactly one person, from a method that was never written down. That is not a staffing problem. It is a reproducibility problem, and it is why the close cannot be delegated, audited cheaply, or scaled to a second entity.
  • The day-count that is a rumor. "We close in eight days." Eight days from what, measured how, and which day slipped last quarter? Nothing timestamped it, so the figure reported to the board about the close is the one number in the company nobody reconciles.

Every other villain in this estate is a gate: a licensed act withheld, a contract required, a fee taken at a choke point. The close has no gate. Nobody forbids you from closing the books. The work is fully permitted, entirely unglamorous, almost completely undocumented, and it fails anyway, every month, in the same places. The villain is a practice, and the product is the practice replaced by a record.

The close as a system of record

A close item carries a named owner, a due date, a typed clock class, its evidence links, and its state. It is closed by evidence, never by assertion: an item without its tie-out stays open no matter who says it is fine.

// illustrative product mechanics, not a live response
GET /v1/close/2026-06/items/recon-1010-operating-cash
{
  "item":    "recon-1010-operating-cash",
  "entity":  "opco-us",
  "owner":   "named-person",              // a person, never a team
  "clock":   { "class": "target", "due": "2026-07-03" },
  "evidence": ["evidence://tie-outs/1010/2026-06"],
  "state":   "open"                        // closes on evidence only
}

The clock classes are typed, because they are not the same object. A deadline set by a statute (an information return, an escheatment window), by a credit agreement (the covenant compliance certificate), or by a limited partnership agreement (a capital call notice period) runs as a Timer Ladder rung: owned by deterministic code, closed only by evidence, carrying a named responsible party, never extendable by configuration. A day-three target you set for yourself runs as a target: real, tracked, and not a statute. Dressing an internal target as a statutory rung is how software teaches people to ignore both, so the schema refuses to.

The posting boundary. An agent prepares an entry; it posts one only through a recorded Authorization from a named party at the entity. A worker that posts on its own authority is not a faster close, it is an unattributed number. The entity closes its own books, always.

The evidence boundary. A reconciliation that produces no tie-out artifact produces nothing, closes nothing, and meters nothing.

The variance arrives with its drivers. A flux is surfaced against your own account names, with the transactions and the period comparison that produced it, drafted for the owner of the account to accept, edit, or reject. The explanation is authored by the person who owns the account; the platform assembles the evidence for it.

Pendinggate: close-orchestration-core live and callable at monthend.finance

The contract above is stated ahead of the surface. The close system of record (items, owners, dependencies, clock classes, evidence links, period state, closing history) is a designed substrate, stamped ROADMAP in the family catalog, and it is claimed as live only when a caller can fetch it cold at this domain.

The close is not reserved. The opinion is.

That sentence is the whole commercial argument, and it is a fact about the statute book, not a claim about the product. Four acts are reserved, and the surface types all four: expressing assurance on financial statements (an audit, a review, an examination) is reserved to a licensed firm under the state accountancy acts; signing a tax return is reserved to a credentialed preparer; representing an entity before a taxing authority is reserved under Circular 230; investment advice is reserved under the advisers regime. Software performs none of the four, and neither does any pool. A call that reaches one returns a typed BLOCKED with a cure that names the act, the reason, the party who may lawfully perform it, and the route.

One exclusion is structural and will never be relaxed: this suite never sells to the firm expressing assurance on the books it closes, because performing the close and expressing assurance on it are independence-incompatible under the professional standards. The auditor is a reader of what this suite produces, never its buyer. The request list is answered from the entity's own record; no procedure is performed for the firm that sent it, and no surface here claims what a third party will conclude from the record.

Pendinggate: Reserved-Act Catalog rows and the accountancy Jurisdiction Rule ratified per state and act class

The reserved-act boundary is canon in the vertical's record today, and its per-state machinery is not yet ratified. Until the rows land, every routed act is typed and refused, which is the promise, not a gap: a refusal that names the lawful party is the product behaving correctly.

What serves today

Serving is a liveness fact about a page, never a tenancy or capability claim. What is live across this family today is a register of holding leaves that say, in one ratified word each, that nothing behind them is live. The candour is deliberate: a capability sentence rendered under a RESERVED stamp is a ship failure in this family's own design law, so the leaves claim a role and nothing else.

Postedmonthend.finance

monthend.finance serves its RESERVED holding leaf: "Reserved for the close, as a product." The leaf names the family mailbox, and nothing at the domain is presented as live.

Postedcontrollers.finance

controllers.finance, the persona door, serves its own RESERVED leaf: "Reserved for the controller's door to the close suite."

Postedaccruals.finance

accruals.finance serves its RESERVED register leaf in the apis.finance family register.

Postedamortizations.finance

amortizations.finance serves its RESERVED register leaf in the apis.finance family register.

Postedreconciliations.finance

reconciliations.finance serves its RESERVED register leaf in the apis.finance family register.

Postedvariances.finance

variances.finance serves its RESERVED register leaf in the apis.finance family register.

Pendinggate: close-suite ruling lands and the flagship ships; work-product names 301 into monthend.finance

The ratified plan is one flagship, not twelve brands: the work-product names above (with forecasts.finance and the .co books doors) become 301 aliases into this door once a SKU is real. Today each stands as its own leaf, and this record does not describe the redirect as existing before it does.

Human~95% of function cost
Agenticorchestration-priced
Generativeinference-priced
Codenear-zero marginal

The fee shape is inherited from the family's money canon and it is the alignment mechanism, not a pricing tactic. A reconciliation that cannot be tied out produces no artifact and meters nothing, so the platform is paid only for records that exist. And because no fee rewards speed, the product has no incentive to close wrong, which is the property a lender, an LP, or a board silently prices when they decide whether the number is worth relying on.

rate cardPendinggate: close-suite rows priced on the family rate card at apis.finance

No figure is published anywhere in this deck before it posts on the family's one rate card. Until then, every price cell in the catalog reads "Price posts with the SKU", exactly.

One ICP, one motion

The ICP is the controller who owns the close: the controller at a company that outgrew its books, the fractional CFO running several books at once, the accounting manager who is the close. The primary motion is B2H2A: that person, working through an agent surface, with everything a credential reserves routed to a credentialed human under a named firm. The channel matches the buyer: the namespace position (the name is the category), the professional community where controllers already compare close practices, and the agent-discovery layer, because the close is built to be callable.

Secondary, the agent is a first-class caller (B2A): an agent can run the calendar, prepare the entries, assemble the reconciliation evidence, and draft the flux, and it stops where the credential starts, in a typed response rather than a footnote. Tertiary (B2A2D), builders embedding close capability in a books platform, a vertical SaaS, or a fund-administration product get their key at the apis.finance hub under the family's one rate card; this door issues nothing at its own address.

controllers.finance is the same suite addressed to a person instead of to a work product: one funnel, two doors, and a standing rule that the two never contradict each other and never price differently. The persona door sells no SKU at its own address; it routes here.

Postedapis.finance

The family hub this door hangs off serves today: apis.finance, the finance vertical's demand rail, where the embedder's key and the family's posted card live.

The credentialed route: attest or abstain

Where a close item needs a credentialed reviewer, it routes to one who takes the work under a named sponsoring firm's licence, performs the act under their own name, and returns an attestation: a statement of fact, never an expression of assurance and never a conclusion about the entity's solvency. Their reasoned refusal is paid, because a refusal memo is completed professional work. The Independence Screen is checked at claim, not asked about afterward: a reviewer who performs close work for an entity is barred from the assurance engagement on that entity, and the reverse, and the interested parties are disclosed before anything unlocks.

The route is described here as what it is today: typed, and refused. Tax reserved acts resolve to the family's live tax door; routed close review resolves to a supply face that is still a holding leaf. No work is being routed yet, and this deck does not imply a marketplace before one exists.

Postedgigs.tax

The family's tax supply door serves today at gigs.tax, recruiting credentialed sign-off on the busy-season rhythm.

Postedgigs.accountants

gigs.accountants, the accounting supply face this suite's close reviews would route to, serves its RESERVED register leaf: "Reserved for the accounting supply face of the gigs estate."

Pendinggate: first routed close review returned by a credentialed reviewer under a named sponsoring firm

The claim that matters on this slide posts when a real close item has gone out through the route and come back with a named credential on it, with the artifact in evidence. Not before.

Where it stands

Stated plainly: this deck precedes the product. Both close-suite doors are RESERVED holding leaves, on purpose, under a family design law that forbids implying a capability beneath a RESERVED stamp. What exists today is the vertical's ratified canon (the vocabulary, the money rules, the reserved-act boundary), the catalog of record with every row stamped ROADMAP, and the live register of leaves shown above. Every amber below is deliberate: the deck is built before the catalog, and says so.

Pendinggate: owner close-suite ruling (fin/CONTEXT.md open questions) graduates the two leaves into full doors

The one-flagship strategy is recommended and the holding structure is deployed; the ruling that lifts the quarantine and lets a close-suite surface claim a capability has not landed. Until it does, this record claims roles and mechanisms as design, never as live product.

Pendinggate: org.ai docket amendment filed (RATIFICATION-PACKET section 2 prerequisite)

The vertical's own canon names one unfiled docket amendment as the prerequisite that gates every page ship in the family, this flagship's included. The gate is recorded here so the deck cannot outrun its estate.

Pendinggate: design registry row assigned and the flagship's design loop run

The campaign ships through the family's full design loop under its charter (own identity, ratified hue window, the craft bar the family's rejected hub designs defined). The loop has not run; this deck's theme is the record's intent, not the ratified identity.

Tell us how you close

The front door is monthend.finance. It serves today, and what it says is RESERVED. Reading this deck next to that leaf is the pitch: a family that refuses to imply a capability before it exists is the same family you can trust to type the difference between a statutory clock and a target, between evidence and assertion, between the close and the opinion.

If this was forwarded to you: monthend.finance is the flagship of the accounting-close family in the dot-do estate's finance vertical, the month-end close as a record instead of a monthly ritual: every item named, owned, and dated; reconciliations closed on attached evidence; variances arriving with their drivers; statutory and contractual clocks typed apart from internal targets; and every act a credential reserves routed to a credentialed person under a named firm, never performed by software. The product is pre-launch and says so: both doors serve RESERVED holding leaves today, and every claim in this deck carries its own state and evidence, including the ones not yet earned. If you own a close: the leaf at monthend.finance names the mailbox. If you know who does: forward this.