crftr / double_double Goto Github PK

Create a new ChartOfAccounts model where it has_many Accounts.

We should consider using the null object pattern for ChartOfAccounts. We can assume that having no Charts defined is to say that all accounts are in one global Chart.

(this issue was split from #3)

Originating from #3, this feature is more of an implication from #5 / enforcing a base currency.

The implication being: If it's possible to enforce a base currency; a mixed currency mode may exist in the absence of base enforcement.

Originating from #3, @danelowe proposed:

Each chart of accounts could then have their own base currency, and all amounts in any of it's accounts would be forced to use that currency.

The project that I'm working on at the moment requires transactions in multiple currencies.

I'd made some changes to make my tests pass when using a currency other than Money.default_currency (danelowe@99ab2fd), but then as I was committing I realised that the solution would actually be to create a form of multi-tenancy, where accounts could (but wouldn't have to) belong to a chart of accounts.

Each chart of accounts could then have their own base currency, and all amounts in any of it's accounts would be forced to use that currency.

What are your thoughts on this? I'll get started on it as soon as I come to that stage in the project.