RE:  BuxBox  and Mvelopes comparison         AS OF:  July 28, 2006 

                        ----- BuxBox Features ------ 

      1>  Software is on your computer  -- not Web Based
      2>  One time payment of old QBPro Edition - maybe less that $100.00
      3>  QBPro readily show "Status Report (or Photo)" or the equivalent of:

>>   "What - Resources do you have"  plus 
>>   "Why - you have such Resources" or
>>    "Net Asset - Assets minus Liabilities like Unpaid Credit Card  and
>>    Imposed Limits per Spending Control areas or BuxBoxes -- See "Two Sides of Same Coin" for more perspective.

      4>  Manually access Online Bank and Credit Card information - you print out hardcopy
      5>  Then you manually enter/assign Bank/CrCard transactions as you view one  side of your Desktop and post to BuxBox Spending Control areas on the other side of your desktop.
      6>  Readily set up Memo accts for status of such things as: Unpaid Student Loans;  Old CrCard debt ; Home Equity etc; Life insurance status, etc.
      7>  Make practical use of the Credit Card float resource.
      8>  Can readily use Memo (or Umbrella) aspects for Savings acct SetASides as the BuxBox system emphasizes Day-by-day Operations via the needed BuxBox spending control aspects
      9)   You mostly use the QBs Equity account features.  But you can utilize QuickBooks (QBs) Class features for reporting of more information of why money can in and went out --- you can especially account for Tax Deductible transactions, etc. as

                         ---- Mvelopes Features---- 

      a>  Has its own Web Based accounting system --- it is not the QBs system
      b>  When you pay for two years in advance, fee is less that $8.00 a month
      c>  Bank/CrCard Online tranx automatically flow to the Mvelopes system then you
      d>  Manually re-assign Bank/CrCard tranx to Spend Control areas.
      e>  Via the easy to use Drag and Drop method 
      f>   There is no Credit Card float capabilities
      f>   Showing Memo and Offset Accts for things such as SetASides is awkward
      g>  In general,  limited amount of "Two Sides of Same Coin" features.