Codex to register missing accounting entries

Shintaro Minowa connected Codex automation to MoneyForward's remote MCP through a local bridge to handle recurring accounting for his company. The task was more careful than copying last month's entries: sales and payroll amounts could change, and bank or card integrations might already have recorded the same event.

At the start of the month, the automation fetched existing journals, consulted the sales and payroll spreadsheets, and compared candidates with manual, API and bank-created entries. It registered only items judged missing, then fetched the month again to check the result. Minowa shows masked entries marked as created through the external API.

A procedure stored in the repository defined which data supplied amounts and how duplication was handled. Pagination had to be exhausted. Missing spreadsheet access or an uncertain duplicate caused the process to stop and report the issue rather than substitute last month's figures. Humans retained exceptions requiring judgment.

A second monthly automation used MoneyForward read-only to review spending. Its notifications separated possible cancellations, pauses, plan changes and unclear purposes, while excluding payroll, taxes and known necessary charges. No automatic subscription cancellation or measured saving is reported. The useful boundary is explicit: journal creation follows documented evidence and rechecks, whereas spending recommendations remain a review list.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: note.com · 三野輪 慎太郎 / Shintaro Minowa