Month-End Accrual Schedule: A Journal That Matches the Contracts Behind It

The schedule is right on day one and wrong by day four

A month-end accrual schedule starts with a close policy and a contract list. Each in-scope contract gets one treatment: accrue the month's amount because the service was delivered and the customer has not been invoiced yet, mark it billed because the month's invoice has already gone out from Stripe, hold it because something is in dispute, or exclude it. The treatment, the reason and the month amount go on the contract record, and the journal is built from those fields.

Contracts sit in Airtable, the close policy in Notion, invoices in Stripe, and every notice that follows lands in a run folder on Google Drive: invoice reconciliation, GL assignment, a pricing dispute, an amendment. Each notice names one contract. The damage comes from what it does not name, such as an amendment that changes a rate card other contracts use, or a resolution that should release a hold.

Who works in the room

The close team keeps one Kylon room for each month-end. Nova is the default agent and leads any thread about a contract's treatment. Ada owns the journal file review, so a question about a journal line goes to it without a mention. When a recomputed amount changes what a contract owner was told, Nova opens a thread for Fin whose first message carries the contract, the old amount and the new one, and Fin drafts the reply from there.

Close week, in order

The precedence in the Notion policy is restated in the room guidelines. Every Stripe lookup Nova makes is kept in the run history step by step, which helps when an auditor asks how an amount was reached.

Notices that name one contract and move three

Every notice after the first pass is a change request in disguise. When the Larkspur amendment arrives, the obvious work is to recompute Larkspur. Nova does that, then re-checks every contract in the portfolio, because the amendment also moves the rate card two other contracts are priced from. All three changes are proposed together, each with the line of the notice that caused it.

Holds behave the same way. When legal resolves a dispute and reinstates an amount, that contract goes back through the full precedence list rather than simply switching back to accrue. Every contract still on hold at the end of the cycle gets the month it is carried to, so nothing disappears between closes. Fin drafts one reply on each named thread with the new amount, and the controller sends it.

What the checks catch

• A Stripe invoice found by a near match instead of its exact id, when the neighboring id belongs to a different customer and amount
• A journal line for a held or excluded contract, which is removed rather than corrected
• A journal line with two wrong fields, recorded as two corrections, not one
• A contract whose amount moved because of an amendment that named a different contract
• A contract still on hold with no carried-to month

What stays with people

• Approving every treatment and amount before Nova writes it to Airtable
• Assigning GL accounts where the policy leaves a choice
• Interpreting a dispute resolution with legal counsel
• Sending each reply, which Fin prepares as a Gmail draft, and signing the closeout

Integrations in this workflow

Kylon is not an accounting system and it does not replace one. It sits across the contract table, the billing account and the policy the team already keeps, and carries the coordination none of them holds on its own.

• Airtable
• Gmail
• Google Drive
• Notion
• Slack
• Stripe

• Airtable holds the contract records, their treatments and amounts, and the closeout journal lines
• Stripe holds the invoices each contract references, looked up by exact id
• Notion holds the close policy and its precedence list
• Google Drive keeps the run folder: notices, the draft journal file and the closeout rules
• Gmail carries the threads with contract owners, with replies drafted for the controller to send
• Slack is where billing and account owners post contract news between notices

Where to start

Run one month-end. Connect the Airtable base that holds your contracts through a lasting grant the controller approves for this room, point Nova at the close policy in Notion, and add one rule to the room guidelines: any notice re-checks the whole portfolio, and no amount changes until the controller approves.

“The notice names one contract. The check covers all of them.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.