all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
||||||
|
||||||
|
|
|
Notes:
|
|
Ideas on sales tax -We are catching all of the details (incoming tax) on the invoice line items. This provides the positive piece. There are 3 known containers (state, county, and city) and a number of other dynamic containers (for taxes). -We need a way to watch for payments going out (paying for sales tax). Each outgoing payment will need to be tied to an expense/type. We are thinking that each location could have a pointer, for each tax container (within that location), to a specific expense/type. -The math would be: on the system-maintained B.S. Item Sum of taxes on invoice line items -(minus) Sum of the e/r types that are setup as pointers The difference would be “Owed Sales Tax” -Changes to make to the store_location table state_account_id - int(10)’ county_account_id - int(10)’ city_account_id - int(10)’ other_1_account_id - int(10)’ other_2_account_id - int(10)’ other_3_account_id - int(10)’ other_4_account_id - int(10)’ other_5_account_id - int(10)’ Ideas on user-maintained balance sheet item: - Original idea was to tie the B.S. expense types to a single user-maintained B.S. item. This would put the load on the e/r types tables. This would also require a tie-in to a user-maintained b.s. item id. - Steve’s idea was to go from the user-maintained b.s. item in a 1-many back to the e/r type. This would not be required but would allow for 0, 1-1, 1-many, etc. It also takes out the need to the user to know the B.S. item number. - Once a user clicks on the e/r type and uses it on an expense, we could help to automate and/or prompt for action. The main reason for the prompt would be to let the user know and to get the bump valve (+/-) and any custom verbage. - Maybe we could add a setting, when setting up the relationship, always bump up (+), always bump down (-) or prompt for action. Going back to the sales tax idea: - We need six new corp-wide settings for dynamic sales tax and fee buckets. These corp-wide settings would be the dynamic names for the system-maintained b.s. items. - The locations table would also hold a new filed that would relate back to the new corp-wide settings. Basically this would allow the user to set-up which system-maintained bucket to use. - New fields on corporations table: o tax_fee_1 - varchar(100) “Owed on Sales Tax” o tax_fee_2 - varchar(100) “Owed on Tax/Fee 1” o tax_fee_3 - varchar(100) “Owed on Tax/Fee 2” o tax_fee_4 - varchar(100) “Owed on Tax/Fee 3” o tax_fee_5 - varchar(100) “Owed on Tax/Fee 4” o tax_fee_6 - varchar(100) “Owed on Tax/Fee 5” - New fields on location table: o state_tax_fee_id - smallint(3)1 o county_tax_fee_id - smallint(3)1 o city_tax_fee_id - smallint(3)1 o other_1_tax_fee_id - smallint(3)0 o other_2_tax_fee_id - smallint(3)0 o other_3_tax_fee_id - smallint(3)0 o other_4_tax_fee_id - smallint(3)0 o other_5_tax_fee_id - smallint(3)0 Ideas on invoices and expense/receipts: - Need to add a physical paid date and paid flag for both - Invoices table: o invoice_paid -tinyint(1)0 o invoice_paid_date -date 0000-00-00 - Receipts table: o receipt_paid* -tmyout(1)0 *already o receipt_paid_date -date 0000-00-00 - Possible problem with the Having clause logic. -Be able to change out the vendor/payee id’s on e/r’s Ideas on a/r’s & a/p’s - What about prepaid items (expenses) - What about prepaid deposits - What about overpayments - What about nay nonlinear actions (not the normal flow) - Do I catch all normal flows -Add a next and previous link on all main items – deposits, PO, invoices, e/r’s (an associate’s idea) -From Post-it note: - What about showing the paid date on e/r’s and invoices? Where? Yes, no? - Default main check writing bank on deposit and e/r mains(add) and e/r payments. - Check receipt_paid and invoice_paid logic. AR’s and A/P paid status on basic reports. Use new date instead of looking up pmts. |