Skip to content


Repository files navigation


The plain text accounting tool of the future. Keep track of your πŸ’΅, πŸ•˜, πŸ–, πŸ„, 🍻 on your command line.

Screenshot Balance

For help, please come visit us on our GitHub Discussions page!


  • Easily editable and processable file format based on YAML
  • Modeled on transactions instead of debiting / crediting accounts => Support for complex transactions made up of several transfers
    • Dedicated payer (from) and payee (to) fields (ledger only supports payee)
  • No misuse of accounts as categories / tags => Direct support for tags
  • Clear separation between
    • Physical account (e.g. wallet, bank account)
    • Entities (e.g. my mum, a company)
    • Purpose of transaction (e.g. food, travel)
  • No hard-coded asset / liability connotation as it is viewpoint dependent => Choose viewpoint by setting the owner of the journal
  • Initial balances
  • High precision timestamps in ISO 8601 format
  • Reference external files (e.g. receipts, contracts, bank statements, …)
  • Safety checks
    • BigInt fractional numbers to eliminate rounding errors
    • Verifies exclusive use of predefined entities
    • Checks in transactions match with verification balances
    • Checks that referenced external files exist and that all external files are referenced
  • Export to other formats for post-processing
    • Gnuplot (for trends)
    • (H)ledger Format (for using (H)ledger exclusive features)
    • CSV and TSV (for further processing in spreadsheet software)
    • XLSX aka Excel (for further processing in spreadsheet software)
  • Multi file support


Transity is distributed as a JavaScript bundle and can therefore be installed via npm:

npm install --global transity


While Transity is licensed under the AGPL-3.0-or-later and can therefore be used free of charge, I hope you will acknowledge the work and effort it takes to maintain and improve this software and make a donation via my GitHub Support page.

If you find Transity valuable and/or use it regularly this should be a small nuisance for you, but it would mean the world for me! It would mean that I can spend more time on this project and bring it to the next level!

Thanks a lot for your support!

For including Transity in proprietary closed source products, please contact me!


$ transity balance examples/journal.yaml
          anna       1        evil-machine
                -49978.02     €
           ben     -50        $
                    -1.432592 BTC
                  -100        €
     evil-corp      -1        evil-machine
                 50015        €
      good-inc    -100        €
  grocery-shop      11.97     €
  john             371.04     €
                    50        $
                     1.432592 BTC
      :default     219.99     €
          giro      50        $
                     1.432592 BTC
                    85        €
        wallet      66.05     €

If linked modules aren't exposed in your path you can also run

cli/main.js balance examples/journal.yaml

List complete usage manual by simply calling transity without any arguments.

$ transity

Usage: transity <command> <path/to/journal.yaml>

Command             Description
------------------  ------------------------------------------------------------
balance             Simple balance of all accounts
transactions        All transactions and their transfers
transfers           All transfers with one transfer per line
entries             All individual deposits & withdrawals
entries-by-account  All individual deposits & withdrawals grouped by account
gplot               Code and data for gnuplot impulse diagram
                    to visualize transfers of all accounts
gplot-cumul         Code and data for cumuluative gnuplot step chart
                    to visualize balance of all accounts

Screenshot Transfers

Check Order of Entries

Check if all entries are in a chronological order

ag --nonumbers "^    utc:" journals/main.yaml | tr -d "\'" | sort -c

Retrieving Data from Banks

Transity includes a few scripts located at ./scripts to automate a Chrome browser to download data. It supports downloading CSV files of all transactions and converting them to journal files and retrieving the current account balance:

Currently supported accounts for transactions:

Currently supported accounts for balances:

Contributions are very welcome!

Script Usage

node scripts/transactions/hypovereinsbank.js > transactions.yaml

This will prompt you for your credentials and afterwards automate a headless Chrome instance to download and convert the data.

Journal File Format

A minimal journal file is a YAML file with following format:

owner: anna
  - id: €
    name: Euro
      - EUR
    note: Currency used in the European Union
    utc: '2017-04-02 19:33:53'

  - id: anna
    name: Anna Smith
    utc: '2017-04-02 19:33:28'
      - person
      - id: wallet
        name: Wallet
        note: Anna's black wallet
        utc: '2017-04-02 19:33:28'
          - wallet

  - id: evil-corp
    name: Evil Corporation
    utc: '2017-04-02 19:33:28'
    note: The Evil Corporation in the United States of Evil
      - company

  - title: Purchase of evil machine
      - utc: '2017-02-17'
        from: anna
        to: evil-corp
        amount: 50000 €
      - utc: '2017-02-17'
        from: evil-corp
        to: anna
        amount: 1 evil-machine


By default all accounts are plotted. To limit it to only a subsection use awk to filter the output.

For example all transactions of Euro accounts:

transity gplot examples/journal.yaml \
| awk '/^$/ || /(EOD|^set terminal)/ || /€/' \
| gnuplot \
| imgcat

Or all account balances of Euro accounts over time:

transity gplot-cumul examples/journal.yaml \
| awk '/^$/ || /(EOD|^set terminal)/ || /€/' \
| gnuplot \
| imgcat

Screenshot of cumulative account balance plot


AI Powered

We built a dedicated OpenAI GPT to convert any financial data (e.g. CSVs, bank statements, chat history, …) to a Transity journal file.

Check it out at

From Ledger CLI

Execute the included ledger2transity script:

./ examples/hledger.journal > transactions.csv

Convert transactions.csv to YAML with e.g.


  • Merge adjacent entries as each entry only debits / credits an account. A transaction always involves 2 accounts (from and to). (For expenses basically copy the ledger-account from the second entry into the from field of the first entry)
  • from and to might be reversed for income (depending on how the payee field was used)
  • Account names of Ledger-CLI are interpreted as tags Transity understands accounts as physical accounts
  • The note is duplicated in the tags field. There is no way to get only the tags in Ledger-CLI πŸ˜”


Why another plain text accounting tool?

Existing accounting tools are historically based on the notion of an account. You add money (debit) and you remove money (credit). (If this sounds backwards to you, read this explanation)

For example you get 50 € from your mum and buy some food for 20 €.

Account | Debit   | Credit
Wallet  | 50.00 € |
Wallet  |         | 20.00 €

Simple, but also incomplete. Where did the money come from, where did it go? This led to double entry bookkeeping. Whenever you add some money to an account, you have to remove the same amount from another.

Account | Debit   | Credit
Wallet  | 50.00 € |
Mum     |         | 50.00 €
Wallet  |         | 20.00 €
Food    | 20.00 € |

But you must never forget a posting, because otherwise your account won't balance.

Account | Debit   | Credit
Wallet  | 50.00 € |
Mum     |         | 50.00 €
Wallet  |         | 20.00 €

Oops, where did the money go? πŸ€·β€

If this looks (and sounds) confusing or too complicated, you're not alone! It made sense in former times as this layout makes it easier to add up the amounts by hand, but not in times of computers.

So how can we simplify it? It's actually quite easy: We just have to model it in terms of transactions, and not accounts.

Amount | From   | To
50 €   | Mum    | Wallet
20 €   | Wallet | Food
  • Simple - No more confusing debit / credit / asset / liability mumbo jumbo
  • Intuitive - Just like you would talk about it
  • Safe - It's obvious if you forget to fill out a field

Together with some further changes it yields an easier to understand, more robust and more complete representation of accounting!

Why is it written in PureScript?

PureScript leverages strong static typing and can therefore give more guarantees about the functionality of the code than weakly typed or untyped languages (like JavaScript).

You wouldn't want your money to get lost in rounding errors or be turned to undefined, would you? πŸ˜‰

Why is it not written in Haskell?

PureScript can also easily be used in the browser or get deployed as a cloud function as it simply compiles to JavaScript. With Haskell you'd have to use another language for a web frontend or quarrel with experimental stuff like GHCJS.

Comparison with Hledger

(H)ledger's transactions are a (balanced) group of account postings. Transity's transactions are a group of transfers between two accounts.


Checkout the files hledger.journal and journal.yaml for similar transactions modeled in Hledger and in Transity.

There is a lot of ambiguity in the ledger journal format. Are you able to tell the difference between the 2 options?

2019-01-17 Bought food
  expenses:food  $10

; vs

2019-01-17 Bought food
  expenses:food  $10

Also, it lacks some fields for more precise recording of which parties where involved.

  • What food?
  • Where did you buy it?
  • When exactly did you buy it?
  • Which supermarket?
2019-01-17 Bought food
  expenses:food  $10


hledger --file examples/hledger.journal balance
# vs
transity balance examples/journal.yaml
hledger --file examples/hledger.journal register
# vs
transity transactions examples/journal.yaml
hledger --file examples/hledger.journal register --output-format=csv
# vs
transity entries examples/journal.yaml

Missing features


Measured with hyperfine including 3 warmups on an early 2015 MacBook Pro.

For a journal file with around 2000 entries:


Benchmark #1: transity balance journals/main.yaml
  Time (mean Β± Οƒ):      1.287 s Β±  0.021 s    [User: 1.790 s, System: 0.140 s]
  Range (min … max):    1.250 s …  1.324 s    10 runs


Benchmark #1: hledger -f test.ledger balance
  Time (mean Β± Οƒ):     409.6 ms Β±   6.1 ms    [User: 366.6 ms, System: 28.5 ms]
  Range (min … max):   398.8 ms … 417.6 ms    10 runs


Benchmark #1: ledger -f test.ledger balance
  Time (mean Β± Οƒ):      76.3 ms Β±   9.1 ms    [User: 62.7 ms, System: 9.4 ms]
  Range (min … max):    65.1 ms … 101.8 ms    28 runs


  • Features for duplicates
    • Print list of possible duplicates
    • Label an entry explicitly as a duplicate to store it in several places
  • CSV import
  • Dashboard
  • Budgets (including progress visualization)
  • Cache-files to speed up processing of large data sets
  • Generate EPC QR Codes for transfers
  • LSP server for journal files
  • Export to Graphviz (for account / entity relations)
  • Export to JS-Sequence-Diagrams (sequence of transactions)
  • Meta data for all entities (transactions, accounts, entities, …)
  • Nanosecond precision for timestamps
  • Additional features for crypto currencies
  • Commodities
    • Treat as scientific units (e.g 1 k€ == 1000 €)
    • First class support for any type of commodity (e.g. time and messages)
    • Support for time limited commodities (e.g. subscription for a month)
    • Define which are allowed / prohibited for each account
    • Hard vs Soft vs Fungible vs …
  • Differentiation between transfers, transactions & exchanges
    • Special syntax for exchanges
  • Support for all states of transaction life cycle
    1. Request - Request to exchange a commodity
    2. Offer - Specification of commodity & expected trade item
    3. Acceptance - Affirmation of interest in offered exchange
    4. Fulfillments
    5. Certification - Acknowledgment that exchange was performed

Entry / Value Date

There are no separate fields for entry or value dates necessary. Simply use ISO 8601 time intervals to specify the duration of a transfer.

  - id: '123456789'
    note: Deposit of savings
      - utc: 2018-01-04T12:00--05T22:10
        from: john
        to: bank
        amount: 100 €


This is a first concept of an alternative syntax for the journal file:

# Comments after a hash

2016-04-16 18:50:28
| 1 year registration of domain ""
+tagOne  # Tags are written after a plus
id: 20135604  # Arbitrary metadata
# Transactions are indentend by 2 spaces
  john -> paypal : 9.95 €
  paypal -> namecheap : {10 + 0.69} $
  paypal -> icann : 0.18 $ +fee
  namecheap -> john : 1 Domain


For a full list of plain text accounting tools check out Here are some of the links that are especially relevant for Transity:

Other Plain Text Accounting Tools

  • Ledger - The original command line accounting tool (written in C++).
  • Hledger - Ledger clone with a focus on UX, reliability, and real-world practicality (written in Haskell).
  • Beancount - Double-entry accounting from text files (written in Python).
  • Rust Ledger - Ledger clone that uses YAML as well (written in Rust).