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.
note.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Follow our accounting procedure: fetch all journals and source sheets, create only clearly missing entries, stop at ambiguity, re-fetch results and report exceptions.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- 三野輪 慎太郎 / Shintaro Minowa
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- API-created MoneyForward journals and monthly spending notifications with reasons and next actions.
- Human involvement
- Humans set accounting procedures and handled exceptions; ambiguous or inaccessible evidence stopped registration.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Fetch all existing journals and authoritative sales and payroll records.
- Register only missing entries and fetch the results again.
- Send a separate read-only spending review for human decisions.
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
Frequently asked questions
Why not copy last month's amounts?
Sales and payroll can change; the source spreadsheets supplied current amounts.
What stopped a write?
Possible duplicates, missing source access or incomplete journal pagination.
Did it cancel subscriptions?
No. The separate spending workflow was read-only and proposed decisions.
More details
About this account
Codex ran monthly reconciliation, permitted missing-entry registration and read-only spending review.
Firsthand source opened and read. Suggested prompt written by us from the reported workflow; no original task prompt is quoted.
Credit: 三野輪 慎太郎 / Shintaro Minowa
Source published
Added to Agents In Use
Source checked
Tools and topics
MoneyForward MCP · Codex automation · Spreadsheets
Monthly bookkeeping · Journal duplicates · Spending review
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.