1 - ACCOUNTS RECEIVABLE

1 - ACCOUNTS RECEIVABLE ACCOUNTS RECEIVABLE 1.01 User defined GL posting dates for receivables documents (e.g. orders, invoices, etc.) to be either the Transaction Date or the System Date. 1.02 User configuration to set the invoice aging date as either the transaction date or the invoice due date. 1.03 User configuration to default sale order and invoice GL accounts by customer. 1.04 Open order (cash receipts applied to invoices) and balance forward cash receipts management. 1.05 For balance forward cash receipts management, system has an automated method to close open invoices. 1.06 Customer record may be classified by customer type and other segmentation criteria. 1.07 Customer record configured by user with customer specific Sales GL account. 1.08 Customer record configured by user with specific currency type. 1.09 Customer record configured by user with customer specific special instructions. 1.10 Customer configured by user with unlimited Bill To addresses. 1.11 Customer configured by user to receive or not receive customer statements. 1.12 Customer records can be assigned to or linked with other related customer records (e.g. related accounts). 1.13 Customer record displays financial information including sales, payments and credit memos. 1.14 Customer record displays customer-specific aging (e.g. outstanding receivable balances by age). 1.15 Customer transactions permit drill-down to see actual current or historical transaction document. 1.16 Default tax accounts setup at the customer address level. 1.17 System supports VAT and HST tax setup and calculations. 1.18 Attach electronic document(s), or links to electronic documents, to transactions including workflow. 1.19 Orders and invoices accommodate non-inventory line items (e.g. services). 1.20 Order and invoice line items individually designated as taxable or non-taxable. 1.21 Order and invoice line items default GL Accounts, however, may be changed to different GL accounts. 1.22 Sales Orders created (e.g. Sales Orders for Corporate Training or Facilities Rental) and managed via workflow through to invoicing and receipt of payments. 1.23 Sale order and invoice transactions default payment terms by Customer. 1.24 Sale orders and invoices default tax codes and tax amounts by Customer Bill-to or Ship-to Address (e.g. configurable by customer). Appendix F FRM Business Requirements 1 of 17

1 - ACCOUNTS RECEIVABLE 1.25 Sale orders and invoices default currency type by Customer. 1.26 Sale orders and invoices default Bill To address by Customer. 1.27 Default tax by customer with option to override if required. 1.28 Systems supports the creation of Credit Memos. 1.29 Credit Memos created from user-defined templates. 1.30 Credit Memos put on account or converted to a disbursement to Customer. 1.31 Credit Memos assigned to an approval workflow based on user-defined criteria. 1.32 Pre-Authorized Withdrawals setup and processed with all Canadian Bank institutions as required to automate receivables from customers and retirees. 1.33 System displays all recurring receivables transactions in a consolidated view by date range. 1.34 User initiated mass modification to change an incorrect attribute on multiple customer records at one time (e.g. change an address or GL account). Appendix F FRM Business Requirements 2 of 17

2 - ASSET MANAGEMENT AND TRACKING FIXED ASSETS Software Configuration 2.01 Depreciation methods include straight line depreciation. 2.02 New depreciation methods configured by user. 2.03 Fixed Asset tag number of at least 10 numbers in length. 2.04 Asset type and other segmentation criteria. 2.05 Asset status designation (e.g. active, inactive, retired, etc.). 2.06 Asset depreciation method. 2.07 Asset depreciation frequency (e.g. month, quarter, year, etc.). 2.08 Asset depreciation life. 2.09 Multiple GL accounts for various types of fixed asset cost additions. 2.10 Multiple GL account for various types of assets' accumulated depreciation. 2.11 Asset tag number. 2.12 Asset serial number. 2.13 Asset location. 2.14 Asset depreciation cost centre. 2.15 Asset purchase date. 2.16 Asset warranty information. 2.17 Asset source purchase order number. 2.18 Asset source system assigned invoice number. 2.19 Each asset displays accumulated deprecation amount at different points in time. 2.20 Each asset displays asset book value. Transaction Processing 2.21 Assets depreciated individually. 2.22 Assets depreciated by group. 2.23 System can calculate prior period depreciation. 2.24 Assets added manually. 2.25 Assets added using integration from AP or Receiving. Appendix F FRM Business Requirements 3 of 17

2 - ASSET MANAGEMENT AND TRACKING 2.26 Assets added as donated assets. 2.27 Assets retired individually. 2.28 Asset location and/or depreciation cost centre updated manually or by batch. 2.29 One Asset automatically created from multiple lines from AP. 2.30 Multiple assets automatically created from a single line from AP. 2.31 Asset additions, retirements, adjustments, depreciation automatically creates journal entry transaction. 2.32 RF Capability to receive scanned bar code to capture and track tag number and serial number. College's Bar Code Scanner Make: Motorola Model number: MC3190. 2.33 Track non-capital assets. Reporting 2.34 Online audit trail displays all asset transactions created, edited and deleted by date, user and specific field changes. Reports run by date range or period for cost, depreciation and net book value showing opening balance, period 2.35 transactions and ending balance. 2.36 Fixed asset reports by asset location, cost centre, custodian and/or other asset criteria. Appendix F FRM Business Requirements 4 of 17

3 - PROCURE TO PAY PROCESS Note: The college does not hold or track inventory but does require visibility, management and reporting of items throughout the procure-to-pay process. These items are created from e-commerce sites, vendor electronic catalogues, request for quotes, contracts and requests for proposals or directly by users of the system. Users of the system must be able to create or pull items from all sources through the procure-to-pay processes below. Item information must include one or many identification numbers, text, descriptions, costs, tax codes, discounts, etc. PURCHASING VENDOR MAINTENANCE 3.01 User-configurable workflows from requisition to payments and returns. 3.02 Classification of vendor records by vendor type and other user-defined segmentation criteria. 3.03 Vendor records with specific currency type. 3.04 Creation of vendor records with multiple address types e.g.. remit to, order, bill-to addresses. 3.05 User configurable vendor records with any supplier specific special instructions. 3.06 Vendor 'snapshot' information, easily accessed directly from vendor maintenance screens, including financial information including purchases, payments and returns accumulated balances. 3.07 Vendor record to support various tax designations. 3.08 Easy setup for one-time vendors and one time payments. 3.09 Lookup of vendor by field or attribute (e.g. PO number, name, address, invoice number). 3.10 User mass modification to change an incorrect attribute on multiple vendor records at one time (e.g. change payment terms, territory or GL account). PURCHASE REQUISITIONS/ORDERS 3.11 Purchase orders fully populated from Purchase Requisitions with the ability to modify PO data. 3.12 Purchase order numbers option to be automatically assigned or permit manual entry. 3.13 Multiple purchase orders types user-configured (e.g. Rush Order, Purchase Order, Blanket Order, Contract, etc.). 3.14 Purchase orders default currency type by vendor or supplier. 3.15 Purchase orders default shipping method by vendor or Item. Appendix F FRM Business Requirements 5 of 17

3 - PROCURE TO PAY PROCESS 3.16 Purchase orders default ship to address. 3.17 Purchase orders default Tax Exempt ID for tax exempt purchases. 3.18 Purchase Orders with user selection among multiple ship to addresses. 3.19 Purchase Order pricing based on designated price book, catalogue or contract.. 3.20 Purchase Orders saved with file attachments (e.g. PDF, Excel or Word files) or links to file attachments. 3.21 Purchase Orders possess 'soft' line items (e.g. services). 3.22 Purchase Order line items default tax codes and tax calculated amounts. 3.23 Purchase Order line items are individually designated as taxable or non-taxable. 3.24 Purchase Order line items default GL Accounts, however, may be changed to different GL accounts. 3.25 System records and processes Return Merchandise Authorizations (RMAs) entries from vendors. 3.26 RMA receipt records created from standard or user-defined templates. 3.27 RMA user-defined workflow. 3.28 RMA process generates Ship Tickets to ship vendor returned items. System sends via email or fax. 3.29 When creating new POs, system defaults all date field values (e.g. Purchase Date, Due Date, Cancel Date, etc.). 3.30 Purchase Orders entered in any currency with conversion to college base currency. 3.31 Purchase Orders designated to recur for a user-defined number of cycles. 3.32 Purchase Orders designated to recur based on an irregular user defined schedule. 3.33 System displays all recurring PO transactions in a consolidated view by date range. 3.34 Purchase Order transactions saved as templates to create new orders from. 3.35 System to prompt end user if they have missed any user-defined mandatory fields. 3.36 Audit trail for purchasing showing date, time and person who created, modified and emailed PO to vendor. 3.37 See when purchase order has been received in receiving in real time. 3.38 Email, print and fax PO's directly from system to vendor. 3.39 System identification of aged requisitions. 3.40 Manually close POs with outstanding balances. 3.41 Create specific 'reusable saved' messages to be added to and viewable on PO (e.g. message to vendor/message to shipping/message to AP). 3.42 Vendor record may be configured for tax and tax exemptions. 3.43 Reopen a closed PO. 3.44 Allocation of various budget codes (splits) in requisition and have it automatically default to PO. Appendix F FRM Business Requirements 6 of 17

3 - PROCURE TO PAY PROCESS 3.45 Due date from Requisition to default to PO. Accounts Payable 3.46 Automated three-way match process - Order/Receipt/Invoice. 3.47 User- configurable workflow for approvals. 3.48 Payment of partially received orders. 3.49 Easy look-up of partially received orders. 3.50 Automatic application of credit notes at invoicing with override option. 3.51 Option to consolidate or non-consolidate payments of invoices (e.g. vendor level and overrides). 3.52 Hold payments - $ or %. 3.53 Easy visibility to outstanding held payments. 3.54 Add text to payments at line and header level. 3.55 Automatic inclusion of text on payment notifications, emails, and AP screens. 3.56 Add notes (during AP process) that do not appear on payments or emails. 3.57 Automated payments by paper cheque. 3.58 Automated payments by EFT. 3.59 Automated payments via wire transfer. 3.60 Default tax codes on AP docs and screens. 3.61 Show HST on all AP docs and screens. 3.62 Calculate PSB Rebate of HST (refer to the tab "9. Tax" for details). 3.63 Automatically apply non-rebated portion of HST to the appropriate Cost Centre. 3.64 Tax application is at line/item level. 3.65 User-override tax at line level. 3.66 Setup recurring payments for any user defined schedule. Receiving 3.67 Scan receipts (Barcodes) into the system using college's handheld devices. College's Bar Code Scanner Make: Motorola Model number: MC3190. 3.68 Lookup of PO based on barcode scanned data. 3.69 Generate receipt based on scanning of items. Appendix F FRM Business Requirements 7 of 17

3 - PROCURE TO PAY PROCESS 3.70 Add text/comments at line and order level during receipt. 3.71 Receive and tract items not related to a requisition or PO. Appendix F FRM Business Requirements 8 of 17

4 - GENERAL LEDGER INTERNATIONAL REQUIREMENTS 4.01 Multi-currency management - multiple currencies with exchange rate calculations. 4.02 System calculates realized and unrealized currency gains and losses. 4.03 International taxing methods including VAT and GST. 4.04 Separate legal entities in a different language and currency and chart of accounts. GENERAL LEDGER 4.05 Chart of accounts configured in a user defined length of up to 20 characters. 4.06 Chart of accounts configured in up to 7 or more user defined segments. 4.07 Chart of accounts segments enforce valid values (e.g. invalid segment value combinations are not permitted). 4.08 Chart of accounts made Inactive using effective dating. 4.09 Fiscal periods permit user defined dates. 4.10 System supports 13 or more individually defined fiscal periods. 4.11 GL transaction posting dates forced to current period. 4.12 GL transactions not allowed posted to closed periods. 4.13 GL accounts configured by company in order to default for all accounting transactions. 4.14 GL transactions and Journal Entries transactions number length and beginning sequence number user defined. 4.15 GL transaction types are user defined. 4.16 The use of workflow to route journals for approval. Includes email notification and attachments. 4.17 Use of effective dating for chart of accounts and ability to correct history. 4.18 Multiple budgets configured and saved for the same chart of account, fiscal year and fiscal periods. 4.19 New budgets created from existing or prior budgets. 4.20 Budgeted chart of accounts designated as Active or Inactive. 4.21 System displays budget view for all chart of accounts in single view. 4.22 System displays budget view for each individual chart of account with actual and variance. 4.23 Ease of creation and maintenance of tree structure to be used in reporting. Transaction Processing Appendix F FRM Business Requirements 9 of 17

4 - GENERAL LEDGER 4.24 Upon new GL transactions and Journal Entries, system defaults current date(s). This may be overridden. 4.25 System can be configured to assign a unique identifier number to each journal. This can be overridden. 4.26 Journal Entries support inter-company processing (e.g. posting debits and credits to different companies in same Journal Entry). 4.27 Journal Entries permit Notes and references and attachments. 4.28 Journal Entries can be saved without posting. 4.29 System supports reversing Journal Entries. 4.30 System supports recurring Journal Entries. 4.31 Recurring Journal Entries based on templates with predefined schedules. 4.32 Recurring Journal Entries configured to recur on specific dates. 4.33 Recurring Journal Entries configured to recur a user-defined number of times. 4.34 System will not permit out of balance journal entry posting. 4.35 Journal entries can be copied and all fields can be revised. 4.36 Unposted journal entries deleted. 4.37 Posted journal entries may not be deleted 4.38 Journals may not be posted more than once. Process Automation 4.39 Journal Entries saved as Templates for future use. 4.40 Journal Entries posted from sub-modules reference their source (e.g. sub-module, transaction number). 4.41 Import tool or wizard to import journal entries from a spreadsheet, text, or CSV file. 4.42 Year-end close process with options to close to multiple or single retained earnings accounts and carry forward balance sheet account balances to new year. Must have ability to reverse and re-do multiple times. 4.43 Journal entries from external systems can be set up for interfacing to General Ledger. Reporting 4.44 Online audit trail displays all ledger transactions created, edited and deleted by date, user and specific field changes. 4.45 Trial balance report by date range and by chart of account range and by company. 4.46 Trial balance report with drill down from period balances to source transactions. Appendix F FRM Business Requirements 10 of 17

4 - GENERAL LEDGER 4.47 Complete ledger detail transaction report. 4.48 Unrealized currency gains and losses report. 4.49 Balance Sheet report by period. 4.50 Income Statement report by period. 4.51 Cash Flow report by period. 4.52 Report to compare posted journals to general ledger. Multi-Company Processing 4.53 System supports multiple-company processing. 4.54 Each company configured with a different base currency. Appendix F FRM Business Requirements 11 of 17

5 - TREASURY AND CASH MANAGEMENT Bank Statements 5.01 Automatic download of most recent banking transactions via common formats. At a minimum BAI2, SWIFT, FINSTA. 5.02 Automated and manual categorization of banking transactions. 5.03 Search options for specific bank transactions. 5.04 Export data to common formats (i.e. CSV, Excel). 5.05 Annotate specific transactions with additional notes. 5.06 Different currency types, USD and CAD at a minimum. 5.07 Ability to add additional currencies in the future to accommodate international growth. 5.08 User ability to Flag specific transactions for investigation 5.09 Report generation for specific transaction periods. 5.10 Report generation for specific transaction categories. Bank Reconciliation 5.11 Automated matching of General Ledger and bank transactions. 5.12 Pattern matching/rules setting for automated matching of transactions. 5.13 One-to-one, one-to-many, and many-to-many matching options. 5.14 Manual matching of unmatched bank/gl transactions 5.15 Generation of journal entries related to bank transactions (i.e. interest, fees). 5.16 Reconciliation of multiple bank accounts to single GL account. 5.17 Tolerance threshold for automated matching of transactions. 5.18 Report generation of reconciled and unreconciled items, including totals. Cash Management 5.19 Generate reports for current cash position. 5.20 Generate statements of cashflow. 5.21 Project future cashflows based on known variables. 5.22 Group cash positions by business units or departmental functions. 5.23 Cash flow volatility analysis. Appendix F FRM Business Requirements 12 of 17

5 - TREASURY AND CASH MANAGEMENT Internal Controls 5.24 Audit trail generation for data entry/modification. 5.25 User login/restrictions based on specific access levels. Appendix F FRM Business Requirements 13 of 17

6 - TRAVEL AND EXPENSES Travel & Expenses 6.01 System generated emails to approvers, payroll (e.g. for payment) and HR (e.g. for international travel only). 6.02 All system generated emails for expenses include a link to the appropriate completed form in the system. 6.03 User-defined workflows based on a field content (i.e. VP approval required for out of province travel). 6.04 Employee dashboard includes all personal claims, and status, when logging in. 6.05 Addition of comments when completing or approving expense forms. The comments are date/time/user ID stamped. Comments required at line and header levels. 6.06 Print completed expense forms. 6.07 Full GL integration from expense transactions. 6.08 Payment of expenses through Payroll. 6.09 Scan receipts or attach electronic files to authorizations and claims. 6.10 Email generated and sent to Manager indicating that a claim is ready for approval. 6.11 Manager sees all pending claims & authorizations when logging in. 6.12 Manager has a link or access to the receipt file from the claim form. 6.13 Employees/managers/Payroll/Finance dashboard view of status of claims (e.g. submitted, approved, pending, submitted to payroll, paid). 6.14 When form approved, auto generate and send an email to the employee indicating the claim was approved. 6.15 If not Approved: Auto generate and send an email to the employee indicating the claim was not approved. 6.16 System auto verifies claims that have already been submitted for duplicates. 6.17 Authorizations and claims are required to be linked in the system. 6.18 Multiple claims submitted against one travel authorization. 6.19 User-defined field limits limits/warnings (i.e. daily meal limit exceeded). 6.20 User defined field formulas/calculations such as mileage (e.g. employee enters mileage, system calculates rates based on cumulative employee use per calendar year). 6.21 Expense amounts split by cost and tax - two separate amounts. 6.22 System application of tax rules to expense non-rebated taxes (Refer to "9. Tax" tab). 6.23 Department and account at line level as well as multiple departments and accounts (i.e. split expense across departments or cost centres). Expenses can be shared across departments and accounts. 6.24 User edit of department and account at line level when entering expenses. Appendix F FRM Business Requirements 14 of 17

7 - COMMITMENT CONTROL Commitment Control 7.01 Check actual expenses and encumbrances (also known as Commitments) against control budget 7.02 Control budget set at account or summarized at account rollup level or type of transaction. 7.03 Create commitments from system entries (e.g. purchase order) 7.04 Budget error/warning notification if close to or exceeding budget 7.05 Single source of data for GL, Payables, Budgeting, Payroll, HR, Expenses, Purchasing 7.06 Create and post commitment journals Appendix F FRM Business Requirements 15 of 17

8 - FINANCIAL REPORTING Financial Reporting 8.01 Drill up/down from College Level, which is the highest to transaction level in all Financial Reporting areas. 8.02 Report by daily, monthly, month to date, user-defined date range, year-to-date, calendar year and fiscal year. 8.03 Comparative reports (LY/TY), Year-over-Year, Actual to Budget, etc. 8.04 Toggle/scroll to view one period to the next. 8.05 Download financial data to excel retaining drill up/down functionality in excel view. 8.06 Easy to use organization look-up functionality (e.g. Cost Centre, name, roll-ups, etc.). 8.07 LOB Reporting by user-defined structure and hierarchy. 8.08 Financial Health/Ratios/Metric Reports. 8.09 Flexible Financial Dashboards configurable by user and/or role. 8.10 Secure data to the field/transaction level by user and/or role. Appendix F FRM Business Requirements 16 of 17

9 -TAX Commodity Tax (on Purchases) 9.01 Option on vendor file to apply or not apply different taxes. 9.02 Default tax application on Vendor File by address. 9.03 Calculate and apply all Canadian federal and provincial tax rates by user-defined criteria (i.e.: HST 13%, HST 8%, HST 5%, exempt). 9.04 System calculation of tax at line and/or header level. 9.05 HST rebates calculated by user-defined tax rate table (i.e. rebates applicable to the College are HST13 - rebated at 73.77%, HST5 - rebated at 67%, HST8 - rebated at 78%). 9.06 System calculated rebates at line level (Refer to requirement 9.05). 9.07 System automated posting of rebate amounts to defined GL accounts which are different based on rebate type. 9.08 System automated posting of non-rebated portion of tax to cost centres. 9.09 User override of default tax at vendor and invoice line level by % and/or $. 9.10 System validity check of tax when invoice line entered. 9.11 User acceptance of invoiced tax at non-calculated/validated rate. 9.12 Full self-assess commodity tax functionality for non-canadian Vendors. 9.13 Automatic system calculation and application of self-assessed tax values. At a minimum on POs and Invoices. 9.14 Automatic system calculation and application of tax rebates on self-assessed tax. 9.15 Automatic system posting of self-assessed tax values including rebate portions. 9.16 Automated system calculation and posting of tax rebates on all employee expense line items. 9.17 Accommodate single or multiple tax rates. Appendix F FRM Business Requirements 17 of 17