For every transaction on Open Collective, multiple transactions are created to reflect the differences in every party's balance. Read on to learn more about how transactions are paired and grouped.
Last updated
Was this helpful?
Transactions are always created in complementary pairs: a credit transaction and a debit transaction. For example, when Contributor A makes a contribution to Collective B, two transactions are created:
Or when an expense is paid from Collective B to Payee C, two transactions are also created:
Though the “transactions pairs” is a fundamental ledger pattern and it may sound like it is compatible with double entry book keeping, it isn’t.
Usually transactions are created in groups that have a shared context. For example, when a contribution is made by Contributor A via Stripe to Collective B that is hosted by Fiscal Host C the following transaction group will be created:
A pair of CONTRIBUTION transactions.
A pair of PAYMENT PROCESSOR FEE transactions.
A pair of HOST FEE transactions
Different users sees a different perspective of the same ledger. The perspective a user sees depends on the account through which they are looking at the ledger. Typically each account sees only transactions related to it. Fiscal hosts are an exception since they see both their own transactions and the transactions of the collectives they host.
In the following contribution example, the contributor will see just one transaction, their contribution debited from their account:
A collective admin will see three transactions which correctly represent the contribution and two fees, resulting in a net $8.50 for the collective:
The Stripe account (though it has no users, there is a global Stripe account to which transactions are attributed) will show just the payment processor fee that it charged:
Fiscal hosts see the largest amount of transactions since they see both their own transactions and the transactions of their hosted collectives (for which they are fiscally responsible):
See more about .
