JevMade

Sign in
← 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 /

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.

GitHub cookbook

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

Your note

Only you can see this. Clear the text and save to remove it.

Keep what you save

Sign in to keep bookmarks and private notes on every device. We email you a link; there is no password, and the same link creates your account.