Purchase journal converter / formatter.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Artémis 9060066698
smash dat estinien
4 weeks ago
src base commit 4 weeks ago
.editorconfig base commit 4 weeks ago
.gitignore base commit 4 weeks ago
Cargo.lock base commit 4 weeks ago
Cargo.toml base commit 4 weeks ago
LICENSE base commit 4 weeks ago
README.md smash dat estinien 4 weeks ago


Tataru (CNPLv6+)

Tataru is a capitalist popoto a purchase journal converter and formatter, made to uniformize and group multiple purchase journals from multiple sources into a single two-pages excel file, split into income and expenses.

What is Tataru?

The core use of tataru is to group multiple purchase journals, of multiple formats, into a single common journal that will be simpler, clearer, and more unified to read.

One of the big goals for this tool is to ease the ability to copy/paste data from your purchase journal into your accounting software / spreadsheet.

What isn't Tataru?

Tataru isn't an accounting software in itself. It aims at being a good middleware between your bank(s) and your accounting software, but will not try to replace it.

How to use Tataru?

Section to write.

Why call it Tataru?

Have you heard of the critically acclaimed MMORPG Final Fantasy XIV with an EXPANDED FREE TRIAL? Which you can play through the entirety of A Realm Reborn and the award winning Heavensward Expansion up to level 60 for FREE with no restrictions on playtime.

TODOs and goals

Those are the main goals for the first version of this project.

  • Output format
    • 2-pages excel (income and expenses)
    • 4 columns
      • Payment date (YYYY-MM-dd, customizable)
      • Payment label
      • Payment amount (always positive)
      • Origin file
  • Input configuration
    • List of structs
      • File name
      • Importer
  • Filters (applied on the label)
    • Regex
    • Kind (exclude / include)

Those are things I'd really like to have.

  • Label reformatting (e.g. to provide a clearer label than some labels); would work with regexes
  • Paypal payment double-check support (i.e. validate that the payment is seen on paypal, and attach the paypal label)
  • Refunds identifier (would probably end up in a third tab, for clearness)

Those are topics that are still left to wonder.

  • Simpler formatter creation than code edition
    • Is there a good way?
    • Scripting language embed?
      • Could embed JanetLisp pretty easily