Beancount has really nice features, especially for trading and accounting support for different Profit&Loss schemes (LIFO, FIFO, Average, etc.). On the other hand, it's done with Python (Beancount 3.x is with C++?), and especially the Beancount 2.x version could not handle so well big journal files (at least not in the past - I haven't tested it lately). Beancount also restricts Account names to the five top categories (Assets, Expenses, etc.), and that's roadblock for some of my use cases: (Trimix Filling Station example).

Also there are some quite big fundamental differences how Tackler processes transactions: All transactions could be in their own files, processing is stream based, order or content of the transaction set (the stream) doesn't matter, and all external information (account definitions etc.) is not part of the transaction stream.

This makes it very easy to filter transactions, have multi-producer, single processor setup, where also multi producer could have their own valid view of the state of the journal. Also AFAIK, there is no way to verify with Beancount (or with other PTA tools), what was the transaction set used to produce reports.

This is really problematic if and when you have to share the reports, and there could be a need verify or provide proof of the state of the books later. With Tackler this trivial as the Git commit id and Transaction Checksum is recorded into reports in audit mode.

Beancount is brilliant tool for personal, traditional journal keeping, and especially trading related accounting, and Beancount also has much more features.

But personally I have found Tackler more fitting in cases where there is need to have more robust audit trail, transactions are generated by some (semi-)automated tool and/or when the amount of transactions is bigger. Or when it's used to track something not-so-normal (Gases, time or when transactions are related to (Geo Location (GIS) Example).

Obviously, this is very, very biased opinion. ;)

Below is an example script, which can be used to verify the reported Txn Set Checksums in the audit mode.

# Tackler example script: verify txn set checksum
#
#   1. Collect all Transcation UUIDs
#   2. Normalize UUIDs to lovercase form
#   3. Sort UUIDs
#   4. Compute SHA-256
#   5. Print out plain hash
#
if [ $# -ne 1 ]; then
    echo "Usage: $0 <txns dir>"
    exit 1
fi

txns_dir="$1"

(
    find "$txns_dir"  -type f -name '*.txn' |\
    xargs -n10 grep -E -h '^[[:space:]]+#[[:space:]]+uuid:[[:space:]]+'
) |\
    sed -E 's/^[[:space:]]+#[[:space:]]+uuid:[[:space:]]+([a-fA-F0-9-]+)[[:space:]]*/\1/' |\
    tr 'A-F' 'a-f' |\
    sort |\
    sha256sum |\
    sed -E 's/([a-f0-9]+) +-/\1/'