US and UK Receivables Close: Final-Rate Balances and Approved Write-offs

Two entities, two currencies and a rate that is not final yet

Closing receivables for a US parent and its UK subsidiary is judgment applied one record at a time. Every open invoice gets a disposition: current, past due, disputed or proposed for write-off. GBP balances are translated to dollars for the group view, each exception gets a review window and an owner, and write-offs follow the memo the controller signed. The rules fit on a page. Applying them to a few hundred records, twice in one close, is where it slips.

The receivables sit in Salesforce, payments and disputes in Stripe, the write-off memo in Google Docs, and the month-end rate arrives as a message from treasury in Slack. The first pass has to run on a draft rate because the final one is published after month end. When it lands, someone re-translates the GBP balances they remember. A closed dispute gets read as a paid invoice, and review windows on changed rows keep running from the old dates.

Who works in the room

The close runs in one room per month, and Ryan is its default agent: a message about a balance or a disposition that names no one goes to Ryan. Ryan is also the only agent that can use Stripe, through a lasting grant the controller approved for it. Questions about the memo, or about a row someone disputes, go to Ada by specialty. When the controller approves the final records, Ryan opens a thread for Myco whose first message is the brief for each closing memo, and Myco leads from there.

The month-end close, step by step

Each stage reads the current records and stops at a person before anything is written.

When the rate or the memo changes after the first pass

The draft rate is a placeholder and everyone knows it. When treasury posts the final rate, Ryan re-derives every open GBP receivable, not only the large ones. A small move in the rate can carry a balance across the write-off amount and change the approval it needs, so a partial re-run leaves the close disagreeing with itself. Every row that changes gets its review window reset, and the collections clock starts again from the figure the controller approved.

Memo changes get the same treatment. When version two of the write-off memo adds the CFO's approval above a set amount, Ada reads both versions side by side and lists the rows the new rule reaches. Those rows stay proposed until both approvals are recorded in the thread. Rows the change does not reach keep their approval, and the thread shows which version each decision was made under.

What the checks catch

• A GBP receivable still carrying the dollar amount from the draft rate after the final rate was posted
• A receivable marked current because its Stripe dispute closed, when the invoice is still unpaid and past its due date
• A re-derived row whose review window still runs from the first pass
• A write-off above the memo v2 amount with only one of its two approvals on record
• A payment that cleared in Stripe on the last day of the month but has not reached the Salesforce receivable

What stays with people

• Approving each disposition, amount and write-off before Ryan writes it to Salesforce
• Setting the month-end rate, which belongs to treasury
• Sending every customer note Myco drafts in Gmail
• Signing the closing memo for each entity

Integrations in this workflow

Kylon is not a consolidation tool or a general ledger, and it replaces neither. It sits across the receivables, payment and document tools the close already depends on and holds the coordination between them.

• Gmail
• Google Docs
• Google Drive
• Salesforce
• Slack
• Stripe

• Salesforce holds the receivable records, with disposition, dollar amount and review window on each
• Stripe shows the payments, refunds and dispute outcomes behind every invoice, which Ryan reads and never changes
• Google Docs holds both versions of the write-off memo and the two closing memos
• Google Drive keeps the close folder with the checklist, the rate file and last month's memos
• Gmail carries past-due notes to customers as drafts the collections lead sends
• Slack is where treasury posts the draft and final rates and the UK team flags late receipts

Where to start

Take one month and one pair of entities. Connect the Salesforce object that holds receivables, approve a Stripe grant for Ryan in this room, and put the write-off memo in the close folder. Then write the one rule that matters into the room guidelines: no disposition, amount or write-off reaches Salesforce until the controller approves it in the thread.

“The final rate moved most balances by a few dollars. The close is right because every one of them moved.”

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.