When I joined, Steve was talking with some of guys and giving out ideas and permission to bring on others who can help on the sales side of things. John reported on his current state of flux - in between homes (his apartment flooded so he's been bouncing) and school starting.

Eric popped on and we went over some flow for financials (P&L and balance sheet and how things flow and get mapped). We went to a page (special system calculator called the financial flow calculator). See attached for a screenshot. This is a help file for the financial flow calculator. As a fun side note, Steve wanted me to build this page and special calculator tool way back. He and I have used it tons of times to play with P&L (income statement) and BS (balance sheet) mappings and flow. Anyways, Eric and I did a session on it going over some of his sales tax aggregates, sales tax liabilities, making payments on the sales tax liabilities, and earned credits for prompt or early payment of sales tax. Good little session.

Eric and I got into some advanced mappings over time. We also talked about helping to protect certain values (special accounts for sales tax liabilities and credits earned). Inside of adilas, the users can change and manipulate almost everything. Sometimes we have to limit certain actions (updating or editing) on things that are required and dynamic per corporation. Sometime we have to limit things on a technical side and sometimes just on a sanity side. Everything else, we let the users make all kinds of changes and then record the history of who did what. It's part of our methodology.

After we got done, I jumped in on the timecard reports and changed out a flag that we were having problems with. We changed it from looking at database values vs real-time calculations to a more simple check for problems with start and end dates. The code was a little bit deeper, but it makes it more simple and got rid of the erroneous errors or flags that it was showing. Much better now.