monthend.finance the close as the company's record controllers.finance · if the close is yours /llms.txt
monthend.finance is software, not a firm. A close calendar the company runs in place of the spreadsheet: every item named, owned, dated, and closed on the evidence attached to it.
Not open yet: no pricing and no signup. RESERVED means the name is held and nothing is running behind it. The records on this page are samples.
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.
keys@apis.finance is the mailbox for monthend.finance · opens your mail app, with three questions already in the message. A person replies: you get an early read of the close record as it stands, and a place on the list for the first companies this opens to.
Further down this page: a sample close item, a sample tie-out, and where it stops and hands anything requiring a license to a credentialed firm, so monthend.finance never signs off on your numbers.
What happens to what you send: a person reads it, it is held as correspondence so the reply can happen, and it is not published, not sold, and not passed to anyone outside the party that answers this address. Send only what you are free to send; the three questions are answerable without naming an entity.
| ITEM | ACCOUNT | OWNER | DUE |
|---|---|---|---|
| Accruals proposed, posted, and reversed | 2100 · Accrued liabilities | A. Reyes | 2026-08-03 |
| Variance drafted for the account's owner | 6200 · Professional fees | R. Okonjo | 2026-08-04 |
| Bank reconciliation, operating account 4471 | 1010 · Operating cash | A. Reyes | OPEN · 2026-08-05 |
| Trial balance, assembled and tied out | all accounts, 2026-07 | R. Okonjo | 2026-08-06 |
| Covenant compliance certificate delivered | 2400 · Long-term debt | R. Okonjo | 2026-08-10 |
| One item is open: the bank reconciliation on account 4471, because its tie-out is not attached. The other four are dated, owned, and not yet due. OPEN marks an item whose evidence is missing, and the long tick in the margin marks its line. | |||
Somewhere on your machine is a spreadsheet with about forty rows on it, and it is probably correct. What it cannot tell you is which of those rows slipped last quarter, because nothing timestamped any of them. A close item here is a record rather than a row: the entity, the period, the account it touches, a named responsible party, the kind of deadline it sits under, and the evidence that will close it. It closes on that evidence and on nothing else, so an item without its support stays open no matter who says it is fine.
The first thing this produces is a calendar with names on it, which is also the first time your close has existed outside a person.
Two kinds of deadline, one list, and no way to tell them apart: that is how most close calendars are built, including yours. A date a statute sets, a credit agreement sets, or a limited partnership agreement sets is somebody's legal obligation with a consequence attached. A day-three target you set for yourself is a management decision, and a good one. They are not the same object, and software that types them the same way teaches people to ignore both. The first kind runs here on machinery you cannot reach: owned by deterministic code, carrying a named responsible party, closed only by evidence, and never extendable by configuration. The second kind is yours to move, and moving it is recorded.
| Clock | Set by | Extendable by configuration | Responsible party | Closes on |
|---|---|---|---|---|
| Information returns furnished and transmitted | a statute | no | named at the entity | accepted transmission and furnished recipient copies |
| Covenant compliance certificate delivered | the credit agreement | no | named at the entity | delivery, with its arithmetic and its support |
| Close complete through day three | you | yes, and the change is recorded | named at the entity | every day-three item closed on evidence |
No configuration on this platform extends, shortens, or silences a deadline a statute or a contract set. Your own target you can move, and moving it lands in the record, because a target that quietly slides is a rumor again.
Bank Rec MAR (final)(2).pdf. The support exists, it is correct, and the only person who can connect it to the account it belongs to is the person who saved it there. Evidence that cannot be found is evidence that does not exist, which the request list will demonstrate in about nine months. The tie-out here is attached to the account, dated, sourced, and addressable by someone who has never seen your close before. That is the whole mechanism, and it is why a close can be handed to a successor rather than explained to one.
{
"object": "reconciliation",
"specimen": true,
"entity": "WESTFORD MILLING LLC",
"period": "2026-07",
"account": "1010 · Operating cash, account 4471",
"ledger_balance": { "amount": "1284310.55", "currency": "USD" },
"source_balance": {
"amount": "1291842.10",
"currency": "USD",
"source": "bank statement, 2026-07-31"
},
"reconciling_items": [
{ "type": "outstanding_check", "reference": "ck_10442", "amount": "-6218.00" },
{ "type": "deposit_in_transit", "reference": "dep_2026-07-31", "amount": "1200.00" },
{ "type": "bank_fee_unposted", "reference": "fee_2026-07", "amount": "-2513.55" }
],
"difference": {
"amount": "0.00",
"currency": "USD",
"derived": true,
"stored": false,
"derivation": "source_balance + reconciling_items - ledger_balance"
},
"tie_out": {
"attached": true,
"attached_to_account": "1010",
"sourced_from": "bank statement, 2026-07-31",
"dated": "2026-08-04T16:11:02Z",
"addressable": true
},
"closed_by": { "name": "A. Reyes", "role": "Staff Accountant" },
"accepted_by": { "name": "R. Okonjo", "role": "Controller" },
"fee": { "line": "Product Fee", "amount": "Price posts with the SKU" },
"note": "The tie-out is the artifact. Without it the item stays open and nothing meters."
}
"Professional fees are up ninety-two percent." Nobody needs software to say that. What is wanted, before the call where someone asks, is what moved it, named in your own accounts. A variance is surfaced here against the entity's own chart, with the transactions and the period comparison that produced it, drafted for the person who owns the account to accept, edit, or reject. The explanation is authored by that owner. The platform assembles the evidence for it, and the draft stays labeled a draft until a person signs their name to it.
Four acts, and everything else. Nobody should need a professional standards library open in another tab to know which call crosses a line, so here is the line: expressing assurance on financial statements, signing a tax return, representing your entity before a taxing authority, and giving investment advice are reserved. The rest of a close, the calendar, the entries, the reconciliations, the variances, the trial balance, the packages, runs agent-native. A call that reaches a reserved act does not fail, and it does not quietly succeed either. It comes back a typed BLOCKED naming the act, the authority, the party who may lawfully perform it, and what happens next.
These three carry no status because a status is a claim about a future, and these have none. They are not on a roadmap, not awaiting a license, and not waiting on a partner. No amount of licensing, contracting, or sponsorship clears them, because performing your close and expressing assurance on it are independence-incompatible: routing this to the people who did the close would be the violation, not the cure.
{
"object": "close.request",
"specimen": true,
"id": "req_01J9ASSURANCE00",
"entity": "WESTFORD MILLING LLC",
"period": "2026-07",
"status": "BLOCKED",
"blocked": {
"act": "EXPRESS_ASSURANCE",
"act_value_status": "DRAFT",
"reason": "RESERVED_ACT",
"detail": "Expressing assurance on financial statements is reserved to a licensed firm independent of the entity, under the accountancy act of the governing state and the applicable professional standards on independence. This platform does not perform it, and does not route it.",
"reserved_to_party": "a licensed firm independent of the entity",
"statutes": [
"the accountancy act of the governing state"
],
"routable": false,
"routable_value_status": "DRAFT",
"cure": {
"route": "NONE",
"route_value_status": "DRAFT",
"needs_human": true,
"human_route": "your own independent firm",
"description": "Performing this close and expressing assurance on it are independence-incompatible. Routing this to the people who did the close would be the violation, not the cure. Your independent firm performs it, and this record is what they ask for."
}
},
"charge": null,
"note": "No act was performed. Nothing was metered."
}
This is the one refusal at any of these addresses that no amount of licensing, contracting, or sponsorship clears, and it is deliberate. The suite never sells to the person expressing assurance on the books it closes.
Some of what is in your inbox is quietly waiting for a credential, and it has been waiting there because there was nowhere obvious to send it. Where a close item needs a credentialed reviewer, it routes to one who takes it under a named sponsoring entity's license, performs the act under their own name, and returns an Attestation: a statement of fact, never a conclusion about your entity and never an expression of assurance. A reasoned refusal is a deliverable and it is paid, because a refusal that costs someone money is not a refusal.
Accounting review routes to gigs.accountants, and tax acts route to the tax doors. Neither route is live. A call to a reserved act returns the typed refusal above and nothing is routed anywhere.
Somewhere in your accounts payable is an invoice for a month in which the thing you bought did not produce anything, and you paid it, because that is how the line was written. Plenty of tools bill for trying. This one bills for the thing it produced, and the difference shows up on the receipt rather than in the pitch:
accruals.finance. reconciliations.finance. journalentries.co. You may be wondering whether the part you need has a product of its own. It does not, and that is the design. A close is one record with many parts, so the suite is one door, and each name below is a section of this page rather than a separate thing to buy.
accruals.finance · held, RESERVED.reconciliations.finance · held, RESERVED.amortizations.finance · held, RESERVED.variances.finance and fluxanalysis.co · held, RESERVED.journalentries.co · held, RESERVED.trialbalance.co · held, RESERVED.capcalls.co · held, RESERVED.investorupdates.co, boardpacks.click, and quarterlies.click · held, RESERVED.payruns.co · held, RESERVED.forecasts.finance · held, RESERVED.Every name above is a section of this page and a name held in the register. None of them is a separate product, a separate price, or a separate key. Each one is already a holding page of its own, stamped RESERVED at its own address, and each says so there before it says anything here.
If you close for other people, none of the above changes and one thing does: you are doing it in three to eight systems, against as many charts of accounts, for owners who each believe their close is the only one. The method that makes that survivable is the same method that makes it expensive, because it lives in your head and it has to be rebuilt every month in a slightly different shape.
Your real product is reproducibility. This is where it stops living in one person.
If you are the person whose sign-off this needs, or the firm that expresses assurance on these books, this section is yours. Send it on as it stands: every claim below lands on a typed artifact printed earlier on this page.
Questions your firm or your counsel wants answered in writing: keys@apis.finance
| Door | What it is |
|---|---|
| monthend.finance RESERVED you are reading it | The close itself, kept as a record. Nothing on it is callable or priced today. |
| controllers.finance RESERVED | The same close suite, addressed to the person who owns the number rather than to the work product. It sells no SKU at its own address. |
| apis.finance LIVE | Where this suite's key is issued and where its prices are posted. |
| apis.credit ROADMAP | A sibling door, for business credit and lien data rather than for a close. Posted and priced in draft; not yet callable. |
| apis.loans ROADMAP | Origination, which is not the close. It stays at its own address until it is live. |
| apis.mortgage WAITLIST · entity-gated | Its own paper, its own entity gate, and no close on it. |
Entities and systems we close in, and whether they are our books or books we close for others:
Our close-day target, and what the last close actually took:
The first thing that breaks:
The same person answers mail at monthend.finance and controllers.finance.
Every reply is written by a person. You get an early read of the close record as it stands, and a place on the list for the first companies this opens to.
Agents: read /llms.txt. Where a close SKU is live, its price is on the family rate card.