That's all the changes you need to make. Your application is now a fully functional banking application, complete with online bill payment and transaction viewing. It is very helpful to lay out, in the beginning, the functions that you'll need to perform with your application. When you started, you first built all the stored procedures that would be necessary. Although this might have seemed tedious, it is a necessary step to ensure that your application has a strong design.
Although it works fully now, there is quite a bit you can do to enhance this application. You could add Validation controls to check that the payee and amount that the user enters on the bills page are valid. You could also add a filter to the transactions DataGrid to allow the user to view only those transactions within a specified time period.
Right now, all the money is stored in a single checking account. You could add another account type to the application, such as a savings account. You could store the account information in the same tblAccounts table, and add a new field for the type of account.
You also might have noticed that there is a lot of duplicate code in the listings, and that it is scattered throughout several pages. Next week, you'll learn about componentizing ASP.NET pages to overcome these problems by encapsulating commonly used code in modules.