Sample output · 1 of 3
A file of transactions in, a bookkeeping summary out: month by month and category by category, a table for each currency, and a workbook that carries the fixed line about what it is and is not.
The first task in a new project also sets up its computer (about 3 min).
Sort a list of transactions into a clear summary
Try this prompt
Use the Bookkeeping Summary skill on our transactions file for the first half of the year. The rules are rent to Rent, taxi to Travel and software to Software, and anything left over goes to Other. Give me the spend per month and per category, with the total of each month and of them all, in a workbook I can open.
Two files for one file of transactions: summary.xlsx, the workbook — a sheet for each currency, showing what was spent in every month and every category, and a second sheet with the fixed line — and the page images of both sheets. Plus a QA report.
| Field | Required | Hint |
|---|---|---|
| path | Yes | The transactions file, at most 200 characters, as a path inside the input folder |
| bytes | Yes | The size of that file in bytes, a whole number; the build refuses a file whose size is not the one stated |
| dateFormat | No | How the dates are written: ymd, dmy or mdy; the default is ymd |
| currency | No | The currency of the file, three letters; only used when the file has no currency column |
| rules | Yes | At most fifty rules: the category a transaction lands in and the text to look for in its description |
| leftovers | No | The agent's answers for the rows no rule matched: a row of the file and a category from the fixed list |
You say
Use the Bookkeeping Summary skill on our transactions file for the first half of the year. The rules are rent to Rent, taxi to Travel and software to Software, and anything left over goes to Other. Give me the spend per month and per category, with the total of each month and of them all, in a workbook I can open.
None
Node 20+; Python with openpyxl; Chromium (playwright-core) for the preview; no network at run time
None
path (The transactions file, at most 200 characters, as a path inside the input folder), bytes (The size of that file in bytes, a whole number; the build refuses a file whose size is not the one stated), rules (At most fifty rules: the category a transaction lands in and the text to look for in its description)
onlypro, claude-code, codex, cursor