HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
envato
double_entry
Ruby2020–2023
envato / double_entry

double_entry

A double-entry accounting system for Ruby applications.

2Distinct people
3Mentions
0Explicit recommenders
461GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A double-entry accounting system for Ruby applications.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year3 dated mentions

Observed mentions: 2020-05-29 19:16:46 UTC to 2023-01-31 04:43:35 UTC.

0122020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202

What Hacker News says

3 sources
>> While this gem acts like a double-entry bookkeeping system, as it creates two entries in the database for each transfer, it does not enforce accounting rules. > And that seems like a far cry from things like "rejecting transfers if the accounts involved would exceed their net debit or credit balances". The READEME needs to be updated[1] for clarity. It doesn't enforce "accounting" rules, however The DoubleEntry gem has rules to optionally ensure a balance cannot go negative, and it also has an allowlist of allowed transfers ( which are defined by source account, dest account and code ). [1] https://github.com/envato/double_entry/pull/216/files > I think they key part is "distributed financial accounting database". For anything that didn't need to be distributed to handle massive volume of transactions I'd also pick Postgres, but I can
Read the rest
imagine there's a limit where that wouldn't work, and as soon as you need to do this in a distributed database things get exciting. That is why I qualified my statement with "you're using Postgres for your main app db". For every financial transaction you'd likely have many more business logic level transactions, and you would want your business transactions to be as consistent as your financial transactions. No point storing a financial transfer if you can't match it up with a purchase on your business db.
In TigerBeetle raises $6.4M to power the future of financial accounting infra
I'm not convinced by the seperate DB/API. Advantages for using Postgres ( assuming a double entry schema[1] ) and you're using Postgres for your main app db; - You can do financial transactions inside business db transactions, and roll back both atomically - Adding up numbers is one of the things computers are best at, and Postgres can easily handle a huge amount of financial transactions - Re-use PaaS Postgres hosting/scaling/clustering/backups - Easier integration with the rest of your app with foreign keys to relevant records relating to the financial transaction - Easy integration with BI tools given Postgres is well connectable [1] Roughy `account(id, cached_balance)`, `transaction_lines(src_account, dst_account, amount)` This gem does literally billions of dollars worth of financial accounting for various companies
Read the rest
at scale: https://github.com/envato/double_entry It's dated, the API is a bit messy and needs work, as it was initially written 10+ years ago, but for a web based app I would choose a v2 of it over a non-postgres ( assuming you are using Postgres for your app ) solution.
In TigerBeetle raises $6.4M to power the future of financial accounting infra
This is pretty cool, I'd wonder how it compares to an open source accounting library like double_entry. I guess I'd be hesitant to integrate with an external service if I could accomplish the same thing with a library. Have no idea if there's a market for this (I'm certainly not a customer), but something none of these libraries are set up to do is convert these balances to erc-20 tokens. The combo of a SaaS with a simple API like this and a trusted mint to sync balances to erc-20 tokens could be interesting. [0]: https://github.com/envato/double_entry
In Show HN: An API to store balances and transactions

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.