JevMade hello@JevMade.com
← Back to guides

JevMade field notes / Worked recipe

Sort bank transactions while keeping the sums exact

A budgeting recipe asks Jev to interpret merchant descriptions, while ordinary software separates income from spending and calculates category totals.

Original by Jeroen Erne / NexibeoClassification

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits and license

“08 · Bank transaction categorizer” by Jeroen Erne / Nexibeo. Read the original source.

This expanded guide is an AI-narrated adaptation of the source’s essential explanation, examples and caveats, not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

License: MIT

MIT License

Copyright (c) 2026 Jeroen Erne (https://nexibeo.com, https://completeaitraining.com)

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Our summary

Bank statements often use shortened merchant names that are hard to recognize. This recipe asks Jev to place transactions into budget categories and flag merchants that usually represent recurring bills. It works from a sample statement or a supplied transaction file.

The program first checks whether money entered or left the account. It only offers categories appropriate to that direction, preventing some impossible answers before asking Jev. The model interprets the description, while regular software calculates totals and can apply known merchant overrides.

A merchant can sell several kinds of goods, so its name may not reveal what someone bought. A likely recurring merchant is not proof of a repeating payment. The author's sample includes an ambiguous shop classification, illustrating why people still need to check important categories.

Key takeaways

  1. Use known payment direction to narrow the options.
  2. Calculate totals with ordinary software.
  3. Keep explicit exceptions for merchants whose transactions you understand.

Transaction descriptions and payment direction go to Jev; amounts stay with the program for sums. Check whether real bank descriptions may be shared before using them. This is not financial advice, and JevMade did not reproduce the results.

GitHub cookbook · Source reviewed

Read the original guide Opens the author’s site in a new tab.