all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Yellow
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Uploaded Media/Content & Other Files
(1)
|
||||
| Media Name | File Type | Date | Description | |
| more_logic_on_special_accounts.jpg | Image/JPEG | 3/14/2017 | This was a drawing on how we wanted to run the special accounts stuff. We used this graphic and drew on top of it again and again. We pitched some different levels and then talked about it and then erased them. We did this a couple different times. | |
|
Notes:
|
|
On a GoToMeeting session with Steve and Eric. We were talking about the special tracking accounts for loyalty points and gift cards and such. - We had some question on taxes and with tax included and how that plays into loyalty points. Technically, some of this stuff should not be taxes but is due to the fact it is an invoice line item. - We are seeing that special account stuff is heavily tied to payments and is almost like a mini bank account in some ways - We may want to steer away from the line items area... that brings up tax issues. We may want to play more in the payment area or a standalone area that interacts with the payments. - Mini bank accounts are totally mini balance sheet items. Keep it separate. - What about special money types (corp specific) and then tracking that (logic) back to payment and to the special accounts. Or we could add a new one called special or use the internal payment and record some notes to help tie things together. - Loyalty points are like "cash power" - in a way, they can use for future payments on invoices. Basically a discount (reduction in price) that is available to be applied as needed. Think of a delayed discount. - If we track things clear out to a mini bank account level, we could really show the total liability that is owed back to the clients. Sum and group things for them. - If a gift card is purchased, that can't be revenue, it has to be a balance sheet item. This may cause a small problem. Currently, all line items get mapped directly to the revenue portion of the P & L (income statement). We may need a destination switch of sorts. Similar to the special line items. - At some point, we have to move the balance sheet liability over to revenue (say the amount collected from gift cards that hasn't been redeemed). How does this transaction take place. As a side note, we have a concept of a standalone declaration (back in 2010 ish). One of the motivation of doing gift cards is taking in money that never gets redeemed. Big return on investment. At some point you have to claim that revenue vs. just leaving it hanging on a balance sheet. - All of these items are balance sheet items or user-maintained items. Also, a lot of these accounts are somewhat of a "funny money" type concept. As a side note, we started way back with stock/units. They have all kinds of phantom costs, slush funds, trade-in allowances, actual cash values, etc. All kinds of funny money stuff. - On parts and general inventory items, we need to allow a switch that allows for a user to declare if the item was a revenue item, cost of good sold item, or a liability. Maybe think about all options for the P & L and the balance sheet. - Credits (vendor and customer) - These could be either assets or liabilities. It comes back to who owes who. These also need to be tied to both invoices and possibly expense/receipts. They may also play into deposits and PO's if you get into credits. Maybe think about all 5 of the major players... invoices, PO's, expense/receipts, deposits, and other balance sheet items. Or we could just say something like main id, app type id, and table name. That would handle all possible tie-ins. - We need a special accounts homepage. These special tracking accounts will be showed as system-maintained balance sheet items of sorts. Some what of a cross between a system-maintained and a user-maintained framework. Think of a mini bank account or mini tracking account. - On a different note, we talked about a client need to be able to break the customer queue into sub queues. This could be sub locations, sub categories, or sub types. Crazy how everything keeps fracturing and breaking into smaller and smaller subs. We are also seeing how things need to be summed up, counted, and treated as a whole as well (stats, logistics, and aggregate analyst stuff). It goes both ways. - Anyways, on the customer queue, we can see that a new option to sub categorize or add a sub location could totally work. That doesn't seem to be as big of a project. We will tackle that project next week. - We are so grateful for the pressure and ideas from the people who use our product. We are trying to focus on operations and it is leading us to the accounting level. We are actively cultivating ideas from the "adilas idea farm". Pretty fun and crazy. |