Munex "export" to DBC Finance

Munex cannot export directly to DBC Finance. There is no 1 to 1 relationship between inputs in Munex and DBC Finance; some data would be lost in any conversion. The export instructions presented here apply to Munex 2006 (and may not hold for subsequent versions). The exported information can be imported by DBC Finance 6.004c or later.

• Exporting data from Munex
• Import data into DBC Finance
• Create custom reports on your own vs. using the custom reports template
• Creating the export custom reports in Munex
• DBC Finance import checklist
• Import naming conventions

Exporting data from Munex

This section assumes you have defined the custom reports required to perform the export or you have downloaded a template that contains the custom report definitions. If neither of these is true then refer to Create custom reports on your own vs. using the custom reports template.

1. Open Munex.
2. Open the Munex file that contains the data/bonds/series to transfer.
3. Specify location for export files
   1. Select Report -> Export Selection.
   2. The Data Export Destination dialog pops up.
   3. Choose a location on the system to save the file.
   4. In the File Name, change the file extension from .mdb to .txt.
   5. Change Save as type to Text File (*.txt).
   6. Hit Save.
4. Specify issues to export
   1. A Select issues for REPORT dialog pops up.
   2. Choose the issues to export. You can transfer more than one issue at a time. For multi-purpose issues, choose all of the individual series within the issue.
   3. Hit OK.
5. Specify export preferences. (This step may be skipped after the first custom report export.)
   1. The Select Reports to Print dialog pops up.
   2. Hit Advanced, then Preferences, then select the Data Export report to edit.
   3. Hit Edit.
   4. Check all 4 boxes. The boxes are:
      • Add Issue Title Information to Exported Data
      • Add Project ID to Exported Data
      • Combine Reports Into Single Table/Spreadsheet
      • Open Target File after Printing to Excel/Word
   5. Close the popup.
   6. Close the dialog.
6. Specify export reports
   1. In the Select Reports to Print dialog, click Custom.
   2. Choose bondmat, bondcall and dsr.
   3. Click Irregular at the frequency prompt for the dsr report. In Munex 2010, this step may be omitted.
   4. Hit OK.
   5. All reports are exported to a .txt file and saved in the location specified in step 5.
7. Close Munex.

Note:

• There is a known problem using this custom report format to export series with overlapping maturities. Munex will generate a "length" error and the export will abort. One alternative is to manually enter those series in DBC Finance. Another alternative is to copy/paste bond structure and call information into DBC Finance's Import tool screens. The Import tool is hidden by default. Follow these steps to unhide the Import tool.
  1. Open DBC Finance.
  2. Right click on the Toolbar. A popup menu should appear.
  3. Select Customize Toolbar.
  4. Under Available toolbar buttons, double-click Import. Import should be added under Current toolbar buttons.
  5. Hit Close.
• The Munex custom report output should not be modified by any other program except DBC Finance. For example, do not use Excel to modify the Munex output, the format of certain fields will change so it can no longer be read by DBC Finance.

Import data into DBC Finance

Existing data in a DBC Finance .df2 data file will not be overwritten. However, an imported maturity, bond component, reserve fund, call table or series that is given the same name as an existing one in the .df2 file may update the existing component. See Import naming conventions for more information. You may want to import data into new or empty .df2 data files.

Follow the steps below to import data into DBC Finance.

1. Open DBC Finance.
2. Close all documents.
3. In the Open dialog, open or create the .df2 data file that will receive the imported data.
4. Close the Open dialog.
5. Press Control + Shift + J. The Import File dialog will pop up.
6. Under Files of type, select All Files (*.*).
7. Click on the .txt file which you exported. You may select multiple files to import by holding down the Ctrl key as you click on each file.
8. Hit Open when you have finished selecting files.
9. You will be prompted to select an existing issuer or create a new issuer that will contain the imported series. The issuer is a logical grouping of series within a .df2 file. All imported series will be saved under that issuer.
10. After you have specified the issuer, the import will start. All series will be added to the selected .df2 file, no existing data in the .df2 file will be overwritten.
11. The Finished Importing dialog pops up. Click OK.
12. Review imported data. Click Open on the Toolbar and the Open dialog pops up with your newly created data transferred over.

Refer to DBC Finance import checklist regarding import assumptions and exclusions. Import naming conventions explains how the imported series and bonds are organized in DBC Finance.

Create custom reports on your own vs. using the custom reports template

The export process uses Munex custom reports to create files that can be imported into DBC Finance. Prior to performing the export, the custom reports must be defined. You can use an already created custom report "template" or create the custom reports from scratch. The custom report template would have been created by your organization. DBC cannot create the custom report template. Below is a discussion of both options followed by instructions for performing the export and importing into DBC Finance.

Your Munex user preferences are stored in a file named defaults.sf. This is the same file that contains custom report definitions. Defaults.sf can be found in C:\Program Files\Munex\Munex 2006\defaults.sf.

If you choose to keep your own defaults.sf, you can create the custom reports yourself by following the directions in Creating the export custom reports in Munex.

If you choose to use the custom report "template", it is important that you preserve a copy of your defaults.sf file:

1. Goto C:\Program Files\Munex\Munex 2006
2. Locate defaults.sf
3. Make a copy of your current defaults.sf
4. Save your organization's custom report template in the defaults.sf file to:
   C:\Program Files\Munex\Munex 2006
5. Now you can use the custom reports to export data from Munex. Follow the instructions in Exporting data from Munex.

To use your original defaults.sf, use the copy of your defaults.sf and replace the existing defaults.sf that you downloaded.

Creating the export custom reports in Munex

Follow these directions to create your own custom report rather than using the template report as shown above.

Note: Custom report definitions are saved with your other user preferences in a file named defaults.sf. If you choose to keep your own defaults.sf, you can create the custom reports yourself. Your custom report definitions will be saved in your defaults.sf file. That file can be found in: C:\Program Files\Munex\Munex 2006\defaults.sf.

1. Open Munex.
2. Create a "maturities" custom report
   1. Go to Report -> Report Writer -> Create.
   2. Specify bondmat as the custom report name.
   3. Click Edit in Table Information.
   4. Under Column Selected choose Maturity.
   5. Add the following fields in this exact order:
      • Maturity
      • Dated
      • 1stCoupon
      • Coupon Period
      • Type
      • ofBond
      • Coupon
      • Yield
      • Price
      • Concession
      • +Takedown
      • =Total
      • TotalTakedown
      • IssuanceValue
      • AccretedValue
      • MaturityValue
      • CallDate
      • CallValue
      • RedemptionId
      • CallPrice
      • DaycountMethod
   6. Under Column Selected select Principal Payments.
   7. Add the following fields in this order:
      • Date
      • FVPrincipal
   8. Once all the fields have been selected, click OK and then Save.
3. Create a "call tables" custom report
   1. Go to Report -> Report Writer -> Create.
   2. Specify bondcall as the custom report name.
   3. Click Edit in Table Information.
   4. Under Column Selected choose Maturity.
   5. Add the following fields in this exact order:
      • Maturity
      • Type
      • ofBond
      • Coupon
   6. Under Column Selected choose Redemption for Export.
   7. Add the following fields in this order:
      • Date
      • Call Date 1
      • Call Price 1
      • Call Date 2
      • Call Price 2
      • Call Date 3
      • Call Price 3
      • Call Date 4
      • Call Price 4
      • Call Date 5
      • Call Price 5
      • Call Date 6
      • Call Price 6
      • Call Date 7
      • Call Price 7
      • Call Date 8
      • Call Price 8
      • Call Date 9
      • Call Price 9
      • Call Date 10
      • Call Price 10
   8. Once all the fields have been selected, click OK and then Save.
4. Create a "DSR" custom report
   1. Go to Report -> Report Writer -> Create.
   2. Specify dsr as the custom report name.
   3. Click Edit in Table Information and under Column Selected choose Flow of Funds.
   4. Select the fields for the custom report. After you select a field, a pop screen will appear, choose Debt Service Reserve and hit OK. Add the following fields in this exact order:
      • Date
      • Event
      • Deposits
      • Rate
      • FundID
      • Principal
      • Cash Balance
   5. Once all the fields have been selected, click OK and then Save.
5. Now you can export data from Munex using the custom reports. Follow the instructions in Exporting data from Munex.

DBC Finance import checklist

DBC Finance has default choices/values for every prompt. Assumptions made by the import include (but are not limited to):

• Dated date and delivery date is the same as the exported dated date.
• All bonds are fixed rate.
• DSR is a net funded GIC.
• DSR amount is an exported fixed dollar amount, not a formula (the amount may have been computed by a formula in Munex).
• Call provision defaults to 0 days notice, callable on any date.

Certain information that is currently not imported includes (but is not limited to):

• Delivery date
• Overlapping maturities (export from Munex not yet determined)
• Variable / adjustable rates
• Premium / discount CABs are imported as par CABs.
• Accreted values for CABs
• Delivery date expenses
• Ongoing expenses
• CAPI
• Project Funds
• Structuring assumptions
• Escrow information
• "Pyramid" call methodology
• Multiple call provisions for maturities in the same bond.

Users should verify data that includes (but is not limited to):

• Call provision information (e.g. # days to call, OK to call on any date or interest payment date)
• Zero coupon bonds
• Premium / discount CABs

Issue titles (if any) labeled Title1, Title2, Title3 and Title4 in the custom report are imported as Additional Titles in DBC Finance. In addition, Print issuer name and Print series name will be unchecked so the titles will print on the reports.

Import naming conventions

The following explains how differences in organizing data and naming conventions were resolved. If desired, users may change the names.

Note: Terms indicated in boldface print in this document are the field names of the data exported from Munex.

Multi-purpose import vs. single issue import

It is possible for single issues and the individual purposes from a multi-purpose deal to be in the same exported file. A purpose would be similar to a Series or Refunding case in Project Finance in DBC Finance.

The Munex export allows for one, some or all of the individual "purposes" in a multi-purpose deal to be exported. Each individual purpose will be saved as a separate series. The import will process whatever was exported.

The IssueName field in the export file is the:

• umbrella name for a multi-purpose deal

Or

• name of an single issue deal

When any part of a multi-purpose deal is in the exported file, there is an extra PurposeName field but only for the records of the multi-purpose deal. When PurposeName is present, it is the name of the individual purpose in a multi-purpose deal.

Naming conventions

The DBC Finance data file (.df2) name is user defined. Before importing, the user must open or create the .df2 file. Both the issuer short and long names are user defined. For short names, legal characters are A - Z, 0 - 9 and the underscore character. Lower case letters are automatically converted to upper case.

Multi-purpose deals

• .df2 Series short name - PurposeName field truncated to 8 characters. Illegal characters changed to "_".
• .df2 Series long name - PurposeName field.

Single issue deals

• .df2 Series short name - IssueName field truncated to 5 characters + serial number. Serial number starts at 1. The last possible serial number would be 999. The idea is to guarantee unique series names. Illegal characters changed to "_". If the short name already exists, the next sequential short name will be selected.
• .df2 Series long name - IssueName field.

Bond components
Munex bond component names are system generated, "SERIAL", "TERM 1", "TERM 2"... "TERM 10".

Munex commingles serial CABs and CIBs are under "SERIAL". The import will separate them into components named "SERIAL" and "CAB" (short name and long name).

The import will bring over the term short names used in Munex, "TERM_01", "TERM_02", etc. DBC Finance will create term long names with following format: "Terms of [yyyy]", where [yyyy] is the 4 digit year of the final sinking fund maturity.