Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Brandon Moore
Created Date/Time: 4/17/2017 10:31 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 2582
Template/Type: Brandon Time
Title/Caption: Adilas Time
Start Date/Time: 5/4/2017 9:00 am
End Date/Time: 5/4/2017 12:30 pm
Main Status: Active

Sorry, no photos available for this element of time.


Uploaded Media/Content & Other Files (3)
Media Name   File Type Date Description
small_drawing_of_tons_of_projects_including_financials.jpg   Image/JPEG 5/4/2017 This is a small graphic that shows a number of converging projects and how tons of them are sales related and some will trickle down into the financials. From a meeting between Steve, Brandon, Kelly, and Danielle.
month_by_month_p_and_l.jpg   Image/JPEG 5/4/2017 This is a screen shot of the month over month P&L that Danielle made for a client using MS Excel.
year_over_year_trial_balance.jpg   Image/JPEG 5/4/2017 This is a screen shot of the year over year trial balance sheet that Danielle had created in MS Excel for a client.


Notes:
On the daily GoToMeeting session with Steve. We started out the day just working through some small tweaks and making some new changes.

9 to 10:30 am - Making a few small changes. We added in a small tweak to the my cart favorites buttons. We made all of the disabled subs disappear from the my cart favorites view for smart groups. All other sub views were left alone. We also added in a date/time stamp to the advanced invoice searches. We added the date/time stamp to main invoices and invoice line items. This will help users see when the invoices were created.

10:30 am - Meeting with Kelly and Danielle about financials and such. In the financial world, they really want to see certain reports and certain views. This is huge for owners, investors, auditors, CPA's, and bankers. They expect a certain format and certain key indicators and such.

- We talked about a possible policy about pushing new code and updates. We have people using this product on a daily basis. They rely on it. When we change it without letting them know, they freak out sometimes.

- Chart of accounts and special groupings. Trial balance, month over month financials, year over year financials.

- Currently, our users have to do tons of manual entry and tweaking the system to get their numbers. For example: The user has to pull data from tons of different pages and reports and then put it together in a manual process to get the views they are looking for. We have tons of the data, but it may not be formatted easily and correctly.

- People want to see tons of different view points, averages, running totals, comparative values, trends, projections, budgets, etc.

- Uploading budgets and then comparing to how things are going and doing.

- People want to see the year over year values vs. a single one month or one year at a time.

- People want to consolidate values, merge locations, look at all kinds of angles, etc. How can we help the person look at their data in a more standard way?

- Currently there are a number of ways that things could get disconnected. People want to see GL (general ledger) details. There are also tons of possible disconnects and possible variables. Some of that is due to how we are built. That isn't bad, it just doesn't follow normal roads and normal expectations (for certain users).

- We talked about us either being able to export to QuickBooks or build it out so that we look like we are a little bit more stable or standard. Somehow we need to bridge that gap.

- Just as an idea... maybe use a simple dash (-) instead of 0.00 on some of the financials. The dash may mean, N/A or nothing to report. Sometimes a 0 (zero) makes it look like it should be part of the reporting but we have nothing. The dash may help show that no data is there to report or don't worry about it. Kind of a mind trick of sorts.

- We may need to open back up the old chart of account number fields. This already exists, we just need to re-expose it. We then need to have some mappings to that number if doing cross corp or consolidated reporting. Also by way of a note, we need a way to flag where those pieces play in and what main group or categories they fit into. This could be to any of the main 6 categories such as: Revenue, COGS, Expenses, Assets, Liabilities, Equity. If we opened up the account numbers, it could help with cross-corp mapping and such. That way you map against the numbers vs. a naming convention that might have spelling differences.

- We need to move more away from transactional data and go more into daily totals per location. The transactional data is awesome but we really need some preformatted numbers, values, and totals. That would really help with speed and reporting. We have tons of cool ideas (back from 2010 ish) dealing with watchers, feeders, and standalone declarations. Supper cool stuff - well worth looking back into.

- On the adilas side, we really need to look into the system-wide defaults and what gets loaded into the system. These are the generic corp-wide settings that get setup when a new system gets created. As a side note, we may even need to take out the defaults for expense types and deposit types. The girls are wanting it super clean and simple (don't even add anything as far as defaults). Maybe figure out some standards and then even keep it super simple from there.

- We talked about light world building and breaking up the bus into smaller motorcycles and smaller cars per corp. This deals with breaking up the database to smaller pieces.

- Some of the problems the girls are having is on the consolidation between multiple corps. The bigger the business, the more pain there is as you try to consolidate things. Making systems talk to each other, that is the trick. This will end up going clear to a full API socket level at some time. Pretty cool.

- We still need the special accounts and custom tracking accounts. This could be customer in-store credits, loyalty points, etc. There are also some other needs that need to be looked at.

- Danielle's top 3-5: overall chart of accounts, month over month, year over year reporting, exportability of the general ledger.

- Kelly's top 3-5: trial balance, general ledger, p&L and balance sheet on the same page (trial balance), formatting of views (month over month, quarter over quarter, and year over year views), setting up the chart of accounts using the chart of account number.

- We have some clients that want a really cool tool for accounting. We need both the simple and automated views as well as a more advanced model that has advanced tools and speaks a standard language. Think of a new view for users. Simple and automated or more robust and showing greater details.

- Task from Kelly to me, look into opening up the chart of account numbers on expense types and deposit types. Check out the cause and effect relationships.

At the end of the session, Kelly and Danielle were excited to maybe look into two different views. One for the general public and one for a more hardcore financial person such as a CPA and/or an auditor. We will tweak a few things around and see if it gives us more of the look and feel we are hoping for. Good meeting.