What changes were made when my document was upgraded?

When upgrading your data from iBank 3 or 4, you may be presented with a window stating, "We fixed your database." This window contains a log of changes that were made to your data during the upgrade process. Due to differences in the way old versions of iBank managed data, modifications are sometimes necessary in order to make the data usable in iBank 5. In addition, iBank examines your database for errors during the upgrade process and corrects any problems that it finds. In both cases, iBank takes care to notify you when any significant changes are made. Below, you will find a description of each message that may appear in the upgrade log.

Two types of messages may appear in the log:

In some cases, you may want to check your accounts to see the effects of the changes that were made, and make adjustments or corrections as needed. Click "Save Log" at the bottom of the log window to save the list of changes to a text file so that you can refer back to it at any time. Enter a name for the file and choose a save location when prompted, then click "Save" to save the file. You can open this file with TextEdit or any other text editor.

Warnings:

All of your accounts were used in budget "budget name". Number budget items were removed. All existing accounts will be used as the source for this budget.
This message indicates that account transfers were removed from one of your budgets. In iBank 5, budgets can be limited to specific accounts. In order to monitor transfers into a particular account, that account must be excluded from the budget setup. In this case, your budget was monitoring transfers into all available accounts, so the transfers needed to be removed (otherwise all accounts would have been excluded from the budget setup).
Budgets have been updated for use with iBank 5. Please review their settings for accuracy. If you use envelope budgeting, you will need to reconfigure your envelopes under the new budgeting system.
This message indicates that you had one or more budgets in your file that were upgraded. Since budgets work differently in iBank 5 than they did in previous versions, you should go through each of your budgets and make sure they are configured properly. You may find some duplicate budget items as a result of scheduled transactions being added to your budgets. If you use envelope budgeting, this feature has been completely overhauled for iBank 5. You will need to enable envelopes for each budget again, and enter how much cash is currently in each envelope.
Duplicate currency codes. Currency with code "old currency code" changed to "new currency code."
This message indicates that two of your currencies shared the same code. iBank 5 does not allow duplicate currency codes, so a number was added to the code of one of the currencies to differentiate it from the other. This will prevent iBank from downloading exchange rates for the currency, so you should either change the code to one that is unique or reconfigure your accounts and transactions to avoid using this currency. The currency can be deleted if no accounts or transactions are associated with it.
iBank estimated the minimum payment for loans, but you should set it according to your loan documents.
iBank 5 handles loans differently from previous versions of iBank, in that you can now enter your loan payment amount directly (previous versions calculated this amount based on the other loan settings). When upgrading loan accounts, iBank 5 determines the minimum payment based on the other loan settings. This message appears simply to remind you to check your loan settings and verify that they are correct after the upgrade.
In account "account name" you have a negative number of shares number of shares for "security name". This may need to be corrected.
iBank 5 handles negative shares differently from previous versions of iBank, in that it does not automatically adjust the cost basis to prevent you from holding negative shares. This message indicates that one of your accounts has a negative number of shares of a particular security, which may represent a short position. If you do not currently have a short position open, then you will need to correct the number of shares held in that security by buying or moving in shares prior to the date on which you sold them.
On date in "account name", you sold more shares than you own of security name. You should correct this.
This message indicates that a "Sell" transaction was recorded in an investment account that caused iBank to deduct more shares of a security than were available at the time. There are two common causes for this error: sales being recorded before purchases on the same date, and short sales being recorded improperly. To correct the error in the former case, locate the transactions in your investment account and move the "Buy" transactions ahead of the "Sell" transactions via drag & drop (this will only work if the transactions have the same date). In the latter case, change the transaction type from "Sell" to "Sell to Open" to indicate that the transaction represents a short sale. You may also need to change one of your "Buy" transactions to "Buy to Close" in order to cover the short sale.
Security info deleted from transaction "payee name" on date in account/category "account name". Security line items have to be in an investment account.
This message indicates that a transaction in one of your banking accounts had investment details associated with it. This is not allowed in iBank 5, so the investment details were removed.
Security security name is in use with an account with a different currency. You should a make new security using currency currency name.
This message indicates that one of your securities is using a different currency than some of the transactions associated with it. Nothing was changed, but we recommend that you fix the problem by creating a new security that uses the appropriate currency.
The ofx setup for account "account name" has an unknown account type.
This message indicates that one of your accounts was configured for direct download (OFX) but did not have a valid OFX account type. To correct this problem, you will need to disable online access for the account and then set up direct download again.
The variable interest rate for your loan to lender's name should be updated.
This message indicates that one or more of your loans has a variable interest rate which may have been modified during the upgrade due to differences in the way interest rates are handled in iBank 5. This message appears simply to remind you to check your loan settings and verify that the current interest rates are correct after the upgrade.
Transaction on date with payee "payee name" had invalid security info. The security info was removed.
This message indicates that one of your transactions had security information associated with it when none should have been present, so the security details were removed. This could affect your current holdings for that security - please check the security using a Portfolio Summary report. If you find a discrepancy, you may want to go back to the previous version of iBank, locate the transaction indicated in the error message, delete it and recreate it, and upgrade to iBank 5 again.
We didn't find a password for OFX connection to bank URL.
This message indicates that an account was configured for direct download, but iBank 5 was unable to retrieve its password from the Mac OS X Keychain. iBank is unable to download transactions into the account until you fix the connection details. To reconnect your account, click the cloud icon next to the account in the source list, click "Refresh Account," and enter your login details when prompted.
You need to set up syncing again if you are using iBank Mobile on an iOS device.
This message indicates that some of your data was corrupted in a way that could result in inconsistent syncing with iBank Mobile or even sync failure. The data has been repaired, but you will need to delete the sync settings for your mobile devices and reconfigure them to ensure that syncing works properly.

Notices:

A budget item for "category name" in budget "budget name" had a repeat frequency of number. We changed it to 1, but this is probably better modeled using a scheduled transaction.
This message indicates that one of your budgets had a category or account with a frequency that is no longer supported in iBank 5. Since scheduled transactions are now included in budgets, you should remove the unscheduled budget item and replace it with a scheduled item that uses the correct frequency.
Account "account name" was assigned "currency name" (currency symbol) as a currency.
This message indicates that one of your accounts did not have a currency assigned to it. Your Mac's default currency was assigned to the account.
Account name changed to "new name" (was "old name")
This message indicates that one of your accounts had the same name as another account or one of your categories. Since this is not permitted in iBank 5, the account's name was changed. Any transfers linked to the account were also changed accordingly.
Added split to balance transfer with payee "payee name".
This message indicates that one of your transfers had split items that did not balance to the transaction's total amount. A split item was added to the transaction to cover the difference.
Category name changed to "new name" (was "old name")
This message indicates that one of your categories had the same name as another category or one of your accounts. Since this is not permitted in iBank 5, the category's name was changed. This message could also indicate that one of your categories had a colon in its name, but was not a sub-category, so its name was changed. Any transactions assigned to the category were also changed accordingly.
Changed invalid transaction type from "old type" to "new type" for "payee name" on date in account/category "account name"
This message indicates that an investment transaction was found in non-investment account, and it was was not identified as part of a transfer from an investment account. Since investment types are reserved for investment accounts, the transaction type was changed to either "Deposit" or "Withdrawal" based on the transaction amount.
Couldn't find a currency for transaction template "payee name". The default currency "currency name" will be used.
This message indicates that one of your transaction templates did not have a currency associated with it, so the default currency was assigned to it. This only affects how the amount is formatted when the template is edited.
Couldn't update search criteria for smart account "account name". The smart account was deleted.
This message indicates that one of your old smart accounts could not be converted for use with iBank 5, due to differences in the way smart accounts function in this version of iBank. The smart account was deleted - you should probably create a new one in its place.
Couldn't update smart import rule criteria for "rule name".
This message indicates that one of your old smart import rules could not be converted for use with iBank 5, due to differences in the way smart import rules function in this version of iBank. You should probably delete the rule and create a new one in its place.
Date for transaction with payee "payee name" was set to date, it was nil.
This message indicates that one of your transactions did not have a date assigned to it. It was assigned the date on which the transaction was originally recorded or imported into iBank. If that date was also missing, it was assigned today's date.
Deleted stranded line item from account/category name. Amount was amount.
This message indicates that one of your accounts or categories contained a corrupted transaction. The corrupted transaction was deleted; the account balance or category value should not be affected.
Duplicate currency names. Currency named "old currency name" changed to "new currency name."
This message indicates that two of your currencies shared the same name. iBank 5 does not allow duplicate currency names, so a number was added to the name of one of the currencies to differentiate it from the other.
Exchange rate changed to 1 (was old exchange rate) for "payee name" on date in account/category "account name".
This message indicates that one of your transactions had an exchange rate applied to it, but did not appear to need one (the transaction currency and the account currency were the same). The exchange rate was discarded; the transaction amount was preserved.
Found a non-account line item associated with security "security name". We will remove the security from it.
This message indicates that some investment details were found where they don't belong (a bad database record was found). The investment details were removed from the database, but your transactions were not affected.
Found a line item associated with security "security name", but this line item's account had no currency. We will remove the security from it.
This message, like the one above, indicates that some investment details were found where they don't belong (a bad database record was found). The investment details were removed from the database, but your transactions were not affected.
Group account name changed to "new name" (was "old name").
This message indicates that one of your account groups had the same name as one of your accounts or categories. Since this is not permitted in iBank 5, the group's name was changed. Any transfers linked to an account in the group were also changed accordingly.
Report date ranges are handled differently in iBank 5. The start dates of your reports were estimated; you should verify and adjust them accordingly.
This message indicates that the starting date for some of your reports may have been adjusted due to differences in the way iBank 5 handles report date ranges. Unlike previous versions, iBank 5 tracks reports from their end dates backwards according to predefined intervals (weekly, monthly, etc.), which may prohibit certain date ranges from being used. In these cases, iBank 5 substitutes the closest available range.
Scheduled transaction payee name next post date was before 1970, we changed it to new post date.
This message indicates that one of your scheduled transactions was configured to post transactions too far in the past. In order to prevent the schedule from stalling iBank, its next posting date was changed to the current month.
Scheduled transaction payee name repeat option was daily, changed to weekly.
This message indicates that one of your scheduled transactions was set to repeat daily. Since this option is no longer available in iBank 5, the scheduled transaction was assigned the closest available setting, which is to repeat weekly.
Scheduled transaction payee name repeat option was once, changed number of times it repeats to 1.
This message indicates that one of your scheduled transactions was set to use the frequency "once." Since this option is no longer available in iBank 5, the scheduled transaction was assigned an equivalent setting, which is to repeat only one time.
Scheduled transaction payee name repeat option was unknown, changed number of times it repeats to 1 and interval to month.
This message indicates that you upgraded from iBank 3 and one of your scheduled transactions was missing a schedule. The template was assigned the default schedule, which is to repeat monthly.
Scheduled transaction payee name repeat option was unknown, changed to monthly.
This message indicates that you upgraded from iBank 4 and one of your scheduled transactions was missing a schedule. The template was assigned the default schedule, which is to repeat monthly.
Securities with duplicate symbols (symbol) found. They will be merged.
This message indicates that your portfolio contained more than one security that was assigned to the same ticker symbol. These securities were combined into a single security for iBank 5.
Security distribution type was unknown, we changed it to cash for "security name" on date in account/category "account name".
This message indicates that an investment transaction with a negative cash value was missing its distribution type (cash, transfer, or reinvest). It was assigned the default type, which is cash.
Security distribution type was unknown, we changed it to deposit for "security name" on date in account/category "account name".
This message indicates that an investment transaction with a positive cash value was missing its distribution type (cash, transfer, or reinvest). It was assigned the default type, which is cash.
Security transaction was a Reinvested Capital Distribution, we changed it to Reinvested Dividend for "security name" on date in account/category account/category name.
This message indicates that one of your "Capital Distribution" transactions was recorded as a reinvestment. Capital distributions cannot be reinvested in iBank 5, so the transaction type was changed to "Dividend" in order to preserve the shares purchased in the reinvestment.
Set transaction's currency to default currency: currency name (currency symbol). None of the transaction's line items had an account with a currency.
This message indicates that one of your transactions did not have a currency assigned to it. Your Mac's default currency was assigned to the transaction.
Smart account name changed to "new name" (was "old name").
This message indicates that one of your smart accounts had the same name as another account or one of your categories. Since this is not permitted in iBank 5, the smart account's name was changed.
The income amount of a reinvested security transaction for "security name" on date in account/category "account name" was adjusted. It was old amount, we changed it to new amount to balance the shares and price.
This message indicates that one of your dividend transactions was recorded as a reinvestment, but the amount of cash received as a dividend did not match the amount that was reinvested. iBank changed the amount recorded in the security income field to equal the value of the reinvestment, determined by multiplying the number of shares purchased by the price per share.
There was no account associated with schedule attached to "template payee name". We fixed this by associating "account name".
This message indicates that one of your scheduled transactions did not have an account to post transactions to. iBank assigned it to one of your accounts, but you should double-check to make sure it was assigned to the appropriate one.
There wasn't a valid repeat interval for schedule attached to "template payee name". We fixed this by assigning 'month' interval.
This message indicates that one of your scheduled transactions did not have a frequency setting to determine how often it should be posted to an account. iBank assigned it to the default frequency, which is monthly.
Transaction templates updated to use the default currency 'currency name'.
This message indicates that your transaction templates were updated to use the default currency assigned to your document. Transaction templates in previous iBank versions did not use currencies, but iBank 5 requires them.