Adilas.biz Developer's Notebook Homepage

Search The Adilas.biz Developer's Notebook
Time Period:	Daily (enter the day you want to see) Monthly Custom Date Range to
Template Filter:
Color Code:
General Text Filter:	(use a plus "+" sign to separate search terms. ex: jack+jill+hill)
Sort Value:

Adilas.biz Developer's Notebook Report - 1/1/2008 to 12/31/2008 - (56)
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	AU 3559		2008	1/1/2008	YEARLY ACCOMPLISHMENTS 2008 Steve, This is a list of things that happened and accomplishments made during the 2008 year on adilas. It was a great year with tons of great stuff. If you need more detail, just let me know. I have everything documented down to the date. January 2008: • adilas, llc. officially became its own llc. • Changed vendors from shared (global) to corp specific. • Added destinations, categories, groups, and sub groups to expense and deposit types. • Moved the location on deposits from the main to the line items. February 2008: • The income statement (P&L) was added to the system. • Added permission pre-sets and color codes. • Split expense/receipts into main, line items, and payments. • Added payment options for expense/receipts to the main during add mode. • Set up our first international client on adilas. • Created the adilas logo. March 2008: • Migrated all fields and databases from old server to new adilas.biz server. • Changed from word “store” to “location” system wide. • Added PO photo gallery. • Added multi clock in/out feature. • Moved all sub navigation links to top of the page. April 2008: • Added the check request system. • Added a quick search to the top of every page. This idea came from David Berkenkotter. • Changed customer and vendor searches from two-part search (fist letter drop-down and optional characters) to a single text field look-up. • Added a printable customer list. • Expanded payroll from semimonthly to all other frequencies (daily, weekly, bi-weekly, semimonthly, monthly, quarterly, semiannually, and annual). • Added running bank balances and special bank balance search page. May 2008: • Added payables section for reimbursements, splits, and PO’s. • Added pages to show sub expense/receipts for splits and reimbursements. • Posted the adilas.biz check write system. Check on the top format. June 2008: • Added a special check write set-up page and section. This allowed for custom settings on the check write system. • Added the first round of the balance sheet (hidden to most users). • Created the adilas, llc. operating agreement, signed papers, and set up adilas bank account. • Allowed individuals to be used for parts and PO’s. Formally, only businesses could be used. • Added the customer or web portion of the adilas.biz site. This is where customers could browse inventory via web services without being in the secure portion of the site. • Added applied to stock flags on expense/receipts that were used as outside repairs on units. • Added drill-down links for outside repairs and internal invoices on the unit detail page. • Added a unit break-down report that show all expense and invoice details (main and line items) for a single stock/unit. • Added holiday pay to payroll options. July 2008: • Added a tie-in between payroll and expense/receipts. • Added key word searches for “last” and “new” on all quick search fields. • Added payables section for stock/units. August 2008: • Added odd days until first payment on finance calculator. • Reworked the floorplan section and allowed for payables on floored units. • Created a “What is adilas?” flyer for a trade show. Posted file online. • Standardized look and feel for all pages. • Added tons of special validation for XSS (cross site scripting) hacks. Page security to prevent hackers from misusing the application. • Added the duplicate to cart function for invoices. • Changed adilas server over to semi-dedicated server. September 2008: • Added save as pdf on income statement (P&L). • Added additional customers to shopping cart, invoices, quotes, and units. • Added ability to add more than one part to an invoice at a time. • Added check in the middle and check on the bottom formats as adilas check write options. October 2008: • Added a grouped receivables report. • Added an apply payments section for invoices. • Added invoice statements. • Added new pagination “next” and “prev” buttons to all reports that show more than one page. • Added the key word “home” to all quick searches. • Added a grouped payables report. November 2008: • Converted all outside web traffic (customer/web side requests) to another server and database. Used web services to push data from adilas to remote server to help with load balancing (server resources). • Added bulk verify pages for deposits and expense/receipt payments. • Added new options and fields to the check/payment search. Showed print status info and payment verification info. • Removed the requirement to lock line items before verifying. December 2008: • Converted the parts from a two-part combo (part number and vendor id) to a single part id number. • Added actual costs to update PO’s. • Added alpha sorts on reimbursements, splits, and PO’s. • Working on the second round of the balance sheet. Created both system maintained and user maintained balance sheet items. Major work on drill-downs for balance sheet look-backs. Files not yet posted. • Posted new 2009 tax files and tables.

	AU 1598		Daily Tasks	1/8/2008	• Brainstorming on balance sheet stuff. Ideas on special expenses and special deposits. • Meeting with Steve going over new changes.

	AU 2400		Brainstorming - Sample Start-up Company	1/8/2008	Sample Start-up Company 1. Initial investment of $10,000 and want to set up a new corporation - Set up new corporation - Set up new bank - $0 balance - Set up a balance sheet item(s) one for each investor o New chart of accounts – balance sheet – Equity – Capital Paid In (chart of account) - New balance sheet item with sub - Go right into a special deposit and tie it to the balance sheet item - New chart of account – balance sheet – Asset – Cash/bank balance - Once all is done fully owed equity goes up by $10,000 and the bank balance and assets goes up by $10,000 Accounting method: item was put in first and then the deposit was made. 1. Initial investment of $10,000 and want to set up a new corporation - Set up new corporation - Set up new bank, $0 balance - Make a deposit - Choose from deposit options: o Sales/invoice deposit o Transfer funds o Special deposit - Choose special deposit - Choose from a list of options: o Special orders – need to stock in a unit or need to create a PO for a part o Deposit on existing inventory – already in the system on an incoming PO o Refund – need to tie to an expense/receipt o Credit – could be money or other current asset form o Shareholder/investment – needs a balance sheet item o Loans – needs a balance sheet item o Donations – tie to invoice – long term liabilities o Sales – tie to invoice o General/Other – flexible and open - Choose shareholder/investment - Choose from existing balance sheet item or create new - Create new balance sheet item and sub - Finish up special deposit – ends up same as above – only difference, we hold your hand through the process Operations method: do a special deposit and let it prompt you to input the balance sheet item Use $6,000 to buy a delivery van – Paid in full - Set up a new balance sheet item and sub - Set up new chart of account o Balance sheet – Assets – Equipment –Delivery Van - Create a special expense/receipt and tie it to the van or balance sheet item - Create a new chart of account for the receipt – don’t want this expense type to go to the income statement – not sure what to do? o Balance sheet – Assets – cash/bank balance Accounting method: item is put in first and then paid for

	AU 2423		Daily Ideas	1/8/2008	Purchasing an asset with cash – in other words cash goes negative and we don’t want to show on income statement - Balance Sheet – Expense – Purchasing an asset for balance sheet items - Add a new id holder to: o Deposit line items o Receipt line items o Invoice line items - Only show this ide when using special balance sheet related actions. - If I need to make the above account 4 deep – Balance Sheet – Expense – Balance Sheet Items – Purchasing a unit - This type of account may be need for things like reimbursements – original idea was to create an account destination called flow through – that terminology may cause people to freak out. These are just expenses that hit the balance sheet as a reduction in cash or bank account funds.

	AU 2424		Daily Ideas	1/9/2008	Questions for Steve: - What are some good default categories, groups, and types? - What about Inventory & Cost of Sales? Where do we get these from? What do we call them? - What about digital signatures? Security? Multi sigs? Custom work rate? - What about logos on checks? Customer work rate? - What about Deposit Types? Where do they show up (if anywhere)? What would be their destination, category, group, etc.? (Assets or Income or Special Income) New Ideas: - Bank statements need to have a photo gallery maybe tie to a new permission also may need statement #’s along with it - Max of 2 signatures per check - Max of 4 approvals on a check – each person will have their own checkbox - Photo gallery on all balance sheet items (PO’s as well) - On special deposits and special expenses we may need to allow an auto verify to help bank accounts - Need a special clean-up report: o Dup checks o Dup deposits o Dup expenses o Etc. - On Amortization schedule need months, percentage, principal, first payment date - Goes on top of income statement: o Bad debt o Total sales – bad debt = adjusted income - Amex is similar to bad debt. It needs to be an adjustment to total revenue. Make a special account for each corp and lock it down/ - Split deposits between stores – user’s request - Invoice/deposit types instead of deposit types - Add a flag so that it checks between invoice and stock details - Kill the part “other” – too open

	AU 1600		Daily Tasks	1/10/2008	• Went into Steve’s house for an all-day brainstorming session on chart of accounts and balance sheet items. 10 miles.

	AU 1645		Daily Tasks	3/17/2008	• Went in to talk with a contact. Showed him the adilas system and he had many questions. My associate went with me and we talked about the presentation on the way home. He had questions about desking the deal, doing the financing, printing, payables, and balance sheet. Great meeting and great brainstorming session with my associate. 335 miles.

	AU 2501		Daily Ideas	5/13/2008	Ideas for Application: - Multiple browse button - Tie between stock & invoice - Allow for multiple people on an invoice - Simple quote process (1 pager) - Default Gap to 0.00 - Clean-up makes and models (Ford & any doubles) - Add due bill paperwork - Validation on employees and time zones - Maybe make a quicker add stock and sell it page (pyramid adds, edits, and sells all at once) - Smaller version of sold info (customer stuff and title stuff) - Customer web application - Privacy settings for reimbursements and splits - Add photos to rei’s and splits builder pages, who-needs, and payables homepage - Automate payroll dates compared with corp settings - Select the store on all pages if record count is 1 - Default blank fields to 0.00 where needed invoice line items, sales process, etc. - Stock payables - Check write system - Balance sheet items - Photo galleries (quite a few different ones) - Automate payroll clear to check write and/or auto withdraw - Usage log (history) - Google and search engines - Add “new” from search form – maybe last as well (po, e/r, cart, check req, stock, etc.) - Rentals & reoccurring invoices - Tie vendors to a default account - Be able to void pay stubs - Add holiday pay to pay stubs and maybe clock-in/out reasons - Report for total days worked - More detail on stock units - PO requests - Recording outside repairs – flagged or not - Print setup by users, custom reports - Put external invoice # on splits & PO’s - Currently tracking dollars ($) and cents on homepage

	AU 2505		Daily Tasks	6/4/2008	• Working on the check write setup application. • Worked on a temporary balance sheet for Steve.

	AU 2507		Daily Tasks	6/6/2008	• Signing off and posting final changes to the check write system. • Small tweaks in Flash and ColdFusion. • Working on small changes and brainstorming on ways to help Steve with the balance sheet.

	AU 2508		Daily Tasks	6/7/2008	• Going over ideas for the balance sheet calcs. • Made some small changes on the receipt subs page. • Working on a client’s backend application.

	AU 2509		Daily Tasks	6/9/2008	• Working on the temporary balance sheet for Steve.

	AU 2510		Daily Tasks	6/10/2008	• Working on a client’s backend application. • Working on the temp balance sheet for Steve. • Meeting with Steve to determine our next steps and going over balance sheet stuff.

	AU 2532		Daily Tasks	7/1/2008	• Worked on new business cards for an associate. • Went into Steve’s house, on bike, for a balance sheet brainstorming party.

	AU 2556		Daily Ideas	7/1/2008	Notes on 7/1/08 • Income statement - 3 main items – stock, loc, and types - We might need to break down the sort by the above items. • On balance sheet - Consignment inventory – show don’t show. If yes, show also as payables. • On parts - Need to switch to part id instead of part number - On parts – track the part number as part of the history - Need a new field called bin # needs to be a varchar (50) allow null – default blank not required • On balance sheet - If we show on the asset side, we also need to show on the liabilities side even if one or the other is $0 • On main inventory types – hide all that are not yet real – assign to corp page. - Need to make these an actual tie-in • On bs date switches – either one or the other – not two different switches (run as verified or non-verified) - Vehicle – truck – GMC – 5-15 - BS – Asset/Lib/Ea – Long term A/R’s, Fixed, Equipment – Loan - (Lock) (Lock) (Suggest flex) (user) - BS – Lia – Long term – 517 House - BS – Asset – Fixed – 517 House - Everything must have 2 posts to check against - Check, cross check, and flag - Deep system check-up - Who do I hold hands with? - Owing vs. own - Containers with totals – conditional with estimates and flags with success counter and unsuccessful counter with error messages of who did what. - Prepaid stuff. This might get tricky – how do we expense it out over time - Roll-call and report – buddy system - Need full internal invoice, outside repairs, and ability to sell balance sheet items. - Percentages - Parent/child relationship - Paint the picture and use broad strokes (go from background to fine details) - Where are you along the ladder and how much are you worth or how much do we give – individual worth - “Net worth” = capital or equity - Appraisal value and date specific tables (might sub table) - Assets = (liabilities + equity), a=(l+e) - Bank – everything revolves around the bank - Corp = “body” the body of the business - Build I.S., B.S., and cash flow reports with possible options of doing a custom hybrid report. - Progress and steps (success meter) how close to complete are we icons and images. - The frosting could by eye-candy and graphs - On the show all BSI show both main and sub types equity and cash - Look-up depreciation schedules (online) normal, accelerating, decelerating, and straight line - Depreciation periods = day, week, month (default), year - What about updates on depreciation schedules

	AU 2533		Daily Tasks	7/2/2008	• Biked into Steve’s house to work more on the balance sheet stuff. • Went by the printer place and got the digital files for Steve and an associate's business cards. • Worked on the tie-in between payroll and expenses.

	AU 2537		Daily Tasks	7/7/2008	• On the phone with Steve going over questions about balance sheet items, manager’s time clock, and general site security. • Worked on po_paid_date fields and converting code and pages to work with the new field. • Started working on stock paid dates.

	AU 2538		Daily Tasks	7/8/2008	• On the phone with Steve and setting up an appointment with a client. • On the phone more with Steve going over question on stock payables, deposits on the P&L, and balance sheet items. • Worked with stock payables. • Went into the accounting office to work with an associate on tax forms. 10 miles.

	AU 2621		Daily Ideas	9/1/2008	Customers: - PO requests, payroll multi - Need statement and multi print option – statement, stub thingy - Reoccurring invoices and balance sheet - W-2 and 1099 reports - “End user” on invoices – “document builder” - Dba – logos – data transfers - Problem: “Unable to connect to the database. Unable to check permissions.” Invoices: Billing - Customer – where the money comes from - Ship to: end user, customer of customer. Example: dealer = customer; customer of dealer - Do a second customer - On vendors – allow for more than one address and allow for choices only on printing checks. - On look and feel and on verbage – need to have defaults on a crop level but custom settings on a location level. o Inventory o Invoices - Co-signer, ship to, end user, 2nd customer – have a field and let them choose the caption

	AU 2596		Daily Tasks	9/2/2008	• Went in to Steve’s house to work on balance sheet options. • At the end of the day we talked about adilas and how to handle two party agreements and how to share info from corp to corp. We decided to set up a system and then allow the parties involved to create their own relationships (we provide the tools but stay out of the actual agreement). 10 miles

	AU 2598		Daily Tasks	9/4/2008	• Went in to Steve’s house to work on balance sheet stuff. Lots of brainstorming on flow. • Migrated 98 vendors for a client in Texas. 10 miles. • Working on a logo for a client.

	AU 2599		Daily Tasks	9/5/2008	• Biked into Steve’s house. • Working on balance sheet items.

	AU 2600		Daily Tasks	9/6/2008	• Biked into Steve’s house to work on balance sheet. • Spent a bunch of time working on pulling parts. Ended up scrapping the idea and going back to the old way. • Started working on saving the income statement as a pdf file.

	AU 2630		Daily Ideas	9/22/2008	-Show a list of who owes what Goals – for statements and multiple invoice payments: - Show outstanding invoices - Allow a date range - Most important thing is select by customer - Show totals of current, over 30, over 60, and over 90 - Receive a single payment and want to be able to apply it to open invoices - How do we handle credit or over payments? - On credits – do we want to create a special items called a credit or do we want to keep a running total per customer? - Do we want to use the word credit? Refund? Overpayment? - How do we apply the credit? - If we prompt for action (if overpayment is found) the user will be able to give them back a refund, create an expense/receipt, or store a credit note. - Maybe force all over payments to an expense/receipt. o Get it out of your hair and keep the books correct o A contact said add the “Taco Bell” account - Maybe add a special line item called “over payment” - Maybe also add a special invoice type called “over payment” - If an over payment – we either need a special invoice, special line item, special payment or we need to add the extra as a special deposit live item. We may also want to prompt for an expense/receipt - If doing a refund (e/r or check req) there may be a time delay – make sure their payment cleared before sending out the refund. - Ideally, the income and expense should be on the balance sheet or both on the income statement so that it washes. Best if done on B.S. - Keep clean books! Help other companies keep clean books.

	AU 2656		Daily Ideas	10/1/2008	On adjustment PO’s need real prices to be recorded: - Receive payments - Statements - Receivables by customer - Payables by vendor/payee - PO request - Payroll Java Script on totals - End of the year stuff - Check REI’s of Payables – back out - Balance sheet items - Add the keyword “Home” to quick search - On part count = use PO’s and invoices to keep track of counts only update counts when used (on demand) counting. Changed to a PO and invoice date per line items. - Change parts to part_id in the background. - Customer based discount (invoices) - Customer based default tax category (invoices) - Migrate customers for a client - Don’t allow splits on a single expense/receipt (no double ups on single pmt) - Clean-up invoices - Fix PO’s and adjustment PO’s to show real cost - Add pagination buttons – next and prev

	AU 2632		Daily Tasks	10/2/2008	• Last minute changes for a client site. Added a podcast button, replaced some text, changed the graphic and changed the Google map it link. Posted files. Invoiced for 70.5 hours. • Went in to work with Steve on adilas stuff. We did some brainstorming on tons of different things. Talked about balance sheet, statements, grouped payables, grouped receivables, and others. 10 miles. • Worked on a client’s calculations and Java Script.

	AU 2652		Daily Tasks	10/28/2008	• Monitoring the ColdFusion server. • Phone calls to a client, add the due date to splits and worked on a grouped payables report. • Added a running bank balance to the top of the payables page. • Posted files online. • On the phone with Steve. Balance sheet is next.

	AU 2412		Brainstorming - Main Balance Sheet Ideas	10/29/2008	Main Balance Sheet Items Ideas: - Owed vs. owned – including quasi deals (on their way – caught in the middle or becoming something) - Something like a stock # or a balance sheet item - Multi cross check – dynamic - New model (where is it really at) - Classic model - Dynamic naming, grouping, and types - Sort order of items, numbers, accounts - Dynamic over time - Monitors, flaggers, and watchers (on demand as things change, not every day just because it has to have a reason to record data) - Pre-calculated totals – speed or reports - Minimum duality (at least two items or accounts) - Assets, Liabilities, Shareholder Equity or (owned, owed, invested, ownership, debt, invested)? - Maybe use invoices, deposits, and expense/receipts as subs of the balance sheet item. What this means is the balance sheet item becomes the master and the sub (inv, dep, e/r’s) need to be fully satisfied (main and line items and payment) - See mini-notebook (brainstorming on a walk) - Deposits = E/R’s + Cash - Keep it simple - Mode of accounting: o Operations – do it (opps) and the system prompts for action (b.s.) o Accounting – do the action (b.s.) side then the operations side

	AU 2653		Daily Tasks	10/29/2008	• Updates and letting people know about new changes. • Brainstorming on balance sheet stuff. • Working on a new flash banner for a client.

	AU 2654		Daily Tasks	10/30/2008	• Problems with ColdFusion server. • On the phone with Steve. • Disabled inventory pages on adilas and Steve’s company’s website. • Emailed Crystal Tech to let them know. • Went in to lunch to meet with Steve. • Brainstormed on balance sheet items. 10 miles. • Working on expense totals report.

	AU 2415		Brainstorming - Questions & Known Issues with Balance Sheet	11/11/2008	Questions & Known Issues with Balance Sheet 1. Things must balance. That can get tricky and hard. Every penny needs to be counted and assigned to the correct can. 2. Some things are real monies and some are book figures (not an actual cash values). Real monies need to be tied to a bank, investment, cash on hand, etc. Items such as depreciation may not actually translate into cash. This creates a disconnect. 3. Things (monies) can change hands, status, and destinations very quickly. What kinds of events trigger a move from an expense to a balance sheet item? Or vice versa? Say you have a customer who owes you money (A/R). You decide to write it off (clear the books). How does it change from A/R to expense or whatever? 4. Quite often you will have items changing status within their own group. Say cash (bank A/R) to inventory which is also an asset. 5. I’m worries about showing things multiple times on the same report. This has been a fear because I wasn’t sure how to show things. Originally, I was going to use expense types and deposit types. Those items would be shown by themselves plus be reflected in the cash or bank balance. The other problem is that some of the expense and deposit types don’t need to be shown on their own and should only be shown in the final bank balance. An example might be bank transfers or reimbursements paid. 6. What about internal repairs (internal invoices), bad debt, credits, NSF on checks, update P.O.’s, shrinkage, pre-paid items, capitalized items, refunds, monies over and short, due bills, breach of contract? And the list goes on…. 7. What about selling or renting a B.S. item? What happens if fully depreciated and still sold for profit? What happens if sold for a lost (loss)? What about gifts or receiving gifts? How do you record values if real money doesn’t change hands. Random note – all deposits require a bank – that might create a disconnect. 8. How do we automate payments (coming in and going out)? Is this required on the first round or sometime later? Along the same lines – what happens if we are ahead or behind the pay cycle (pre-paid or under paid)? 9. I need to set up a number of watchers or flaggers that can work over time. How do I do that so they can keep running totals and also be able to drill-down to details (in the past). I don’t see a problem if running on current data. What happens if the user wants a snap shot of days and time past? Random thought – if you use a snapshot analogy – a true snap shot is taken at the current time and then you look at it later on. In the digital world – I imagine that a user would like to virtually go back in time and see the snap shot of how it was even though things have changed and continued. This is where it gets tricky. 10. Classic model vs. new adilas model – The classic model is Assets, Liabilities, and Equity. The new model would be similar but show real , where am I values, with how much is owned, how much is still owed, and current value. An example might be: classic model – an asset (van) for $10,000 and long term A/P (loan) for $10,000. I would like to show it as an asset (van) valued at $10,000, paid $6,000, owe $4,000 and long term A/P (loan) value of $10,000, paid $6,000, and only owe $4,000. Paper doesn’t do it justice. Basically, I want to include real-time values to give a cleaner look at where we are. 11. How are we going to handle starting values? Say you know that at the end of last year you owed xyz. How do you keep things straight without having all of the details (or do we need all of the details)? This could get tough if we start signing up existing businesses that have years and years of history. Another thing to consider is the starting bank balance and the starting bank date. These are already included on the add/edit bank pages. 12. How do I maintain a duality (at least two offsetting accounts)? Not every transaction is processed in the exact same way. Plus, it may require a transfer within the same type or a 1-many relationship that could be any number. 13. I’m hoping to use an item called a “balance sheet item”. Each item would have its own name, destination, starting value, running value, sort, etc. We can tie in photos, sub, tables, etc. to each item. Basically, each item will be a special “can” with a name. The basic info will be ongoing and the details of what happened to it (baggage) will be carried by each item. We will record history info and possibly “snap shot” history. I’m not exactly sure on the snap shot history (what that means or how we will do that) but it might help with look backs. 14. The above item (B.S. Items) are a great idea but how do you deal with things the system is doing on its own (short term A/R’s, short term A/P’s, bank balances, inventory counts, P&L net profit, etc.). Maybe these things keep going in the background until the user “takes a picture” and thus create a snap shot history. 15. One of my main goals is to have the system be functioning and the balance sheet show up as an “effect” of good data. A number of other software systems require a post or physically recording where things are at. I want the numbers to just flow through as a result of normal usage. Let operations dictate to accounting what is happening. This takes the word “adjustment” out of the picture. It is what it is… 16. Speed vs. flexibility vs. server load vs. dynamic vs. static vs. frequency – This will be a full on balancing act. What is the most important? What is the easiest/hardest to maintain? What do our customer and users want? How easy/complex is this report going to be? 17. Because we are not doing traditional double entry accounting, how do we incorporate cross checking and dynamic multi checking? Instead of 1 to 1 (standard double entry) – what about multi-cross checking. How do we empower the users (corps) to set up their own cross checks that the system can monitor? If we can figure this out, it would help the users know where the problems are. This would be worth tons and would end up saving tons of time looking for the problems. 18. The good thing about B.S. Items is they are changed less frequently than normal day-to-day items. Maybe weekly, monthly, quarterly, or annually. Usually not daily. This is the outer loop (inter loop being daily business transactions) 19. What happens if the balance sheet won’t balance? Do we provide a force balance or do we require the users to check the cross checks and really make the data correct? It would be so cool if there was no way to trick it. That will be tough. 20. What prep steps do we need to do? Maybe create watchers, flaggers, history points, etc. What about parts and running off or part-id instead of vendor and part number? 21. Maybe we need to have the B.S. report be dynamic. This means we only show things that are active and have a value. Maybe we allow the users to rename a system generated category (default to what we think but give them some flexibility on what to call it). Maybe we only provide drill-downs on current date. B.S. reports. Archived “snap shots” won’t have drill-downs, just numbers and text values. Current is crunch on the fly and archived is just a saved report. 22. Maybe we allow users to look up small sections of the balance sheet (in the current time or in the past) but we limit it to just a certain section at a time. This would lessen the server load and allow for special code and loops or smaller groups of data. These more detailed looks would crash the server if done as a whole.

	AU 2667		Daily Tasks	11/11/2008	• Emailed an update to Steve and associates. • Testing web service calls. • Changed the web services to work as either add or edits on every call. • Brainstorming on balance sheet items. • On the phone with an associate at Crystal Tech. Problem with JDBC driver.

	AU 2416		Brainstorming - Balance Sheet Groupings	11/12/2008	On Balance Sheet Groupings: Use Category: unchangeable (required) - Assets - Liabilities - Equity Use Groups: allow dynamic naming (required) Defaults: (instead of creating all of these maybe just provide a special help file with the values) - Assets: o Cash o Bank Account(s) o Accounts Receivable o Other Current Assets o Fixed Assets o Other Assets o Accumulated Depreciation - Liabilities: o Accounts Payable o Other Current Liabilities o Long Term Liabilities - Equity o Capital o Other Equity Allow for an optional sub group: allow dynamic naming this is not required but may be used. I will need to create a system wide blank value or hidden sub group. (optional) Show B.S. report in the following levels: (same as P&L) 1. Quick look only (basic) 2. Show main groups (small) 3. Show main and sub groups (medium) 4. Show everything fully expanded (large)

	AU 2668		Daily Tasks	11/12/2008	• Testing the application and web services. • Emailing Steve some info on Crystal Tech. • Brainstorming on balance sheet items. • On the phone with Steve going over bank statements and verifying receipts and deposits. • Made some small updates on receipt payments. • Called and talked with a client about the flash banner.

	AU 2687		Daily Ideas	11/17/2008	-On receive multiple invoices – add money type as a search criteria. -Change the lock permission to basic around the board -Create the automate invoice section. Reoccurring invoices and payments. -Create the history look-up section “activity per corp” -Add anchor tags to the permissions page -Balance sheet items and balance sheet report -Report and form builder -Payroll IRA calcs – no federal but full ss and medicare -On verify bank reports. Allow a check range (numeric) and show only deposits or expenses. -On reports – convert day, month, year look-ups to text entries. -Check the math on the payables page under splits when dates are used. Is shows all payments not just satisfying pmts. Doubles the “split” pmts. -At some point, it might be nice to record verify bank history; include date/time and person.

	AU 2417		Tech & Brainstorming - Balance Sheet Tables & Sample Groupings	12/2/2008	Sample Balance Sheet Groupings: Destination: Balance Sheet Category: Assets (Groups & Sub Groups) - Current Assets: o Cash/bank Accounts o Petty Cash o Inventory o Accounts Receivable o Other Current Assets - Long-Term Assets (Fixed): o Fixed Assets o Equipment o Tools o Buildings o Real Estate o Other Assets o Accumulated Depreciation Category: Liabilities (Groups & Sub Groups) - Current Liabilities o Accounts Payable o Other Current Liabilities - Long-Term Liabilities o Long-Term Accounts Payable o Loans/Notes Payable o Other Liabilities Category: Equity (Groups & Sub Groups) - Capital o Paid in Capital - Other Equity o Net Profit o Retained Earnings o Distributions (Please see diagram on scan in photo gallery) Balance Sheet Subs & Items Planning (Please see scans in photo gallery) Finished Balance Sheet Items Tables with subs: Page was originally started on 11/12/08 Balance Sheet Items Table Balance System Type Table Balance Sheet History Table Balance Sheet Subs Balance System Types (Please see scan in photo gallery)

	AU 2689		Daily Tasks	12/2/2008	• Went in to Steve’s house to brainstorm on balance sheet items. • Talked about me going in the field more. 10 miles. • Working on balance sheet groupings and stuff.

	AU 2418		Brainstorming - Balance Sheet Items & Steps in Starting a New Corp	12/3/2008	Requirements for Creating a Balance Sheet Item: - Must have a bank - Must have balance sheet items turned on o This is where I will create the system defaults o First check and then create if needed System Generated B.S. Items: - B.S. – Assets – Current Assets – Cash/Bank Accounts o Each bank account name (dynamic) - B.S. – Assets – Current Assets – Petty Cash o Each active location with a positive petty cash value (dynamic) - B.S. – Assets – Current Assets – Inventory o Each vendor for parts (dynamic) o Each make for units (dynamic) o ??? does inventory go with current assets or by itself under B.S. – Assets – Inventory • Then grouped by inventory type • Parts by part category and then vendor • Units by make - B.S. – Assets – Current Assets – Accounts Receivable - B.S. – Liabilities – Current Liabilities – Accounts Payable - B.S. – Equity – Other Equity – Net Profit - Others: REI’s, Units, PO’s, Floorplan, Payroll - Keep a record of crop B.S. groupings and id number. This will help when system creates new system B.S. item. If everything starts at zero… only add as needed Steps that a new corp makes: 1. New corp - No B.S. items created 2. Assign new corp to inventory types - If assigned to B.S. inventory types - Set up all defaults groups, sub groups, etc. 3. On locations, watch for petty cash values - If yes, create B.S. item 4. On banks, watch for new banks - If yes, create a B.S. items 5. On units, watch for new items - B.S. item 6. On parts, watch for abnormal part (unlimited don’t count) this may be part of a P.O. or a standalone part. It really doesn’t count until it gets brought into inventory. - (5 & 6 – could be multiple on a per vendor or per make basis) 7. On PO’s – watch for 1st PO 8. On units, watch for 1st floorplan item 9. On e/r watch for 1st Split 10. On e/r watch for 1st REI 11. On invoices watch for 1st unpaid invoice

	AU 2690		Daily Tasks	12/3/2008	• Brainstorming on balance sheet items. • On the phone with Steve going over brainstorming ideas. • Small help file update.

	AU 2419		Note - On the Balance Sheet	12/5/2008	Ideas about the balance sheet and how we provide the tools but we let the users make the final call. Very similar to the B.S. round 1, we need to pull back everything we can for the users. We also need to leave some flexibility into the tool or builder. Options on round 1 that are pretty cool: - Pulls back data into a giant form - Items may be added/edited/combined/shown/hidden/etc. - All refreshed are done on the form page. The actual report page is just changes and data from the form. No calcs are done on the actual report page. All it does (the report) is bring the data (form) forward and format it. Options on round 2 that would make it cool: - Local java script to help with calcs - Allow for sort # to be changed on the fly - Button for show/save as pdf - Maybe when we save as a pdf, allow them to save a physical copy online and that becomes the history or archived copy. o This could make the database table really small – just record the date, the pdf name and loc, and the name of balance sheet. Let the users browse their saved and archived copies at any time. o Small server load. All we do is pull up a saved pdf and show it. We don’t even car what it has on it. No calcs, no drill-downs, no look back on the database. It is what it is…

	AU 2692		Daily Tasks	12/5/2008	• Brainstorming on balance sheet items and how to tie-in update PO’s. • Also spend some time documenting ideas on what kind of tool to make the balance sheet report and how to use pdf docs as the archived copy. Definitely had some inspiration here. • Working on the part id conversion.

	AU 2420		Tech - Balance Sheet Tables	12/11/2008	Tech – Balance Sheet Tables Balance Sheet Photos Table Balance Sheet Archives Table (Please see scan in photo gallery) On inventory look-backs: - Maybe use reverse filters. Do a quick simple search (counter only) to see if there are more records before or behind. This could easily be translated into something… IN (value) or something… NOT IN (value)

	AU 2696		Daily Tasks	12/11/2008	• Small help file update. • Also added a new error message if changing part #’s. • Brainstormed on balance sheet items. • Built six new tables to hold balance sheet items. • On the phone with Steve.

	AU 2698		Daily Tasks	12/13/2008	• Finished up the new alpha sort order for reimbursements, splits, and PO’s. • Fixed some math calc problems. Tried to post files but had major internet problems. • Went in to town to use the internet and got things to work. I spent almost 3 hours trying to get files posted. In the mean-time, the adilas application was down (partially). 10 miles. • Sent an email update to Steve about uploading problem. • Worked on creating balance sheet groupings.

	AU 2699		Daily Tasks	12/15/2008	• Working on default grouping for balance sheet items. • Working add/edit grouping page. Changed the dates on the deposit and receipt totals page. • Added sort options for groups, sub groups, and types. • Other changes to help with flow.

	AU 2700		Daily Tasks	12/16/2008	• Working on the add/edit balance sheet pages.

	AU 2701		Daily Tasks	12/17/2008	• Working on balance sheet items. • Started pulling in system generated balance sheet items.

	AU 2702		Daily Tasks	12/18/2008	• Working on balance sheet inventory reports (dynamic look-back reports). • On the phone with Steve going over manufacturing stuff and research on SQL joins and sub queries. • More research on advanced join and unions. • Spent some time playing with SQL concepts.

	AU 2713		Daily Ideas	12/18/2008	On balance sheet items – what are the goals for parts • Qty, cost – what do I have left? – I don’t care how much is still there; I only want what is left and how much it is worth.

	AU 2704		Daily Tasks	12/20/2008	• Went in to work with Steve on balance sheet items. Brainstorming and talking about a business plan. 10 miles. • Updated all of the add and edit pages that deal with date stamping the PO/invoice line items. This is for date sensitive quantity tracking.

	AU 2705		Daily Tasks	12/22/2008	• Working on system balance sheet items. • Worked on unit group reports and inventory drill-downs. • Started on parts inventory drill-downs.

	AU 2706		Daily Tasks	12/23/2008	• Working on accounts receivable drill-downs and started on accounts payable drill-downs for balance sheet items.

	AU 2707		Daily Tasks	12/24/2008	• Working on accounts receivable drill-downs and started on accounts payable drill-downs for balance sheet items.

	AU 2708		Daily Tasks	12/26/2008	• Worked on b.s. and payables drill-downs. • Steve came over and we went over balance sheet items and direction. • Changed the main page to allow a checkbox interface to select either assets, liabilities, or equity.

	AU 2711		Daily Tasks	12/31/2008	• Working on 2009 tax tables and balance sheet stuff. • Worked on tying in locations to payables.

	AU 3560		2008	12/31/2008	YEARLY ACCOMPLISHMENTS 2008 Steve, This is a list of things that happened and accomplishments made during the 2008 year on adilas. It was a great year with tons of great stuff. If you need more detail, just let me know. I have everything documented down to the date. January 2008: • adilas, llc. officially became its own llc. • Changed vendors from shared (global) to corp specific. • Added destinations, categories, groups, and sub groups to expense and deposit types. • Moved the location on deposits from the main to the line items. February 2008: • The income statement (P&L) was added to the system. • Added permission pre-sets and color codes. • Split expense/receipts into main, line items, and payments. • Added payment options for expense/receipts to the main during add mode. • Set up our first international client on adilas. • Created the adilas logo. March 2008: • Migrated all fields and databases from old server to new adilas.biz server. • Changed from word “store” to “location” system wide. • Added PO photo gallery. • Added multi clock in/out feature. • Moved all sub navigation links to top of the page. April 2008: • Added the check request system. • Added a quick search to the top of every page. This idea came from David Berkenkotter. • Changed customer and vendor searches from two-part search (fist letter drop-down and optional characters) to a single text field look-up. • Added a printable customer list. • Expanded payroll from semimonthly to all other frequencies (daily, weekly, bi-weekly, semimonthly, monthly, quarterly, semiannually, and annual). • Added running bank balances and special bank balance search page. May 2008: • Added payables section for reimbursements, splits, and PO’s. • Added pages to show sub expense/receipts for splits and reimbursements. • Posted the adilas.biz check write system. Check on the top format. June 2008: • Added a special check write set-up page and section. This allowed for custom settings on the check write system. • Added the first round of the balance sheet (hidden to most users). • Created the adilas, llc. operating agreement, signed papers, and set up adilas bank account. • Allowed individuals to be used for parts and PO’s. Formally, only businesses could be used. • Added the customer or web portion of the adilas.biz site. This is where customers could browse inventory via web services without being in the secure portion of the site. • Added applied to stock flags on expense/receipts that were used as outside repairs on units. • Added drill-down links for outside repairs and internal invoices on the unit detail page. • Added a unit break-down report that show all expense and invoice details (main and line items) for a single stock/unit. • Added holiday pay to payroll options. July 2008: • Added a tie-in between payroll and expense/receipts. • Added key word searches for “last” and “new” on all quick search fields. • Added payables section for stock/units. August 2008: • Added odd days until first payment on finance calculator. • Reworked the floorplan section and allowed for payables on floored units. • Created a “What is adilas?” flyer for a trade show. Posted file online. • Standardized look and feel for all pages. • Added tons of special validation for XSS (cross site scripting) hacks. Page security to prevent hackers from misusing the application. • Added the duplicate to cart function for invoices. • Changed adilas server over to semi-dedicated server. September 2008: • Added save as pdf on income statement (P&L). • Added additional customers to shopping cart, invoices, quotes, and units. • Added ability to add more than one part to an invoice at a time. • Added check in the middle and check on the bottom formats as adilas check write options. October 2008: • Added a grouped receivables report. • Added an apply payments section for invoices. • Added invoice statements. • Added new pagination “next” and “prev” buttons to all reports that show more than one page. • Added the key word “home” to all quick searches. • Added a grouped payables report. November 2008: • Converted all outside web traffic (customer/web side requests) to another server and database. Used web services to push data from adilas to remote server to help with load balancing (server resources). • Added bulk verify pages for deposits and expense/receipt payments. • Added new options and fields to the check/payment search. Showed print status info and payment verification info. • Removed the requirement to lock line items before verifying. December 2008: • Converted the parts from a two-part combo (part number and vendor id) to a single part id number. • Added actual costs to update PO’s. • Added alpha sorts on reimbursements, splits, and PO’s. • Working on the second round of the balance sheet. Created both system maintained and user maintained balance sheet items. Major work on drill-downs for balance sheet look-backs. Files not yet posted. • Posted new 2009 tax files and tables.

What's New

Products

Find Us