Single-entry accounting schema I've already built a double-entry accounting schema on a previous app, and it was very complicated. For a new app I want the simplest and most elegant accounting schema possible (transaction volume is low, and uncomplicated).

People can earn money via ad on their website (like google adsense)
We issue them payments for their earnings at a varying interval (weekly, monthly, etc)
Their account can be debited (eg. their website had fraud robot visits), or it could be credited (signup bonus, or a technical error where we didnt pay them enough)

In its simplest form, I have a transactions table with these core columns (ignoring other fluff columns):

id (string)
type (enum: DEBIT/CREDIT)
description (string)
amount (integer)

All of this is well and good, there is only 2 confusing parts that I would like someone to tell me if my solution is sane or not.

First is the fact that earnings need to be &quot;settled&quot; in some way. Fraud and other hiccups are common, so &quot;live&quot; earnings are constantly adjusted. Without an intermediate settlement step, these price variations disappear into the ether.

So my first idea as to create a transactions record every single day for the previous days &quot;settled&quot; earnings. It might look like this, including one demo &quot;fraud&quot; example:
&quot;CREDIT&quot;, &quot;User Earnings - Jan 3, 2021&quot;, 12021
&quot;CREDIT&quot;, &quot;User Earnings - Jan 4, 2021&quot;, 8319
&quot;CREDIT&quot;, &quot;User Earnings - Jan 5, 2021&quot;, 9130
&quot;DEBIT&quot;, &quot;Fraud Adjustment&quot;, 771

Question 1 is, &quot;does this seem sane so far?&quot;

The next confusion deals with how to cleanly link a payment (transaction) with other transactions (the 4 rows above).

If I wanted to pay the above 3 earnings rows + 1 adjustment row, it would look like this:
&quot;DEBIT&quot;, &quot;User Payment&quot;, 28699

This is fine, except that it's not in the database which transactions this transaction is associated with. One solution might be to make a many-to-one relation on transaction to itself, but a transaction being associated with other transactions feels &quot;wrong&quot;.
I envisioned when an admin issued a payment, it would show a list of all un-associated transactions with checkboxes next to them you could choose from, which would make those transactions tied to the payment somehow, and then they wouldn't accidentally be paid for again, as they would disappear from the list.
My biggest fear is re-inventing the wheel. I'm OK with doing a simpler solution if its &quot;normal&quot; in the real world. I don't want to be a single developer trying to &quot;invent&quot; a solution that's actually really stupid and is easily solved in a different way.
Thank you!
For your first question, that's an appropriate approach to balancing the Transactions. Every monetary change should be recorded as a Transaction. So at whatever rate you consolidate things like fraud, e.g. once a day (or as frequent as every minute, doesn't really matter as long as you record the Transaction for the consolidated amount every time) will result in how many of those kinds of Transactions to be generated.
To your second question, there's nothing inherently wrong with it being a one-to-many relationship, and business context aside, that's how I'd first imagine it. Bringing business context back in, normally a financial system in this space would handle these things through journaling. The concept of a journal is usually represented by two tables, JournalHeader and JournalLines. The JournalHeader represents generic information such as who created it and when it was created, whereas the JournalLines represent the individual Transactions consolidated via settlement. Usually there's a field on the JournalLines table that ties back to the original source of the transactions that were consolidated (generally another table, e.g. if there were SalesOrders that generated Transactions, the JournalLines would tie back to the original SalesOrder they consolidated). This relationship is one-to-many in nature, and standard.
I'm a little fuzzy on the exact implementation of such (as I haven't worked with that kind of finance in a while), but hopefully that helps paint the picture. Long story short, it is ok and normal practice to have a one-on-many relationship between the settling Transaction to its settled Transactions.