District Data and FCA Data Extract

Transcription

1 District Data and FCA Data Extract Liz Turner, Manager, Financial Applications May 13, 2014 Agenda District Data Tables Overview Data Sources Override Processes (discussed in greater detail in Loan Coding session) Timing of Data Feeds and Uses of Data FCA Data Extract Overview Types of Data Included Validation Data Warehouse Confirmation Process Proposed Confirmation Process Specified in Regulations 2 1

2 District Data Tables - Overview Introduced concept of District Data Tables in Allows AgriBank to capture critical reporting fields for all District Associations regardless of system platform. Materially scaled back number of data fields compared to DSS. First data available Jan, 2007 with monthly feeds through current time period. Process is continually evolving to align with new reporting requirements and process improvement initiatives. Currently working on data governance requirements, data dictionaries and security processes to enable Associations to access District tables. 3 District Data Tables Data Sources General Ledger (GL) Information DB2 tables. Includes GL balance information for most District Associations (excludes FCSA). Includes GL transactions for Associations using Infor (formerly Trisyn) (AgriBank-hosted GL). Supports Hyperion applications (Finance, DISTREPT and Planning cubes). Information is used to balance data between systems. Most data feeds follow GL cycle timelines (i.e., subsequent to GL cycles, data is extracted from systems and loaded to tables). Supports Association management reporting processes. Supports District reporting processes. 4 2

3 District Data Tables Data Sources Loan and Loan Investment information DB2 tables. Includes loans, and loan investment information for all Associations from the various loan accounting systems used throughout the District. Data from various systems is mapped to common table structures to ensure consistency of: key fields used to distinguish source of data, time period, Association and record identifiers. amount fields (assists with ties to ledger balances). codes used for reporting. The base District tables are sourced for District Hyperion tables. District Hyperion tables are sourced for Finance, DISTREPT and Planning cubes (Loans cube will be converted to source from District tables). Includes balancing and override processes (these processes are covered in greater detail in the Loan Coding presentation.) Asset pool data - excludes big pool records to allow for more specific and accurate reporting using shadow records. 5 District Data Tables Data Sources Commitments DB2 tables. Includes commitments from Cornerstone. New commitment table process rolled out in 2013 allows for inclusion of shadow sold commitment records. This change reduced risk in reporting processes by eliminating the need for users to run calculations to determine net (gross amount less sales) position for the commitment. The main District tables are sourced for District Hyperion tables. District Hyperion tables are sourced for Finance, DISTREPT and Planning cubes (Loans cube will be converted to source from District tables). Includes override processes (these processes are covered in greater detail in the Loan Coding presentation.) Commitment data is used for reporting available commitment and LOC amounts. Reporting for volume and other balances from funded (draw) records occurs through the Loan tables. 6 3

4 District Data Tables Data Sources Leases DB2 tables Includes finance and operating lease records for all Associations from the various lease accounting systems used throughout the District. Additional processes were introduced in Q to encompass feeds from JDR for AgCountry and Mid-America Data from various systems is mapped to common table structures to ensure consistency of codes used for reporting. Key fields used to distinguish source of data, time period, Association and record identifiers Amount fields (assists with ties to ledger balances) Codes used for reporting The main District tables are sourced for District Hyperion tables. District Hyperion tables are sourced for Finance, DISTREPT and Planning cubes (Loans cube will be converted to source from District tables). Includes balancing and override processes (these processes are covered in greater detail in the Loan Coding presentation.) 7 District Data Override Processes Process designed to ensure subsequent events can be captured at granular (record) levels in reporting databases. Capture of data at record levels allows for one source of truth and ensures loan level reports and data extracts tie to summary level information provided on FCA Call, shareholder and other internal and external reports. Common events captured in overrides include: Changes of accrual status (including impact to volume) Transaction rejects/suspense (impacting volume) Changes in past due status Record coding changes (participation, restructure, FC loan type, similar entity, etc.) For more information related to the override processes, please see the conference materials for the Loan Coding session. 8 4

5 District Data Tables Timing and Uses General Ledger Data Daily for Infor (formerly Trisyn) and FPI and monthly for FCSA Loan Commitments, Loans, Loan Investments, Leases, Debt Investments Monthly (timing of receipt varies by provider) Used in Association management reports, FCA Call Reports, syndication study, shareholder reports, FCA data extract, MASK reporting to the Funding Corp, and many other processes. 9 FCA Data Extract Overview Replacement to LARS (Loan Account Reporting System) and Loans1 (legacy FCA data extract). The new extract is referred to as Loans2. First submission of Loans2 extract submitted to FCA for Q Loans2 files are submitted to FCA by 12 data providers across the System. Used by FCA Office of Examination and Policy divisions. First benefits from Loans2 extract: sunset of Loans1 requirements effective December 1, 2012 sunset of LARS requirements after Q Additional reporting relief as benefit of Loans2 is being analyzed. 10 5

6 FCA Data Extract Data Included AgriBank provides records to FCA for commitments, loans, leases and loan investments. These records are designated in the Loans2 extract using the Record Type field. Loans2 extracts include 20+ records of aggregated data (referred to as hash totals). These are sent by UNINUM (unique number FCA assigns to all system entities) to indicate the totals of certain items in the extract. The purpose of these records is to provide a balancing source between provider data files and FCA data load processes. 11 FCA Data Extract Data Included 4 fields are included to enable FCA to determine the source, time period, system entity (UNINUM) and schema version (defines data file requirements). 30 customer-related fields are provided including: CIF, name, FIPS (Federal Information Processing Standard code for geographical indicator), balance sheet components, income statement components and ratio data. 12 6

7 FCA Data Extract Data Included The remaining, approximately 89 fields, are related to the individual records - commitments, loans, leases in the file and include: Nearly 50 fields to define characteristics of the records (i.e., branch, type, performing status, PD rating, LGD, YBS, etc.) 9 fields to assist the FCA with tracking participation relationships (i.e., master/bought/sold, inside or outside system, syndications, assignments, shared asset numbers, etc.). 26 record-level balance related fields (i.e., principal, accrued interest, book value, past due amounts, charge-offs, recoveries, appraisal amounts, etc). 13 FCA Data Extract - Validations Reconcile data to Call Report Schedules (performed by AgriBank). Each quarter end, AgriBank reconciles the extract data against the Call report schedules for all District Associations. FCA allows variances up to a 5% tolerance level for all fields where FCA requires the data tie to the call reports. AgriBank s reconciliation process ensures there are no out of tolerance conditions before extract submission date by 20 th of month following quarter end. FCA is notified of post-submission Call Report changes that would yield an out of tolerance condition. Specific Call Report Schedules reconciled: Schedule RC: Line 2. Securities Line 4. Loans, notes, sales contracts, and leases Line 5. Accrued interest receivable Schedule RC-1: Loans by Loan Type Finance and Operating Lease Totals 14 7

8 FCA Data Extract - Validations Reconcile data to Call Report Schedules (performed by AgriBank). Specific Call Report Schedules reconciled (continued): Schedule RC-F: All Loan and Finance Leases Performance data (accrual, accruing-formal restructures, nonaccruals and by past due status) Schedule RC-F2: Loans and leases by Type by Credit Classification Schedule RC-F3: Loans and Finance leases by Probability Of Default and Loss Given Default Codes We also tie out transfers to OPO (other property owned). We will begin tying out new money with the implementation of a new data project in Data Warehouse - File Certification FCA regulation on Reports of Accounts and Exposures (Loans2 file) became effective on February 21, Rule authorizes Funding Corp. to collect data from all banks and Associations and serve as the central data repository manager. Each reporting bank and association is responsible for submitting a certification signed by a board-appointed officer. AgriBank is working with our legal department to coordinate District certifications and anticipate using a process similar to other existing certifications. 16 8

9 Data Warehouse - File Certification Certifications begin with September 30, 2014 data (due in October) To District Banks (from affiliated Associations) Each association whose district bank submits Loans2 data on behalf of the association will submit a full certification (see Certification statement section below). To Service Providers (from member Associations) Each association who relies on a service provider (AgVantis, FPI) to submit Loans2 data on behalf of the association will submit a full certification (see Certification statement section below). To Funding Corp. (from District Banks, CoBank, Service Providers, Independent Assoc.) This would be done by AgriBank for most District Associations and FPI for AgCountry. To FCA (from Funding Corp.) Certification statement: the information provided in the report of accounts and exposures has been prepared in accordance with all applicable regulations and instructions, and is a true and accurate record of the data maintained by the bank or association (as applicable), to the best of its knowledge and belief. The report of accounts and exposures is being provided for the purpose of compliance with the requirements of regulation Questions? 18 9

10 For questions or comments, please contact Liz Turner at or 19 10