Thanks for the examples @Brucanna / @Tut. Found them both helpful to understand.
Trying to separate actionable changes to the cash/accrual calculation that @lubos could consider, from the rest of the discussion.
From an accounting point of view, I’d assume that getting the calculation correct is most important, and the user interface to control that comes second (but is still important to consider).
With Tut’s example, it sounds like Billable Time that has not yet been invoiced (Billable time - movement account) should affect reports under the accrual basis. Is that correct?
Based on lubos’ comment, this is not currently how it works, as he wrote that the program currently only considers invoices. So there may be a change required in that calculation to also consider the value of uninvoiced Billable Time, irrespective of any user interface changes being discussed.
With Brucanna’s example, my understanding is that most or all of those are adjustments entered manually into the journal. So until they are entered, there is no way for the program to differentiate from a programming / calculation point-of-view, because it doesn’t know about the need for an adjustment.
The difference between cash vs accrual here is entirely within the realm of the accountant’s head, until it gets entered into Manager. At that point, it’s been locked in as an adjustment, because it now exists as a journal entry record.
If that journal entry uses accounts like Billable time - movement or Accounts receivable or Accounts payable, perhaps Manager should treat that entry differently based on the accounting basis in use.
Which brings me back to lubos’ comment, that the calculation currently only considers invoices. Perhaps a change is required there.
I think it’s important to consider what is subjective vs what must not be changed. The user interface, naming of items, etc is important; but subjective … the most important thing would be to ensure the calculation is correct so that reports show accurate values.
If the developer believes that only invoices affect the calculation difference in a cash/accrual basis, then that is probably correct from the program’s point of view. If it is not correct from an accounting point of view, that’s a problem to be fixed.
It just feels like the elephant in the room is being ignored.