XLS - wwwjfmipgov

Document Sample
XLS - wwwjfmipgov Powered By Docstoc
					Financial Systems Integration Office                          Requirements Tested Matrix
                                                             Spreadsheet Use Instructions
This FSIO provided workbook is password protected but allows individuals to filter, sort, and copy information.
This spreadsheet is password protected from all changes.


   Colum
  Identifier        Column Name                  Column Description                                                Valid Values
Column A          Requirement Year      This represents the year a given         2001
                                        requirement grouping was published.      2006
                                                                                 2001 Addendum - Requirements added or revised for 2004 CCR incremental test
                                                                                 2006 Addendum - Requirements added for 2008 incremental test
                                                                                 2006 Clarification - Requirements revised for 2008 incremental test

Column B          Requirement Number This is the unique number given to a        Published 2001 requirement numbers
                                     requirement. The requirement is             2001 incremental test addendum requirement numbers
                                     unique by its requirement year and          Published 2006 requirement numbers
                                     requirement number combined.                2008 incremental test addendum requirement numbers
Column C          Description        This is the text describing a given         Unique to each requirement.
                                     requirement.
Column D          Requirement Status Identifies whether a Core Financial         Mandatory - A Core Financial System must provide this functionality.
                                     System must provide the required            Value-added - A Core Financial System may include this desirable system
                                     functionality or whether the                feature.
                                     functionality is a desirable system
                                     feature.
Column E          Test Cycle         This column identifies the cycle of         Full 2003 - Tested as part of the full 2003 core financial system test.
                                     testing (e.g., Full 2003, incr. 2005) in    Incr(emental) 2004/2005 - Tested as part of the 2004/2005 CCR incremental
                                     which a given requirement was               test.
                                     originally tested or is scheduled to be     Incr(emental) 2005/2006 - Tested as part of the 2005/2006 P224 incremental
                                     tested.                                     test.
                                                                                 Pending - Not currently scheduled to be tested.
                                                                                 Not Applicable - Value added or were deleted from requirements set prior to
                                                                                 testing.




Printed on 5/20/2010                                         93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                            Page 1 of 79
Financial Systems Integration Office                          Requirements Tested Matrix
                                                             Spreadsheet Use Instructions
   Colum
  Identifier         Column Name                Column Description                                                Valid Values
Column F          Test Status          This identifies whether a requirement Not Tested/Value Added - Only mandatory requirements are tested by FSIO.
                                       has been tested, scheduled for testing, Not Scheduled - These requirements have not yet been scheduled for testing.
                                       or deleted if no longer applicable.     Tested - Tested in the full 2003 test and/or in a 2004/2005 or 2005/2006
                                                                               incremental test.
                                                                               Deleted - Requirement was deleted as part of the 2008 incremental test errata.
                                                                               Not Tested - These requirements were not tested because of a reason given in
                                                                               the notes section.



Column G          Process              The category Identifies the process       Those processes listed in the 2001 and 2006 Core Requirements documents.
                                       group that a given requirement
                                       belongs to (e.g. in the payments
                                       management function requirements
                                       are currently grouped by "processes"
                                       that support payee information
                                       maintenance, accounts payable,
                                       invoicing, disbursing, and payment
                                       follow-up).
Column H          Test Notes           This column is used to disclose           Blank - No further information provided
                                       information about the provisional         Notes unique to each applicable requirement
                                       testing that may have been done on a
                                       given requirement or to explain the
                                       need for a requirement clarification or
                                       addendum, when warranted.
Column I          Requirement Short    The title given to a given requirement.   Blank - No short name assigned
                  Name                 Prior to 2006 requirements did not        Short name unique to each applicable requirement
                                       have titles.




Printed on 5/20/2010                                        93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                            Page 2 of 79
Financial Systems Integration Office                                                                    Requirements Tested Matrix
                                                                                                      Core Requirements & Test Status

 Requirement                                                                                                                                                                                                      Requirement Short
    Year               Req. No.                                 Description                                       Status        Test Cycle     Test Status         Process               Test Notes                     Name
                                  Classify accounting transactions by: Treasury Account
                                  Symbol/Treasury Account Fund Symbol (TAS/TAFS), Internal fund
                                  code (see CFA-04 below), Budget fiscal year, Accounting quarter and
                                  month, Program, Organization, Project, Activity, Cost center, Object                                                       Accounting
                                  class, Budget function (and sub function code), and Remaining U.S.                                                         Classification   Tested all aspects except for
           2001 CFA-01            SGL attributes not specified above.                                          Mandatory      Full 2003       Tested         Management       Activity.
                                                                                                                                                             Accounting
                                  Define additional accounting classification elements. Classify and                                                         Classification
           2001 CFA-02            report accounting transactions by each type of element.                      Mandatory      Full 2003       Tested         Management

                                  Achieve consistency in budget and accounting classifications and
                                  synchronization between those classifications and the organizational
                                  structure. Consistency will include maintaining data relationships
                                  between: Budget formulation classifications (budget function and sub
                                  function classification codes, per OMB Circular No. A-11), budget
                                  execution and accounting classifications (e.g., TAS/TAFS, internal                                                         Accounting
                                  fund, program, project, activity), and the agency’s organizational                                                         Classification
           2001 CFA-03            structure.                                                                   Mandatory      Full 2003       Tested         Management

                                  Provide a fund structure that identifies TAS/TAFS established by OMB
                                  and Treasury. Accommodate additional detail below the TAS level,                                                           Accounting       A large number of the test
                                  such as an internal fund code to support fiscal year accounting, and                                                       Classification   scripts involve transactions that
           2001 CFA-04            appropriation sub-accounts used for reporting to Treasury.                   Mandatory      Full 2003       Tested         Management       support this requirement.
                                  Differentiate among the type of budgeting, accounting, and reporting
                                  treatments to be used based on various TAS/TAFS characteristics. At
                                  a minimum, the following fund characteristics must be supported in
                                  accordance with Treasury and OMB reporting and budget execution
                                  requirements: Fund type, (e.g., general fund, deposit fund, trust fund,
                                  special fund, revolving fund, receipt account); Funding source (e.g.,
                                  borrowing authority, contract authority, direct appropriation, spending
                                  authority from offsetting collections); and Budget status (e.g., on                                                        Accounting
                                  budget, off budget, or financing account); (d) TAS/TAFS status (e.g.,                                                      Classification
           2001 CFA-05            annual, multiyear, and no-year).                                             Mandatory      Full 2003       Tested         Management
                                  Provide a program structure with sufficient levels of detail to allow
                                  reporting for all categories on which budgetary decisions are made,
                                  whether legally binding, as in appropriation limitations, or in the nature                                                 Accounting
                                  of policy guidance, as in Presidential pass-backs and congressional                                                        Classification
           2001 CFA-06            markup tables.                                                               Mandatory      Full 2003       Tested         Management
                                  Establish an organizational structure based on responsibility
                                  segments, such as bureaus, divisions, and branches. Provide for the                                                        Accounting
                                  ability to tie responsible organizational units to programs, projects and                                                  Classification
           2001 CFA-07            activities.                                                                  Mandatory      Full 2003       Tested         Management
                                  Support the management of multiple Agency Location Codes (ALC)
                                  and associate the appropriate ALC with each transaction involving
                                  Fund balance with Treasury to facilitate external reporting (e.g.,                                                         Accounting
                                  Financial Management Service (FMS)-224) and reconciliation with                                                            Classification
           2001 CFA-08            Treasury.                                                                    Mandatory      Full 2003       Tested         Management
                                  Provide a project structure that is independent of the other accounting                                                    Accounting
                                  classification elements to allow multiple organizations, programs, and                                                     Classification
           2001 CFA-09            funding sources to be associated with a project.                             Mandatory      Full 2003       Tested         Management

                                  Provide an object class structure consistent with the standard object                                                      Accounting       All BOC values created by the
                                  class codes contained in OMB Circular No. A-11. Provide flexibility to                                                     Classification   SE4 test case support this
           2001 CFA-10            accommodate additional levels (lower) in the object class structure.   Mandatory            Full 2003       Tested         Management       requirement.
                                  Process additions, changes and deletions to elements of the
                                  accounting classification design, and related valid domain values                                                          Accounting       A full range of instances were
                                  within accounting classifications, without extensive program or system                                                     Classification   tested but possibilities are too
           2001 CFA-11            changes (e.g., through on-line table updates).                         Mandatory            Full 2003       Tested         Management       numerous for all to be tested.



Printed on 5/20/2010                                                                                    93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                              Page 3 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                                       Requirement Short
    Year               Req. No.                                   Description                                    Status        Test Cycle     Test Status         Process                  Test Notes                    Name
                                  Allow the user to enter, edit, and store accounting classification table                                                  Accounting
                                  changes so that the changes automatically become effective at any                                                         Classification
           2001 CFA-12            future date determined by the user.                                        Mandatory       Full 2003       Tested         Management
                                  Reject or suspend interfaced transactions that contain accounting                                                         Accounting
                                  classification elements or domain values that have been deactivated                                                       Classification
           2001 CFA-13            or discontinued.                                                           Mandatory       Full 2003       Tested         Management
                                  Provide a revenue source code structure to identify and classify types
                                  of revenue and receipts as defined by the user. For example,                                               Not            Accounting
                                  categories could be rental income, sales by product type, income by                    Not                 Tested/Value   Classification
           2001 CFA-14            type of service performed and others.                                      Value Added Applicable          Added          Management
                                  Validate all transactions involving Treasury and other disbursing                                          Not            Accounting
                                  centers for valid combinations of ALC and TAS/TAFS, as defined by                      Not                 Tested/Value   Classification
           2001 CFA-15            the user.                                                                  Value Added Applicable          Added          Management

                                  Derive the full accounting classifications from abbreviated user input
                                  so that user input is minimized, data entry is made easier, and errors
                                  are controlled and reduced. Examples of methods include entering                                           Not          Accounting
                                  "shorthand codes," using a keyboard function to look up additional                     Not                 Tested/Value Classification
           2001 CFA-16            elements, "clicking" on a "pop-up menu," and scanning a bar code.          Value Added Applicable          Added        Management

                                  Provide for an automated method to reclassify accounting data at the
                                  document level when a restructuring of the existing values pertaining                                      Not          Accounting
                                  to the mandatory accounting classification elements is needed.                             Not             Tested/Value Classification
           2001 CFA-17            Maintain an audit trail from the original postings to the final posting. Value Added       Applicable      Added        Management
                                  Use standard transactions when recording accounting events. The                                                                               U.S. SGL posting models were
                                  standard transactions must specify the postings to the general ledger                                                                         used to support the GL entries
                                  accounts, and update document balances and any related tables (e.g.,                                                                          and are used throughout the test
           2001 CFB-01            available funding).                                                      Mandatory         Full 2003       Tested         Transaction Control cases.
                                  Allow the user to include proprietary, budgetary and memorandum
           2001 CFB-02            accounts in the definition of a standard transaction.                    Mandatory         Full 2003       Tested         Transaction Control
                                                                                                                                                                                U.S. SGL posting models were
                                                                                                                                                                                used to support the GL entries
                                                                                                                                                                                and are used throughout the test
           2001 CFB-03            Record transactions consistent with U.S. SGL posting rules.                Mandatory       Full 2003       Tested         Transaction Control cases.
                                  Reject a transaction or provide a warning message when attempting to
                                  post a transaction that would cause general ledger debits and credits
                                  to be out-of-balance at a level below the TAS/TAFS (e.g., internal
           2001 CFB-04            fund, organization level).                                                 Mandatory       Full 2003       Tested         Transaction Control
                                  Allow users to define and maintain standard rules that control general
                                  ledger account postings for all accounting events. The process of
                                  defining posting rules can be accomplished in a variety of ways,
                                  including (but not limited to) using: transaction codes, screen
           2001 CFB-05            ―templates,‖ derivation rules, and others.                                 Mandatory       Full 2003       Tested         Transaction Control
                                  Enable users to selectively require, omit, or set a default value for
                                  individual accounting classification elements. For example, a budget
                                  object class code value is not necessarily needed when recording
           2001 CFB-06            depreciation expense.                                                      Mandatory       Full 2003       Tested         Transaction Control
                                  Update all applicable general ledger account balances (i.e., budgetary,
                                  proprietary and memorandum accounts) based on a single input
           2001 CFB-07            transaction.                                                               Mandatory       Full 2003       Tested         Transaction Control
                                  Define, generate and post compound general ledger debit and credit
                                  entries for a single transaction. Accommodate at least 10 debit and
                                  credit pairs or 20 accounts when defining and processing a single
           2001 CFB-08            transaction.                                                               Mandatory       Full 2003       Tested         Transaction Control




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                Page 4 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                                     Requirement Short
    Year               Req. No.                                 Description                                      Status       Test Cycle     Test Status         Process                  Test Notes                   Name

                                  Allow users to define and process system-generated transactions,
                                  such as automated accruals (e.g., payroll accrual entries), pre-closing
                                  and closing entries, cost assignment transactions, recurring payments,
                                  and transactions that generate other transactions in those cases                                                                             Tested for instances except for
           2001 CFB-09            where a single transaction is not sufficient.                           Mandatory         Full 2003       Tested         Transaction Control payroll accruals.

                                  Automatically liquidate, partially or in full, the balance of open
                                  documents by line item. This capability will be used in the liquidation
                                  of various documents such as commitments, obligations, undelivered
                                  orders, payables, receivables, and advances, upon the processing of
                                  subsequent related transactions (e.g., liquidate an obligation upon
           2001 CFB-10            entry of the related receiving report).                                     Mandatory     Full 2003       Tested         Transaction Control
                                  Automatically determine and record the amount of upward or
                                  downward adjustments to existing obligations upon liquidation,
                                  cancellation or other adjustment. This is to include transactions
                                  entered directly to the Core system and those received from interfaced
           2001 CFB-11            modules or systems.                                                         Mandatory     Full 2003       Tested         Transaction Control
                                  When adjustments are made to existing obligations or previously
                                  recorded expenditures, automatically distinguish between upward and
                                  downward adjustments to unexpired and expired budget authority, and
                                  generate the appropriate general ledger postings, without user
           2001 CFB-12            intervention.                                                               Mandatory     Full 2003       Tested         Transaction Control
                                  Relative to expired funds, provide an overrideable error message
                                  when attempting to post (previously unrecorded) obligations to current
                                  year general ledger obligation accounts (e.g., U.S. SGL accounts
           2001 CFB-13            4801, 4802).                                                                Mandatory     Full 2003       Tested         Transaction Control
                                  When recording adjustments to prior year obligations (including
                                  previously expended authority), automatically classify upward and
                                  downward adjustments as paid and or unpaid according to the status
                                  of the related obligation or expenditure. This is to include transactions
                                  entered directly to the Core system and those received from interfaced
           2001 CFB-14            modules or systems.                                                         Mandatory     Full 2003       Tested         Transaction Control
                                  Control the correction and reprocessing of all erroneous transactions
                                  through the use of error/suspense files. Erroneous transactions must
                                  be maintained until either corrected and posted or deleted at the
           2001 CFB-15            specific request of a user.                                                 Mandatory     Full 2003       Tested         Transaction Control
                                  Provide immediate, on-line notification to the user of erroneous
                                  transactions. Advise reason for error and provide the ability to enter
           2001 CFB-16            corrections on-line.                                                        Mandatory     Full 2003       Tested         Transaction Control
                                  Provide controls to prevent the creation of duplicate transactions. For                                                                      Tested for duplicate
                                  example, prevent the use of the same unique transaction identification                                                                       transactions, not duplicate
           2001 CFB-17            number (e.g., document number).                                             Mandatory     Full 2003       Tested         Transaction Control document numbers.
                                  Provide a warning message when the user attempts to input an
                                  external vendor invoice number that has already been recorded for the
           2001 CFB-18            related vendor.                                                             Mandatory     Full 2003       Tested         Transaction Control

                                  Validate the fields for all accounting classification elements required to
                                  process the transaction prior to posting. For example, fields pertaining
           2001 CFB-19            to TAS/TAFS, object class, vendor code, organization, and others.          Mandatory      Full 2003       Tested         Transaction Control
                                  Enter, edit, and store transactions in the current accounting period for
           2001 CFB-20            automatic processing in a future accounting period.                        Mandatory      Full 2003       Tested         Transaction Control

                                  Put transactions in a hold status (saved, but not processed or posted)
                                  within the core system (i.e., importing transactions from a spreadsheet
                                  or database application is not acceptable). Allow users to select held
           2001 CFB-21            transactions and continue processing at a later date.                   Mandatory         Full 2003       Tested         Transaction Control




Printed on 5/20/2010                                                                                  93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                               Page 5 of 79
Financial Systems Integration Office                                                                  Requirements Tested Matrix
                                                                                                    Core Requirements & Test Status

 Requirement                                                                                                                                                                                                          Requirement Short
    Year               Req. No.                                 Description                                     Status        Test Cycle     Test Status         Process                    Test Notes                      Name

                                  Capture the six-digit trading partner code (as specified by Treasury)
                                  when processing all transactions that directly involve another Federal
           2001 CFB-22            entity (i.e., both parties to a transaction are Federal entities).         Mandatory      Full 2003       Tested         Transaction Control
                                  For all transactions, capture transaction dates (effective date of the
                                  transaction) and posting dates (date transaction posted to general
           2001 CFB-23            ledger).                                                                   Mandatory      Full 2003       Tested         Transaction Control
                                  Automatically determine the posting date from the system date for all
                                  transactions. Automatically associate a default accounting period for
           2001 CFB-24            each transaction, but allow user to override.                              Mandatory      Full 2003       Tested         Transaction Control
                                  Automatically reverse entries by the following parameters: transaction
                                  or document type, date range, schedule numbers, transaction                                                                                  Multiple instances tested but
                                  identification number (i.e., document number) range, and trading                                                                             possibilities are too numerous
           2001 CFB-25            partner.                                                                   Mandatory      Full 2003       Tested         Transaction Control for all to be tested
                                  Post to the current and prior months concurrently until the prior month
           2001 CFB-26            closing is complete.                                                       Mandatory      Full 2003       Tested         Transaction Control
                                  Provide and maintain on-line queries and reports on balances
                                  separately for the current and prior months. At a minimum, balances
                                  must be maintained on-line for both the current and prior months until
           2001 CFB-27            the prior month closing is complete.                                       Mandatory      Full 2003       Tested         Transaction Control
                                  Post to the current fiscal year and prior fiscal year concurrently until
           2001 CFB-28            prior yearend closing is complete.                                         Mandatory      Full 2003       Tested         Transaction Control
                                  Provide and maintain on-line queries and reports on balances
                                  separately for the current and prior fiscal years. At a minimum,
                                  balances must be maintained on-line for both the current and prior
           2001 CFB-29            fiscal years until the prior fiscal year closing is complete.              Mandatory      Full 2003       Tested         Transaction Control
                                  Perform validation checks for use of certain general ledger accounts                                      Not
                                  associated with specific Record Type 7 authority (e.g., Imprest fund,                  Not                Tested/Value
           2001 CFB-30            borrowing authority) prior to posting a transaction.                       Value Added Applicable         Added          Transaction Control
                                  Have all functions of the system, including budgeting, spending,                                          Not
                                  accounts payable, and accounts receivable, process and track                           Not                Tested/Value
           2001 CFB-31            transactions in both foreign currency and U.S. dollars.                    Value Added Applicable         Added          Transaction Control
                                                                                                                                            Not
                                  Calculate progress payments to foreign vendors based on current                        Not                Tested/Value
           2001 CFB-32            exchange rates.                                                            Value Added Applicable         Added          Transaction Control

                                  Provide audit trails to trace transactions from their initial source
                                  through all stages of related system processing. The initial source may
                                  be source documents transactions originating from other systems (e.g.
           2001 CFB-33            feeder systems) or internal system-generated transactions.                 Mandatory      Full 2003       Tested         Transaction Control
                                  Select items for review based on user-defined criteria by type of
                                  transaction (e.g. by obligation transactions vendor date range).
                                  Examples of reasons to select items are payment certification and
           2001 CFB-34            financial statement audits.                                                Mandatory      Full 2003       Tested         Transaction Control
                                  Provide audit trails that identify document input change approval and
           2001 CFB-35            deletions by user.                                                         Mandatory      Full 2003       Tested         Transaction Control
                                  Use the agency’s accounting classification elements to identify and                                                                            Used accounting classification
                                  establish unique cost objects (for the purpose of cost and revenue                                                                             structure to establish
                                  capture, accumulation and reporting). Cost objects might include:                                                                              organizational units, projects,
                                  organizational units, programs, projects, activities, targeted outputs,                                                  Cost Setup and        activities and GPRA goals as
           2001 CMA-01            specific contracts, specific customers, work orders, etc.                  Mandatory      Full 2003       Tested         Accumulation          cost objects.
                                  Allocate and distribute the full cost and revenue of cost objects as
                                  defined in SFFAS No. 4. Full cost includes: support costs provided by
                                  other responsibility segments, both internal and external; identifiable                                                                        All charges to 6000 accounts
                                  support costs provided by other Government agencies such as                                                                                    are allocated in the test in
                                  pension and other retirement benefits; unfunded costs such as                                                                                  determining full-cost, regardless
                                  accrued annual leave that accrue in the current reporting period;                                                        Cost Setup and        of funding (internal, external, or
           2001 CMA-02            depreciation expense; and, amortization costs.                             Mandatory      Full 2003       Tested         Accumulation          unfunded).


Printed on 5/20/2010                                                                                  93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                    Page 6 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                                         Requirement Short
    Year               Req. No.                                 Description                                     Status        Test Cycle     Test Status         Process                    Test Notes                     Name
                                                                                                                                                                               Lease agreement with GSA
                                                                                                                                                                               represents the full cost of an
                                  Allocate and distribute the full cost of goods and services provided by                                                  Cost Setup and      inter entity service and is
           2001 CMA-03            one Federal entity to another.                                            Mandatory       Full 2003       Tested         Accumulation        allocated with other costs.
                                                                                                                                                                               Cost tracking is done
                                                                                                                                                                               semiannually in lieu of monthly
                                  Track current cost information against prior month and prior-year-to                                                                         to reduce testing burden.
                                  date cost data for selected cost objects, and track progress against                                                     Cost Setup and      Tracking against pre-determined
           2001 CMA-04            pre-determined plans.                                                     Mandatory       Full 2003       Tested         Accumulation        plans is not tested.
                                                                                                                                                                               Cost incurred against revolving
                                                                                                                                                                               and appropriated funds are
                                  Identify all costs incurred by the agency in support of activities of                                                                        allocated. Costs incurred
                                  revolving funds, trust funds, or commercial functions, including the                                                                         against other funds are not
                                  applicable portions of any related salaries and expense accounts                                                         Cost Setup and      tested, but would not differ
           2001 CMA-05            identified with those activities.                                         Mandatory       Full 2003       Tested         Accumulation        materially.
                                  Accumulate non-financial data relating to cost objects such as output                                                    Cost Setup and      Test verifies the accumulation of
           2001 CMA-06            units to allow the calculation of both total and unit costs.              Mandatory       Full 2003       Tested         Accumulation        unit data.
                                                                                                                                                                               Tested by posting of
                                  Transfer (and trace) cost data directly to and from other cost                                                           Cost Setup and      administrative expenses through
           2001 CMA-07            systems/applications that produce or allocate cost information.           Mandatory       Full 2003       Tested         Accumulation        API facility.
                                                                                                                                                                               Tests the ability to accumulate
                                                                                                                                                                               and retrieve data necessary for
                                  Calculate prices, fees, and user charges for reimbursable agreements                                                                         calculation of prices and fees.
                                  and other purposes using full cost, consistent with the guidance of                                                      Cost Setup and      Does not test automated
           2001 CMA-08            OMB Circular No. A-25 User Charges.                                       Mandatory       Full 2003       Tested         Accumulation        calculation of prices.
                                  Use the accrual basis of accounting when recognizing costs and
                                  revenue. Recognize costs in the period of time when the events                                                                               Tests recognition of revenue,
                                  occurred regardless of when ordered received or paid for. Recognize                                                                          and depreciation and payroll
           2001 CMB-01            revenue when earned.                                                      Mandatory       Full 2003       Tested         Cost Recognition    cost.
                                  Associate with the appropriate cost objects the reductions of balances
                                  such as inventories prepaid expenses and advance payments as the
           2001 CMB-02            balances are used or liquidated.                                          Mandatory       Full 2003       Tested         Cost Recognition    Tests advance reduction only.
                                  Identify and record costs incurred by each cost object including input                                                                       Tests the capture of cost object
                                  of costs from feeder systems such as inventory travel property                                                                               data from simulated feeder
           2001 CMB-03            management (depreciation) or payroll.                                     Mandatory       Full 2003       Tested         Cost Recognition    system entries.
                                                                                                                                                                               Tests allocations based on
                                                                                                                                                                               criteria (percentages and
                                                                                                                                                                               dollars) provided by the user.
                                  Assign indirect costs on a cause-and-effect basis or allocate costs                                                                          The criteria were derived using
                                  through any reasonable and consistent basis such as a percentage of                                                                          simulated allocation basis
                                  total cost incurred direct labor hours used square footage or metered                                                                        (cause-and-effect or reasonable
           2001 CMB-04            usage.                                                                Mandatory           Full 2003       Tested         Cost Recognition    & consistent).
                                                                                                                                                                               Tested one possible user
                                                                                                                                                                               defined distribution. Not all
                                  Perform multi-layer overhead distributions that are user-defined (at                                                                         possible user needs can be
                                  least 3 levels of distribution) using multiple rates fixed amount and                                                                        anticipated or tested. Three
           2001 CMB-05            other appropriate allocation methods.                                     Mandatory       Full 2003       Tested         Cost Recognition    levels of distribution are tested.

                                                                                                                                                                               Production of income statement
                                                                                                                                                                               at the cost object level is tested,
                                                                                                                                                                               not distribution, and not status of
                                                                                                                                                                               funds. Reword in next version
                                  Distribute information (such as income statements and status of funds                                                                        of requirements. What does
           2001 CMC-01            reports) on costs and revenue associated with cost objects.           Mandatory           Full 2003       Tested         Cost Distribution   "distribute" mean? Email?




Printed on 5/20/2010                                                                                  93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                   Page 7 of 79
Financial Systems Integration Office                                                                    Requirements Tested Matrix
                                                                                                      Core Requirements & Test Status

 Requirement                                                                                                                                                                                                         Requirement Short
    Year               Req. No.                                  Description                                      Status        Test Cycle     Test Status         Process                    Test Notes                   Name
                                  Provide consistent information on financial, budget, and program
                                  matters in different reports. For example, bills generated for                                                                                   Requirement involved testing
                                  customers in the receivables system should match customer status                                                                                 data outside the Core system
                                  reports generated by the cost management system for the same                                                                                     where the noted interface was
           2001 CMC-02            periods.                                                                   Mandatory        Full 2003       Not Tested     Cost Distribution     not in scope for the 2003 test.
                                  Use historical information to conduct variance and time-series
                                  analyses, and to demonstrate the fairness and appropriateness of                                                                                 Test compares two semi-annual
           2001 CMC-03            rates and charges that are based on actual historical costs.               Mandatory        Full 2003       Tested         Cost Distribution     periods in time series.

                                                                                                                                                                                 Costs are originally allocated
                                                                                                                                                                                 using one cost model, and later
                                                                                                                                                                                 reversed and reallocated using a
                                  Distribute costs to other cost objects regardless of how they were                                                                             new cost model irrespective of
           2001 CMC-04            originally assigned.                                                       Mandatory        Full 2003       Tested         Cost Distribution   the first allocation.
                                                                                                                                                                                 Only one example of many
                                  Provide an audit trail that traces a transaction from its origin to the final                                                                  possible cost objects tracking is
           2001 CMC-05            cost object(s).                                                               Mandatory     Full 2003       Tested         Cost Distribution   tested.
                                                                                                                                                                                 Revolving fund tested is not a
                                                                                                                                                                                 working capital fund, but
                                  Use cost management in revolving funds, including working capital                                                          Working Capital and allocation would not be
           2001 CMD-01            programs.                                                                  Mandatory        Full 2003       Tested         Revolving Fund      materially different if it were.
                                                                                                                                                                                 Revolving fund tested is not a
                                                                                                                                                                                 working capital fund, but
                                  Allocate working capital and revolving fund costs across organization                                                      Working Capital and allocation would not be
           2001 CMD-02            and program lines and generate appropriate journal entries.                Mandatory        Full 2003       Tested         Revolving Fund      materially different if it were.
                                  Create and track the funding associated with cost objects (e.g.,
                                  contracts, work-orders, projects, reimbursable agreements) and
                                  provide funding status on fiscal year-to-date and project inception-to-                                                    Working Capital and
           2001 CMD-03            date bases.                                                                Mandatory        Full 2003       Tested         Revolving Fund
                                  Support the aggregation of project cost and funding information to a
                                  higher level, for example linking the costs of a set of related projects                                                   Working Capital and
           2001 CMD-04            for a particular customer on one report.                                   Mandatory        Full 2003       Tested         Revolving Fund
                                  Verify funds availability for orders placed against a specific contract,
                                  work-order or agreement for a particular customer of the revolving                                                         Working Capital and
           2001 CMD-05            fund operation.                                                            Mandatory        Full 2003       Tested         Revolving Fund

                                  Support funding of revolving fund contracts, work-orders, and projects                                                     Working Capital and
           2001 CMD-06            through the use of advances, prepayments or reimbursements.            Mandatory            Full 2003       Tested         Revolving Fund
                                  Establish and maintain operating/financial plans at or below the level
           2001 FMA-01            of funds control.                                                      Mandatory            Full 2003       Tested         Budget Preparation
                                  Establish operating/financial plans by month and quarter at any level
           2001 FMA-02            of the organizational structure specified by the user.                 Mandatory            Full 2003       Tested         Budget Preparation

           2001 FMA-03            Track and report on the use of funds against operating/financial plans. Mandatory   Full 2003               Tested         Budget Preparation
                                  Prepare operating/financial plans based on multiple measures,                                               Not
                                  including obligations, costs, labor hours, and full time equivalents                Not                     Tested/Value
           2001 FMA-04            (FTEs).                                                                 Value Added Applicable              Added          Budget Preparation
                                                                                                                                              Not
                                                                                                                         Not                  Tested/Value
           2001 FMA-05            Modify/revise an existing operating/financial plan by line item.           Value Added Applicable           Added          Budget Preparation
                                                                                                                                              Not
                                                                                                                         Not                  Tested/Value
           2001 FMA-06            Maintain original and modified operating/financial plans.                  Value Added Applicable           Added          Budget Preparation
                                                                                                                                              Not
                                  Identify legal and administrative limitations on funds in                              Not                  Tested/Value
           2001 FMA-07            operating/financial plans.                                                 Value Added Applicable           Added          Budget Preparation




Printed on 5/20/2010                                                                                    93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                 Page 8 of 79
Financial Systems Integration Office                                                                       Requirements Tested Matrix
                                                                                                         Core Requirements & Test Status

 Requirement                                                                                                                                                                                                            Requirement Short
    Year               Req. No.                                  Description                                        Status        Test Cycle     Test Status      Process                      Test Notes                     Name
                                                                                                                                                Not
                                  Generate allotments and sub-allotments (including limitations based                      Not                  Tested/Value
           2001 FMA-08            on approved changes to operating/financial plans).                           Value Added Applicable           Added        Budget Preparation
                                                                                                                                                Not
                                                                                                                           Not                  Tested/Value
           2001 FMA-09            Enter operating/financial plans for future operating periods.                Value Added Applicable           Added        Budget Preparation
                                                                                                                                                Not
                                  Roll future plans into active budget plans based on future date or                            Not             Tested/Value
           2001 FMA-10            retrieval function.                                                       Value Added         Applicable      Added        Budget Preparation
                                  Report information for all categories on which budgetary decisions are
                                  made, whether legally binding (e.g., appropriation limitations) or in the
                                  nature of policy guidance and decision making (e.g., Presidential/OMB                                         Not
                                  pass backs, congressional markup documents, or internal agency                                Not             Tested/Value
           2001 FMB-01            decisions).                                                               Value Added         Applicable      Added          Budget Formulation
                                                                                                                                                Not
                                  Populate the budget formulation system with prior year budgeted and                           Not             Tested/Value
           2001 FMB-02            actual amounts.                                                           Value Added         Applicable      Added          Budget Formulation
                                  Perform projections of obligations, income, and expenditures at any                                           Not
                                  level of the organizational structure (e.g., projecting obligations based                     Not             Tested/Value
           2001 FMB-03            on prior periods and applying these to a future period).                  Value Added         Applicable      Added          Budget Formulation
                                                                                                                                                Not
                                  Adjust projection rates (e.g., 90 percent, 100 percent, and 110                          Not                  Tested/Value
           2001 FMB-04            percent) and exclude specified obligations from projection.                  Value Added Applicable           Added          Budget Formulation
                                                                                                                                                Not
                                  Create, store, and modify payroll forecasts, including anticipated                       Not                  Tested/Value
           2001 FMB-05            monthly compensation and benefits, at the individual employee level.         Value Added Applicable           Added          Budget Formulation
                                                                                                                                                Not
                                                                                                                           Not                  Tested/Value
           2001 FMB-06            Incorporate overhead distribution as part of budget formulation.             Value Added Applicable           Added          Budget Formulation
                                                                                                                                                Not
                                                                                                                           Not                  Tested/Value
           2001 FMB-07            Develop budgets on line and via upload from spreadsheets.                    Value Added Applicable           Added          Budget Formulation
                                  Prepare budget submission guidance, budget narratives, and budget                                             Not
                                  briefing packages on line and via upload from desktop software                           Not                  Tested/Value
           2001 FMB-08            applications.                                                                Value Added Applicable           Added          Budget Formulation
                                                                                                                                                Not
                                  Distribute budget submission guidance to subordinate organizations                       Not                  Tested/Value
           2001 FMB-09            electronically.                                                              Value Added Applicable           Added          Budget Formulation
                                                                                                                                                Not
                                                                                                                           Not                  Tested/Value
           2001 FMB-10            Establish and maintain multiple budget cycles.                               Value Added Applicable           Added          Budget Formulation
                                                                                                                                                Not
                                  Tie budget formulation to the agency’s stated goals and objectives                       Not                  Tested/Value
           2001 FMB-11            required by GPRA.                                                            Value Added Applicable           Added          Budget Formulation
                                  Record funding and related budget execution documents (e.g.,
           2001 FMC-01            warrants, apportionments, allotments) and limitations.                       Mandatory        Full 2003       Tested         Funds Allocation
                                  Control the use of funds against limitations consistent with
                                  appropriation and authorization language (including congressional
                                  intent and continuing resolutions) and administrative limitations
           2001 FMC-02            established by agency management.                                            Mandatory        Full 2003       Tested         Funds Allocation
                                  Distribute, track, and control, funds at various levels, based on the
           2001 FMC-03            elements of the accounting classification and project structure.             Mandatory        Full 2003       Tested         Funds Allocation

                                                                                                                                                                                    Only tested for one distribution
                                                                                                                                                                                    level (Branch). Exceeding other
                                  Verify that funds distributed do not exceed the amount of funds                                                                                   levels - Bureau, Directorate, and
           2001 FMC-04            available for allotment or sub-allotment at each distribution level.         Mandatory        Full 2003       Tested         Funds Allocation     Division - are not tested.




Printed on 5/20/2010                                                                                      93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                  Page 9 of 79
Financial Systems Integration Office                                                                  Requirements Tested Matrix
                                                                                                    Core Requirements & Test Status

 Requirement                                                                                                                                                                                                       Requirement Short
    Year               Req. No.                                  Description                                     Status        Test Cycle     Test Status        Process                  Test Notes                     Name
                                  Support Public Law (P. L.) 101-510 (M-year legislation) by assuring
                                  that amounts paid out of current year funds to cover obligations made
                                  against a closed account do not exceed 1 percent of the current year
           2001 FMC-05            appropriation.                                                            Mandatory        Full 2003       Tested         Funds Allocation
                                  Record and control all types of budgetary authority, including
                                  appropriations, spending authority from offsetting collections,
                                  borrowing authority and contract authority. Identify the type of
           2001 FMC-06            authority and track obligations by funding source                         Mandatory        Full 2003       Tested         Funds Allocation
                                  Record the expiration and cancellation of appropriation authority in
           2001 FMC-07            accordance with OMB Circular No. A-34 and the U.S. SGL.                   Mandatory        Full 2003       Tested         Funds Allocation
                                  Account for spending transactions at a lower level in the accounting
           2001 FMC-08            classification than they are budgeted.                                    Mandatory        Full 2003       Tested         Funds Allocation
                                                                                                                                                                               Funds are recorded and spent at
                                                                                                                                                                               the BOC level, but are budgeted
                                                                                                                                                                               at higher levels. For FY 2003
                                                                                                                                                                               only, funds are spent below the
                                  Account for budgetary resources at a lower level in the accounting                                                                           Bureau level, but controlled at
           2001 FMC-09            classification than they are budgeted and controlled.                     Mandatory        Full 2003       Tested         Funds Allocation   the Bureau level.

                                                                                                                                                                               The test requires that vendors
                                                                                                                                                                               produce an SF-132 in the format
                                                                                                                                                                               currently in use by OMB. The
                                                                                                                                                                               form can be produced manually,
                                                                                                                                                                               if necessary, although automatic
                                                                                                                                                                               generation is preferred.
                                  Prepare and electronically transmit SF-132s (Apportionment and                                                                               "Electronic transmission" can
                                  Reapportionment Schedules and associated financial information) to                                                                           mean E-mailing the
           2001 FMC-10            OMB. Store prepared requests as submitted for future use.                 Mandatory        Full 2003       Tested         Funds Allocation   spreadsheet.
                                                                                                                                             Not
                                                                                                                        Not                  Tested/Value
           2001 FMC-11            Generate budgetary data in format required by OMB's MAX system.           Value Added Applicable           Added          Funds Allocation
                                  Automatically prepare the formal allotment and sub-allotment                                               Not
                                  documents and electronically distribute them to subordinate                           Not                  Tested/Value
           2001 FMC-12            organizations.                                                            Value Added Applicable           Added          Funds Allocation
                                                                                                                                             Not
                                  Create continuing resolution funding levels based on a percentage of                  Not                  Tested/Value
           2001 FMC-13            prior-year funding.                                                       Value Added Applicable           Added          Funds Allocation

           2001 FMD-01            Record budget authority at multiple levels of distribution (at least five). Mandatory      Full 2003       Tested         Budget Execution

                                                                                                                                                                               Rescissions, supplementals,
                                                                                                                                                                               transfers, reprogrammings,
                                                                                                                                                                               limitations, and changes to CRs
                                  Track and record all changes to budget authority - including                                                                                 are all recorded and tracked.
                                  rescissions, supplementals, transfers between TAS/TAFS,                                                                                      However, only the supplemental
                                  reprogramming, limitations and changes to continuing resolutions prior                                                                       is distributed to five levels-the
                                  to appropriation enactment - at multiple levels of distribution (at least                                                                    other changes are distributed to
           2001 FMD-02            five).                                                                    Mandatory        Full 2003       Tested         Budget Execution   fewer than five levels.

                                  Track actual amounts and verify commitments and obligations against
           2001 FMD-03            the budget as revised, consistent with each budget distribution level. Mandatory           Full 2003       Tested         Budget Execution
                                  Modify funding distribution (including apportionments and allotments)
           2001 FMD-04            at multiple organizational levels (at least five).                     Mandatory           Full 2003       Tested         Budget Execution
           2001 FMD-05            Manage and control prior-year funds in the current year.               Mandatory           Full 2003       Tested         Budget Execution




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                               Page 10 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                                       Requirement Short
    Year               Req. No.                                  Description                                     Status        Test Cycle     Test Status        Process                  Test Notes                     Name
                                                                                                                                                                               Not all document types are
                                                                                                                                                                               tested. The test tests tolerances
                                                                                                                                                                               between obligations and the
                                                                                                                                                                               related invoice, between
                                                                                                                                                                               expenditures and the related
                                                                                                                                                                               invoice, and between obligations
                                                                                                                                                                               and the related commitment.
                                                                                                                                                                               Tolerances for relationships
                                  Establish and maintain user-defined variance tolerances by document                                                                          between other document types
           2001 FMD-06            type, percentage, and a ―not-to-exceed‖ dollar threshold.                  Mandatory       Full 2003       Tested         Budget Execution   are not tested.
                                  Automatically withdraw (or cancel) uncommitted and unobligated
                                  allotments and sub-allotments for all or selected TAS/TAFS at the end
           2001 FMD-07            of a specific fiscal period.                                               Mandatory       Full 2003       Tested         Budget Execution
                                  Automatically withdraw (or cancel) uncommitted and unobligated
                                  allotments and sub-allotments for selected organizations at the end of
           2001 FMD-08            a specific fiscal period.                                                  Mandatory       Full 2003       Tested         Budget Execution
                                  Distribute the annual budget in accordance with the latest SF-132
           2001 FMD-09            Apportionment and Reapportionment Schedule approved by OMB.                Mandatory       Full 2003       Tested         Budget Execution
                                  Request approval for reprogramming and request additional funds
                                  outside the periodic budget review process. Allow such requests to be                                      Not
                                  submitted reviewed revised and approved. Approval would update                         Not                 Tested/Value
           2001 FMD-10            current operating budgets.                                                 Value Added Applicable          Added        Budget Execution
                                                                                                                                                                               Tested establishment of funds
                                                                                                                                                                               control at all ACEs except object
                                  Establish and modify multiple levels of funds control using elements of                                                                      class. Modified funds control
                                  defined accounting classifications, including object class, program,                                                                         only at the organization level.
           2001 FME-01            organization, project, and fund.                                        Mandatory          Full 2003       Tested         Funds Control      Other levels not tested.
                                  Establish and modify the system’s response (either reject transaction                                                                        Tested for obligations only - not
                                  or provide warning) to the failure of funds availability edits for each                                                                      tested for other transaction
           2001 FME-02            transaction type.                                                       Mandatory          Full 2003       Tested         Funds Control      types.

                                  Perform on-line inquiry of funds availability prior to the processing of
           2001 FME-03            spending transactions (commitments, obligations, and expenditures).        Mandatory       Full 2003       Tested         Funds Control

                                  Determine funds availability based on whether funds cited are current,
                                  expired, or canceled and record appropriate accounting entries when
                                  de-obligation of expired funding occurs. Do not allow the use of de-
           2001 FME-04            obligated prior-year funds for current year expenditures.              Mandatory           Full 2003       Tested         Funds Control
                                  Record transactions that affect the availability of funds, including
           2001 FME-05            commitments, obligations, and expenditures.                            Mandatory           Full 2003       Tested         Funds Control
                                  Provide for modification to spending documents (commitments,
                                  obligations and expenditures), including ones that change the dollar
                                  amount or the accounting classification cited. Check for funds
           2001 FME-06            availability when changes are made.                                    Mandatory           Full 2003       Tested         Funds Control

                                  Provide on-line notification to users of transactions failing funds
                                  availability edits, and make the rejected transactions available for
                                  corrective action. This is to include transactions entered directly to the
           2001 FME-07            core system and those received from external modules or systems.           Mandatory       Full 2003       Tested         Funds Control
                                                                                                                                                                               Transactions previously rejected
                                                                                                                                                                               for exceeding user-defined
                                  Override funds availability edits, including automatically releasing and                                                                     tolerances are not tested
                                  processing transactions previously rejected for exceeding user-defined                                                                       because tolerances are related
                                  tolerances. Produce a report or otherwise notify management of the                                                                           to funds control, not funds
           2001 FME-08            over obligation of funds.                                                Mandatory         Full 2003       Tested         Funds Control      availability checking.
                                  Automatically update all appropriate budgetary accounts and or tables
                                  to ensure that the system always maintains and reports the current
           2001 FME-09            status of funds.                                                         Mandatory         Full 2003       Tested         Funds Control


Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                               Page 11 of 79
Financial Systems Integration Office                                                                  Requirements Tested Matrix
                                                                                                    Core Requirements & Test Status

 Requirement                                                                                                                                                                                                Requirement Short
    Year               Req. No.                                    Description                                   Status       Test Cycle     Test Status        Process               Test Notes                  Name
                                  Check for funds availability when the obligation exceeds the
                                  commitment document or when the expenditure (upon receipt or
                                  disbursement) exceeds the obligating document due to quantity or
                                  price variances, additional shipping charges, etc., within tolerances.
                                  Provide on-line notification when tolerances are exceeded. When                                                                          Price variances are tested,
                                  variances are within tolerances, process and adjust the obligation                                                                       Variations in quantity are not
           2001 FME-10            accordingly.                                                                Mandatory     Full 2003       Tested         Funds Control   tested.
                                  Allow for available fund balances to be based on reimbursable
                                  customer orders accepted. In the case of reimbursable orders from the
                                  public, ensure that an advance must also be received before
           2001 FME-11            additional funding authority is recorded.                                   Mandatory     Full 2003       Tested         Funds Control
                                  Track all activity related to an individual reimbursable agreement.
                                  When recording commitments, obligations, and expenditures incurred
                                  in support of reimbursable agreements, check for funds availability
                                  against the amount authorized by the agreement and the
           2001 FME-12            corresponding start and end dates.                                          Mandatory     Full 2003       Tested         Funds Control
                                  Record and maintain reimbursable agreements, (e.g., inter-agency
                                  agreements,) so that monthly, quarterly, and fiscal year-to-date as well
           2001 FME-13            as inception-to-date information can be presented.                          Mandatory     Full 2003       Tested       Funds Control
                                  Automatically notify users when funds availability is reduced by                                          Not
                                  transactions from external systems (e.g. credit card payments and                       Not               Tested/Value
           2001 FME-14            payroll).                                                                   Value Added Applicable        Added        Funds Control
                                  Maintain information related to each commitment document, including
                                  amendments. The Core financial system must capture: Requisition                                                                          Requisition numbers tested
                                  number, Appropriate accounting classification values, and Estimated                                                                      through posting of test step
           2001 FME-15            amounts.                                                                    Mandatory     Full 2003       Tested         Funds Control   document numbers.
                                  Input line item detail for commitment documents, including item
                                  description, unit price, quantity of goods and services, accounting
           2001 FME-16            information, and amounts.                                                   Mandatory     Full 2003       Tested         Funds Control
                                  Future-date, store, and automatically post commitment documents at
                                  the appropriate date. Subject these documents to edit and validation
                                  procedures prior to posting. Provide notification when transactions are
           2001 FME-17            posted.                                                                     Mandatory     Full 2003       Tested         Funds Control
                                  Close commitments by document and line item under the following
                                  circumstances: (1) automatically by the system upon issuance of an
                                  obligating document, (2) by an authorized user, and (3) automatically
           2001 FME-18            as part of the yearend pre-closing process.                                 Mandatory     Full 2003       Tested         Funds Control
           2001 FME-19            Record obligations for which there is no related commitment.                Mandatory     Full 2003       Tested         Funds Control
                                  Maintain information related to obligation documents and related
                                  amendments, including obligating document number and type; vendor
                                  information, accounting classification elements, referenced
           2001 FME-20            commitment (if applicable); and dollar amounts.                             Mandatory     Full 2003       Tested         Funds Control
                                  Future-date, store, and automatically post obligation documents at the
                                  appropriate date. Subject these documents to edit and validation
                                  procedures prior to posting. Provide notification when transactions are
           2001 FME-21            posted.                                                                     Mandatory     Full 2003       Tested         Funds Control
                                  Enter recurring obligation transactions that will be automatically posted
                                  at various time intervals such as monthly, quarterly or a specific
           2001 FME-22            number of days determined by the user.                                      Mandatory     Full 2003       Tested         Funds Control
                                  Allow multiple commitments to be combined into one obligating
           2001 FME-23            document.                                                                   Mandatory     Full 2003       Tested         Funds Control
                                  Allow one commitment document to be split between multiple
           2001 FME-24            obligating documents.                                                       Mandatory     Full 2003       Tested         Funds Control
                                  Reference multiple funding sources on a single commitment or
           2001 FME-25            obligation.                                                                 Mandatory     Full 2003       Tested         Funds Control
                                  Allow authorized modifications and cancellations of posted obligating
           2001 FME-26            documents.                                                                  Mandatory     Full 2003       Tested         Funds Control




Printed on 5/20/2010                                                                                  93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                         Page 12 of 79
Financial Systems Integration Office                                                                 Requirements Tested Matrix
                                                                                                   Core Requirements & Test Status

 Requirement                                                                                                                                                                                                   Requirement Short
    Year               Req. No.                                   Description                                  Status        Test Cycle     Test Status        Process               Test Notes                      Name
                                  Provide on-line access to all obligations by selection criteria, (e.g.,
                                  document number, vendor number, accounting classification
           2001 FME-27            elements).                                                                Mandatory      Full 2003       Tested         Funds Control
                                  Maintain an on-line history file of closed-out documents for a user-                                                                    Tested for closed commitment
           2001 FME-28            defined period of time.                                                   Mandatory      Full 2003       Tested         Funds Control   and obligation document lines.
                                  Allow the vendor used on an obligation to be different from suggested
           2001 FME-29            vendor recorded on the related commitment document.                       Mandatory      Full 2003       Tested         Funds Control
                                  Close obligation documents under the following circumstances: (1)
                                  automatically by the system upon final payment for goods or services,
                                  or (2) by an authorized user. Upon the closing of an obligation,
                                  automatically classify any de-obligation of excess funds to the
                                  appropriate budgetary status (i.e., expired, unexpired, available for                                                                   Impact on funds not available for
           2001 FME-30            obligation or unavailable).                                               Mandatory      Full 2003       Tested         Funds Control   obligation is not tested.
                                  Record and maintain contracts and grants and related financial activity
                                  so that fiscal year-to-date and inception-to-date information can be
           2001 FME-31            presented.                                                                Mandatory      Full 2003       Tested         Funds Control
                                  Record blanket purchase agreements (BPAs), and record, control, and
           2001 FME-32            track records of call.                                                    Mandatory      Full 2003       Tested         Funds Control

           2001 FME-33            Record, control, and track delivery orders against a contract limitation. Mandatory      Full 2003       Tested         Funds Control
                                  Record advance payments made, such as travel advances, contract
                                  advances, and grants. Ensure that an obligation exists prior to
           2001 FME-34            recording an advance.                                                     Mandatory      Full 2003       Tested         Funds Control
                                  Record expenditures claimed against advance payments made, and
                                  automatically liquidate the advance either partially or fully, as
           2001 FME-35            appropriate. Allow the recording of advance refunds.                      Mandatory      Full 2003       Tested         Funds Control

                                  Automatically link transactions in the spending chain, and bring
                                  forward accounting and non-financial information from one document
                                  to another, when the previously accepted document is referenced,
           2001 FME-36            (e.g., commitment to obligation, obligation to receiving report).         Mandatory      Full 2003       Tested         Funds Control
                                  Maintain the following additional data fields for each obligating
                                  document: Requester’s name, Telephone number of requester,
                                  Contract number/GSA schedule number, Deliver to location (e.g.,
                                  room number, division), Comment field, Contact name, COTR name,                                          Not
                                  COTR telephone number, Prompt Pay indicator, Approval date, and                       Not                Tested/Value
           2001 FME-37            Discount payment terms.                                                   Value Added Applicable         Added        Funds Control
                                  Maintain current information on commitments and obligations
                                  according to the required accounting classification elements (see CFA-
           2001 FME-38            01).                                                                      Mandatory      Full 2003       Tested         Funds Control
                                  Produce detailed listings and summary reports of commitments,
                                  obligations and expenditures by the elements of the defined
           2001 FME-39            accounting classifications.                                               Mandatory      Full 2003       Tested         Funds Control
                                  Provide control features that ensure that the amounts reflected in the
                                  fund control structure agree with the related general ledger account
           2001 FME-40            balances at the end of each update cycle.                                 Mandatory      Full 2003       Tested         Funds Control
                                                                                                                                                                          Period of time for on-line history
                                                                                                                                                                          file is defined as through the end
                                                                                                                                                                          of the fiscal year after the
                                  Maintain historical data on all commitment, obligation, payment and                                                                     effective date of the transaction.
           2001 FME-41            collection transactions.                                                  Mandatory      Full 2003       Tested         Funds Control   .
                                  Maintain open documents to show the status of commitments,
           2001 FME-42            obligations, accruals, and disbursements by document line item.           Mandatory      Full 2003       Tested         Funds Control




Printed on 5/20/2010                                                                                 93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                             Page 13 of 79
Financial Systems Integration Office                                                                  Requirements Tested Matrix
                                                                                                    Core Requirements & Test Status

 Requirement                                                                                                                                                                                                      Requirement Short
    Year               Req. No.                                 Description                                      Status       Test Cycle     Test Status         Process                   Test Notes                   Name

                                  Provide the ability to perform document cross-referencing in which a
                                  user can query on any document and identify the document numbers
                                  of associated transactions in the processing "chain" (e.g., querying on
                                  a purchase order would provide any amendments to purchase orders,
                                  receiving reports, requisitions, and invoices; querying on a receivable
           2001 FME-43            would provide any associated cash receipts).                                Mandatory     Full 2003       Tested         Funds Control
                                  Allow users to define and maintain a chart of accounts consistent with
                                  the U.S. SGL, including account titles and the basic numbering                                                           General Ledger
           2001 GLA-01            structure.                                                                  Mandatory     Full 2003       Tested         Account Definition
                                  Incorporate proprietary, budgetary, and memorandum (credit reform)
                                  accounts in the system, and maintain the relationships between U.S.                                                      General Ledger
           2001 GLA-02            SGL accounts as described in the current TFM Supplement.                    Mandatory     Full 2003       Tested         Account Definition
                                  Provide U.S. SGL control accounts for detailed subsidiary accounts in                                                    General Ledger
           2001 GLA-03            the core or external systems.                                               Mandatory     Full 2003       Tested         Account Definition
                                  Create additional sub-accounts to the U.S. SGL for agency specific
                                  tracking and control. These sub-accounts will summarize to the                                                           General Ledger
           2001 GLA-04            appropriate U.S. SGL accounts.                                              Mandatory     Full 2003       Tested         Account Definition
                                  Capture U.S. SGL attribute information required for both FACTS I and
                                  FACTS II reporting as specified by the current supplement(s) to the                                                      General Ledger
           2001 GLA-05            TFM.                                                                        Mandatory     Full 2003       Tested         Account Definition

                                  Provide flexibility so that the system can adapt to changes in FACTS I
                                  and FACTS II reporting requirements. For example, the user should be                                                     General Ledger
           2001 GLA-06            able to add or modify valid values within an existing attribute domain.     Mandatory     Full 2003       Tested         Account Definition
                                  Process additions, deletions, and changes to the chart of accounts
                                  without extensive program or system changes, (e.g., through on-line                                                      General Ledger
           2001 GLA-07            table updates).                                                             Mandatory     Full 2003       Tested         Account Definition
                                  Prohibit new transactions from posting to general ledger accounts that                                                   General Ledger
           2001 GLA-08            have been de-activated.                                                     Mandatory     Full 2003       Tested         Account Definition
                                  Allow for accruals relating to contracts or other items that cross fiscal                                                Accruals, Closing
           2001 GLB-01            years.                                                                      Mandatory     Full 2003       Tested         and Consolidation
                                  Automatically generate selected recurring accrual entries and                                                            Accruals, Closing    Tested for instances except for
           2001 GLB-02            reversals in subsequent accounting periods (e.g., payroll accrual).         Mandatory     Full 2003       Tested         and Consolidation    payroll accruals.
                                  Close an accounting period and prohibit subsequent postings to the                                                       Accruals, Closing
           2001 GLB-03            closed period.                                                              Mandatory     Full 2003       Tested         and Consolidation
                                  Automatically determine an accounting period’s opening balances
                                  based on the prior accounting period’s closing balances, without user
                                  intervention or adjustment. The rollover of general ledger balances
                                  must be accomplished in a detailed manner to maintain the U.S. SGL
                                  attribute information required to satisfy FACTS I and FACTS II                                                           Accruals, Closing
           2001 GLB-04            reporting requirements.                                                     Mandatory     Full 2003       Tested         and Consolidation
                                  Perform multiple preliminary yearend closings, while maintaining the                                                     Accruals, Closing
           2001 GLB-05            capability to post current and prior period data.                           Mandatory     Full 2003       Tested         and Consolidation
                                  Automatically generate fiscal yearend pre-closing and closing entries                                                    Accruals, Closing
           2001 GLB-06            as they relate to fund types.                                               Mandatory     Full 2003       Tested         and Consolidation
                                  Provide for an automated yearend rollover of appropriate system                                                          Accruals, Closing
           2001 GLB-07            tables into the new fiscal year.                                            Mandatory     Full 2003       Tested         and Consolidation
                                  Compare amounts in the general ledger accounts with the amounts in
                                  the related subsidiary records and create reports for those accounts
                                  that are out of balance. This capability must be available for all open                                                  General Ledger
                                  accounting period balances and at frequencies defined by the user,                                                       Analysis and
           2001 GLC-01            such as daily, weekly and monthly.                                          Mandatory     Full 2003       Tested         Reconciliation
                                  Perform on-line "drill downs" from general ledger summary balances                                                       General Ledger
                                  to detail transactions and referenced documents (e.g., purchase                                                          Analysis and
           2001 GLC-02            orders, receiving reports, etc.).                                           Mandatory     Full 2003       Tested         Reconciliation




Printed on 5/20/2010                                                                                  93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                               Page 14 of 79
Financial Systems Integration Office                                                                Requirements Tested Matrix
                                                                                                  Core Requirements & Test Status

 Requirement                                                                                                                                                                                                Requirement Short
    Year               Req. No.                                   Description                                  Status       Test Cycle     Test Status         Process               Test Notes                   Name
                                  Record subsequent activity related to a closed document under a                                                        General Ledger
                                  unique document ID and provide an audit trail that associates the new                                                  Analysis and
           2001 GLC-03            activity with the transaction history of the original document.           Mandatory     Full 2003       Tested         Reconciliation
                                  Maintain payee (vendor) information to support obligation, accounts
                                  payable, and disbursement processes, including: Vendor name,
                                  Vendor ID number, Vendor type (e.g., Federal agency, state/local
                                  government, commercial entity, individual, employee), TIN, Three or
                                  more payment addresses, Three or more separate instances of
                                  banking information (i.e., account and routing numbers) for issuing
                                  payments, Bank account type (check or savings), Three or more
                                  contact names, Three or more contact telephone numbers, Federal
                                  vs. Non-federal indicator, Six-digit Trading Partner codes, Entity type                                                                 Clarification: Delete SIC code,
                                  (e.g., small business, 8A, women owned business), Multiple vendor                                                                       add CAGE code.
                                  payment methods (e.g., Electronic Funds Transfer (EFT), check),
                                  Third-party information (e.g., payee TIN for notice of assignment),                                                                     Tested for three (not more) of
                                  Data Universal Numbering System (DUNS) number, ALC number (for                                                                          the following: payment
                                  Federal vendors), Subject to Prompt Pay indicator, Internal Revenue                                                    Payment          addresses, instances of banking
2006                              Service (IRS) -1099 indicator, W-2 indicator, Comment field, Date of                                                   Information      information, contact names,
Clarification     PMA-01          last update, and(vendor) information to support obligation, accounts
                                  Maintain payee User ID of last update.                                    Mandatory     Full 2003       Tested         Maintenance      contact telephone numbers.
                                  payable, and disbursement processes, including:
                                  • Vendor name (Legal name and DBA name as appropriate)
                                  • TIN
                                  • Vendor ID number (Agency assigned)
                                  • DUNS (Maintain ability to associate multiple DUNS to a TIN)
                                  • Organization type (accommodate CCR published business rules for
                                  organization type: sole proprietorship/Individual; partnership,
                                  employee, etc.)
                                  • Business type (accommodate CCR published business rules for
                                  business type: Federal agency; local government, etc.)
                                  • Federal vs. Non-federal indicator for FACTS reporting
                                  • ALC number (for Federal vendors)
                                  • Six-digit Trading Partner code (for Federal vendors)
                                  • Multiple payment methods (e.g., Electronic Funds Transfer (EFT),
                                  check)
                                  • Three or more ―remit to‖ addresses (to facilitate payments to vendors
                                  not required to register in CCR)
                                  • Three or more separate instances of banking information required to
                                  execute an EFT transaction (e.g., account and routing transit
                                  numbers, etc.). For CCR vendors , maintain DUNS ―+ Four‖ for each
                                  instance of banking information.
                                  • Bank account type (checking or savings)
                                  • Capability to maintain three or more contact names and telephone
                                  numbers, (accommodate contact types defined as ―mandatory‖ in CCR
                                  business rules
                                  • Third-party information (e.g., payee TIN for notice of assignment) as
                                  appropriate
                                  • Subject to Prompt Pay indicator
                                  • Internal Revenue Service (IRS) -1099 indicator
                                  • W-2 indicator                                                                                                        Payment
2001                              • CCR registration indicator (required, exempt)                                         Incr.                          Information
Addendum          PMA-01a         • CCR registration status (i.e., active, inactive, unregistered)          Mandatory     2004/2005       Tested         Maintenance
                                  Support payments made to third parties (payees) that act as an agent                                                   Payment
                                  for the payee (vendor). Maintain information needed to produce IRS                                                     Information
           2001 PMA-02            –1099s for the principal party rather than the agent.                     Mandatory     Full 2003       Tested         Maintenance
                                  Prevent the duplicate entry of vendor records, (e.g., by editing vendor                                                Payment
                                  ID numbers or vendor names.) Provide an on-line warning message to                                                     Information
           2001 PMA-03            the user when duplication is identified.                                  Mandatory     Full 2003       Tested         Maintenance




Printed on 5/20/2010                                                                                93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                           Page 15 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                                 Requirement Short
    Year               Req. No.                                 Description                                      Status        Test Cycle     Test Status        Process              Test Notes                   Name
                                  Track and maintain a history of changes to the vendor file, including
                                  vendor additions and purges, and changes to vendor specific
                                  information such as payment address, bank account and routing                                                           Payment
                                  information, and payment type. Maintain an audit trail of payments                                                      Information
           2001 PMA-04            made to historical vendor information.                                      Mandatory      Full 2003       Tested       Maintenance
                                                                                                                                                          Payment
                                  Query and report on payee information by user-defined criteria, such                                                    Information
           2001 PMA-05            as payee name, payee number, and IRS -1099 reporting status.                Mandatory      Full 2003       Tested       Maintenance
                                                                                                                                                          Payment          Activate portion of requirement
                                  Activate and deactivate vendors that meet user selected criteria (e.g.,                                                 Information      not tested since not normally
           2001 PMA-06            such as length of time with no activity.)                                   Mandatory      Full 2003       Tested       Maintenance      done in practice.
                                                                                                                                             Not          Payment
                                  Capture vendor information required when registering with the Central                   Not                Tested/Value Information
           2001 PMA-07            Contractor Registration (CCR) and track activity by CCR identifier.         Value Added Applicable         Added        Maintenance
                                  Support an agency’s use of the Central Contractor Registration (CCR)
                                  by providing the ability to import and automatically process data that is
                                  pertinent to the Core financial system. At a minimum, the system
                                  must provide the capability to:
                                  • Automatically update the mandatory payee information required by
                                  PMA-01 (previously recorded) in existing vendor records to reflect the
                                  relevant changes contained in the daily updates provided by the CCR
                                  via extract files.
                                  • Accommodate the data definitions (e.g. data types; field names; field
                                  lengths) used in CCR for all fields that are common in both the CCR
                                  and the Core vendor file.
                                  • Prevent users’ ability to manually update the relevant data fields
                                  specified in PMA-01, whose source must be the CCR (as specified by                                                        Payment
2001                              OMB and the FAR) relative to vendors that are required to register in                      Incr.                          Information
Addendum          PMA-07a         the CCR                                                                     Mandatory      2004/2005       Tested         Maintenance
                                  Record an accrued liability upon receipt and acceptance of goods and
                                  services and properly identify them as capital asset, expense, prepaid                                                    Payment
           2001 PMB-01            expense, or construction.                                                   Mandatory      Full 2003       Tested         Warehousing
                                  Record "full" or "partial" receipt and acceptance of goods and services                                                   Payment
           2001 PMB-02            by line item.                                                               Mandatory      Full 2003       Tested         Warehousing
                                  Automatically update the funds control and budget execution balances
                                  to reflect changes in the status of obligations and expended                                                              Payment
           2001 PMB-03            appropriations, as well as changes in amounts.                              Mandatory      Full 2003       Tested         Warehousing
                                                                                                                                                            Payment
           2001 PMB-04            Warehouse payment vouchers for future scheduling.                           Mandatory      Full 2003       Tested         Warehousing
                                  Allow a warehoused payment to be modified, cancelled, and put on                                                          Payment
           2001 PMB-05            hold.                                                                       Mandatory      Full 2003       Tested         Warehousing
                                  Automatically match invoices to obligations and receiving reports by
                                  document and line item. Provide for two-way matching (obligation and
                                  invoice) and three-way matching (obligation, receiving report, and                                                        Payment
           2001 PMB-06            receipt of invoice).                                                        Mandatory      Full 2003       Tested         Warehousing
                                  Process "obligate and pay" transactions where payment scheduling                                                          Payment
           2001 PMB-07            and obligation occurs simultaneously.                                       Mandatory      Full 2003       Tested         Warehousing
                                                                                                                                                            Payment
           2001 PMB-08            Reference multiple obligations on a single invoice document.                Mandatory      Full 2003       Tested         Warehousing
                                  Set up recurring payments in the system and automatically schedule
                                  items (e.g. contracts, leases, etc.) for payment on an interval                                                                          Monthly and quarterly recurring
                                  determined by the user (i.e., weekly, bi-weekly, monthly, quarterly or                                                    Payment        payments are tested. No
           2001 PMB-09            other specified number of days).                                            Mandatory      Full 2003       Tested         Warehousing    contract or lease involved.
                                                                                                                                                                           Change in amount and
                                  Modify recurring payment information for changes in agreement terms,                                                      Payment        frequency are tested, which are
           2001 PMB-10            amounts, frequency, etc.                                             Mandatory             Full 2003       Tested         Warehousing    agreement terms.




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                         Page 16 of 79
Financial Systems Integration Office                                                                      Requirements Tested Matrix
                                                                                                        Core Requirements & Test Status

 Requirement                                                                                                                                                                                                    Requirement Short
    Year               Req. No.                                    Description                                    Status          Test Cycle     Test Status        Process             Test Notes                    Name
                                  Capture, store and process the following information for each vendor
                                  invoice, for audit trail, research and query purposes: Invoice number,
                                  Invoice date, Invoice receipt date, Invoice due date, Invoice amount,
                                  Unit price and quantity, Description, Discount terms, as applicable,
                                  Obligating document reference(s), Vendor identification number and                                                           Payment
           2001 PMB-11            address code.                                                                Mandatory        Full 2003       Tested         Warehousing
                                  Edit the TIN field to ensure that it is a nine digit numeric field, does not
                                  include dashes, and is not all zeroes. Allow for override for agency                                                         Payment
           2001 PMB-12            specific requirements.                                                       Mandatory        Full 2003       Tested         Warehousing    Override not tested.
                                                                                                                                                                              The current TFM requirement of
                                  Accommodate an invoice number field of up to 30 characters or the                                                            Payment        a 20 character invoice field is
           2001 PMB-13            current requirement of I TFM-6-5000.                                           Mandatory      Full 2003       Tested         Warehousing    tested.

                                  Determine the due date and amount of vendor payments in
                                  accordance with Title 5, Part 1315 of the CFR which states, in part,
                                  that for agencies subject to prompt payment requirements, payment is
                                  due on either: (1) 30 days after the receipt of a proper invoice for
                                  services and non-dairy products; (2) 10 days after the receipt of a
                                  proper invoice for dairy products; (3) the date specified in the contract;
                                  (4) in accordance with discount terms when discounts are offered and                                                         Payment
           2001 PMB-14            taken; or (5) in accordance with Accelerated Payments Methods.             Mandatory          Full 2003       Tested         Warehousing
                                                                                                                                                               Payment
           2001 PMB-15            Manually override a system-calculated payment due date.                        Mandatory      Full 2003       Tested         Warehousing

                                  Split an invoice into multiple payments on the appropriate due dates                                                         Payment
           2001 PMB-16            when items on the invoice have different due dates or discount terms.          Mandatory      Full 2003       Tested         Warehousing
                                  Record discount terms and automatically determine whether taking the                                                         Payment
           2001 PMB-17            discount is economically justified as defined in I TFM-6-8040.                 Mandatory      Full 2003       Tested         Warehousing
                                  Record additional shipping and other charges to adjust the payment                                                           Payment
           2001 PMB-18            amount, if they are authorized and within variance tolerances.                 Mandatory      Full 2003       Tested         Warehousing
                                  Record obligations, expenses, assets, etc., associated with payments
                                  made through use of Imprest funds, third-party drafts, and
                                  Government credit cards. Establish payables to replenish the Imprest                                                         Payment
           2001 PMB-19            fund.                                                                          Mandatory      Full 2003       Tested         Warehousing
                                  Record detailed transactions associated with credit card purchases.
                                  Allow users to change accounting classification information by line                                                          Payment
           2001 PMB-20            item for specific transactions.                                                Mandatory      Full 2003       Tested         Warehousing

                                  Schedule payments of advances, prepaid expenses, loans, and                                                                  Payment        Tested loan payment and grant
           2001 PMB-21            grants, with the appropriate accounting entries for each.                      Mandatory      Full 2003       Tested         Warehousing    advance payment already made.

                                  Establish payables and make payments on behalf of another agency,
                                  citing the other agency’s funding information. For each disbursement
                                  made on behalf of another agency, provide the information required
                                  (e.g., purchase order number or reimbursable agreement number and                                                                           Tested payment made with
                                  the ALC) by Central agency systems (e.g., OPAC (On-line Payment                                                                             other agency's funding. IPAC
                                  and Collection System (OPAC)/Intra-governmental Payment and                                                                  Payment        transaction not required for
           2001 PMB-22            Collection System (IPAC) to the appropriate Central agency system.             Mandatory      Full 2003       Tested         Warehousing    same.
                                  Record expense or assets when goods have been received, or
                                  services performed, for items that were funded by advances, prepaid
                                  expenses, and grants and make the appropriate liquidations. Verify
                                  funds availability and automatically update funds control account and                                                        Payment
           2001 PMB-23            or table balances to reflect obligation changes.                               Mandatory      Full 2003       Tested         Warehousing
                                  Indicate if a payment is ―partial‖ or ―final.‖ If ―final,‖ automatically de-                                                 Payment
           2001 PMB-24            obligate any unliquidated balances.                                            Mandatory      Full 2003       Tested         Warehousing
                                  Automatically generate a payment voucher if the purchase order                                                Not
                                  matches the receiver information. Provide this option as a function of                     Not                Tested/Value Payment
           2001 PMB-25            the matching process.                                                          Value Added Applicable         Added        Warehousing


Printed on 5/20/2010                                                                                      93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                         Page 17 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                                    Requirement Short
    Year               Req. No.                                 Description                                      Status        Test Cycle     Test Status        Process                  Test Notes                  Name
                                                                                                                                             Not
                                  Use the Fast Payment clause indicator on the obligating document to                    Not                 Tested/Value   Payment
           2001 PMB-26            determine whether or not an accelerated payment is to be made.             Value Added Applicable          Added          Warehousing
                                  Compare discount terms on the invoice with discount terms on the                                           Not
                                  related obligating document. Notify the user when differences are                      Not                 Tested/Value   Payment
           2001 PMB-27            identified.                                                                Value Added Applicable          Added          Warehousing
                                  Provide a system-generated letter or e-mail to the vendor stating the                                      Not
                                  reason for rejection or "notice of intent to disallow" an invoice within               Not                 Tested/Value   Payment
           2001 PMB-28            seven days of receipt of invoice.                                          Value Added Applicable          Added          Warehousing
                                  Automatically identify and select payments to be disbursed in a
                                  particular payment cycle based on their due dates. Provide for on-line
           2001 PMC-01            review and certification by an authorized certifying officer.              Mandatory       Full 2003       Tested         Payment Execution
                                  Automatically compute amounts to be disbursed, including discounts,
                                  interest, and penalties, in accordance with Title 5, Part 1315 of the
                                  CFR. Generate the appropriate transactions to reflect the payment
           2001 PMC-02            deductions and additions.                                                  Mandatory       Full 2003       Tested         Payment Execution Penalties not tested.
                                  Automatically apply interest and discount across multiple accounting
                                  lines on an invoice in the same rule used to apply the original
           2001 PMC-03            payment.                                                                   Mandatory       Full 2003       Tested         Payment Execution
                                  Apply the appropriate Treasury interest rate tables, (e.g., Prompt Pay
           2001 PMC-04            rate and Current Value of Funds rate).                                     Mandatory       Full 2003       Tested         Payment Execution

                                  Capture prompt payment information required by Title 5, Part 1315 of
           2001 PMC-05            the CFR, including discounts taken, discounts lost, and interest paid.     Mandatory       Full 2003       Tested         Payment Execution

                                                                                                                                                                              Tested inclusion of invoice
                                                                                                                                                                              number in bulk data and ECS
                                  Automatically include relevant identification information on each                                                                           check records, invoice number
                                  remittance, including: vendor invoice number(s); obligating document                                                                        and interest amount in ECS
                                  number or other reference number; and discount, interest and offset                                                                         ACH record, and offset type and
           2001 PMC-06            amounts, as applicable.                                                    Mandatory       Full 2003       Tested         Payment Execution offset amount in CTX record.
           2001 PMC-07            Record user comments for each voucher/invoice.                             Mandatory       Full 2003       Tested         Payment Execution
                                                                                                                                                                              Feature demonstrated without
           2001 PMC-08            Provide for up to 9,999 line items per invoice.                            Mandatory       Full 2003       Tested         Payment Execution actual invoice processing.
                                  Record reason codes for returned and adjusted invoices, lost
           2001 PMC-09            discounts, and late payments.                                              Mandatory       Full 2003       Tested         Payment Execution
                                  Track the status of invoices in the payment process, including those
                                  that were not accepted and returned to the vendor and those that are
                                  awaiting administrative approval. Maintain the time and aging of
           2001 PMC-10            approvals in relation to payments.                                         Mandatory       Full 2003       Tested         Payment Execution
                                  Provide for various forms of payment to be used, (i.e., check or EFT
                                  (e.g., Automated Clearing House (ACH) and wire). Capture, store and
                                  process information needed to create EFT payments in accordance
                                  with Treasury standards, including American Bankers Association
                                  Routing Transit Number (RTN), recipient bank account number, and
                                  bank account type (checking or savings). This includes the ability to                                                                       PPD+ and CCD+ testing covers
                                  identify employees versus companies to ensure use of correct ACH                                                                            PPD and CCD formats. Fedwire
           2001 PMC-11            formats.                                                                   Mandatory       Full 2003       Tested         Payment Execution payments not tested.
                                  Generate ACH payments in Corporate Trade Exchange (CTX) (820 or
                                  Flat File), Cash Concentration or Disbursement (CCD), Cash
                                  Concentration or Disbursement Plus Addendum (CCD+), Prearranged                                                                             PPD+ and CCD+ testing covers
                                  Payment and Deposit (PPD), and Prearranged Payment and Deposit                                                                              PPD and CCD formats. CTX flat
           2001 PMC-12            Plus Addendum (PPD+) formats.                                              Mandatory       Full 2003       Tested         Payment Execution file tested, not 820 file.
                                  Ensure that employee ACH payments are generated only as PPD or
           2001 PMC-13            PPD+ payments.                                                             Mandatory       Full 2003       Tested         Payment Execution
                                  Ensure that vendor ACH payments are generated only as CCD, CCD+                                                                             CCD format covered by CCD+
           2001 PMC-14            or CTX formats.                                                            Mandatory       Full 2003       Tested         Payment Execution format testing.




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                            Page 18 of 79
Financial Systems Integration Office                                                                     Requirements Tested Matrix
                                                                                                       Core Requirements & Test Status

 Requirement                                                                                                                                                                                                         Requirement Short
    Year               Req. No.                                   Description                                      Status        Test Cycle     Test Status        Process                   Test Notes                    Name

                                  Prohibit the creation of an ACH payment in any format (PPD, PPD+,
           2001 PMC-15            CCD+, or CTX) that does not contain a RTN and an account number.             Mandatory       Full 2003       Tested         Payment Execution

                                  Consolidate multiple payments to a single payee in accordance with
                                  TFM prescribed limitations (currently up to 14 lines of 55 characters
                                  each for check payments, up to 9,999 lines of 80 characters each for
                                  CTX payments). Itemize all payments covered by the one check or
           2001 PMC-16            EFT (CTX only). However, allow for separate checks to a payee.               Mandatory       Full 2003       Tested         Payment Execution Line/character limits not tested.
                                  Create check files and EFT payment files in all formats (CTX (820 or                                                                          PPD+ and CCD+ testing covers
                                  Flat File), CCD, CCD+, PPD, and PPD+) using different media                                                                                   PPD and CCD formats. CTX flat
                                  (telecommunications, tape, direct entry to Electronic Certification                                                                           file tested. Tape and direct entry
           2001 PMC-17            System (ECS), and third party upload through ECS).                           Mandatory       Full 2003       Tested         Payment Execution to ECS not tested.
                                  Provide an edit on the RTN field. The field is a nine-digit numeric-only
                                  field. Prohibit fewer or more than nine characters, allow for only
                                  numeric characters, and prohibit the entry of all zeroes in this field.
                                  Edit RTN’s against the data supplied in the Financial Organization
                                  Master File (FOMF) (or other verified update file) to ensure the validity
           2001 PMC-18            of the check digit (Modulus 10 check).                                       Mandatory       Full 2003       Tested         Payment Execution
                                  Edit the invoice number field to ensure it is populated. Prohibit the
                                  generation of a (vendor) payment that does not contain properly
           2001 PMC-19            structured remittance information on the addendum.                           Mandatory       Full 2003       Tested         Payment Execution
                                  Generate multiple payments using the same invoice number, to
                                  accommodate utility and telecommunication companies’ use of an
           2001 PMC-20            account number as a recurring invoice number.                                Mandatory       Full 2003       Tested         Payment Execution

                                  Edit the ALC field to ensure it is an eight digit numeric field. Allow for
           2001 PMC-21            override, (e.g., by agencies that have their own disbursing authority.)      Mandatory       Full 2003       Tested         Payment Execution

                                                                                                                                                                                Tested for bulk file only.
                                                                                                                                                                                Treasury payment formats do
                                                                                                                                                                                not support combining employee
                                                                                                                                                                                and vendor payments in the
           2001 PMC-22            Create one check file regardless of payee type (employee or vendor).         Mandatory       Full 2003       Tested         Payment Execution same ECS check file.
                                  Combine payment files from multiple ALCs into a single file for
                                  transmission to Treasury. Provide summary totals (items and dollars)
           2001 PMC-23            by ALC and for the entire file for certification purposes.                   Mandatory       Full 2003       Tested         Payment Execution
                                  Make CTX payments using a separate file. The transactions need to
                                  be balanced (sum of all the remittance records must equal the
                                  transaction total). The file must include a valid settlement date (next
                                  business day or later). The file must be able to accommodate the
           2001 PMC-24            inclusion of Credit Memos.                                                   Mandatory       Full 2003       Tested         Payment Execution
                                  Schedule and disburse U.S. dollar payments (SF-1166) through the
                                  Treasury’s ECS, containing up to the limit of 60 payments per                                                                                 Direct entry to ECS and its
           2001 PMC-25            schedule and 100 schedules for each ECS terminal per day.                    Mandatory       Full 2003       Tested         Payment Execution schedule limitations not tested
                                  Process payment transactions from other systems, such as payroll
                                  and travel. Identify whether or not disbursement has already been                                                                             Tested API payments already
                                  made, and record the appropriate accounting entries. Schedule those                                                                           made. API payments to be
                                  disbursements not already made for payment through the core                                                                                   made will be addressed in
           2001 PMC-26            financial system.                                                            Mandatory       Full 2003       Tested         Payment Execution incremental testing.

                                  Automatically generate transactions to reflect disbursement activity
                                  initiated by other agencies and recorded in Central agency electronic
                                  systems (such as OPAC/IPAC). Capture related information required
                                  by the Central agency system for each transaction (e.g., purchase
           2001 PMC-27            order number, reimbursable agreement number, ALC).                           Mandatory       Full 2003       Tested         Payment Execution IPAC disbursement tested.




Printed on 5/20/2010                                                                                     93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                               Page 19 of 79
Financial Systems Integration Office                                                                    Requirements Tested Matrix
                                                                                                      Core Requirements & Test Status

 Requirement                                                                                                                                                                                                    Requirement Short
    Year               Req. No.                                   Description                                     Status       Test Cycle     Test Status        Process                  Test Notes                  Name
                                  Flag vouchers selected for payment that will disburse a fund into a
                                  negative cash position. (Reimbursable work can result in this type of
           2001 PMC-28            transaction with appropriate authority.)                                     Mandatory     Full 2003       Tested         Payment Execution
                                  Process credit memoranda for returned goods or other adjustments.
                                  Apply the credit to the specific obligation that resulted in the credit,
                                  reducing the expenditure attributed to that obligation. If a credit is not
                                  fully liquidated by one payment, maintain the balance of the credit
                                  (e.g., as an account receivable) for application against a future
                                  payment. Create the appropriate notice to the vendor that a credit has
           2001 PMC-29            been applied to the affected payment.                                        Mandatory     Full 2003       Tested         Payment Execution
                                  Apply credits against subsequent disbursements to the same vendor
           2001 PMC-30            regardless of the funding source.                                            Mandatory     Full 2003       Tested         Payment Execution
                                  Allow for the exclusion of payments from agency offset based on user-
                                  defined criteria including funding source, object class, vendor type and
           2001 PMC-31            vendor number.                                                               Mandatory     Full 2003       Tested         Payment Execution
                                  Provide, generate, and maintain a sequential numbering system for
                                  scheduling payments to the disbursing office. Assign different
                                  schedule number ranges for different payment types, such as travel
                                  schedules, transportation schedules, payroll schedules, vendor
           2001 PMC-32            schedules, etc. Require each schedule number to be unique.                   Mandatory     Full 2003       Tested         Payment Execution

                                                                                                                                                                              Treasury payment
                                                                                                                                                                              formats/systems did not support
                                                                                                                                                                              reporting of TAS/TAFS totals at
           2001 PMC-33            On each payment schedule/file, report totals by TAS/TAFS.               Mandatory          Full 2003       Not Tested     Payment Execution the time of the 2003 test.
                                  Cancel an entire payment schedule or a single payment within a
                                  payment schedule, prior to transmission to Treasury. Allow for reversal
                                  of an entire schedule in a single, interactive action. Perform the                                                                          Tested cancellation of entire
           2001 PMC-34            appropriate accounting reversals.                                       Mandatory          Full 2003       Tested         Payment Execution payment schedule.
                                  Cancel an entire payment schedule prior to actual disbursement by or
                                  upon rejection by Treasury. Allow for reversal of an entire schedule in
                                  a single, interactive action. Perform the appropriate accounting                                                                            Testing the same as for
           2001 PMC-35            reversals.                                                              Mandatory          Full 2003       Tested         Payment Execution requirement PMC-34.
                                                                                                                                             Not
                                  When consolidating multiple payments to a single payee, include the                      Not               Tested/Value
           2001 PMC-36            TAS/TAFS associated with each payment in the payment file.                   Value Added Applicable        Added          Payment Execution
                                                                                                                                             Not
                                  When combining payment files for multiple ALCs into a single file for                    Not               Tested/Value
           2001 PMC-37            transmission to Treasury, provide summary totals by TAS/TAFS.                Value Added Applicable        Added          Payment Execution
                                                                                                                                             Not
                                  Provide National Automated Clearing House Association (NACHA)                            Not               Tested/Value
           2001 PMC-38            payment formats for Non-Treasury Disbursing Offices.                         Value Added Applicable        Added          Payment Execution
                                                                                                                                             Not
                                  Split a single payment into separate bank accounts (e.g., benefit                        Not               Tested/Value
           2001 PMC-39            payments to recipients).                                                     Value Added Applicable        Added          Payment Execution
                                                                                                                                             Not
                                  Provide statistical sampling capabilities to support agency payment                      Not               Tested/Value
           2001 PMC-40            certification.                                                               Value Added Applicable        Added          Payment Execution
                                  Identify and report payment and deposit amounts at a detail suitable                                       Not
                                  for reporting large dollar notifications as described in I TFM-6-8500,                   Not               Tested/Value
           2001 PMC-41            Cash Forecasting Requirements.                                               Value Added Applicable        Added          Payment Execution
                                  Provide information about each payment to reflect the stage of the
                                  scheduling process that the payment has reached and the date each
                                  step was reached for the following processing steps: Payment                                                              Payment
                                  scheduled, Schedule sent to appropriate disbursing office, Payment                                                        Confirmation and
           2001 PMD-01            issued by appropriate disbursing office.                                     Mandatory     Full 2003       Tested         Follow-up




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                            Page 20 of 79
Financial Systems Integration Office                                                                Requirements Tested Matrix
                                                                                                  Core Requirements & Test Status

 Requirement                                                                                                                                                                                                     Requirement Short
    Year               Req. No.                                   Description                               Status          Test Cycle     Test Status        Process                   Test Notes                     Name
                                  For each payment made by the Core financial system, maintain a
                                  history of the following information: Vendor Invoice number, Invoice
                                  amount, Vendor identification number, Vendor name, Payment
                                  address or banking information, Payment amount, Interest paid, when
                                  applicable, Discount taken, when applicable, Offset made, when                                                         Payment
                                  applicable, Payment method (e.g., check, EFT), Referenced obligation                                                   Confirmation and
           2001 PMD-02            number, and Appropriation charged.                                     Mandatory        Full 2003       Tested         Follow-up
                                  Automatically update the payment information when confirmation is                                                      Payment
                                  received from the disbursing office, including the paid schedule                                                       Confirmation and
           2001 PMD-03            number, payment date and check number or trace number.                 Mandatory        Full 2003       Tested         Follow-up
                                  Automatically liquidate the in-transit amount and reclassify budgetary                                                 Payment
                                  accounts from unpaid to paid when the payment confirmation updates                                                     Confirmation and
           2001 PMD-04            the system.                                                            Mandatory        Full 2003       Tested         Follow-up
                                                                                                                                                         Payment
                                  Record more than one check range for a payment schedule, along                                                         Confirmation and
           2001 PMD-05            with a break in check numbers.                                         Mandatory        Full 2003       Tested         Follow-up
                                                                                                                                                         Payment
                                                                                                                                                         Confirmation and
           2001 PMD-06            Provide on-line access to vendor and payment information.            Mandatory          Full 2003       Tested         Follow-up
                                  Provide on-line access to open documents based on agency selection                                                     Payment
                                  criteria, including the accounting classification elements, document                                                   Confirmation and
           2001 PMD-07            number, and vendor number.                                           Mandatory          Full 2003       Tested         Follow-up
                                                                                                                                                         Payment
                                  Reverse disbursement transactions for voided checks or for other                                                       Confirmation and
           2001 PMD-08            payments that have not been negotiated.                                 Mandatory       Full 2003       Tested         Follow-up
                                  Produce IRS-1099s (such as 1099-INT, 1099-MISC, 1099-C and 1099-
                                  G) in accordance with IRS regulations and current IRS acceptable
                                  format, including hard copy and electronic form. For example, when
                                  payment to a sole proprietor for services performed (not including cost                                                Payment
                                  of merchandise) exceeds a specified dollar amount (e.g., $600)                                                         Confirmation and    1099-MISC and 1099-C's tested.
           2001 PMD-09            produce a 1099-M.                                                       Mandatory       Full 2003       Tested         Follow-up           Electronic IRS format not tested.
                                  Electronically download monthly ―Fund Balance with Treasury‖ and
                                  activity recorded by Treasury (and related warrant information) for                                                    Payment
                                  comparison to cash activity in the agency’s general ledger. Produce a                                                  Confirmation and    Will be addressed in future
           2001 PMD-10            report of differences.                                                  Mandatory       Full 2003       Not Tested     Follow-up           testing.
                                                                                                                                          Not            Payment
                                  Include the TAS/TAFS charged and the associated amount(s) in the                 Not                    Tested/Value   Confirmation and
           2001 PMD-11            history of each payment made by the Core financial system.           Value Added Applicable             Added          Follow-up
                                  Provide an automated interface to the Department of Treasury system                                     Not            Payment
                                  containing paid schedule data (i.e., GOALS Regional Finance Center               Not                    Tested/Value   Confirmation and
           2001 PMD-12            Agency Link, or its successor).                                      Value Added Applicable             Added          Follow-up
                                  Provide written notification to payees (vendors, travelers, etc.) of                                    Not            Payment
                                  payments made by disbursing offices. Allow for agency flexibility in             Not                    Tested/Value   Confirmation and
           2001 PMD-13            defining the contents of the notifications.                          Value Added Applicable             Added          Follow-up
                                                                                                                                          Not            Payment
                                  Provide e-mail notification to employees of travel payments made by                Not                  Tested/Value   Confirmation and
           2001 PMD-14            disbursing offices.                                                    Value Added Applicable           Added          Follow-up
                                                                                                                                          Not            Payment
                                                                                                                     Not                  Tested/Value   Confirmation and
           2001 PMD-15            Track and report on aged, unmatched vendor invoices.                   Value Added Applicable           Added          Follow-up
                                                                                                                                          Not            Payment
                                  Track and report on spending agency-wide by state and congressional              Not                    Tested/Value   Confirmation and
           2001 PMD-16            district.                                                            Value Added Applicable             Added          Follow-up
                                  Produce reports and transmittable files using data maintained by the
           2001 RA-01             core financial management system.                                    Mandatory   Full 2003              Tested         General Reporting

                                  Report on financial activity by any element of accounting classification
           2001 RA-02             (e.g., individual or hierarchical organization code, project code).      Mandatory      Full 2003       Tested         General Reporting


Printed on 5/20/2010                                                                                93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                Page 21 of 79
Financial Systems Integration Office                                                                 Requirements Tested Matrix
                                                                                                   Core Requirements & Test Status

 Requirement                                                                                                                                                                                                      Requirement Short
    Year               Req. No.                                Description                                     Status        Test Cycle     Test Status      Process                    Test Notes                      Name
                                                                                                                                           Not
                                  Report the financial information required for program management                    Not                  Tested/Value
           2001 RA-03             performance reporting.                                                  Value Added Applicable           Added        General Reporting
                                  Provide data in hard copy and electronic formats required by the
                                  Department of the Treasury for the following reports: FMS Form 224,
                                  Statement of Cash Transactions, FMS Form 1219, Statement of
                                  Accountability, and FMS Form 1220, Statement of Transactions
           2001 RB-01             According to Appropriations, Funds, and Receipt Accounts.               Mandatory        Full 2003       Tested       External Reporting   FMS Forms 224 only.
                                  Provide data in the electronic formats required by the Department of
           2001 RB-02             the Treasury for FACTS I and FACTS II reporting.                        Mandatory        Full 2003       Tested       External Reporting
                                                                                                                                                                             Only test hard copy as electronic
                                  Produce a monthly SF-133, Report on Budget Execution and                                                                                   format is not tested since data is
                                  Budgetary Resources, in the hard copy and electronic formats                                                                               now submitted through FACTS
           2001 RB-03             required by OMB.                                                        Mandatory        Full 2003       Tested       External Reporting   II.
                                  Perform the validation edits specified by Treasury to ensure the
                                  accuracy of data transmitted for FACTS I and FACTS II reporting, (at
                                  least) on a monthly basis. See the FACTS II Client Bulk Users Guide
           2001 RB-04             for examples.                                                           Mandatory        Full 2003       Tested       External Reporting
                                  Automate the preparation of consolidated financial statements as
                                  required by the current OMB Bulletin on Form and Content of Agency
           2001 RB-05             Financial Statements.                                                   Mandatory        Full 2003       Tested       External Reporting

                                  Produce a report of transaction level details for the TAS/TAFS totals
           2001 RC-01             reported on the FMS that is 224, Statement of Cash Transactions.
                                  For each TAFS/TAS Form subject to FACTS II reporting                      Mandatory      Full 2003       Tested       Internal Reporting
                                  requirements, produce a daily on-line Available Funds report(s). The
                                  report(s) must accommodate the following parameters: ―internal fund‖,
                                  budget object class, organization, program, project, and activity and
                                  contain the following data elements as described below.At the internal
                                  fund level, report data on budget execution as follows:Total resources
                                  by budget fiscal year and by authority type, (including warrant
                                  information) as follows: Total Authority Brought forward, Total
                                  appropriated for by budget fiscal year, Total contract authority, Total
                                  borrowing authority (realized and unrealized), Total Estimated and
                                  total actual spending authority from offsetting collections, and Funding
                                  distribution, including: Total not yet apportioned, Total apportioned,
                                  Total allotted, and Total allowances. Spending Activity, including: Total
                                  amount of commitments, Total obligations (including paid and unpaid),
                                  Total expenditures (including paid and unpaid). Balances available,
                                  such as: Balance of apportionments available for allotment, Balance of
                                  allowance available for commitment (uncommitted), Balance of
           2001 RC-02             allowances available for obligation (unobligated). When reporting on      Mandatory      Full 2003       Tested       Internal Reporting

                                  Provide on-line summary trial balances at the internal fund,
                                  organization, and TAS/TAFS levels. The trial balances must provide
                                  the following minimum data elements for each general ledger account:
                                  The balance at the beginning of the accounting period, The total
                                  amount of debits for the accounting period, The total amount of credits
                                  for the accounting period, and The cumulative ending balance for the
                                  accounting period. Grand totals for TAS/TAFS must be provided for
                                  beginning balance, current period activity and ending balance
                                  columns. The system must produce both pre-closing and post-closing
           2001 RC-03             trial balances at yearend.                                              Mandatory        Full 2003       Tested       Internal Reporting




Printed on 5/20/2010                                                                                 93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                Page 22 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                  Requirement Short
    Year               Req. No.                                    Description                              Status             Test Cycle     Test Status         Process        Test Notes         Name
                                  Support FACTS I and FACTS II reporting and analysis by producing on-
                                  line trial balances at the internal fund, organization, and TAS/TAFS
                                  levels. The trial balances must provide the data elements listed below
                                  for each general ledger account. The related official U.S. SGL account
                                  number, The following items at the U.S. SGL attribute level (i.e.,
                                  separate amounts whenever there is more than one attribute domain
                                  value within an U.S. SGL account): The balance at the beginning of
                                  the accounting period, The total amount of debits for the current
                                  accounting period, The total amount of credits for the accounting
                                  period, and The cumulative ending balance for the accounting period.
                                  Grand totals for each TAS/TAFS must be provided for beginning
                                  balance, current period activity, and ending balance columns. The
                                  system must produce both pre-closing and post-closing trial balances
           2001 RC-04             at year end.                                                           Mandatory           Full 2003       Tested         Internal Reporting
                                  Provide an on-line transaction register at the internal fund,
                                  organization, and TAS/TAFS level, for each accounting period, that
                                  provides the following data elements: Fiscal year, TAS/TAFS, Internal
                                  fund, Document number; Document entry date, Document entry time,
                                  Document entry User ID, Document transaction date, Debit account
                                  number; Debit account object class Debit amount, Credit account
                                  number, Credit account, Object class, U.S. SGL attribute domain
                                  headings, U.S. SGL attribute values associated with the transaction.
                                  The report must include all transactions that occurred within the
           2001 RC-05             accounting period specified.                                           Mandatory           Full 2003       Tested         Internal Reporting
                                  Provide an integrated data query facility that supports ad hoc query
                                  access to agency financial data sources and provides data analysis
           2001 RD-01             reporting tools.                                                       Mandatory           Full 2003       Tested         Ad hoc Query
                                  Allow users to create and submit parameter-based query scripts or to
           2001 RD-02             store them in a common library for future use.                         Mandatory           Full 2003       Tested         Ad hoc Query
                                  Allow users to run queries on-line or in batch mode and to stage
           2001 RD-03             output for later access by authorized users.                           Mandatory           Full 2003       Tested         Ad hoc Query
                                  Allow users to automatically distribute copies of report/query results
           2001 RD-04             via e-mail to multiple pre-identified individuals or groups.           Mandatory           Full 2003       Tested         Ad hoc Query
                                  Provide run-time controls to limit "run-away" queries and large data
           2001 RD-05             download requests.                                                     Mandatory           Full 2003       Tested         Ad hoc Query
                                  Support graphical output display on the desktop. Output display should
                                  also support dynamic report reformatting, regrouping and drill-down to
           2001 RD-06             detail records from summary report lines.                              Mandatory           Full 2003       Tested         Ad hoc Query
                                  Allow authorized users to download selected financial data. This
                                  download capability must be able to automatically reformat
                                  downloaded information for direct access by common desktop
           2001 RD-07             applications (e.g., ASCII formatted).                                  Mandatory           Full 2003       Tested         Ad hoc Query
                                  Provide the ability to preview a report, form, or other query result
           2001 RD-08             before printing.                                                       Mandatory           Full 2003       Tested         Ad hoc Query
           2001 RD-09             Support access to current year and historical financial data.          Mandatory           Full 2003       Tested         Ad hoc Query

                                  Provide the following ad hoc query interface features: Graphical
                                  display of data sources, The ability to ―point and click‖ on selectable
                                  table, data, and link objects for inclusion in a custom query, An active
                                  data dictionary to provide users with object definitions, The ability to                                   Not
                                  share user developed query scripts with other authorized agency                        Not                 Tested/Value
           2001 RD-10             users, query optimization, and On-line help.                               Value Added Applicable          Added        Ad hoc Query




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                          Page 23 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                                      Requirement Short
    Year               Req. No.                                  Description                              Status               Test Cycle     Test Status        Process                 Test Notes                     Name
                                  Maintain customer information to support receivable management
                                  processes, including, at a minimum: Customer name, Customer ID
                                  number, Customer type (federal agency, state/local government,
                                  commercial entity, individual, employee), Taxpayer Identification
                                  Number (TIN), Customer address, Contact names, Contact telephone
                                  number, Federal vs. Non-Federal indicator, Six-digit Trading Partner
                                  codes, ALC number (for Federal customers), Internal Revenue Service                                                       Customer
                                  (IRS) 1099 indicator, Comment field, Date of last update, User ID of                                                      Information
           2001 RMA-01            last update, DUNS number.                                            Mandatory             Full 2003       Tested         Maintenance

                                  Maintain customer account information for audit trail purposes and to
                                  support billing, reporting and research activities, including, at a
                                  minimum: Account number, Account balance, Associated Customer ID                                                          Customer
                                  number, Date due and age of accounts receivable, Reimbursable                                                             Information
           2001 RMA-02            order number, travel order number, etc., where applicable.            Mandatory            Full 2003       Tested         Maintenance
                                  Record the establishment of receivables along with the corresponding                                                      Receivable
           2001 RMB-01            revenues, expense reductions, or other offsets.                       Mandatory            Full 2003       Tested         Establishment
                                  Accept transactions that generate receivables from other systems in a                                                     Receivable
           2001 RMB-02            standard format for entry into the Core financial system.             Mandatory            Full 2003       Tested         Establishment

                                  Support the calculation and establishment of accounts receivable
                                  based upon billing source, event and time period, and type of claim.
                                  Automatically generate related bills to customers. Bases used for
                                  billing may include: Percentage of reimbursable obligations, accrued
                                  expenditures, or costs, using data recorded by the cost accumulation
                                  function; Fee schedules for goods or services provided; and Payment                                                       Receivable
           2001 RMB-03            schedules or other agreements with other entities.                        Mandatory        Full 2003       Tested         Establishment
                                  Establish receivables and credit memos from vendors to whom the                                                           Receivable
           2001 RMB-04            agency has made duplicate or erroneous payments.                          Mandatory        Full 2003       Tested         Establishment

                                  Uniquely identify multiple types of bills (e.g., overpayments, user fee                                                   Receivable
           2001 RMB-05            based) and the supporting data used to verify the specific charges.       Mandatory        Full 2003       Tested         Establishment

                                  Automatically establish receivables to be paid under installment plans,
                                  including plans for which payments have been rescheduled. Generate                                                        Receivable
           2001 RMB-06            flexible repayment schedules for delinquent indebtedness.                Mandatory         Full 2003       Tested         Establishment
                                  Record billings and collections by line item in order to identify unique                                                  Receivable
           2001 RMB-07            accounting classification codes.                                         Mandatory         Full 2003       Tested         Establishment
                                  Support bills and collections between Federal agencies through the
                                  use of electronic systems such as IPAC. Provide supporting data to                                                        Receivable
           2001 RMB-08            agencies billed which can be used to verify the charges.                 Mandatory         Full 2003       Tested         Establishment
                                                                                                                                                                              Test will only require vendors to
                                  Print bills, accommodating the generation of standard forms, such as                                                                        print a 1081. Revise this
                                  SF-1080s or SF-1081s, and turnaround documents to be used as a                                                                              requirement in the future to call
                                  remittance advice. Allow for customized text in generated billing                                                         Receivable        for 1081 edp and related batch
           2001 RMB-09            documents.                                                              Mandatory          Full 2003       Tested         Establishment     file (FMS Form 5908).
                                  Date the bills with the system-generated date or with the date supplied                                                   Receivable
           2001 RMB-10            by the user.                                                            Mandatory          Full 2003       Tested         Establishment
                                                                                                                                                            Receivable
           2001 RMB-11            Consolidate multiple accounts receivable for a customer onto one bill. Mandatory           Full 2003       Tested         Establishment
                                  Allow transactions related to manually prepared bills to be entered by                                                    Receivable
           2001 RMB-12            authorized personnel.                                                  Mandatory           Full 2003       Tested         Establishment
                                                                                                                                                            Receivable
           2001 RMB-13            Record adjustments to bills and post to customer accounts.                Mandatory        Full 2003       Tested         Establishment
                                                                                                                                                            Receivable
           2001 RMB-14            Generate monthly statements to customers showing account activity.        Mandatory        Full 2003       Tested         Establishment
                                  Maintain data on individual receivables and referenced transactions
           2001 RMC-01            supporting the receivable.                                                Mandatory        Full 2003       Tested         Debt Management


Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                              Page 24 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                                     Requirement Short
    Year               Req. No.                                Description                                        Status       Test Cycle     Test Status        Process                 Test Notes                    Name
                                  Maintain accounts for reimbursable orders and identify Government
                                  and non-government accounts that are designated as advance
           2001 RMC-02            funding.                                                                     Mandatory     Full 2003       Tested         Debt Management

                                  Update each customer account when: billing documents are
                                  generated; collections are received; interest, penalty or administrative
           2001 RMC-03            fees are applied, and when amounts are written-off or offset.                Mandatory     Full 2003       Tested         Debt Management
                                  Automatically calculate interest charges using the appropriate
                                  Treasury Late Payment Charge rate and user-defined criteria (e.g.,
                                  customer, customer type). Automatically generate a separate line item
           2001 RMC-04            for interest charges on the customer bill.                                   Mandatory     Full 2003       Tested         Debt Management
                                  Allow the user to specify administrative and penalty amounts and
                                  record these amounts to different accounting classification elements                                                                        Generation of separate line item
                                  for which the principle amount is recorded. Automatically apply these                                                                       for the administrative/penalty
                                  charges to customer accounts and generate separate line items for                                                                           charges on the customer bill not
           2001 RMC-05            the charges on the customer bills.                                           Mandatory     Full 2003       Tested         Debt Management   tested.
                                  Automatically generate dunning (collection) letters for overdue
                                  receivables when accounts become delinquent, and incorporate, as
           2001 RMC-06            appropriate, due process notices for referring delinquent accounts.          Mandatory     Full 2003       Tested         Debt Management
           2001 RMC-07            Customize the dunning process parameters and dunning letter text.            Mandatory     Full 2003       Tested         Debt Management
                                  Provide information on the age of receivables to allow for
                                  management and prioritization of collection activities. This is to include
                                  aging information on individual receivables and on a summary basis,
                                  such as by customer, type of customer, fund, and general ledger
           2001 RMC-08            account.                                                                     Mandatory     Full 2003       Tested         Debt Management
                                  Identify and report receivables that meet predetermined criteria for
           2001 RMC-09            write-off, or referral and generate the appropriate entries.                 Mandatory     Full 2003       Tested         Debt Management
                                  Automatically calculate (as a percentage of gross receivables or
                                  related revenues) and record the allowance for loss on accounts
           2001 RMC-10            receivable.                                                                  Mandatory     Full 2003       Tested         Debt Management
                                                                                                                                                                              At the time of the 2003 test,
                                                                                                                                                                              Treasury guidance did not
                                                                                                                                                                              support reporting of delinquent
                                  Provide information to allow for the automated reporting of delinquent                                                                      accounts to commercial credit
           2001 RMC-11            accounts to commercial credit bureaus.                                       Mandatory     Full 2003       Not Tested     Debt Management   bureaus.
                                  Automatically create files of delinquent accounts for electronic                                                                            We do not test the submission
                                  submission to collection agencies and appropriate governmental                                                                              of data to private collection
           2001 RMC-12            organizations.                                                               Mandatory     Full 2003       Tested         Debt Management   agencies.
                                  Maintain data for receivables referred to other Federal agencies and
           2001 RMC-13            outside organizations for collections.                                       Mandatory     Full 2003       Tested         Debt Management
                                  Record the waiver and write-off of receivables, including interest,                                                                         Tested write-off of accounts
                                  penalties, and administrative charges. Maintain data to monitor closed                                                                      receivable and interest. Waiver
           2001 RMC-14            accounts.                                                                    Mandatory     Full 2003       Tested         Debt Management   not tested.
                                  Track and report on the date and nature of a change in the status of
                                  an accounts receivable, including the following: In Forbearance or in
                                  Formal Appeals Process, In Foreclosure, In Wage Garnishment,
                                  Rescheduled, Waived/unwaived, Eligible for Referral to Treasury for
                                  Offset, Referred to Treasury for Offset, Eligible for Internal Offset,                                                                      We test the ability to produce
                                  Eligible for Referral to Treasury or a Designated Debt Collection                                                                           the data required to complete
                                  Center for Cross-servicing, Referred to Treasury for cross-servicing,                                                                       the report on receivables due
                                  Referred to private collection agency, Referred to Department of                                                                            from the public per Treasury
                                  Justice (DOJ), Offset, Suspended, Compromised, Written-off, Closed                                                                          requirements. Not all statuses
           2001 RMC-15            Out.                                                                         Mandatory     Full 2003       Tested         Debt Management   tested.
                                  Perform on-line queries of account activity (billing, collection, and                                                                       Tested query of collection by
           2001 RMC-16            adjustment) by customer and receivable.                                      Mandatory     Full 2003       Tested         Debt Management   customer.
                                  Perform on-line queries of miscellaneous cash receipts (applied to any
                                  Treasury fund symbol) by customer, when identified, and by
           2001 RMC-17            accounting period.                                                           Mandatory     Full 2003       Tested         Debt Management


Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                             Page 25 of 79
Financial Systems Integration Office                                                                 Requirements Tested Matrix
                                                                                                   Core Requirements & Test Status

 Requirement                                                                                                                                                                                                   Requirement Short
    Year               Req. No.                                 Description                                    Status        Test Cycle     Test Status         Process               Test Notes                     Name

                                  Uniquely record, classify, and report on reimbursable funds including:
                                  billing limit, amount obligated, amount expended, amount billed,
                                  advanced amount (unearned revenue), and earnings and collections
                                  received, based on customer and customer agreement number.
                                  Support the ability to query and report on these items by any of the
           2001 RMC-18            accounting classification elements (e.g., fund or object class).          Mandatory      Full 2003       Tested         Debt Management
                                  Automatically produce IRS-1099-C’s in the amounts of debts forgiven
                                  which meet or exceed a user-defined dollar threshold (e.g., $600 or
           2001 RMC-19            more).                                                                    Mandatory      Full 2003       Tested         Debt Management
                                  Automatically record the application of complete and partial payments
                                  made by the debtor on a delinquent debt to administrative fees,
                                  penalties, interest, and then to principal, unless otherwise stated in                                                  Collections and
           2001 RMD-01            program statute.                                                          Mandatory      Full 2003       Tested         Offsets
                                  Record revenues, expenditure reductions, or other appropriate offsets
                                  associated with collections for which no receivable was previously                                                      Collections and   Tested receipt of advances and
           2001 RMD-02            established.                                                              Mandatory      Full 2003       Tested         Offsets           revenue.
                                  Apply collections back to the specific contract or purchase order award
                                  to reduce cumulative payments and expenditures, (e.g., upon the                                                         Collections and
           2001 RMD-03            refund of erroneous payments.)                                            Mandatory      Full 2003       Tested         Offsets
                                  Record the receipt of an advance repayment and an advance from
                                  others with a reference to the related reimbursable agreement (RA)
                                  obligation, whether or not an account receivable was previously                                                         Collections and   Receipt of advance repayment
           2001 RMD-04            established.                                                              Mandatory      Full 2003       Tested         Offsets           not tested.
                                  Process cash or credit card collections. Match collections to the
                                  appropriate receivables and update related bills and customer                                                           Collections and
           2001 RMD-05            accounts.                                                                 Mandatory      Full 2003       Tested         Offsets
                                  Record information associated with a collection at the time funds are
                                  applied to an open receivable document , including the deposit ticket                                                   Collections and
           2001 RMD-06            number and date, and ALC code.                                            Mandatory      Full 2003       Tested         Offsets
                                  Support the receipt of collection files from banks for application to                                                   Collections and
           2001 RMD-07            open receivables.                                                         Mandatory      Full 2003       Tested         Offsets
                                                                                                                                                          Collections and
           2001 RMD-08            Record collections received against advance payments made.                Mandatory      Full 2003       Tested         Offsets
                                                                                                                                                          Collections and
           2001 RMD-09            Apply collections to more than one receivable.                            Mandatory      Full 2003       Tested         Offsets
                                  Re-open closed accounts to record collections after a waiver or write-                                                  Collections and
           2001 RMD-10            off of a receivable has been recorded.                                    Mandatory      Full 2003       Tested         Offsets
                                                                                                                                                                            This requirement would be
                                                                                                                                                                            accomplished through an
                                  Electronically download monthly deposit and debit voucher                                                                                 interface with CA$HLINK. No
                                  confirmation information from Treasury and the banking system for                                                                         mandatory requirement for such
                                  comparison to activity in the agency’s general ledger. Produce a report                                                 Collections and   an interface existed at the time
           2001 RMD-11            of differences.                                                         Mandatory        Full 2003       Not Tested     Offsets           of the 2003 test.
                                  Support the receipt of payment offset information from Treasury. Apply
                                  offset collections to open receivables and generate the appropriate                                                     Collections and
           2001 RMD-12            accounting entries to record the collections.                           Mandatory        Full 2003       Tested         Offsets
                                  Automatically offset payments to vendors for amounts due to the
                                  agency, (e.g., outstanding accounts receivable, credit memo, and
                                  open advances.) When an entire payment is offset, create the                                                          Collections and
           2001 RMD-13            appropriate notice to the vendor that the offset has been made.         Mandatory        Full 2003       Tested       Offsets             Tested credit memo offset.
                                                                                                                                           Not
                                  Record TAS/TAFS(s) associated with collections received on deposit                       Not             Tested/Value Collections and
           2001 RMD-14            tickets and debit vouchers.                                         Value Added          Applicable      Added        Offsets
                                  When downloading monthly deposit and debit voucher confirmation
                                  information from the Treasury and the banking system for comparison                                      Not
                                  to the agency general ledger, include both the TAS/TAFS(s) and the                       Not             Tested/Value Collections and
           2001 RMD-15            associated amount(s).                                               Value Added          Applicable      Added        Offsets


Printed on 5/20/2010                                                                                 93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                             Page 26 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                               Requirement Short
    Year               Req. No.                                   Description                                  Status   Test Cycle            Test Status       Process       Test Notes         Name
                                  Interface with CA$HLINK, in order to reconcile Treasury recorded                                           Not
                                  collections to the collections recorded in the core financial system and             Not                   Tested/Value Collections and
           2001 RMD-16            generate exception reports.                                              Value Added Applicable            Added        Offsets
                                  Be modular in design, utilize open-systems architecture, and be
                                  upgradeable by core system module to accommodate changes in                                                               General Design/
           2001 TA-01             laws, regulations, best practices and new technology.                    Mandatory   Full 2003             Tested         Architecture

                                  Be a commercially available product, subject to regular maintenance                                                       General Design/
           2001 TA-02             based on vendor developed and scheduled software releases.                 Mandatory       Full 2003       Tested         Architecture
                                  Include internal transaction processing controls, including the
                                  capability in the event of a system failure to automatically: Back out
                                  incompletely processed transactions, Restore the system to its last
                                  consistent state before the failure occurred, and Re-apply all                                                            General Design/
           2001 TA-03             incomplete transactions previously submitted by the user.                  Mandatory       Full 2003       Tested         Architecture
                                  Enforce internal database consistency during all on-line and batch                                                        General Design/
           2001 TA-04             update operations, including distributed databases, if applicable.         Mandatory       Full 2003       Tested         Architecture

                                  Have fully documented restart capabilities for the application’s on-line
                                  and batch processing components. Batch jobs must be segmented to                                                          General Design/
           2001 TA-05             facilitate their recovery in the event of a system failure.                Mandatory       Full 2003       Tested         Architecture

                                  Include complete installation, operating, and system maintenance
                                  documentation covering: Product installation and configuration steps,
                                  Application access procedures, User screen layout and content,
                                  Transaction entry procedures, Batch job set-up, processing and
                                  recovery/re-start procedures, Error codes with full descriptions and
                                  recovery steps, Standard report layout and content, Internal
                                  processing controls, Application security, Operating specifications and
                                  system flowcharts, Database entity relationships, table formats and                                                       General Design/
           2001 TA-06             data element descriptions, and Program module descriptions.             Mandatory          Full 2003       Tested         Architecture
                                  Include revised documentation concurrent with the distribution of new                                                     General Design/
           2001 TA-07             software releases.                                                      Mandatory          Full 2003       Tested         Architecture
                                  Employ common error-handling routines across functional modules
                                  and present error messages that allow the user or system operator to                                                      General Design/
           2001 TA-08             respond to reported problems.                                           Mandatory          Full 2003       Tested         Architecture
                                                                                                                                                            General Design/
           2001 TA-09             Common error message text must be customizable by the agency.         Mandatory            Full 2003       Tested         Architecture
                                  Generate output information to formats specified by functional
                                  requirements. In cases where a functional requirement does not
                                  specify an output format, required information must be viewable using                                                     General Design/
           2001 TA-10             the application’s on-line user interface by default.                  Mandatory            Full 2003       Tested         Architecture
                                  Be customizable to meet agency specific business/accounting needs
                                  using agency supplied application configuration and operating                                                             General Design/
           2001 TA-11             parameters.                                                           Mandatory            Full 2003       Tested         Architecture

                                  Provide fault-free performance in the processing of date and date-
                                  related data (including, calculating, comparing, and sequencing) by all
                                  hardware and software products included as part of the application                                                        General Design/
           2001 TA-12             both individually and in combination (i.e., year 2000 compliance).      Mandatory          Full 2003       Tested         Architecture
                                                                                                                                             Not
                                  Include an integrated relational, Structured Query Language (SQL)                      Not                 Tested/Value   General Design/
           2001 TA-13             compliant database.                                                        Value Added Applicable          Added          Architecture
                                                                                                                                             Not
                                  Simultaneously process on-line transactions and transactions                           Not                 Tested/Value   General Design/
           2001 TA-14             submitted via system interface.                                            Value Added Applicable          Added          Architecture




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                       Page 27 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                             Requirement Short
    Year               Req. No.                                    Description                               Status           Test Cycle     Test Status         Process    Test Notes         Name
                                  Identify all software and hardware products needed by an agency to
                                  install operate access and maintain the application. This requirement
                                  includes identification of distinct products that are intended to be
                                  purchased or licensed as part of the product licensing agreement. The
                                  vendor is also required to identify products needed to meet any
                                  technical and functional requirement that must be acquired separately
           2001 TB-01             by the agency.                                                          Mandatory         Full 2003       Tested         Infrastructure
                                  Utilize transaction Control Protocol/Internet Protocol (TCP/IP)
                                  communications protocol for application database and workstation
           2001 TB-02             connectivity.                                                           Mandatory         Full 2003       Tested         Infrastructure
                                  At a minimum support application client operation on a 32-bit Microsoft
           2001 TB-03             Windows compatible operating system.                                    Mandatory         Full 2003       Tested         Infrastructure
                                                                                                                                            Not
                                  Operate in a mainframe environment (e.g., Multiple Virtual System                      Not                Tested/Value
           2001 TB-04             (MVS), Operating System (OS/) 390).                                        Value Added Applicable         Added          Infrastructure
                                                                                                                                            Not
                                  Operate in a server-computing environment running under UNIX or NT             Not                        Tested/Value
           2001 TB-05             (e.g., Windows Server 2000).                                       Value Added Applicable                 Added          Infrastructure
                                                                                                                                            Not
                                  Support application client operation on an Apple Macintosh Windows                     Not                Tested/Value
           2001 TB-06             compatible operating system.                                               Value Added Applicable         Added          Infrastructure
                                                                                                                                            Not
                                                                                                                         Not                Tested/Value
           2001 TB-07             Support application client operation on a UNIX operating system.           Value Added Applicable         Added          Infrastructure
                                                                                                                                            Not
                                  Support automated touch-tone telephone access for standardized,                        Not                Tested/Value
           2001 TB-08             commonly requested, inquiries (such as payment status).                    Value Added Applicable         Added          Infrastructure
                                                                                                                                            Not
                                  Support automated fax-back access for standardized, commonly                           Not                Tested/Value
           2001 TB-09             requested, documents (such as account statements).                         Value Added Applicable         Added          Infrastructure
                                                                                                                                            Not
                                                                                                                         Not                Tested/Value
           2001 TB-10             Provide the capability to accept bar-coded documents.                      Value Added Applicable         Added          Infrastructure
                                                                                                                                            Not
                                  Include a report spooling capability to enable on-line viewing, re-                    Not                Tested/Value
           2001 TB-11             printing, and permanent archiving of requested reports.                    Value Added Applicable         Added          Infrastructure
                                  Provide a consistent, Windows-compatible, on-line user interface to all
                                  modules and integrated subsystems. Interface consistency includes                                         Not
                                  the use of common command entry syntax, dialog window styles, data                     Not                Tested/Value
           2001 TC-01             entry structures, and information presentation.                            Value Added Applicable         Added        User Interfaces
                                  Incorporate common GUI characteristics: Mouse activated icons,
                                  Buttons, Scroll bars, Drop-down lists, Check boxes, Menu bars, Text                                       Not
                                  boxes, Tool tips, Resizable windows, and Cut, copy, and paste                          Not                Tested/Value
           2001 TC-02             functions.                                                                 Value Added Applicable         Added        User Interfaces
                                  Incorporate data entry features designed to reduce the amount of
                                  direct keying required to initiate transaction processing. Desired
                                  efficiencies include the use of default values, look-up tables, and
                                  automatic data recall. Other desirable features include: Single function
                                  windows (e.g., one input screen per transaction), The ability to pass
                                  common data from screen to screen, Highlighting of required fields,
                                  Auto tabs, Function keys (e.g., retrieve previous data, invoke help
                                  facility, suspend transaction, clear screen, etc.), Disabling of non-
                                  supported function keys, Menu mode and an expert mode of screen
                                  navigation, The ability to retrieve suspended transactions by user,
                                  document, vendor, etc., Transaction entry undo/redo, Context-                                             Not
                                  sensitive on-line help, and The ability to select records from a list by               Not                Tested/Value
           2001 TC-03             scrolling or by typing in only part of an entry.                           Value Added Applicable         Added        User Interfaces




Printed on 5/20/2010                                                                                  93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                      Page 28 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                Requirement Short
    Year               Req. No.                                 Description                                      Status        Test Cycle     Test Status       Process        Test Notes         Name
                                  Support desktop integration with other common workstation                                                  Not
                                  applications used for word processing, spreadsheets, data                               Not                Tested/Value
           2001 TC-04             management, and graphics.                                                   Value Added Applicable         Added        User Interfaces
                                                                                                                                             Not
                                                                                                                          Not                Tested/Value
           2001 TC-05             The application help facility should be customizable by the agency.         Value Added Applicable         Added        User Interfaces
                                  Provide an application user interface that complies with the software                                      Not
                                  application standards required by Section 508 of the Rehabilitation                     Not                Tested/Value
           2001 TC-06             Act, as detailed in 36 CFR 1194, Subpart B.                                 Value Added Applicable         Added        User Interfaces
                                  Include an application program interface (API) to accept financial data
                                  generated by external applications (e.g., the financial portion of mixed
                                  program systems, Electronic Data Interchange (EDI) translators, and
                                  modules such as travel or payroll). This interface must support the
                                  receipt of transactions for all core accounting components, as well as,
           2001 TD-01             vendor information updates.                                                 Mandatory      Full 2003       Tested         Interoperability
                                  Include an application program interface (API) to accept and process
                                  financial data generated by external applications (e.g., IGTE, IPAC) as
                                  well as other internal applications (e.g., the financial portion of mixed
                                  program systems, Electronic Data Interchange (EDI) translators, and
                                  modules such as travel or payroll) and the ability to export data
                                  required by Governmentwide systems. This interface must support
                                  the receipt and continued processing of transactions for all Core
2001                              accounting components, as well as, vendor information updates (TD-                         Incr.
Addendum          TD-01a          01).                                                                        Mandatory      2004/2005       Tested         Interoperability

                                  Process API submitted transactions using the same business rules,
                                  program logic, and edit table entries as are used by the application in
           2001 TD-02             editing transactions submitted on-line (e.g., via user interface).      Mandatory          Full 2003       Tested         Interoperability
                                  Hold API submitted transactions that do not pass required edits in
                                  suspense pending appropriate corrective action by the user. Suspense
                                  processing must include the ability to: View, update, or delete
                                  suspended transactions, Automatically re-process suspended
           2001 TD-03             transactions.                                                           Mandatory          Full 2003       Tested         Interoperability

                                  Provide internal controls with the API (e.g., control totals, record
           2001 TD-04             counts) to ensure the integrity of received and processed transactions.     Mandatory      Full 2003       Tested         Interoperability
                                  For the API, generate transaction editing error records in a standard
                                  format defined by the vendor for return to the originating feeder
           2001 TD-05             application (i.e., provide two-way interface support).                      Mandatory      Full 2003       Tested         Interoperability
                                  Support direct EDI translation compliant with American National
                                  Standards Institute (ANSI) X-12 standards to enable electronic data                                        Not
                                  exchanges with designated trading partners such as a bank credit                        Not                Tested/Value
           2001 TD-06             card service provider, major supplier, or customer.                         Value Added Applicable         Added          Interoperability
                                  Interface with the agency electronic communications system to                                              Not
                                  distribute application generated documents and messages                                 Not                Tested/Value
           2001 TD-07             electronically to either intranet or Internet users.                        Value Added Applicable         Added          Interoperability
                                                                                                                                             Not
                                  Accept vendor invoices and other external originated transactions over                  Not                Tested/Value
           2001 TD-08             the Internet (e.g., Extensible Markup Language (XML)).                      Value Added Applicable         Added          Interoperability
                                  Support emerging XML-based specifications for the exchange of                                              Not
                                  financial data such as Extensible Business Reporting Language                           Not                Tested/Value
           2001 TD-09             (XBRL).                                                                     Value Added Applicable         Added          Interoperability
                                  Provide an integrated workflow management capability, including
                                  generation and routing of internal forms, reports, and other financial                                                  Workflow/
           2001 TE-01             documents for on-line approval or subsequent processing.                    Mandatory      Full 2003       Tested       Messaging
                                  Enable authorized users to define workflow processes and business                                          Not
                                  rules, including approval levels, and to modify workflow (e.g. assigning                Not                Tested/Value Workflow/
           2001 TE-02             a proxy approving authority).                                               Value Added Applicable         Added        Messaging


Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                        Page 29 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                 Requirement Short
    Year               Req. No.                                  Description                                       Status        Test Cycle     Test Status      Process        Test Notes         Name
                                  Provide the capability to establish multiple levels of document                                              Not
                                  approvals based on user-defined criteria including dollar amounts,                      Not                  Tested/Value Workflow/
           2001 TE-03             types of items purchased, and document types.                               Value Added Applicable           Added        Messaging

                                  Provide an internal calendar or user-defined routing tables to generate
                                  rule-based or exception reports to support the generation of work flow                                       Not
                                  messages (i.e., notification of Accounts Payable office for invoices                Not                      Tested/Value   Workflow/
           2001 TE-04             warehoused over 30 days with no matching receiving report).             Value Added Applicable               Added          Messaging
                                                                                                                                               Not
                                  Provide the ability to track approval events on-line by transaction,                    Not                  Tested/Value   Workflow/
           2001 TE-05             including the time/date and approving party.                                Value Added Applicable           Added          Messaging
                                                                                                                                               Not
                                  Provide the capability to automatically generate electronic routing and             Not                      Tested/Value   Workflow/
           2001 TE-06             status messages to individuals or groups.                               Value Added Applicable               Added          Messaging
                                                                                                                                               Not
                                                                                                                          Not                  Tested/Value   Workflow/
           2001 TE-07             Support Workflow Management Coalition (WFMC) standards.                     Value Added Applicable           Added          Messaging
                                                                                                                                               Not
                                                                                                                          Not                  Tested/Value   Workflow/
           2001 TE-08             Support Messaging API-Workflow (MAPI-WF) standards.                         Value Added Applicable           Added          Messaging
                                                                                                                                               Not
                                                                                                                          Not                  Tested/Value   Workflow/
           2001 TE-09             Support Vendor Independent Messaging (VIM) standards.                       Value Added Applicable           Added          Messaging
                                                                                                                                               Not
                                                                                                                          Not                  Tested/Value   Document
           2001 TF-01             Support Document Management Alliance (DMA) standards.                       Value Added Applicable           Added          Management
                                                                                                                                               Not
                                  Support Open Document Management Architecture (ODMA)                                    Not                  Tested/Value   Document
           2001 TF-02             standards.                                                                  Value Added Applicable           Added          Management
                                                                                                                                               Not
                                  Support Open Document Architecture/Open Document Interface                              Not                  Tested/Value   Document
           2001 TF-03             Format (ODA/ODIF) standards.                                                Value Added Applicable           Added          Management
                                                                                                                                               Not
                                                                                                                          Not                  Tested/Value   Document
           2001 TF-04             Support Portable Document Format (PDF) standards.                           Value Added Applicable           Added          Management
                                                                                                                                               Not
                                                                                                                         Not                   Tested/Value   Document
           2001 TF-05             Support Standard Generalized Markup Language (SGML) standards. Value Added Applicable                        Added          Management
                                  Provide the capability to electronically image, index, store, and retrieve                                   Not
                                  document reference material (e.g., signed contracts, purchase orders                   Not                   Tested/Value   Document
           2001 TF-06             and vendor invoices).                                                      Value Added Applicable            Added          Management
                                                                                                                                               Not
                                  Notify the user of the presence of associated document images and                            Not             Tested/Value   Document
           2001 TF-07             allow an on-screen display of this material.                          Value Added            Applicable      Added          Management
                                  Support secure web browser access to all financial management
                                  system modules including workflow related features for the purpose of                                        Not
                                  entering new financial documents/transactions and to review/approve                          Not             Tested/Value
           2001 TG-01             their processing.                                                     Value Added            Applicable      Added          Internet Access
                                                                                                                                               Not
                                  Support secure Internet access to the integrated ad hoc data query                      Not                  Tested/Value
           2001 TG-02             facility.                                                                   Value Added Applicable           Added          Internet Access
                                                                                                                                               Not
                                  Provide the capability to receive public payment collections via the                    Not                  Tested/Value
           2001 TG-03             Internet (e.g., Web-based collections via credit card).                     Value Added Applicable           Added          Internet Access
                                                                                                                                               Not
                                  Support the use of standard Public Key Infrastructure (PKI) technology             Not                       Tested/Value
           2001 TG-04             to control access to sensitive data over the Internet.                 Value Added Applicable                Added          Internet Access




Printed on 5/20/2010                                                                                     93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                       Page 30 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                              Requirement Short
    Year               Req. No.                                 Description                                      Status        Test Cycle     Test Status         Process    Test Notes         Name
                                  Have integrated security features that are configurable by the system
                                  administrator to control access to the application, functional modules,
                                  transactions, and data. The application’s integrated security features
                                  should be compliant with the National Institute of Standards and
           2001 TH-01             Technology (NIST) Security Standards.                                       Mandatory      Full 2003       Tested         Security
                                  Ensure that the agency’s access policies are consistently enforced
                                  against all attempts made by users or other integrated system
                                  resources including software used to submit ad-hoc data query
           2001 TH-02             requests or to generate standard reports.                                   Mandatory      Full 2003       Tested         Security
                                  Require the use of unique user identifications and passwords for
                                  authentication purposes. Passwords must be non-printing and non-
                                  displaying. The application must allow the enforcement of password
                                  standards, (e.g., minimum length and use of alpha, numeric and
                                  special characters.) The application must also allow for the
                                  establishment of a specified period for password expiration and
           2001 TH-03             accommodate prohibiting the user from reusing recent passwords.             Mandatory      Full 2003       Tested         Security

                                  Enable the system administrator to define functional access rights
                                  (e.g., to modules, transactions, approval authorities) and data access
                                  rights (e.g., record create, read, update and delete) by assigned user
           2001 TH-04             ID, functional role (e.g., payable technician) and owner organization. Mandatory           Full 2003       Tested         Security
                                  Permit the system administrator to assign multiple levels of approval
                                  to a single user, but prevent that user from applying more than one
                                  level of approval to a given document in order to conform to the
           2001 TH-05             principle of separation of duties.                                     Mandatory           Full 2003       Tested         Security
                                  Allow the system administrator to restrict access to sensitive data
                                  elements such as social security numbers and banking information by
           2001 TH-06             named user, groups of users, or functional role.                       Mandatory           Full 2003       Tested         Security

                                  Maintain an audit logging capability to record access activity including:
                                  All log-in/log-out attempts by user and workstation, User submitted
                                  transactions, Initiated processes, System override events; and Direct
           2001 TH-07             additions, changes or deletions to application maintained data.             Mandatory      Full 2003       Tested         Security
                                  Provide the ability to query the audit log by type of access, date and
           2001 TH-08             time stamp range, user identification, or terminal ID.                      Mandatory      Full 2003       Tested         Security
                                  Include a process scheduling capability that enables the operator to                                                      Operations and
                                  initiate, monitor, and stop scheduled processes (e.g., on-line                                                            Computing
           2001 TI-01             availability, batch jobs, and system maintenance).                          Mandatory      Full 2003       Tested         Performance
                                  Provide online status messages indicating job or transaction type and                                                     Operations and
                                  name, when requested processing starts, completes, and system                                                             Computing
           2001 TI-02             errors.                                                                     Mandatory      Full 2003       Tested         Performance
                                                                                                                                                            Operations and
                                  Allow reports to be produced in the background while other system                                                         Computing
           2001 TI-03             processing takes place.                                                Mandatory           Full 2003       Tested         Performance
                                  Provide the system administrator the ability to control the archiving
                                  process. The system must include the capability to establish and
                                  maintain user-defined archival criteria, such as date, accounting
                                  period, closed items, and vendors inactive for a specific time period.                                                    Operations and
                                  The system must allow selective action on those documents that meet                                                       Computing
           2001 TI-04             the criteria.                                                          Mandatory           Full 2003       Tested         Performance
                                  Retain archived data and system records in accordance with Federal
                                  regulations established by the National Archives and Records                                                              Operations and
                                  Administration (NARA), GAO, and the National Institute of Standards                                                       Computing
           2001 TI-05             and Technology (NIST).                                                 Mandatory           Full 2003       Tested         Performance
                                                                                                                                                            Operations and
                                  Provide the ability to selectively retrieve archived data based on user-                                                  Computing
           2001 TI-06             defined criteria such as date, accounting period, or vendor.                Mandatory      Full 2003       Tested         Performance




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                      Page 31 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                  Requirement Short
    Year               Req. No.                                 Description                                      Status        Test Cycle     Test Status         Process       Test Notes          Name
                                                                                                                                                            Operations and
                                                                                                                                                            Computing
           2001 TI-07             Maintain and report on productivity statistics about application usage. Mandatory          Full 2003       Tested         Performance
                                  Provide audit trails to identify changes made to system parameters                                                        Operations and
                                  and tables that would affect the processing or reprocessing of any                                                        Computing
           2001 TI-08             financial transactions.                                                 Mandatory          Full 2003       Tested         Performance
                                  Provide computing performance metrics, for platforms and systems
                                  environments that the application is certified to run on. Performance
                                  metrics provided by the vendor should describe: Transaction
                                  processing throughput capacity, Expected workstation client response                                       Not            Operations and
                                  time by transaction type, Data storage capacity, and Limitations on                        Not             Tested/Value   Computing
           2001 TI-09             concurrent user connectivity.                                           Value Added        Applicable      Added          Performance
                                                                                                                                             Not            Operations and
                                  Process an agency’s projected accounting activity without impacting                     Not                Tested/Value   Computing
           2001 TI-10             projected on-line response time.                                            Value Added Applicable         Added          Performance
                                  Complete routine batch processing (e.g., backups, nightly interface
                                  processing, core GL posting, table updates, standard reporting, and                                        Not          Operations and
                                  systems assurance) within an agency defined batch-processing                            Not                Tested/Value Computing
           2001 TI-11             window.                                                                     Value Added Applicable         Added        Performance

                                  Maintain the agency’s current and historical financial data (e.g. general                                  Not            Operations and
                                  ledger records, documents, transactions, lines, and vendor records)                   Not                  Tested/Value   Computing
           2001 TI-12             with no degradation to on-line or batch processing performance.           Value Added Applicable           Added          Performance
                                                                                                                                             Not            Operations and
                                  Support concurrent access to functional modules by the agency's                         Not                Tested/Value   Computing
           2001 TI-13             defined user community.                                                     Value Added Applicable         Added          Performance
                                  Disclose processing jobs, steps, and dependencies that are required                                        Not            Operations and
                                  to operate the system on a daily, weekly, monthly, quarterly, and                       Not                Tested/Value   Computing
           2001 TI-14             annual basis.                                                               Value Added Applicable         Added          Performance
                                  Provide the capability to process batched transactions during online                                       Not            Operations and
                                  hours and accept online transactions from interfacing systems with no                   Not                Tested/Value   Computing
           2001 TI-15             on-line performance degradation.                                            Value Added Applicable         Added          Performance
                                  Define the following types of cost objects for accumulation, distribution
                                  and reporting purposes:
                                  •     Accounting classification elements
                                  •     Specific customers, vendors, reimbursable agreements,
                                  contracts, PAs, task orders, work orders, and grants                                                       Not            Cost Setup and
           2006 CMA-01            •     GPRA goals.                                                           Mandatory      Pending         Scheduled      Accumulation                     Define cost objects
                                                                                                                                             Not            Cost Setup and
           2006 CMA-02            Accumulate costs—Accumulate costs and revenue by cost object.               Mandatory      Pending         Scheduled      Accumulation                     Accumulate costs

                                  Costs objects on prepaid expenses—Associate the purchase of fixed
                                  assets and inventory and the payment of advances with related cost
                                  objects so that subsequent expenditures are identified by cost object.
                                                                                                                                             Not            Cost Setup and                   Costs objects on
           2006 CMA-03                                                                                        Mandatory      Pending         Scheduled      Accumulation                     prepaid expenses
                                  Full cost—Accumulate the full cost of cost objects. Full costs include
                                  direct costs, indirect cost allocations, implicit costs (e.g., costs
                                  provided by other government agencies such as pension costs), and                                          Not            Cost Setup and
           2006 CMA-04            unfunded costs (e.g., annual leave costs).                              Mandatory          Pending         Scheduled      Accumulation                     Full cost
                                  Non-financial data—Accumulate non-financial data (e.g., units                                              Not            Cost Setup and
           2006 CMA-05            purchased, units sold) by cost object at the transaction level.         Mandatory          Pending         Scheduled      Accumulation                     Non-financial data
                                  ecording cost distribution entries in GL—Distribute the full cost of                                                                                       Recording cost
                                  goods and services by cost object. Record the cost distribution entries                                    Not                                             distribution entries in
           2006 CMB-01            in the GL.                                                              Mandatory          Pending         Scheduled      Cost Distribution                GL




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                             Page 32 of 79
Financial Systems Integration Office                                                                    Requirements Tested Matrix
                                                                                                      Core Requirements & Test Status

 Requirement                                                                                                                                                                                                         Requirement Short
    Year               Req. No.                                  Description                               Status              Test Cycle     Test Status         Process                  Test Notes                      Name
                                  Attributes on cost distribution—Capture U.S. SGL attributes on cost
                                  distribution entries needed to prepare the Statement of Net Cost. For
                                  example, costs distributed to programs and used in the preparation of
                                  the Statement of Net Cost should retain the Federal/Non-Federal,
                                  Exchange/Non-Exchange, and Custodial/Non-Custodial                                                         Not                                                                    Attributes on cost
           2006 CMB-02            classifications.                                                      Mandatory            Pending         Scheduled      Cost Distribution                                       distribution

                                  Multi-layer overhead distributions—Perform multi-layer overhead
                                  distributions that are agency-defined (at least 3 levels of distribution)                                  Not                                                                    Multi-layer overhead
           2006 CMB-03            using multiple rates and fixed amount allocation methods.                    Mandatory     Pending         Scheduled      Cost Distribution                                       distributions
                                  Re-distribute costs—Re-distribute costs based on revised rates and                                         Not
           2006 CMB-04            allocation amounts.                                                          Mandatory     Pending         Scheduled      Cost Distribution                                       Re-distribute costs
                                  Comparative income statement by cost object—Generate the
                                  Comparative Income Statement by Cost Object. Parameters include
                                  cost object and accounting periods (month and year). Result is a
                                  report that compares month and year-to-date activity to prior month
                                  and prior year-to-date activity, by cost object. The report must list the
                                  following data:
                                  •     Revenue
                                  •     Direct expenses
                                  •     Indirect expenses (overhead)                                                                                                                                                Comparative income
                                  •     Total expenses                                                                                       Not                                                                    statement by cost
           2006 CMC-01            •     Net revenue/cost.                                                      Mandatory     Pending         Scheduled      Cost Distribution                                       object
                                  Cost object income statement—Generate Cost Object Income
                                  Statement. Parameters include any cost object and accounting
                                  period. Result is a report with revenue, direct cost, and indirect cost                                    Not                                                                    Cost object income
           2006 CMC-02            (overhead) by cost object.                                                   Mandatory     Pending         Scheduled      Cost Distribution                                       statement
                                  Cost object audit trail—Maintain an audit trail of transactions from their                                 Not
           2006 CMC-03            origin to the final cost object(s).                                          Mandatory     Pending         Scheduled      Cost Distribution                                       Cost object audit trail
                                                                                                                                                            Treasury
                                                                                                                             Incr.                          Information
           2006 FBA-01            Maintain multiple ALCs.                                                      Mandatory     2005/2006       Tested         Maintenance                                             Multiple ALCs
                                                                                                                                                            Treasury
                                                                                                                             Incr.                          Information
           2006 FBA-02            Define an ALC as a GWA reporter or a non-GWA reporter.                       Mandatory     2005/2006       Tested         Maintenance                                             ALC Type
                                                                                                                                                            Treasury
                                                                                                                             Incr.                          Information                                             ALC Business
           2006 FBA-03            Maintain ALC Business Activities.                                            Mandatory     2005/2006       Tested         Maintenance                                             Activities
                                  Define an ALC's Business Activity as:
                                  •    IPAC only
                                  •    CA$HLINK II only
                                  •    TDO Payments only
                                  •    IPAC and CA$HLINK II
                                  •    IPAC and TDO payments                                                                                                Treasury
2006                              •    TDO payments and CA$HLINK II                                                          Incr.                          Information         Clarification: Corrected the req.   ALC Business
Clarification     FBA-04          •    IPAC, CA$HLINK II, and TDO payments.                                    Mandatory     2005/2006       Tested         Maintenance         short name.                         Acitivity Definition
                                                                                                                                                            Treasury
                                                                                                                             Incr.                          Information                                             GWA Reporter
           2006 FBA-05            Maintain GWA Reporter Categories.                                            Mandatory     2005/2006       Tested         Maintenance                                             Categories
                                  Define the GWA Reporter Category for GWA reporter ALCs as
                                  •    IPAC Only
                                  •    CA$HLINK II Only
                                  •    TDO Payments Only
                                  •    IPAC and CA$HLINK II
                                  •    IPAC and TDO Payments                                                                                                Treasury
2006                              •    TDO Payments and CA$HLINK II, or                                                      Incr.                          Information         Clarification: Corrected the req.   GWA Reporter
Clarification     FBA-06          •    IPAC, CA$HLINK II and TDO Payments.                                     Mandatory     2005/2006       Tested         Maintenance         short name.                         Category Definition




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                     Page 33 of 79
Financial Systems Integration Office                                                                Requirements Tested Matrix
                                                                                                  Core Requirements & Test Status

 Requirement                                                                                                                                                                                                 Requirement Short
    Year               Req. No.                                  Description                              Status            Test Cycle     Test Status         Process                 Test Notes                  Name
                                  Capture the ALC on all transactions that impact the FBWT and are                                                       Treasury
                                  reported to Treasury on the FMS 224, Partial 224, or through the GWA                    Incr.                          Information
           2006 FBA-07            system.                                                              Mandatory          2005/2006       Tested         Maintenance                                        Capture ALC
                                  Maintain valid TAS/BETC combinations as provided by Treasury's                                                         Treasury
                                  SAM for classification of the agency's FBWT transactions in the GWA                                     Not            Information                                        TAS/BETC
           2006 FBA-08            system.                                                              Mandatory          Pending         Scheduled      Maintenance                                        combinations
                                                                                                                                                         Treasury
                                  Capture the TAS/BETC on all transactions that impact the FBWT and                                       Not            Information
           2006 FBA-09            are reported through the GWA system.                                  Mandatory         Pending         Scheduled      Maintenance                                        Capture TAS/BETC
                                  Define transactions that impact the FBWT and are reported on the                                                       Treasury
                                  FMS 224, Partial 224, or through the GWA system as "IPAC",                              Incr.                          Information                                        FBWT transaction
           2006 FBA-10            "CA$HLINK II", "TDO Payments", or "Reclassifications".                Mandatory         2005/2006       Tested         Maintenance                                        types
                                  Capture the "Treasury Document #" on all transactions that impact the                                                                       Clarifications:
                                  FBWT. The Treasury Document Number is the source document                                                                                   1-Added sentence defining
                                  number specified by Treasury on the Agency Confirmation Report                                                         Treasury             Treasury Document Number.
2006                              (ACR), Deposit Ticket/Deposit Voucher Support Listing, IPAC                                             Not            Information          2-Changed IPAC support listing Treasury Document
Clarification     FBA-11          download file, and CASHLINK Report.                                   Mandatory         Pending         Scheduled      Maintenance          to IPAC download file.         Number
                                                                                                                                                         Treasury
                                  Import payment confirmation data from the GOALS II/ IAS RFC                                             Not            Information                                        Payment confirmation
           2006 FBB-01            Agency Link.                                                             Mandatory      Pending         Scheduled      Maintenance                                        data
                                  Liquidate individual disbursement-in-transit transactions and record                                                   Treasury                                           Liquidate
                                  confirmed disbursements upon receipt of payment confirmation from                                       Not            Information                                        disbursements-in-
           2006 FBB-02            the GOALS II IAS RFC Agency Link.                                        Mandatory      Pending         Scheduled      Maintenance                                        transit
                                  Update payments with paid schedule number, confirmed date, and                                                         Treasury
                                  check number or trace number upon receipt of confirmation data from                                     Not            Information                                        Update payment
           2006 FBB-03            the GOALS II IAS RFC Agency Link.                                        Mandatory      Pending         Scheduled      Maintenance                                        information
                                  Assign check numbers to individual payments, based upon the                                                            Treasury
                                  payment schedule's check range received from the GOALS II IAS RFC                                       Not            Information                                        Assign check
           2006 FBB-04            Agency Link.                                                             Mandatory      Pending         Scheduled      Maintenance                                        numbers
                                  Correct system-assigned check numbers on payment records that do                                        Not            Payment
           2006 FBB-05            not match the actual check number assigned by Treasury.                  Mandatory      Pending         Scheduled      Confirmation                                       Correct check number

                                  Assign check numbers to individual payment records when a payment                                       Not            Payment
           2006 FBB-06            schedule has multiple check ranges or a break in check numbers.          Mandatory      Pending         Scheduled      Confirmation                                       Multiple check ranges
                                  Record disbursement cancellations for individual payments that have                                     Not            Payment                                            Disbursement
           2006 FBB-07            not been negotiated.                                                     Mandatory      Pending         Scheduled      Confirmation                                       cancellations
                                  Import the ACR support listing from the GOALS II/IAS RFC Agency
                                  Link to facilitate reconciliation of agency recorded disbursements and                                  Not            Reconciliation and
           2006 FBC-01            cancellations with Treasury.                                             Mandatory      Pending         Scheduled      Reporting                                          Import ACR listing
                                  Compare individual amounts on the ACR support listing with amounts
                                  recorded in the agency's general ledger by schedule number and
                                  accounting period. The accounting period is the fiscal month and year                                   Not            Reconciliation and                                 Compare ACR
           2006 FBC-02            used for financial reporting purposes                                    Mandatory      Pending         Scheduled      Reporting                                          support listing with GL


                                  Generate the GL/ACR Discrepancy Report. Parameter is accounting
                                  period. Result is a report including schedule number, dollar amount,
                                  and confirmed date or transaction date of:
                                  •    Items on the ACR listing and not in the agency's general ledger
                                  •    Items on the ACR listing for a different amount than in the
                                  agency's
                                       general ledger                                                                                     Not            Reconciliation and                                 GL/ACR Discrepancy
           2006 FBC-03            •    Items in the agency's general ledger and not on the ACR listing.    Mandatory      Pending         Scheduled      Reporting                                          Report
                                  Import IPAC support listing from the GOALS II/IAS to facilitate                                         Not            Reconciliation and                                 Import IPAC support
           2006 FBC-04            reconciliation of agency recorded IPAC transactions with Treasury.       Mandatory      Pending         Scheduled      Reporting                                          listing

                                  Compare IPAC transactions on the IPAC support listing with IPAC                                         Not            Reconciliation and                                 Compare IPAC
           2006 FBC-05            transactions recorded in the agency's general ledger.                    Mandatory      Pending         Scheduled      Reporting                                          support listing with GL


Printed on 5/20/2010                                                                                93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                               Page 34 of 79
Financial Systems Integration Office                                                                Requirements Tested Matrix
                                                                                                  Core Requirements & Test Status

 Requirement                                                                                                                                                                                                     Requirement Short
    Year               Req. No.                                Description                                    Status        Test Cycle     Test Status         Process                  Test Notes                     Name

                                  Generate the GL/IPAC Discrepancy Report. Parameter is the
                                  accounting period. Result is report including document reference
                                  number (from IPAC Support Listing), dollar amount, and audit date or
                                  transaction date of:
                                  •      Items on the IPAC support listing and not in the agency's general
                                  ledger
                                  •      Items on the IPAC support listing for a different amount than in
                                  the agency's general ledger
                                  •      Items in the agency's general ledger and not on the IPAC support                                 Not            Reconciliation and                                     GL/IPAC Discrepancy
           2006 FBC-06            listing.                                                                 Mandatory      Pending         Scheduled      Reporting                                              Report
                                  Import DT/DV support listing—Import the Monthly DT/DV support
                                  listing from the GOALS II/ IAS to facilitate reconciliation of agency                                   Not            Reconciliation and                                     Import DT/DV support
           2006 FBC-07            recorded deposits and debit vouchers with Treasury.                      Mandatory      Pending         Scheduled      Reporting                                              listing
                                  Compare individual amounts on the DT/DV support listing with
                                  amounts recorded in the agency's general ledger by document                                             Not            Reconciliation and                                     Compare DT/DV
           2006 FBC-08            number and accounting period.                                            Mandatory      Pending         Scheduled      Reporting                                              support listing with GL
                                  Generate the GL Deposit Ticket/Debit Voucher Discrepancy Report.
                                  Parameter is the accounting period. Result is a report including
                                  document number (Deposit Ticket or Debit Voucher number), dollar
                                  amount, and document date of:
                                  •      Items on the DT/DV support listing and not in the agency's
                                  general ledger
                                  •      Items on the DT/DV support listing for a different amount than in
                                  the agency's general ledger
                                  •      Items in the agency's general ledger and not on the DT/DV
                                  support listing.                                                                                        Not            Reconciliation and                                     GL/DT/DV
           2006 FBC-09                                                                                     Mandatory      Pending         Scheduled      Reporting                                              Discrepancy Report
                                  Generate the FMS 224 Report. Parameter is the accounting period.
                                  Result is the FMS 224, Statement of Transactions, for non-GWA
                                  reporting ALC's. Generate the report in both hard copy and electronic                   Incr.                          Reconciliation and
           2006 FBC-10            formats required by the Department of the Treasury.                      Mandatory      2005/2006       Tested         Reporting                                              FMS 224 Report

                                  Generate the FMS Partial 224 Report. Parameters are ALC and
                                  accounting period. Result is the FMS Partial 224 for transactions
                                  associated with the ALC's Business Activity (IPAC, CA$HLINK II, TDO
                                  Payments) and not reported through the GWA system, and
2006                              Reclassification transactions. Generate the report in both hard copy                    Incr.                          Reconciliation and   Clarification: Deleted some of
Clarification     FBC-11          and electronic formats required by the Department of Treasury.          Mandatory       2005/2006       Tested         Reporting            the required report parameters.   Partial 224 Report
                                  Generate the SF1219/1220 statements. Parameter is accounting
                                  period. Result is SF 1219/1220, Statement of Accountability/
                                  Transactions in both hard copy and electronic formats required by the                                   Not            Reconciliation and                                     1219/1220
           2006 FBC-12            Department of Treasury.                                                 Mandatory       Pending         Scheduled      Reporting                                              Statements
                                  Generate the FMS 224 Transaction Detail Report. Parameter is the
                                  accounting period. Result is a report listing the detailed transactions
                                  supporting each TAS total reported in each section of the FMS 224.
                                  Detailed transactions must include:
                                  •    ALC
                                  •    TAS
                                  •    Transaction amount
                                  •    Confirmation date
                                  •    Transaction document number or Treasury document number.                                                                                                                 FMS 224 Cash
                                  Separate report totals for disbursement and receipt activity by ALC                     Incr.                          Reconciliation and                                     Transaction Detail
           2006 FBC-13            and TAS must be provided.                                               Mandatory       2005/2006       Tested         Reporting                                              Report




Printed on 5/20/2010                                                                                93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                  Page 35 of 79
Financial Systems Integration Office                                                                  Requirements Tested Matrix
                                                                                                    Core Requirements & Test Status

 Requirement                                                                                                                                                                                  Requirement Short
    Year               Req. No.                                   Description                                   Status        Test Cycle     Test Status         Process        Test Notes          Name
                                  Partial 224 Transaction Detail Report—Generate the Partial 224
                                  Transaction Detail Report. Parameter is the accounting period.
                                  Result is a report listing the detailed transactions supporting each TAS
                                  total reported in each section of the Partial 224. Detailed transactions
                                  must include:
                                  •     ALC
                                  •     TAS
                                  •     Transaction amount
                                  •     Confirmation date
                                  •     Transaction document number or Treasury document number.
                                  Separate report totals for disbursement and receipt activity by ALC
                                  and TAS must be provided.                                                                                                                                  Partial 224
                                                                                                                            Incr.                          Reconciliation and                Transaction Detail
           2006 FBC-14                                                                                       Mandatory      2005/2006       Tested         Reporting                         Report
                                  Generate a Partial 224 Exception Report. Parameter is accounting
                                  period. Result is a list of the FBWT transactions that were posted to
                                  an ALC, but are ineligible for inclusion on the P224 based on the
                                  ALC's business activity. Transactions must include:
                                  •      ALC
                                  •      TAS
                                  •      Transaction amount
                                  •      Confirmation date                                                                  Incr.                          Reconciliation and                Partial 224 Exception
           2006 FBC-15            •      Document number.                                                    Mandatory      2005/2006       Tested         Reporting                         Report
                                  Generate the Cash Forecasting Report. Result is a report with
                                  payment and deposit amounts at a detail suitable for reporting large
                                  dollar notifications as described in I TFM-6-8500, Cash Forecasting                                       Not            Reconciliation and                Cash Forecasting
           2006 FBC-16            Requirements.                                                              Mandatory      Pending         Scheduled      Reporting                         Report
                                  Capture financial operating plans for any funded organization level or                                    Not                                              Financial operating
           2006 FMA-01            other accounting classification.                                           Mandatory      Pending         Scheduled      Budget Planning                   plans
                                  Capture spending plans for any funded organization level or other                                         Not
           2006 FMA-02            accounting classification.                                                 Mandatory      Pending         Scheduled      Budget Planning                   Spending plans
                                  Capture financial operating and spending plans by month, quarter and                                      Not
           2006 FMA-03            year.                                                                      Mandatory      Pending         Scheduled      Budget Planning                   Plan periods
                                  Export financial operating and spending plan data at the accounting                                       Not
           2006 FMA-04            line item level in an Excel or ASCII text delimited file format.           Mandatory      Pending         Scheduled      Budget Planning                   Export plan data
                                  Generate plan results based on multiple measures including fixed                                          Not
                                  dollar amounts, unit costs, cost allocations, labor hours or full-time                 Not                Tested/Value
           2006 FMA-05            equivalents (FTEs).                                                        Value Added Applicable         Added          Budget Planning                   Plan measurements
                                                                                                                                            Not
                                                                                                                         Not                Tested/Value
           2006 FMA-06            Maintain current and multiple historical versions of plans.                Value Added Applicable         Added          Budget Planning                   Plan versions
                                                                                                                                            Not
                                  Compare multiple versions of plans.                                                    Not                Tested/Value
           2006 FMA-07                                                                                       Value Added Applicable         Added          Budget Planning                   Compare plans
                                                                                                                                            Not
                                  Maintain financial operating and spending plans for future periods (i.e.,             Not                 Tested/Value
           2006 FMA-08            future fiscal years).                                                     Value Added Applicable          Added          Budget Planning                   Future plans
                                                                                                                                            Not
                                  Activate future period plans based on a specified plan start date or on-             Not                  Tested/Value
           2006 FMA-09            demand.                                                                  Value Added Applicable           Added          Budget Planning                   Plan activation
                                                                                                                                            Not
                                                                                                                         Not                Tested/Value
           2006 FMA-10            Compare planned spending to actual spending.                               Value Added Applicable         Added          Budget Planning                   Planned to actual
                                                                                                                                            Not
                                  Classify budget projections using accounting classification elements                   Not                Tested/Value
           2006 FMB-01            (e.g., Apportionment categories, Authority type, etc.).                    Value Added Applicable         Added          Budget Preparation                Budget information




Printed on 5/20/2010                                                                                  93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                               Page 36 of 79
Financial Systems Integration Office                                                                 Requirements Tested Matrix
                                                                                                   Core Requirements & Test Status

 Requirement                                                                                                                                                                                 Requirement Short
    Year               Req. No.                                Description                                     Status        Test Cycle     Test Status        Process         Test Notes          Name
                                                                                                                                           Not
                                  Import budget formulation data (e.g., Presidential/OMB pass backs,                  Not                  Tested/Value                                     Import budget
           2006 FMB-02            congressional markup documents, and internal agency decisions).         Value Added Applicable           Added          Budget Preparation                formulation data
                                                                                                                                           Not
                                  Calculate prior year budgets, actual spending amounts and variances                 Not                  Tested/Value                                     Calculate prior year
           2006 FMB-03            at the line item level.                                                 Value Added Applicable           Added          Budget Preparation                budget data
                                                                                                                                           Not
                                  Export prior year budgets, actual spending and variances at the line                     Not             Tested/Value                                     Export prior year
           2006 FMB-04            item level in an excel or ASCII text delimited file format.              Value Added     Applicable      Added          Budget Preparation                budget data
                                  Generate projected future period obligations, income, and                                                Not
                                  expenditures at any level of the organizational structure based on prior                 Not             Tested/Value
           2006 FMB-05            year actual activity using agency-defined projection rates.              Value Added     Applicable      Added          Budget Preparation                Projected activity
                                                                                                                                           Not
                                  Define projection rates (e.g., 90%, 100%, 110%) by budget object                    Not                  Tested/Value                                     Define projection
           2006 FMB-06            class for use in budget formulation.                                    Value Added Applicable           Added          Budget Preparation                rates
                                                                                                                                           Not
                                  Calculate budget amounts for all, selected groups, or individual budget             Not                  Tested/Value
           2006 FMB-07            line items based on agency-defined projection rates.                    Value Added Applicable           Added          Budget Preparation                Apply projection rates
                                                                                                                                           Not
                                  Generate multiple budgets based on alternative agency-specified                     Not                  Tested/Value
           2006 FMB-08            accounting structures, funding levels, and spending criteria.           Value Added Applicable           Added          Budget Preparation                What if analysis
                                                                                                                                           Not
                                  Generate payroll forecasts (i.e., anticipated compensation and                      Not                  Tested/Value
           2006 FMB-09            benefits) at the object class and individual employee level.            Value Added Applicable           Added          Budget Preparation                Payroll forecasts
                                                                                                                                           Not
                                                                                                                      Not                  Tested/Value                                     Modified payroll
           2006 FMB-10            Generate modified payroll forecasts.                                    Value Added Applicable           Added          Budget Preparation                forecasts
                                                                                                                                           Not
                                                                                                                      Not                  Tested/Value
           2006 FMB-11            Generate overhead projections using agency defined overhead rates.      Value Added Applicable           Added          Budget Preparation                Projected overhead
                                                                                                                                           Not
                                  Import budget formulation data submitted in Excel or ASCII text                     Not                  Tested/Value                                     Import budget
           2006 FMB-12            delimited format.                                                       Value Added Applicable           Added          Budget Preparation                information
                                  Import budget submission guidance, other narrative text and briefing                                     Not
                                  material written using common PC desktop applications (e.g., MS                     Not                  Tested/Value                                     Import budget
           2006 FMB-13            Word).                                                                  Value Added Applicable           Added          Budget Preparation                submission guidance
                                                                                                                                           Not
                                                                                                                      Not                  Tested/Value                                     Distribute budget
           2006 FMB-14            Distribute budget submission guidance electronically.                   Value Added Applicable           Added          Budget Preparation                submission guidance
                                                                                                                                           Not
                                  Generate budget information for multiple budget cycles (e.g. monthly,               Not                  Tested/Value
           2006 FMB-15            quarterly, semi-annual, and yearly).                                    Value Added Applicable           Added          Budget Preparation                Budget cycles
                                                                                                                                           Not
                                  Associate budget formulation line items to the agency’s stated goals                Not                  Tested/Value                                     Budget and GPRA
           2006 FMB-16            and objectives required by GPRA.                                        Value Added Applicable           Added          Budget Preparation                goals
                                  Generate budget formulation information for all categories on which                                      Not
                                  legally binding budgetary decisions are made (e.g., appropriation                   Not                  Tested/Value
           2006 FMB-17            limitations).                                                           Value Added Applicable           Added          Budget Preparation                Budget information
                                  Generate budget formulation information for administrative purposes
                                  as in the nature of policy guidance and decision making (e.g.,                                           Not
                                  Presidential/OMB pass backs, congressional markup documents, or                     Not                  Tested/Value                                     Administrative budget
           2006 FMB-18            internal agency decisions).                                             Value Added Applicable           Added        Budget Preparation                  information
                                                                                                                                           Not
                                                                                                                      Not                  Tested/Value
           2006 FMB-19            Capture SF-132 Schedule data by TAFS.                                   Value Added Applicable           Added        Budget Preparation                  SF 132 TAFS data
                                                                                                                                           Not
                                  Export SF-132 Schedules for each TAFS requiring apportionment in                    Not                  Tested/Value                                     Export SF 132
           2006 FMB-20            Excel file format specified by OMB.                                     Value Added Applicable           Added        Budget Preparation                  Schedules


Printed on 5/20/2010                                                                                 93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                               Page 37 of 79
Financial Systems Integration Office                                                                       Requirements Tested Matrix
                                                                                                         Core Requirements & Test Status

 Requirement                                                                                                                                                                                                            Requirement Short
    Year               Req. No.                                Description                                           Status        Test Cycle     Test Status         Process                  Test Notes                     Name
                                  Record funding based on related budget execution documents (e.g.,                                              Not                                                                   Budget execution
           2006 FMC-01            appropriation warrants and apportionments).                                    Mandatory       Pending         Scheduled      Budget Authority                                       documents

                                  Capture fund specific information (e.g., public law, program, authority                                        Not                                                                   Budget execution
           2006 FMC-02            type, apportionment category, etc.) on budget execution documents.             Mandatory       Pending         Scheduled      Budget Authority                                       documents data
                                  Record budgetary authority (defined in OMB Circular A-11) including
                                  direct appropriations, borrowing authority, contract authority, and                                            Not                                                                   Budget authority
           2006 FMC-03            spending authority from offsetting collections.                                Mandatory       Pending         Scheduled      Budget Authority                                       types

                                  Capture multiple internal fund codes based on a single apportionment schedule,
2006                              ensuring that unique fund characteristics (e.g. direct or reimbursable indicator,                              Not                                 Clarification: Changed the fund   Internal funds control
Clarification     FMC-04          BEA category, apportionment category) are available for funds control purposes. Mandatory      Pending         Scheduled      Budget Authority     characteristic examples.          document
                                  Record changes to budget authority including reductions; rescissions;
                                  amounts withheld or made unavailable; supplementals, transfers;
                                  reprogramming; legal limitations and changes to continuing                                                     Not                                                                   Changes to budget
           2006 FMC-05            resolutions.                                                          Mandatory                Pending         Scheduled      Budget Authority                                       authority
                                  Record the expiration and cancellation of budget authority in                                                  Not                                                                   Expirations of budget
           2006 FMC-06            accordance with OMB Circular A-11.                                    Mandatory                Pending         Scheduled      Budget Authority                                       authority
                                                                                                                                                 Not                                                                   Continuing
           2006 FMC-07            Record multiple, successive continuing resolutions.                            Mandatory       Pending         Scheduled      Budget Authority                                       resolutions
                                  Capture the start and end dates, amount, and public law number of a                                            Not
           2006 FMC-08            continuing resolution.                                                         Mandatory       Pending         Scheduled      Budget Authority                                       CR effective dating
                                  Record amendments to the amount and/or effective dates of an                                                   Not
           2006 FMC-09            existing Continuing Resolution.                                                Mandatory       Pending         Scheduled      Budget Authority                                       CR amendments
                                  Establish contracts, work orders and projects and associate related activity
2006                              (advances, prepayments and reimbursements) so that balances are maintained                                     Not                                 Clarification: Re-worded the
Clarification     FMC-10          and queries show all related activity.                                       Mandatory         Pending         Scheduled      Budget Authority     requirement to be more specific. Revolving funds
                                  Calculate available fund balances based on reimbursable agreement                                              Not                                                                  Reimbursable
           2006 FMC-11            authority.                                                                     Mandatory       Pending         Scheduled      Budget Authority                                      authority

2006                              Prevent the use of funds against reimbursable agreements with the public and                                   Not                                 Clarification: Added a sentence
Clarification     FMC-12          other non-federal entities without an advance. Allow for override.             Mandatory       Pending         Scheduled      Budget Authority     allowing for override.            Advance funding edit
                                  Record apportioned funds in accordance with the latest OMB                                                     Not                                                                   SF 132
           2006 FMC-13            approved SF 132 Apportionment and Reapportionment Schedule.                    Mandatory       Pending         Scheduled      Budget Authority                                       apportionment data
                                  Capture legal (statutory) and administrative (agency imposed)                                                  Not
           2006 FMD-01            limitations on the use of funds.                                               Mandatory       Pending         Scheduled      Funds Distribution                                     Limitations
                                  Record allotments, sub-allotments, allocations and allowances (i.e.
                                  distribute funds) to multiple organizational levels or other elements of                                       Not
           2006 FMD-02            accounting classification.                                                     Mandatory       Pending         Scheduled      Funds Distribution                                     Fund distributions
                                  Record up to eight levels of funds distribution including levels used for                                      Not                                                                   Fund distribution
           2006 FMD-03            appropriation and apportionment of budget authority.                           Mandatory       Pending         Scheduled      Funds Distribution                                     levels
                                  Prevent the distribution of funds in excess of the amount of funds                                             Not                                                                   Fund distribution
           2006 FMD-04            available at the next highest distribution level.                              Mandatory       Pending         Scheduled      Funds Distribution                                     availability
                                  Record the modification of funding distributions at multiple
                                  organizational levels or elements of the accounting classification                                             Not                                                                   Fund distribution
           2006 FMD-05            structure.                                                                     Mandatory       Pending         Scheduled      Funds Distribution                                     modification
                                  Record the withdrawal (or cancellation) of unobligated allotments and                                                                                                                Withdrawal of
                                  sub-allotments (both expired and unexpired) for all or selected TAFS                                           Not                                                                   unobligated funds by
           2006 FMD-06            at the end of a fiscal period or on demand as in rescissions.                  Mandatory       Pending         Scheduled      Funds Distribution                                     TAFS

                                  Record the withdrawal (or cancellation) of unobligated allotments and                                                                                                                Withdrawal of
                                  sub-allotments (both expired and unexpired) for selected organizations                                         Not                                                                   unobligated funds by
           2006 FMD-07            at the end of a specific fiscal period or on demand as in rescissions. Mandatory               Pending         Scheduled    Funds Distribution                                       organization
                                                                                                                                                 Not
                                  Update allotments, sub-allotments, allocations and legal and                               Not                 Tested/Value                                                          Plan-based funding
           2006 FMD-08            administrative limitations based on changes to operating plans.                Value Added Applicable          Added        Funds Distribution                                       updates
                                                                                                                                                 Not
                                  Generate allotment and sub-allotment information with sufficient detail             Not                        Tested/Value
           2006 FMD-09            to support funds control.                                               Value Added Applicable                 Added        Funds Distribution                                       Generated allotments


Printed on 5/20/2010                                                                                       93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                  Page 38 of 79
Financial Systems Integration Office                                                                          Requirements Tested Matrix
                                                                                                            Core Requirements & Test Status

 Requirement                                                                                                                                                                                                               Requirement Short
    Year               Req. No.                                     Description                                         Status        Test Cycle     Test Status         Process                    Test Notes                   Name
                                                                                                                                                    Not
                                  Distribute system-generated allotment and sub-allotment information                           Not                 Tested/Value
           2006 FMD-10            electronically to subordinate organizations.                                      Value Added Applicable          Added          Funds Distribution                                     Distribute allotments
                                                                                                                                                    Not
                                  Capture requests for reprogramming of funds or additional funds                               Not                 Tested/Value                                                          Reprogramming
           2006 FMD-11            outside the formal budget process.                                                Value Added Applicable          Added          Funds Distribution                                     requests
                                                                                                                                                    Not
                                  Capture submitted, reviewed and approved status information on re-                            Not                 Tested/Value                                                          Reprogramming
           2006 FMD-12            programming requests.                                                             Value Added Applicable          Added          Funds Distribution                                     request status
                                                                                                                                                    Not                                                                   Record
                                  Record budget authority changes based upon approval of                                        Not                 Tested/Value                                                          reprogramming
           2006 FMD-13            reprogramming requests.                                                           Value Added Applicable          Added          Funds Distribution                                     requests
                                  Monitor the use of funds at each organizational level and other
                                  accounting classification to which budget authority is distributed.
                                  Reject, warn or inform the agency by spending document line when                                                  Not
           2006 FME-01            distributed authority is exceeded.                                                Mandatory       Pending         Scheduled      Funds Control                                          Monitor use of funds
                                                                                                                                                                                        Clarification: Changed
2006                              Process spending documents that affect the availability and/or status of funds,                                   Not                                 "availability" to "availability
Clarification     FME-02          including commitments, obligtions, advances and expenditures.                     Mandatory       Pending         Scheduled      Funds Control        and/or status" of funds.          Spending documents
                                  Record spending transactions, including commitments, obligations,
                                  advances and expenditures, at or below the level in the accounting                                                Not                                                                   Spending
           2006 FME-03            classification than they are budgeted.                                            Mandatory       Pending         Scheduled      Funds Control                                          transactions
                                  Record transactions against prior year funds, both expired and                                                    Not
           2006 FME-04            unexpired, in the current year.                                                   Mandatory       Pending         Scheduled      Funds Control                                          Prior year funds
                                  Monitor amounts paid out of current year funds to cover obligations
                                  made against a cancelled account (TAFS). Prevent payments that
                                  cumulatively exceed 1 percent of the current year appropriation or the                                            Not                                                                   Closed account
           2006 FME-05            total amount available prior to close of the original appropriation.              Mandatory       Pending         Scheduled      Funds Control                                          payments
                                  Capture accounting classification information on commitments,
                                  obligations, advances, and expenditures at the accounting line item                                               Not                                                                   Spending document
           2006 FME-06            level.                                                                            Mandatory       Pending         Scheduled      Funds Control                                          classification
                                  Maintain a history of changes made to commitment, obligation,                                                     Not                                                                   Historical spending
           2006 FME-07            advance, and expenditure documents.                                               Mandatory       Pending         Scheduled      Funds Control                                          data
                                                                                                                                                                                        Clarifications:
                                                                                                                                                                                        1-Changed document line to
                                                                                                                                                                                        accounting line.
2006                              Maintain open documents to show the status of commitments, obligations,                                           Not                                 2-Changed disbursements to        Open spending
Clarification     FME-08          advances, accruals and disbursements-in-transit by accounting line item.          Mandatory       Pending         Scheduled      Funds Control        disbursements-in-transit..        document detail
                                                                                                                                                    Not                                                                   Validate funds
           2006 FME-09            Validate funds availability prior to recording spending transactions.             Mandatory       Pending         Scheduled      Funds Control                                          availability
                                  Derive funds availability based on the budget fiscal year of the
                                  originating document, i.e., whether funds cited are unexpired, expired,                                                                                                                 Use of unexpired,
                                  or cancelled. Record U.S. SGL prescribed general ledger entries when                                              Not                                                                   expired or cancelled
           2006 FME-10            de-obligation of expired funding occurs.                                          Mandatory       Pending         Scheduled      Funds Control                                          funds
                                  Validate period of availability. Prevent the allotment and reuse of de-                                           Not                                                                   Reuse of de-obligated
           2006 FME-11            obligated balances for new obligations in expired funds.                          Mandatory       Pending         Scheduled      Funds Control                                          funds
                                  Update balances used for funds controls to reflect changes in the
                                  status and amounts of commitments, obligations, expenditure and                                                   Not
           2006 FME-12            available balances.                                                               Mandatory       Pending         Scheduled      Funds Control                                          Fund control updates
                                  Monitor the use of funds against financial operating and spending                                                 Not
           2006 FME-13            plans.                                                                            Mandatory       Pending         Scheduled      Funds Control                                          Monitor plans
                                  Monitor the use of funds against legal (statutory) and administrative                                             Not
           2006 FME-14            (agency imposed).                                                                 Mandatory       Pending         Scheduled      Funds Control                                          Monitor limitations
                                  Monitor the use of funds against specific object class limitations.                                               Not                                                                   Monitor object class
           2006 FME-15                                                                                              Mandatory       Pending         Scheduled      Funds Control                                          limitations
                                                                                                                                                    Not                                                                   Monitor reimbursable
           2006 FME-16            Monitor spending against reimbursable agreement amounts.          Mandatory                       Pending         Scheduled      Funds Control                                          agreements
                                  Reduce reimbursable authority and reimbursable agreement balances                                                 Not                                                                   Reduce reimbursable
           2006 FME-17            when customer orders are recorded.                                Mandatory                       Pending         Scheduled      Funds Control                                          balance


Printed on 5/20/2010                                                                                          93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                    Page 39 of 79
Financial Systems Integration Office                                                                         Requirements Tested Matrix
                                                                                                           Core Requirements & Test Status

 Requirement                                                                                                                                                                                                            Requirement Short
    Year               Req. No.                                Description                                              Status       Test Cycle     Test Status        Process               Test Notes                       Name
                                  Monitor the use of funds against contracts, work-orders, task orders,                                            Not
           2006 FME-18            and grants.                                                                      Mandatory       Pending         Scheduled      Funds Control                                        Monitor contracts
                                                                                                                                                   Not
           2006 FME-19            Capture a suggested vendor on commitment documents.               Mandatory                      Pending         Scheduled      Funds Control                                        Suggested vendor
                                  Close commitment documents and document lines under the following
                                  circumstances:
                                      •   By the system upon issuance of an obligating document
                                      •   By an authorized user                                                                                    Not
           2006 FME-20                •   As part of the year-end pre-closing process.              Mandatory                      Pending         Scheduled      Funds Control                                        Close commitments
                                  Capture the following additional data elements on obligating documents:
                                  •    Obligation type
                                  •    Prompt pay indicator and type, or payment terms (including discount terms)
                                  •    Fast Pay indicator
                                  •    Matching terms (2-way, 3-way, 4-way)
                                  •    Vendor ID number
                                  •    Vendor name (legal, DBA or division)
                                                                                                                                                                                  Clarifications:
                                  •    Vendor DUNS (BPN) number                                                                                                                   1-Deleted SIC code as required
                                  •    DUNS + 4 number                                                                                                                            data.
2006                              •    NAICS code                                                                                                  Not                            2-Added DUNS (BPN) number Obligating document
Clarification     FME-21          •    Approval date.                                                                  Mandatory   Pending         Scheduled      Funds Control   as required data.              data
                                  Define agency-specific obligation types to identify the activity which initiated the
2006                              obligation, such as: travel order, purchase order, grant, task order, work order,                                Not                            Clarification: Deleted budget        Define obligation
Clarification     FME-22          and BPA call.                                                                        Mandatory   Pending         Scheduled      Funds Control   object class example.                types
2006                              Validate that the vendor name on an obligation is the same as the vendor name                                    Not                            Clarification: Added sentence        Validate CCR vendor
Clarification     FME-23          on the vendor file, for registered CCR vendors. Allow for override.           Mandatory          Pending         Scheduled      Funds Control   allowing for override.               name on obligations
                                                                                                                                                   Not                                                                 No related
           2006 FME-24            Record obligations when there is no related commitment.                 Mandatory                Pending         Scheduled      Funds Control                                        commitment
                                  Capture a different vendor on an obligating document than the vendor                                             Not
           2006 FME-25            captured on a referenced commitment.                                    Mandatory                Pending         Scheduled      Funds Control                                        Different vendors
                                  Close obligation documents under the following
                                  circumstances:
                                  •     By the system upon final payment for goods or services, or
                                  •     By an authorized user.
                                  Upon the closing of an obligation, classify any de-obligation of excess
                                  funds by budgetary status (i.e., expired, unexpired, available for
                                  obligation or unavailable).                                                                                      Not
           2006 FME-26                                                                                    Mandatory                Pending         Scheduled      Funds Control                                        Close obligations
                                  Process, track, and control records of call against blanket purchase                                             Not
           2006 FME-27            agreements.                                                             Mandatory                Pending         Scheduled      Funds Control                                        Records of call
                                                                                                                                                   Not
           2006 FME-28            Process, track, and control delivery orders against contract limitations.        Mandatory       Pending         Scheduled      Funds Control                                        Delivery orders
                                  Record advance payments made, such as travel advances, contract
                                  prepayments, and grant advances. When recording an advance
2006                              payment, reference an obligating document and bring forward all                                                  Not
Clarification     FME-29          accounting information.                                                          Mandatory       Pending         Scheduled      Funds Control   Deleted unnecessary last sentence.   Advance payments
2006                              Record advance payment refunds by document or accounting line                                                    Not                            Clarification: Changed document line Expenditures against
Clarification     FME-30          item. Update the advance balance.                                                Mandatory       Pending         Scheduled      Funds Control   to accounting line.                  advances
                                  Record expenditures incurred against advance payments made,
                                  reducing the advance balance and liquidating the referenced                                                      Not
           2006 FME-31            obligation.                                                                      Mandatory       Pending         Scheduled      Funds Control                                        Expenditures incurred
                                  Capture the following other data fields on obligating documents:
                                  •      Requester's name
                                  •      Telephone number of requester
                                  •      Deliver to location (e.g., room number, division)
                                  •      Contact name
                                  •      COTR name                                                                                                 Not
                                  •      COTR telephone number                                                                 Not                 Tested/Value                                                        Additional obligation
           2006 FME-32            •      Comments.                                                                 Value Added Applicable          Added        Funds Control                                          data



Printed on 5/20/2010                                                                                         93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                Page 40 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                             Requirement Short
    Year               Req. No.                                   Description                                    Status        Test Cycle     Test Status        Process   Test Notes          Name
                                  Generate the Status of Funds Report. Parameter is the accounting
                                  period. Result is a report providing the following information for each
                                  allotment recorded by the agency:
                                  •      Accounting classification elements
                                  •      Total Allotment
                                  •      Commitments
                                  •      Obligations
                                  •      Expenditures
                                  •      Available Balance
                                  Available balance must equal the GL balance in the 4610 or 4620
                                  account. Amounts should be cumulative from the beginning of the
                                  fiscal year through the accounting period specified. If reporting for the
                                  current period, amounts must be cumulative up through the current                                          Not                                        Status of Funds
           2006 FMF-01            date.                                                                       Mandatory      Pending         Scheduled      Funds Status                Report
                                  Query budget information. Parameters include accounting
                                  classifications. Result is budgetary authority amounts (all types, as
                                  applicable to the fund type), spending activity (e.g., obligations,
                                  expenditures), and the available balance. Displayed amounts should
                                  be consistent with amounts derived using the U.S. SGL crosswalk to                                         Not
           2006 FMF-02            the SF-133.                                                                 Mandatory      Pending         Scheduled      Funds Status                Budget query
                                  Generate a contract/BPA activity report. Parameters include
                                  contract/BPA number accounting period and period covered (monthly,
                                  quarterly, fiscal year-to-date, or inception-to-date). Result is list of
                                  accounting activity (obligations, expenditures, disbursements, etc.)
                                  under the contract/BPA, with vendor information, period of
                                  performance, document numbers, delivery order/task order numbers,
                                  accounting classification information, transaction dates and amounts.
                                  Sorting options include transaction date, document type and                                                Not                                        Contract/BPA Activity
           2006 FMF-03            accounting classification.                                                  Mandatory      Pending         Scheduled      Funds Status                Report
                                  Generate a reimbursable agreement activity report. Parameters
                                  include reimbursable agreement number, accounting period and
                                  period covered (monthly, quarterly, fiscal year-to-date, or inception-to-
                                  date). Result is a list of accounting activity (commitments, obligations,
                                  advances, expenditures, etc.) under the reimbursable agreement, with
                                  customer/vendor information, period of performance, document
                                  numbers, accounting classification information, transaction dates and                                                                                 Reimbursable
                                  amounts. Sorting options include transaction date, document type and                                       Not                                        Agreement Activity
           2006 FMF-04            accounting classification.                                                  Mandatory      Pending         Scheduled      Funds Status                Report
                                  Query status of funds. Parameters include accounting period, and
                                  allotment accounting classification. Result is a display providing the
                                  following information:
                                  •      Accounting classification elements
                                  •      Total Allotment
                                  •      Commitments
                                  •      Obligations
                                  •      Expenditures
                                  •      Available Balance (available balance must equal the balance in
                                  the 4610 or 4620 account).
                                  Drill down from the commitments line, obligations line, and the
                                  expenditures line to the detailed transactions, documents, and                                             Not                                        Status of Funds
           2006 FMF-05            document detail that support these lines.                                   Mandatory      Pending         Scheduled      Funds Status                Query
                                  Validate that funds availability balances used for funds control and                                       Not                                        System assurance for
           2006 FMF-06            funds status reporting agree with the general ledger.                       Mandatory      Pending         Scheduled      Funds Status                funds availability
                                  Maintain budget data needed to support OMB’s MAX A-11 system
                                  requirements that agencies currently fulfill via their FACTS II                                            Not
           2006 FMF-07            submissions to FMS.                                                         Mandatory      Pending         Scheduled      Funds Status                MAX budget data




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                        Page 41 of 79
Financial Systems Integration Office                                                                    Requirements Tested Matrix
                                                                                                      Core Requirements & Test Status

 Requirement                                                                                                                                                                                 Requirement Short
    Year               Req. No.                                  Description                                      Status        Test Cycle     Test Status        Process      Test Notes          Name
                                  Generate Excel files that are consistent with the presentation of the                                       Not
                                  program and financing schedule and the object class schedule                             Not                Tested/Value                                  MAX budget data
           2006 FMF-08            published in OMB Circular A-11.                                              Value Added Applicable         Added          Funds Status                   reporting
                                  Notify the agency when funds availability is reduced based on the                                           Not                                           Funds availability
                                  processing of agency-specified transaction types or sources (e.g.,                       Not                Tested/Value                                  notification by
           2006 FMF-09            credit card payments and payroll).                                           Value Added Applicable         Added          Funds Status                   exception
                                  Notify the agency when funds availability by TAFS or internal fund                                          Not
                                  code reaches a pre-defined percent of the original total funding                            Not             Tested/Value                                  Funds availability
           2006 FMF-10            amount.                                                                      Value added    Applicable      Added          Funds Status                   notification by percent
                                                                                                                                              Not
                                  Generate Excel files that are consistent with the presentation of                           Not             Tested/Value                                  Other MAX Budget
           2006 FMF-11            budget schedules published in OMB Circular A-11.                             Value added    Applicable      Added          Funds Status                   Data Reporting
                                  Maintain a chart of accounts consistent with the U.S. SGL Chart of
                                  Accounts, including the proprietary, budgetary, and memorandum                                              Not            GL Account
           2006 GLA-01            accounts, basic numbering structure, and account titles.                     Mandatory      Pending         Scheduled      Definition                     Chart of accounts
                                  Maintain an association between the chart of accounts and valid
                                  attribute domain values used for Treasury reporting (e.g., FACTS I,                                         Not            GL Account
           2006 GLA-02            FACTS II and GFRS reporting).                                                Mandatory      Pending         Scheduled      Definition                     Account attributes
                                  Define specific GL accounts as control accounts for purposes of                                             Not            GL Account
           2006 GLA-03            tracking activity in subsidiary ledgers.                                     Mandatory      Pending         Scheduled      Definition                     Control accounts
                                  Define agency-specific GL sub-accounts that summarize to U.S. SGL                                           Not            GL Account
           2006 GLA-04            accounts.                                                                    Mandatory      Pending         Scheduled      Definition                     Sub-accounts
                                  Accommodate an additional 2 digits beyond the U.S. SGL account for                                          Not            GL Account
           2006 GLA-05            agency-specific GL sub-accounts.                                             Mandatory      Pending         Scheduled      Definition                     Sub-account length
                                  Define agency-specific memorandum accounts in the chart of                                                  Not            GL Account                     Memorandum
           2006 GLA-06            accounts.                                                                    Mandatory      Pending         Scheduled      Definition                     accounts
                                  Add, change or de-activate accounts in the chart of accounts without                                        Not            GL Account
           2006 GLA-07            programming changes.                                                         Mandatory      Pending         Scheduled      Definition                     Account changes
                                  Add, change or de-activate U.S. SGL attribute domain values in order
                                  to accommodate changes in Treasury reporting (e.g. FACTS I, FACTS                                           Not            GL Account                     Attribute value
           2006 GLA-08            II, or GFRS) without programming changes.                                    Mandatory      Pending         Scheduled      Definition                     changes
                                  Deliver the Core financial system software populated with the current                                       Not            GL Account                     Pre-configured U.S.
           2006 GLA-09            published values for the U.S. SGL chart of accounts.                         Mandatory      Pending         Scheduled      Definition                     SGL accounts
                                  Deliver the Core financial system software populated with the current                                       Not            GL Account                     Pre-configured
           2006 GLA-10            published values for the FACTS II attributes.                                Mandatory      Pending         Scheduled      Definition                     FACTS II attributes
                                  Record like accounting events consistently using standard
                                  transactions. Standard transactions must specify the general ledger
                                  account postings, and update document balances and any related                                              Not            Transaction
           2006 GLB-01            tables (e.g. available funding).                                             Mandatory      Pending         Scheduled      Definition                     Standard transactions
                                  Define the general ledger account postings used in a standard                                               Not            Transaction
           2006 GLB-02            transaction.                                                                 Mandatory      Pending         Scheduled      Definition                     GL account posting
                                  Define standard transactions that include proprietary, budgetary and                                        Not            Transaction
           2006 GLB-03            memorandum accounts.                                                         Mandatory      Pending         Scheduled      Definition                     Transaction accounts
                                                                                                                                              Not            Transaction
           2006 GLB-04            Define standard transactions consistent with U.S. SGL posting rules.         Mandatory      Pending         Scheduled      Definition                     U.S. SGL consistency
                                  Define standard transactions that derive general ledger postings
                                  based on accounting classification elements or other document data                                          Not            Transaction
           2006 GLB-05            elements.                                                                    Mandatory      Pending         Scheduled      Definition                     Posting derivation
                                  Define edit rules for standard transactions to require, prohibit, or set a                                  Not            Transaction
           2006 GLB-06            default value for accounting classification elements.                        Mandatory      Pending         Scheduled      Definition                     Transaction rules
                                                                                                                                              Not            Transaction                    Number of GL
           2006 GLB-07            Define up to 10 debit and credit pairs in a single standard transaction. Mandatory          Pending         Scheduled      Definition                     account pairs
                                  Update all general ledger account balances (i.e., budgetary,
                                  proprietary and memorandum accounts) based on a single input                                                Not            GL Updating and                Updating GL
           2006 GLC-01            transaction.                                                             Mandatory          Pending         Scheduled      Editing                        balances
                                  Classify accounting transactions by U.S. SGL attributes required for                                                                                      Classifying
                                  FACTS I, FACTS II, and GFRS reporting as specified by the current                                           Not            GL Updating and                transactions by
           2006 GLC-02            supplement(s) to the TFM.                                                Mandatory          Pending         Scheduled      Editing                        attribute


Printed on 5/20/2010                                                                                    93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                           Page 42 of 79
Financial Systems Integration Office                                                                 Requirements Tested Matrix
                                                                                                   Core Requirements & Test Status

 Requirement                                                                                                                                                                              Requirement Short
    Year               Req. No.                                  Description                                   Status        Test Cycle     Test Status         Process     Test Notes          Name
                                  alidate U.S. SGL attributes on transactions (whether entered or                                          Not            GL Updating and
           2006 GLC-03            derived) prior to the posting.                                          Mandatory        Pending         Scheduled      Editing                        Validate attributesV
                                  Prevent transactions from posting that would cause general ledger
                                  debits and credits to be out-of-balance at any level of the agency's                                     Not            GL Updating and                Balanced GL postings
           2006 GLC-04            accounting classification structure specified on a transaction.         Mandatory        Pending         Scheduled      Editing                        by ACS
                                  Prevent transactions from posting that would cause general ledger
                                  debits and credits to be out of balance within the proprietary,
                                  budgetary, or memorandum accounts. Proprietary, budgetary, and                                           Not            GL Update and                  Balanced GL postings
           2006 GLC-05            memorandum accounts must each be self-balancing.                        Mandatory        Pending         Scheduled      Editing                        by account type
                                  Update general ledger control accounts consistent with postings made
                                  to subsidiary ledgers. Prevent transactions from posting that would                                                                                    GL control accounts
                                  cause the general ledger control accounts to be out-of-balance with                                      Not            GL Update and                  balanced with
           2006 GLC-06            the subsidiary ledgers                                                  Mandatory        Pending         Scheduled      Editing                        subsidiary ledgers
                                  Prevent transactions from posting to general ledger accounts that                                        Not            GL Update and                  De-activated
           2006 GLC-07            have been de-activated.                                                 Mandatory        Pending         Scheduled      Editing                        accounts

                                  Derive and record the amount of upward or downward spending
                                  adjustments upon liquidating, canceling, or modifying the dollar
                                  amount of prior year obligations or expenditures. Record the spending                                    Not            Upward/Downward                Record spending
           2006 GLD-01            adjustment at the time of posting the transaction which generated it.   Mandatory        Pending         Scheduled      Spending Adj                   adjustments
                                  When correcting documents that previously generated spending
                                  adjustment entries, reverse the original spending adjustment entries                                     Not            Upward/Downward                Spending adjustment
           2006 GLD-02            and generate new spending adjustments for the correct amounts.          Mandatory        Pending         Scheduled      Spending Adj                   reversals
                                  Determine if upward and downward adjustments are to expired or
                                  unexpired budget authority in order to derive the U.S. SGL prescribed                                    Not            Upward/Downward                Adjustments to
           2006 GLD-03            entries to record spending adjustments.                                 Mandatory        Pending         Scheduled      Spending Adj                   expired vs. unexpired
                                  Determine if anticipated recoveries have been previously recorded in
                                  order to derive the U.S. SGL prescribed entries to record downward                                       Not            Upward/Downward
           2006 GLD-04            spending adjustments.                                                   Mandatory        Pending         Scheduled      Spending Adj                   Anticipated recoveries
                                  Determine if upward and downward adjustments are to paid or unpaid
                                  obligations and/or expenditures in order to derive the U.S. SGL                                          Not            Upward/Downward                Adjustments to paid
           2006 GLD-05            prescribed entries for recording spending adjustments.                  Mandatory        Pending         Scheduled      Spending Adj                   vs. unpaid
                                  Determine if upward and downward adjustments are to delivered or                                                                                       Adjustments to
                                  undelivered orders in order to derive the U.S. SGL prescribed entries                                    Not            Upward/Downward                delivered vs.
           2006 GLD-06            to record spending adjustments.                                         Mandatory        Pending         Scheduled      Spending Adj                   undelivered orders
                                  Permit recording of previously unrecorded obligations to prior year                                                                                    Previously
                                  budget authority or expired budget authority and generate related                                        Not            Upward/Downward                unrecorded
           2006 GLD-07            upward spending adjustments in the current year.                        Mandatory        Pending         Scheduled      Spending Adj                   obligations
                                  Identify when posting transactions will invoke upward spending
                                  adjustments, and apply the agency-defined level of validation (I.e.,                                     Not            Upward/Downward                Spending adjustment
           2006 GLD-08            rejection, warning or information only).                                Mandatory        Pending         Scheduled      Spending Adj                   validation

                                  Query general ledger account balances. Parameters include beginning
                                  and ending accounting period, and TAS or internal fund code. Result
                                  is beginning account balances, period activity, and ending account
                                  balances for the period and TAS, or internal fund code, specified. Drill-
                                  down from period activity to supporting general ledger transactions;                                                                                   General ledger
                                  from general ledger transactions to supporting documents; and from                                       Not            GL Analysis and                account balances
           2006 GLE-01            supporting documents to other documents in the document chain.            Mandatory      Pending         Scheduled      Reconciliation                 query
                                  Generate the Daily GL and Subsidiary Ledger Exception Report.
                                  Result is a list of GL control accounts by internal fund code whose
                                  balances differ from the subsidiary ledgers. Report lines include the                                                                                  Daily GL and
                                  GL control account balance, the balance of the open documents in the                                     Not            GL Analysis and                Subsidiary Ledger
           2006 GLE-02            subsidiary ledger, and the difference.                                    Mandatory      Pending         Scheduled      Reconciliation                 Exception Report




Printed on 5/20/2010                                                                                 93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                          Page 43 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                    Requirement Short
    Year               Req. No.                                  Description                                     Status        Test Cycle     Test Status         Process         Test Notes          Name

                                  Generate the GL Supporting Documents Report as of the current
                                  system date. Parameters include a GL control account and TAS or
                                  internal fund code. Result is the GL account balance, and a list of the                                    Not            GL Analysis and                    GL Supporting
           2006 GLE-03            open documents and balances supporting the GL account balance.              Mandatory      Pending         Scheduled      Reconciliation                     Document Report
                                  Maintain fifteen accounting periods per fiscal year. Provide the option
                                  to designate one period for recording opening balances, twelve
                                  periods for recording monthly activity and two additional periods for                                      Not            Acctng Prd Maint
           2006 GLF-01            year end pre-closing and closing entries                                    Mandatory      Pending         Scheduled      and Closing                        Accounting periods
                                  Record transactions to any open accounting period. Provide the option
                                  to keep multiple accounting periods (minimum of 3) open                                                    Not            Acctng Prd Maint                   Open accounting
           2006 GLF-02            simultaneously.                                                             Mandatory      Pending         Scheduled      and Closing                        periods
                                  Close accounting periods and prevent the posting of new transactions                                       Not            Acctng Prd Maint                   Closed accounting
           2006 GLF-03            to any closed period.                                                       Mandatory      Pending         Scheduled      and Closing                        periods
                                                                                                                                             Not            Acctng Prd Maint                   Re-opening
           2006 GLF-04            Re-open closed accounting periods and record transactions to them.          Mandatory      Pending         Scheduled      and Closing                        accounting periods
                                  Provide a year-end closing process that records U.S. SGL prescribed
                                  closing entries in accounting periods separate from other accounting                                       Not            Acctng Prd Maint
           2006 GLF-05            periods.                                                                    Mandatory      Pending         Scheduled      and Closing                        Closing entries
                                  Perform multiple closings in a trial/test mode so that users can review
                                  the closing results, clear the closing entries and re-run the closing
                                  process. This functionality must be available for both "pre-closing"                                       Not            Acctng Prd Maint
           2006 GLF-06            entries and "closing" entries                                               Mandatory      Pending         Scheduled      and Closing                        Multiple closings
                                  Generate trial balances that support the review of the closing process                                     Not            Acctng Prd Maint
           2006 GLF-07            run in trial/test mode.                                                     Mandatory      Pending         Scheduled      and Closing                        Closing results
                                  Record transactions to the current and prior fiscal year (i.e., until the                                  Not            Acctng Prd Maint
           2006 GLF-08            closing process is complete).                                               Mandatory      Pending         Scheduled      and Closing                        Open fiscal years
                                  Derive an accounting period’s opening balances based on the prior
                                  accounting period’s closing balances at the U.S. SGL attribute level.
                                  The opening of general ledger account balances must maintain the
                                  U.S. SGL attribute information required to satisfy FACTS I, FACTS II,                                      Not            Acctng Prd Maint
           2006 GLF-09            and GFRS reporting requirements.                                            Mandatory      Pending         Scheduled      and Closing                        Roll forward balances
                                  Fiscal year driven tablesMake fiscal year driven tables available in                                       Not            Acctng Prd Maint                   Fiscal year driven
           2006 GLF-10            subsequent fiscal years.                                                    Mandatory      Pending         Scheduled      and Closing                        tables
                                  Single year tablesMake single year appropriation and fund tables                                           Not            Acctng Prd Maint
           2006 GLF-11            available in subsequent fiscal years.                                       Mandatory      Pending         Scheduled      and Closing                        Single year tables
                                                                                                                                             Not
                                  Deliver a capability to make mass changes to tables rolled forward to                Not                   Tested/Value   Acctng Prd Maint                   Mass table changes
           2006 GLF-12            a subsequent fiscal year.                                                Value Added Applicable            Added          and Closing                        at fiscal year end
                                  Generate all standard reports as of any accounting period. Amounts
                                  reported must reflect the cumulative amount of all transactions posted
                                  to the general ledger up through the accounting period specified for
                                  running the report. If reporting for the current period, amounts must be                                   Not
           2006 GLG-01            cumulative up through the current date.                                  Mandatory   Pending               Scheduled      Financial Reporting                Report end dates




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                              Page 44 of 79
Financial Systems Integration Office                                                                  Requirements Tested Matrix
                                                                                                    Core Requirements & Test Status

 Requirement                                                                                                                                                                                   Requirement Short
    Year               Req. No.                                 Description                                     Status        Test Cycle     Test Status         Process         Test Notes          Name

                                  Ensure consistency between the data sources used to generate
                                  internal and external financial reports for the same accounting period.
                                  The following relationships must be maintained:
                                  •     The beginning and ending balances and total debit and credit
                                  activity reported on the Standard Trial Balance must equal the
                                  beginning and ending balances and total debit and credit activity
                                  reported on the FACTS I and FACTS II trial balances.
                                  •     The debit and credit activity reported on the Transaction Register
                                  must equal the debit and credit activity reported on all of the trial
                                  balances.
                                  •     The system-generated FACTS I transfer file must agree with the
                                  system-generated Balance Sheet, Statement of Net Cost, and
                                  Statement of Changes in Net Position
                                  •     The system-generated FACTS II transfer file must agree with the                                     Not
           2006 GLG-02            system-generated Statement of Budgetary Resources and the SF-133. Mandatory               Pending         Scheduled      Financial Reporting                Report consistency

                                  Generate a transaction register report. Parameters are:accounting
                                  period, transaction date range, or system date range. Result is a
                                  report displaying the following data elements for each transaction
                                  posted during the accounting period or date range specified:
                                  •       Fiscal year
                                  •       TAS
                                  •       Internal fund code
                                  •       Document number
                                  •       Transaction number
                                  •       Transaction date
                                  •       System date
                                  •       System time
                                  •       Entry user ID
                                  •       Debit account number(s)
                                  •       Debit amount(s)
                                  •       Credit account number(s)
                                  •       Credit amount(s)
                                  •       Object class
                                  •       U.S. SGL attribute values.
                                  Provide an option to group transactions at the TAS, internal fund, or
                                  organization level. Transactions which occur from a single posting
                                  event must be grouped together. The report must include headings for
                                  each data element displayed. The report must include all transactions
                                  in all funds that occurred within the accounting period specified.                                        Not
           2006 GLG-03                                                                                      Mandatory       Pending         Scheduled      Financial Reporting                Transaction register
                                  Generate a trial balance report. Parameter is the accounting period.
                                  Result is a report providing the following amounts for each general
                                  ledger account:
                                  •      Beginning balance for the accounting period
                                  •      Total amount of debits for the accounting period
                                  •      Total amount of credits for the accounting period
                                  •      Cumulative ending balance for the accounting period.
                                  Provide the option to select whether general ledger account balances
                                  are rolled up to the TAS level, internal fund level, or organization level,
                                  and also whether they are displayed at the GL sub-account level
                                  (actual accounts used for posting transactions) or the U.S. SGL
                                  account level. Sub-totals for beginning balance, accounting period
                                  activity, and ending balance columns must be provided after each
                                  change in organization, internal fund and TAS on the report. The
                                  report must include the balances of all funds and all fiscal years                                        Not
           2006 GLG-04            maintained by the agency.                                                   Mandatory     Pending         Scheduled      Financial Reporting                Trial balance


Printed on 5/20/2010                                                                                  93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                Page 45 of 79
Financial Systems Integration Office                                                                    Requirements Tested Matrix
                                                                                                      Core Requirements & Test Status

 Requirement                                                                                                                                                                                     Requirement Short
    Year               Req. No.                                  Description                                       Status       Test Cycle     Test Status         Process         Test Notes          Name

                                  Generate a FACTS I trial balance report. Parameter is the accounting
                                  period. Result is a report displaying the following balances for each
                                  U.S. SGL account or U.S. SGL account and attribute combination:
                                  •     Beginning balance for the accounting period
                                  •     Total amount of debits for the accounting period
                                  •     Total amount of credits for the accounting period
                                  •     Cumulative ending balance for the accounting period.
                                  Provide the option to specify whether general ledger account balances
                                  are rolled up to the TAS level, internal fund level, or organization level.
                                  The report must include all general ledger accounts (both FACTS I
                                  accounts and non-FACTS I accounts). FACTS I accounts must be
                                  displayed at the U.S. SGL and attribute level (I.e. separate amounts
                                  should be displayed when there is more than one attribute value within
                                  an U.S. SGL account). Non-FACTS I accounts must be displayed at
                                  the U.S. SGL account level. Subtotals for beginning balance,
                                  accounting period activity, and ending balance columns must be
                                  provided after each change in TAS, internal fund, and organization on
                                  the report.
                                                                                                                                              Not
           2006 GLG-05                                                                                          Mandatory     Pending         Scheduled      Financial Reporting                FACTS I trial balance

                                  Generate a FACTS II trial balance report. Parameter is the accounting
                                  period. Result is a report displaying the following balances for each
                                  U.S. SGL account or U.S. SGL account and attribute combination:
                                  •     Beginning balance for the accounting period
                                  •     Total amount of debits for the accounting period
                                  •     Total amount of credits for the accounting period
                                  •     Cumulative ending balance for the accounting period.
                                  Provide the option to specify whether general ledger account balances
                                  are rolled up to the TAFS level, internal fund level, or organization
                                  level. The report must include all general ledger accounts (both
                                  FACTS II accounts and non-FACTS II accounts). FACTS II accounts
                                  must be displayed at the U.S. SGL and attribute level (i.e., separate
                                  amounts should be displayed when there is more than one attribute
                                  value within a U.S. SGL account). Non-FACTS II accounts must be
                                  displayed at the U.S. SGL account level. Subtotals for beginning
                                  balance, accounting period activity, and ending balance columns must
                                  be provided after each change in TAFS, internal fund, and
                                  organization on the report.                                                                                 Not
           2006 GLG-06                                                                                          Mandatory     Pending         Scheduled      Financial Reporting                FACTS II trial balance
                                  Export bulk transfer files for FACTS I and FACTS II Adjusted Trial                                          Not
           2006 GLG-07            Balances (ATBs) to the Department of Treasury's FMS.                Mandatory               Pending         Scheduled      Financial Reporting                FACTS ATB
                                  Validate FACTS I and FACTS II data prior to submission of the FACTS
                                  I and FACTS II ATBs and the GFRS report to Treasury's FMS. Provide                                          Not
           2006 GLG-08            the option to run validation edits on demand.                       Mandatory               Pending         Scheduled      Financial Reporting                FACTS validation

                                  Generate the Report on Budget Execution and Budgetary Resources
                                  (SF-133). Parameters include TAFS and accounting period end date.
                                  When no TAFS is specified, generate a report for each reportable
                                  TAFS. Results are reports in accordance with OMB Circular A-11                                              Not
           2006 GLG-09            instructions and the U.S. SGL crosswalk to the SF-133 report.     Mandatory                 Pending         Scheduled      Financial Reporting                SF 133




Printed on 5/20/2010                                                                                    93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                              Page 46 of 79
Financial Systems Integration Office                                                              Requirements Tested Matrix
                                                                                                Core Requirements & Test Status

 Requirement                                                                                                                                                                                                 Requirement Short
    Year               Req. No.                               Description                                   Status        Test Cycle     Test Status         Process                   Test Notes                  Name

                                  Generate the following consolidated agency financial statements:
                                  •    Balance Sheet
                                  •    Statement of Net Cost
                                  •    Statement of Changes in Net Position
                                  •    Statement of Budgetary Resources
                                  •    Statement of Financing
                                  •    Statement of Custodial Activity (if applicable).
                                  Parameter is the accounting period end date. Reports are to be
                                  generated from the general ledger account balances and attributes
                                  crosswalked in accordance with the U.S. SGL Crosswalks to Standard
                                  External Reports. Results are reports in accordance with the current
                                  OMB Bulletin on Form and Content of Agency Financial Statements.                                      Not
           2006 GLG-10                                                                                   Mandatory      Pending         Scheduled      Financial Reporting                                  Financial statements
                                  Customize agency financial statement formats by adding or deleting
                                  line items, changing the name of line items, inserting additional
                                  subtotals, or modifying account crosswalks through table updates or                                   Not                                                                 Statement
           2006 GLG-11            report writing capability.                                             Mandatory      Pending         Scheduled      Financial Reporting                                  customization
                                  Generate reclassified consolidated agency financial statements for
                                  input to GFRS in accordance with current TFM Agency Reporting
                                  Requirements for the Financial Report of the United States                                            Not
           2006 GLG-12            Government and the U.S SGL Crosswalks to the Closing Package.          Mandatory      Pending         Scheduled      Financial Reporting                                  GFRS Statements
                                  Generate consolidated financial statements on-line. Drill-down from
                                  the consolidated amounts to the GL accounts and balances that make
                                  up the amounts, from the GL account balances to the individual                                        Not
           2006 GLG-13            balancesthe following vendor information:
                                  Capture by TAS, and to detailed GL transactions.                       Mandatory      Pending         Scheduled      Financial Reporting                                  On-line statements
                                  •      Vendor ID number (agency-assigned)
                                  •      Vendor name (Legal)
                                  •      Vendor name (DBA)
                                  •      Vendor name (Division)
                                  •      Vendor address
                                  •      Business type (support CCR published business rules for
                                  business type: Federal govt., state govt., small business, etc.)
                                  •      Organization type (support CCR published business rules for
                                  organization type: sole proprietorship/Individual; partnership,
                                  employee, etc.)
                                  •      US or Non-US
                                  •      Product Service codes
                                  •      NAICS code
                                  •      Credit Card Vendor Indicator
                                  •      DUNS (BPN) number
                                  •      CAGE code
                                  •      DUNS + 4 number for each instance of banking information, for
                                  CCR vendors
                                  •      Prompt Pay indicator and type, or payment terms
                                  •      IRS 1099 indicator
                                  •      IRS W-2 indicator
                                  •      CCR registration indicator (required, exempt)
                                  •      CCR registration status (active or expired)
                                  •      Comment field                                                                                                                       Clarifications:
                                  •      Active/Inactive indicator                                                                                                           1-Deleted SIC code as required
                                  •      Debarment indicator                                                                                                                 data.
                                  •      Debarment start and end dates                                                                                                       2-Changed DUNS to DUNS
                                  •      GFRS and FACTS I trading partner codes for Federal vendors                                                                          (BPN) number.
                                  •      ALC (for Federal vendors)                                                                                                           3-Added CAGE code as
                                  •      Disbursing Office Symbol (for Federal vendors)                                                                                      required data.
2006                              •      Default payment method, e.g., check, EFT, IPAC                                                 Not            Payee Information     4-Added IPAC as a default
Clarification     PMA-01          •      Alternate payment methods                                       Mandatory      Pending         Scheduled      Maintenance           payment method.                Vendor information


Printed on 5/20/2010                                                                              93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                  Page 47 of 79
Financial Systems Integration Office                                                                          Requirements Tested Matrix
                                                                                                            Core Requirements & Test Status

 Requirement                                                                                                                                                                                         Requirement Short
    Year               Req. No.                                     Description                                         Status        Test Cycle     Test Status        Process        Test Notes          Name
                                  Capture the following vendor information:
                                  •     Vendor ID number (agency-assigned)
                                  •     Business Name
                                  •     Trading Style Name
                                  •     Vendor name (Division)
                                  •     Physical address
                                  •     Business type (support FedReg published business rules for business
                                  type: Seller, Buyer, Buyer and Seller)
                                  •     Mailing address
                                  •     Headquarters DUNS (BPN) Number
                                  •     Headquarters Name
                                  •     Agency DUNS (BPN) Number
                                  •     Agency Name
                                  •     Hierarchy Code
                                  •     Status Code (0 - Not a subsidiary, 3 Subsidiary)
                                  •     Source
                                  •     Treasury Index (Treas Dept Code)
                                  •     Employer Identification Number
                                  •     ALC
                                  •     Disbursing Office
                                  •     POC email (registration, elimination, sales, accounts receivable, accounts
                                  payable)
                                  •     POC Name (First, Last, Middle Initial for POCs to include registration,
                                  elimination, sales, accounts receivable, accounts payable))
                                  •     POC Phone (area code, phone number, extension for POCs to include
                                  registration, elimination, sales, accounts receivable, accounts payable))
                                  •     POC Phone International (POCs to include registration, elimination, sales,
                                  accounts receivable, accounts payable)
                                  •     POC Fax (POCs to include registration, elimination, sales, accounts
                                  receivable, accounts payable)
                                  •     POC Address (POCs to include registration, elimination, sales, accounts
                                  receivable, accounts payable)
                                  •     Annual Revenue
                                  •     Merchant ID (ID1)
2006                              •     Product Service codes                                                                                       Not            Payee Information                Federal Vendor
Addendum          PMA-01a         •     FSC code                                                                     Mandatory      Pending         Scheduled      Maintenance                      Information
                                  Capture third-party payee information associated a primary vendor
                                  including:
                                  •     Payee name
                                  •     Payee point of contact
                                  •     Payee telephone number
                                  •     Payee email address
                                  •     Remittance address or/banking information (account number,                                                  Not            Payee Information                Third-party vendor
           2006 PMA-02            account type, RTN).                                                       Mandatory               Pending         Scheduled      Maintenance                      information
                                  Associate vendor and customer records that represent the same                                                     Not            Payee Information                Vendor/customer
           2006 PMA-03            entity.                                                                   Mandatory               Pending         Scheduled      Maintenance                      relationships
                                  Import CCR data. Update vendor data for relevant changes contained
                                  in the CCR's daily extract files. Support the data definitions (e.g. data
                                  types; field names; field lengths) used in CCR for fields that are                                                Not            Payee Information                CCR updates to
           2006 PMA-04            common to the CCR and the Core vendor file.                               Mandatory               Pending         Scheduled      Maintenance                      vendor data

                                  Import FedReg data. Update agency data for relevant changes
                                  contained in the FedReg daily extract files. Support the data definitions
2006                              (e.g. data types; field names; field lengths) used in FedReg for fields                                           Not            Payee Information                FedReg updates to
Addendum          PMA-04a         that are common to the FedReg, CCR and the Core vendor file.              Mandatory               Pending         Scheduled      Maintenance                      agency data
                                  Identify updated CCR company names (legal, DBA or division) that are
                                  different than vendor names on obligations. Generate an exception
                                  report to notify agencies of contracts that require modification. Result
                                  is a list of selected vendor numbers, details of the CCR company                                                                                                  CCR company name
                                  name change, related obligation document numbers and associated                                                   Not            Payee Information                change exception
           2006 PMA-05            vendor names.                                                             Mandatory               Pending         Scheduled      Maintenance                      report




Printed on 5/20/2010                                                                                          93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                           Page 48 of 79
Financial Systems Integration Office                                                              Requirements Tested Matrix
                                                                                                Core Requirements & Test Status

Requirement                                                                                                                                                                                                       Requirement Short
     Year      Req. No.                               Description                                           Status        Test Cycle     Test Status         Process                   Test Notes                       Name
2006                    Prevent the agency from manually updating CCR data for vendors                                                  Not            Payee Information   Clarification: Deleted the first      Agency updates to
Clarification PMA-06    required to register in the CCR.                                               Mandatory        Pending         Scheduled      Maintenance         "vendor."                             CCR vendor data

2006                        Prevent the agency from manually updating FedReg data for agencies                                          Not            Payee Information                                         Agency updates to
Addendum          PMA-06a   required to register in the Federal Agency Registration System.    Mandatory                Pending         Scheduled      Maintenance                                               FedReg Agency data
                                                                                                                                        Not            Payee Information                                         DUNS number to TIN
           2006 PMA-07      Associate multiple DUNS numbers with a single TIN.                         Mandatory        Pending         Scheduled      Maintenance                                               association
                                                                                                                                        Not            Payee Information                                         DUNS+4 to DUNS
           2006 PMA-08      Associate multiple DUNS plus 4 numbers to a single DUNS number.            Mandatory        Pending         Scheduled      Maintenance                                               number association
                                                                                                                                                                           Clarification: Revised                Banking information
2006                        Associate one DUNS+4 with each instance of a vendor's CCR banking                                           Not            Payee Information   requirement to also cover             to DUNS+4 number
Clarification     PMA-09    information or an agency's FedReg ALC information.                         Mandatory        Pending         Scheduled      Maintenance         FedReg.                               association
                            Validate for duplicate TIN when adding or updating vendor records.
                            Notify the agency when duplicate TINs are identified. Allow the error                                       Not            Payee Information
           2006 PMA-10      message to be overridden.                                                  Mandatory        Pending         Scheduled      Maintenance                                               Validate vendor TINs
                            Query vendor file. Parameters include:
                            •     Vendor number
                            •     Vendor legal name
                            •     Vendor DBA Name
                            •     Vendor Division
                            •     Vendor TIN
                            •     DUNS number
                            •     IRS 1099 indicator.
                            Result is a display of all vendor data for the specified vendor. Output                                     Not            Payee Information
           2006 PMA-11      options include an Excel formatted a data file.                            Mandatory        Pending         Scheduled      Maintenance                                               Vendor file query
                            Maintain a history of changes made to vendor information. Capture
                            name of data item changed, before and after values, entry date and                                          Not            Payee Information
           2006 PMA-12      time and ID of user who made the change.                                   Mandatory        Pending         Scheduled      Maintenance                                               Vendor file history
                            Query vendor history. Parameters include vendor number, change
                            date range. Results include date and time of change, ID of user who                                         Not            Payee Information
           2006 PMA-13      made the change, item name, before and after data values.                  Mandatory        Pending         Scheduled      Maintenance                                               Vendor history query
                            Deactivate vendors on demand or based on agency-specified length                                            Not            Payee Information                                         Criteria for
           2006 PMA-14      of time with no activity.                                                  Mandatory        Pending         Scheduled      Maintenance                                               deactivating vendors
                            Prevent the deactivation of vendors that have unliquidated obligations                                      Not            Payee Information                                         Vendor deactivation
           2006 PMA-15      or unpaid invoices in the system.                                          Mandatory        Pending         Scheduled      Maintenance                                               edit
                                                                                                                                        Not            Payee Information
           2006 PMA-16      Prevent new obligations that reference inactive or debarred vendors.       Mandatory        Pending         Scheduled      Maintenance                                               Debarred vendors
                                                                                                                                                                           Clarification: Revised
2006                        Prevent new obligation and payment to vendors with expired CCR or FedReg                                    Not            Payee Information   requirement to include FedReg         Expired CCR and
Clarification     PMA-17    registrations.                                                             Mandatory        Pending         Scheduled      Maintenance         validation.                           FedReg registrations

                            Record full or partial receipt and/or acceptance of goods and services
                            by document line item. This is to include the receipt and/or acceptance                                     Not                                                                      Receipt and
           2006 PMB-01      of partial quantities of goods and services on each document line.      Mandatory           Pending         Scheduled      Accounts Payable                                          acceptance
                                                                                                                                                                           Clarification: Changed delivered to
2006                        Record an accrued liability and the reclassification of the order from                                      Not                                undelivered, undelivered to           Accrued liability upon
Clarification     PMB-02    undelivered to delivered upon receipt of goods or services.                Mandatory        Pending         Scheduled      Accounts Payable    delivered.                            receipt
                                                                                                                                                                                                                 Liquidate
                            Liquidate advance or prepaid expense when recording an accrued                                              Not                                                                      advance/prepaid
           2006 PMB-03      liability (receipt of goods or services).                                  Mandatory        Pending         Scheduled      Accounts Payable                                          expense
                            Capture the following additional information on receipt documents
                            (receiving reports):
                            •      Receiving official
                            •      Dates products were delivered or services were provided
                            •      Quantity/amount received
                            •      Vendor ID number and name                                                                            Not                                                                      Receipt document
           2006 PMB-04      •      Ship to locations.                                                  Mandatory        Pending         Scheduled      Accounts Payable                                          data




Printed on 5/20/2010                                                                              93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                     Page 49 of 79
Financial Systems Integration Office                                                                      Requirements Tested Matrix
                                                                                                        Core Requirements & Test Status

 Requirement                                                                                                                                                                                                            Requirement Short
    Year               Req. No.                                 Description                                         Status        Test Cycle     Test Status         Process                  Test Notes                      Name
                                  Capture the following additional information on the acceptance of
                                  goods/services:
                                  •   Acceptance official
                                  •   Dates products were delivered or services were provided
                                  •   Date products/services accepted
                                  •   Quantity/amount accepted
                                  •   Date products/services rejected
                                  •   Quantity/amount rejected
                                  •   Vendor ID number and name                                                                                 Not
           2006 PMB-05            •   Ship to locations.                                                       Mandatory        Pending         Scheduled      Accounts Payable                                        Acceptance data


                                  Capture the following additional information on invoice documents:
                                  •   Vendor invoice number or account number
                                  •   Invoice date
                                  •   Invoice receipt date
                                  •   Vendor ID number and name
                                  •   DUNS (BPN) number
                                  •   Contract line/subline number                                                                                                                Clarifications:
                                  •   Name and address of contractor official to whom payment is to be sent                                                                       1-Added DUNS (BPN) number
                                  •   DUNS+4 number for CCR and FedReg vendors                                                                                                    as required data.
                                  •   Payment terms (including discount for prompt payment)
                                                                                                                                                                                  2-Added DUNS+4 number for
                                  •   Shipping terms (e.g., shipment number and date of shipment)
                                  •   Vendor contact name and telephone number
                                                                                                                                                                                  FedReg vendors as required
                                  •   Dates products were delivered or services were provided                                                                                     data.
                                  •   User comments                                                                                                                               3-Deleted EFT banking
2006                              •   Date invoice returned to vendor                                                                           Not                               information (same as DUNS+4
Clarification     PMC-01          •   Date improper invoice resubmitted by vendor.                             Mandatory        Pending         Scheduled      Invoicing          number).                             Invoice data
                                  Capture a vendor invoice number of up to 30 characters or the current
                                  requirement of I TFM-6-5000. Report the complete number on all                                                Not
           2006 PMC-02            payment files, reports and query results.                             Mandatory               Pending         Scheduled      Invoicing                                               Invoice data
                                                                                                                                                Not
           2006 PMC-03            Capture up to 9,999 document line items per invoice document.                Mandatory        Pending         Scheduled      Invoicing                                               Invoice line items

                                  Define the criteria to be used in editing for duplicate vendor invoices,
                                  including one or more of the following: agency code, vendor number,
                                  vendor account number, vendor TIN, vendor invoice number, invoice                                             Not                                                                    Duplicate vendor
           2006 PMC-04            date, invoice amount, referenced obligation document number.                 Mandatory        Pending         Scheduled      Invoicing                                               invoice edit criteria
                                  Validate for duplicate vendor invoices based on the agency-defined                                            Not                                                                    Validate for duplicate
           2006 PMC-05            editing criteria.                                                            Mandatory        Pending         Scheduled      Invoicing                                               vendor invoices
                                  Validate invoices from registered CCR vendors for the following CCR vendor
                                  information:
                                  •    Active status                                                                                                                              Clarifications:
                                  •    Vendor name on invoice or referenced obligation same as CCR company                                                                        1-Changed banking information to
                                  name (legal, DBA or division)                                                                                                                   DUNS+4 number.
                                  •    DUNS+4 number on referenced obligation same as DUNS+4 number on                                                                            2-Added a sentence allowing for
2006                              vendor file.                                                                                                  Not                               override of vendor name validation   Validate invoices from
Clarification     PMC-06          Allow for override of failed vendor name validations.                        Mandatory        Pending         Scheduled      Invoicing          failures.                            CCR vendors
                                  Validate invoices from registered FedReg agencies for the following
                                  FedReg information:
                                  •    Active status
2006                              •    DUNS+4 on referenced reimbursable agreement same as                                                      Not                                                                    Validate invoices from
Addendum          PMC-06a         DUNS+4 on vendor file.                                                       Mandatory        Pending         Scheduled      Invoicing                                               FedReg agencies




Printed on 5/20/2010                                                                                      93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                    Page 50 of 79
Financial Systems Integration Office                                                                            Requirements Tested Matrix
                                                                                                              Core Requirements & Test Status

 Requirement                                                                                                                                                                                                              Requirement Short
    Year               Req. No.                                    Description                                           Status        Test Cycle     Test Status         Process               Test Notes                      Name
                                  At the time of preliminary payment scheduling, validate payments to registered
                                  CCR vendors for the following CCR vendor information:
                                  •    Active status
                                  •    Vendor name same as CCR company name (legal, DBA or division) on
                                  vendor file                                                                                                                                       Clarifications:
                                  •    DUNS+4 number on referenced obligation same as DUNS+4 number on                                                                              1-Changed banking information to
                                  vendor file.                                                                                                                                      DUNS+4 number.
                                  Allow for override of failed vendor name validations. Hold payments that fail                                                                     2-Added a sentence allowing for
2006                              these validations (unless overriden) from inclusion in the final payment                                           Not                            override of vendor name validation   Validate payments to
Clarification     PMC-07          schedules.                                                                        Mandatory        Pending         Scheduled      Invoicing       failures.                            CCR vendors
                                  Prior to IPAC file generation, validate payments to registered FedReg agencies
                                  for the following registration information:
                                  •     Active status
                                  •     DUNS+4 number on referenced reimbursable agreement same as
2006                              DUNS+4 number on vendor file.                                                                                      Not                                                                 Validate payments to
Addendum          PMC-07a         Hold payments that fail these validations from inclusion in IPAC files.           Mandatory        Pending         Scheduled      Invoicing                                            FedReg Agencies
                                  Match invoices to obligations, receiving reports and acceptance
                                  information by document line item and quantity. Perform two-way
                                  matching (obligation and invoice, or obligation and receipt), three-way
                                  matching (obligation, simultaneous receipt/acceptance and invoice),
                                  and four-way matching (obligation, receipt, acceptance and invoice).
                                  Prevent the payment of invoices until the matching process is                                                      Not
           2006 PMC-08            complete.                                                               Mandatory                  Pending         Scheduled      Invoicing                                            Matching options
                                                                                                                                                                                                                         Invoices for partial
                                                                                                                                                                                                                         amount of quantities
                                  Process invoices for payment of partial quantities received and                                                    Not                                                                 received and
           2006 PMC-09            accepted.                                                                         Mandatory        Pending         Scheduled      Invoicing                                            accepted
                                  Validate that invoice dates that products were delivered or services were
                                  performed are within the period of performance dates on the referenced                                             Not                                                                 Validate invoice
           2006 PMC-10            obligation document lines.                                                        Mandatory        Pending         Scheduled      Invoicing                                            period of performance
                                  Validate that the invoice dates that products were delivered or
                                  services were performed are dates for which the products/services
                                  have been received and accepted. Prevent the processing of invoices                                                                                                                    Validate invoice
                                  with unmatched dates and the duplicate processing of invoices with                                                 Not                                                                 delivery/performance
           2006 PMC-11            matched dates.                                                                    Mandatory        Pending         Scheduled      Invoicing                                            dates
                                  Record an invoice as a "partial" or "final" payment of the referenced
                                  obligation. If "final", deobligate any unliquidated balance and close the                                          Not
           2006 PMC-12            obligation and receipt.                                                           Mandatory        Pending         Scheduled      Invoicing                                            Final payment
                                  Record additional shipping and other charges to adjust the payment                                                 Not                                                                 Adjust payment
           2006 PMC-13            amount, if they are authorized and within variance tolerances.                    Mandatory        Pending         Scheduled      Invoicing                                            amounts
                                  Define recurring payments in the system and schedule items (e.g.
                                  contracts, leases, etc.) for payment on an interval determined by the
                                  agency (i.e., weekly, bi-weekly, monthly, quarterly or other specified
                                  number of days). Capture the actual payment dates on the individual                                                Not                                                                 Set up recurring
           2006 PMC-14            payment records.                                                                  Mandatory        Pending         Scheduled      Invoicing                                            payments
                                  Update recurring payment information for changes in agreement                                                      Not                                                                 Update recurring
           2006 PMC-15            terms, amounts, frequency, etc.                                                   Mandatory        Pending         Scheduled      Invoicing                                            payment terms
                                                                                                                                                     Not
           2006 PMC-16            Warehouse approved invoices for future scheduling.                                Mandatory        Pending         Scheduled      Invoicing                                            Warehouse Invoices
                                  Define reason codes and related descriptions for invoice processing
                                  errors in the following categories:
                                  •    Advantageous discount lost
                                  •    Interest paid, and                                                                                                                                                                Define reason codes
                                  •    Improper payment made.                                                                                        Not                                                                 for invoice processing
           2006 PMC-17            For example, DL01, Discount Lost because invoice misplaced.                       Mandatory        Pending         Scheduled      Invoicing                                            errors




Printed on 5/20/2010                                                                                           93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                Page 51 of 79
Financial Systems Integration Office                                                                        Requirements Tested Matrix
                                                                                                          Core Requirements & Test Status

 Requirement                                                                                                                                                                                                           Requirement Short
    Year               Req. No.                                    Description                                          Status        Test Cycle     Test Status         Process              Test Notes                     Name
                                                                                                                                                                                   Clarifications:
                                                                                                                                                                                   1-Deleted the need to define invoice
                                                                                                                                                                                   held and invoice cancelled reason
                                                                                                                                                                                   codes.
                                                                                                                                                                                   2-Made related change to             Define reason codes
2006                              Define reason codes and related descriptions for invoice adjustments. For                                         Not                            requirement short name.              for invoice
Clarification     PMC-18          example, IA03, Invoice Total Adjusted.                                           Mandatory        Pending         Scheduled      Invoicing       3-Gave a more specific example.      adjustments
                                  Define reason codes and related descriptions for improper invoices.                                               Not                                                              Define reason codes
           2006 PMC-19            For example, IP01- Improper Invoice, X data missing.                             Mandatory        Pending         Scheduled      Invoicing                                         for improper invoices
                                  Capture reason codes and related descriptions for the following types of invoice
                                  processing errors and actions:
                                  •    Advantageous discount lost
                                  •    Interest paid                                                                                                                               Clarification: Deleted the need to Capture reason codes
2006                              •    improper payment made                                                                                        Not                            capture invoice held and invoice for invoice processing
Clarification     PMC-20          •    Invoice adjusted.                                                           Mandatory        Pending         Scheduled      Invoicing       cancelled reason codes.            errors and actions

                                  Capture reason codes and related descriptions for improper invoices                                               Not                                                              Capture reason codes
           2006 PMC-21            held or suspended (i.e., failed validations).                                    Mandatory        Pending         Scheduled      Invoicing                                         for improper invoices
                                  Generate a letter or e-mail to the vendor notifying them of the return of
                                  an improper invoice, upon the recording of an improper invoice reason
                                  code. Include the following information in the notice:
                                  •     Vendor invoice number and date
                                  •     Reason code(s) and description(s) of invoice discrepancies
                                  •     Date of notice.
                                  •     Request for a corrected invoice                                                                                                                                              Notify vendor of return
                                  •     Name, title, telephone number and e-mail address of Agency                                                  Not                                                              of improper invoice
           2006 PMC-22            contact person.                                                                  Mandatory        Pending         Scheduled      Invoicing                                         notice
                                  Import vendor updates from the CCR system and release previously
                                  suspended invoices and payment vouchers for the following:
                                  •     Vendor status change from expired to active
                                  •     Vendor name on document or referenced obligation now the
                                  same as CCR company name (legal, DBA, or division)
                                  •     DUNS+4 on referenced obligation now the same as DUNS+4 on
                                  vendor file.                                                                                                                                     Clarification:
2006                              Calculate payment due dates for released invoices and re-calculate                                                Not                            Changed banking information to    Import CCR vendor
Clarification     PMC-23          payment due dates for released payment vouchers.                                 Mandatory        Pending         Scheduled      Invoicing       DUNS+4 number.                    updates
                                  Import vendor updates from the FedReg system and release
                                  previously suspended invoices and payment vouchers for the
                                  following:
                                  •     Vendor status change from expired to active
2006                              •     DUNS+4 on referenced reimbursable agreement same as                                                         Not                                                              Import FedReg
Addendum          PMC-23a         DUNS+4 on vendor file.                                                           Mandatory        Pending         Scheduled      Invoicing                                         vendor updates
                                  Calculate the due date of vendor payments in accordance with 5 CFR
                                  1315, including but not limited to the following factors:
                                  •     Commodity type
                                  •     Contract terms
                                  •     Invoice receipt
                                  •     Goods/services receipt and acceptance
                                  •     Fast Payment
                                  •     Discount terms
                                  •     Accelerated payment methods
                                  •     Governmentwide commercial purchase card rebates                                                             Not
           2006 PMD-01            •     Improper invoices returned more than 7 days after receipt.                 Mandatory        Pending         Scheduled      Disbursing                                        Prompt payment
                                  Calculate multiple due dates when items on an invoice have different                                              Not                                                              Invoices with multiple
           2006 PMD-02            payment terms.                                                                   Mandatory        Pending         Scheduled      Disbursing                                        due dates
                                                                                                                                                                                                                     Override vendor
                                  Capture payment terms on obligations that are different than those                                                Not                                                              record payment terms
           2006 PMD-03            specified on the associated vendor record.                                       Mandatory        Pending         Scheduled      Disbursing                                        on obligation



Printed on 5/20/2010                                                                                          93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                              Page 52 of 79
Financial Systems Integration Office                                                                     Requirements Tested Matrix
                                                                                                       Core Requirements & Test Status

 Requirement                                                                                                                                                                                                        Requirement Short
    Year               Req. No.                                 Description                              Status                  Test Cycle     Test Status         Process               Test Notes                      Name
                                  Validate payment terms on invoices against the payment terms on the
                                  related obligating documents. Calculate the most advantageous
                                  terms, store them on the invoice documents, and use them to                                                  Not                                                                 Validate invoice
           2006 PMD-04            calculate the payment due dates and amounts.                        Mandatory                Pending         Scheduled      Disbursing                                           payment terms

                                                                                                                                                                              Clarifications:
                                  Schedule an invoice for payment on a date other than the system-calculated due                                                              1-Replaced override with schedule.
2006                              date, as specified by the user. Capture a reason code for the user change in                                 Not                            2-Made related change in             User-specified
Clarification     PMD-05          payment date.                                                                  Mandatory     Pending         Scheduled      Disbursing      requirement short name.              payment date
                                  Define dates (e.g., weekends, Federal holidays) for which payments
                                  cannot be scheduled. Prevent payment scheduling that falls on agency-                                        Not
           2006 PMD-06            excluded dates.                                                       Mandatory              Pending         Scheduled      Disbursing                                           System calendar
                                  Calculate whether taking a discount is economically justified as                                             Not                                                                 Advantageous
           2006 PMD-07            defined in I TFM-6-8040.                                              Mandatory              Pending         Scheduled      Disbursing                                           discounts
                                  Calculate amounts to be disbursed, including discounts, interest, and
                                  penalties, in accordance with 5 CFR 1315. Record U.S. SGL
                                  prescribed transactions for discounts taken, and interest, penalties                                         Not                                                                 Calculate payment
           2006 PMD-08            and principal paid.                                                   Mandatory              Pending         Scheduled      Disbursing                                           amounts

                                  Calculate payment amounts and due dates using Treasury rate tables,                                          Not                                                                 Use Treasury interest
           2006 PMD-09            i.e., Prompt Pay Act Interest rate and Current Value of Funds rate.         Mandatory        Pending         Scheduled      Disbursing                                           rate tables
                                  Apply interest and discount amounts across multiple accounting lines
                                  on an invoice using the ratio of the original invoice accounting line                                        Not                                                                 Apply interest and
           2006 PMD-10            amounts to the invoice total.                                               Mandatory        Pending         Scheduled      Disbursing                                           discounts
                                  Define the default for recording late payment interest, i.e., to the same
                                  accounting classification as the original payment or to another
                                  specified accounting classification in the same fund as the original                                         Not                                                                 Record late payment
           2006 PMD-11            payment.                                                                    Mandatory        Pending         Scheduled      Disbursing                                           interest
                                  Maintain a sequential numbering system for scheduling payments to
                                  be made by the disbursing office. Define different schedule number
                                  ranges for different payment types, such as travel schedules,
                                  transportation schedules, payroll schedules, vendor schedules, etc.
                                  Generate appropriate and unique schedule numbers for the payments                                            Not                                                                 Numbering payment
           2006 PMD-12            scheduled for disbursement.                                                 Mandatory        Pending         Scheduled      Disbursing                                           schedules
                                  Identify payments to be disbursed in a particular payment cycle based
                                  on their due date. Provide for on-line review and certification by an
                                  authorized certifying officer, including the holding of individual                                           Not
           2006 PMD-13            payments from inclusion in the payment schedule.                            Mandatory        Pending         Scheduled      Disbursing                                           Payment certification
                                  Generate a payment if the receiver information matches the obligation,                                       Not                                                                 Payment based on
           2006 PMD-14            under related 2-way matching option.                                        Mandatory        Pending         Scheduled      Disbursing                                           receipt
                                                                                                                                               Not                                                                 Disbursements-in-
           2006 PMD-15            Record disbursements-in-transit entries when payments are certified. Mandatory               Pending         Scheduled      Disbursing                                           transit
                                  Validate that invoices selected for payment will not disburse a fund                                                                                                             Do not disburse to
                                  into a negative cash position. Notify the agency of invoices that fail this                                  Not                                                                 negative cash
           2006 PMD-16            edit.                                                                       Mandatory        Pending         Scheduled      Disbursing                                           position
                                                                                                                                               Not
           2006 PMD-17            Select and process warehoused invoices for manual payment.               Mandatory           Pending         Scheduled      Disbursing                                           Manual payments
                                  Query preliminary payment schedule data. Identify a sample of
                                  invoices for certification based on agency-defined sampling criteria
                                  and the payment due date. Result is a list of invoice document
                                  numbers with drill down to invoice details, including data required on a                                     Not                                                                 Statistical sample of
           2006 PMD-18            proper vendor invoice per 5 CFR 1315.                                    Mandatory           Pending         Scheduled      Invoicing                                            invoices query
                                                                                                                                               Not                                                                 Distribute invoice
           2006 PMD-19            Distribute the payment of a single invoice to multiple bank accounts.       Mandatory        Pending         Scheduled      Disbursing                                           payment
                                  Export check and EFT payment files in the current Treasury FMS                                               Not
           2006 PMD-20            defined formats.                                                            Mandatory        Pending         Scheduled      Disbursing                                           Payment files




Printed on 5/20/2010                                                                                     93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                  Page 53 of 79
Financial Systems Integration Office                                                                 Requirements Tested Matrix
                                                                                                   Core Requirements & Test Status

 Requirement                                                                                                                                                                          Requirement Short
    Year               Req. No.                              Description                                  Status            Test Cycle     Test Status        Process   Test Notes          Name
                                  Export Automated Clearing House (ACH) payment files in the following
                                  formats:
                                  •   Corporate Trade Exchange (CTX) 820 file
                                  •   CTX Flat File
                                  •   Cash Concentration or Disbursement (CCD)
                                  •   CCD Plus Addendum (CCD+)
                                  •   Prearranged Payment and Deposit (PPD)                                                               Not
           2006 PMD-21            •   Prearranged Payment and Deposit Plus Addendum (PPD+).            Mandatory          Pending         Scheduled      Disbursing                  ACH payment formats
                                                                                                                                          Not                                        NACHA payment
           2006 PMD-22            Export NACHA payment formats for Non-Treasury DOs.                        Mandatory     Pending         Scheduled      Disbursing                  formats
                                  Validate that EFT payment file data submitted to Treasury will pass the
                                  following edits:
                                  •      RTNs exist in the Financial Organization Master File (FOMF) or
                                  other verified update file, for the financial institution.
                                  •      RTNs pass the Modulus 10 check on the validity of the check
                                  digit.
                                  •      RTNs for domestic banks are nine-digits, numeric-only, and not
                                  all zeroes
                                  •      RTNs for foreign banks are eight-digits, alpha-numeric, and not
                                  all zeroes
                                  •      ALCs are eight-digits and numeric only.
                                  •      Taxpayer Identification Numbers are nine-digits, numeric-only,                                   Not                                        Treasury edits on EFT
           2006 PMD-23            and not all zeroes.                                                       Mandatory     Pending         Scheduled      Disbursing                  files
                                  Prevent the creation of an EFT (Fedwire, ACH or CTX) payment that
                                  does not contain a RTN, bank account number and account type                                            Not                                        Treasury edits on
           2006 PMD-24            (checking or savings).                                                    Mandatory     Pending         Scheduled      Disbursing                  banking information
                                  Validate that employee ACH payments are generated only as PPD or                                        Not                                        ACH employee
           2006 PMD-25            PPD+ payments.                                                            Mandatory     Pending         Scheduled      Disbursing                  payments
                                  Validate that vendor ACH payments are generated only as CCD,                                            Not                                        ACH vendor
           2006 PMD-26            CCD+ or CTX formats.                                                      Mandatory     Pending         Scheduled      Disbursing                  payments
                                  Generate CTX payment files that meet the following specifications:
                                  •      Reflect balanced transactions (sum of all remittance records
                                  equals the transaction total).
                                  •      Include a valid settlement date (next business day or later).                                    Not                                        CTX vendor
           2006 PMD-27            •      Accommodate credit memos.                                          Mandatory     Pending         Scheduled      Disbursing                  payments
                                  Validate that CTX vendor payments contain properly structured
                                  remittance information, as specified in the CTX payment file's                                          Not                                        Treasury edits on
           2006 PMD-28            remittance record format.                                                 Mandatory     Pending         Scheduled      Disbursing                  CTX files
                                  Schedule and disburse U.S. dollar payments (SF 1166) through the
                                  Treasury's ECS, containing up to the limit of 60 payments per
                                  schedule (for non-summary schedules) and 100 schedules for each                                         Not
           2006 PMD-29            ECS terminal per day.                                                     Mandatory     Pending         Scheduled      Disbursing                  ECS payments
                                  Schedule and disburse U.S. dollar payments (SF 1166) through the
                                  Treasury's SPS containing up to the limit of 60 payments per schedule                                   Not
           2006 PMD-30            (for non-summary schedules).                                              Mandatory     Pending         Scheduled      Disbursing                  SPS payments
                                                                                                                                                                                     TAFS information on
                                  Capture the TAFS associated with each payment in ECS, SPS and                                           Not                                        Treasury payment
           2006 PMD-31            Bulk Vendor/Miscellaneous payment files.                                  Mandatory     Pending         Scheduled      Disbursing                  files
                                                                                                                                          Not                                        Payment schedule
           2006 PMD-32            Generate totals by TAFS on each ECS and SPS payment file.                 Mandatory     Pending         Scheduled      Disbursing                  totals by TAFS
                                  Combine ECS and SPS payment files with multiple ALCs into single
                                  files for transmission to Treasury. Include summary totals (items and                                                                              ECS and SPS
                                  dollars) by ALC and TAFS and for the entire file for certification                                      Not                                        payment files for
           2006 PMD-33            purposes.                                                                 Mandatory     Pending         Scheduled      Disbursing                  multiple ALCs
                                                                                                                                                                                     Bulk check payment
                                  Generate one bulk check payment file regardless of payee type                                           Not                                        files for multiple
           2006 PMD-34            (employee or vendor).                                                     Mandatory     Pending         Scheduled      Disbursing                  payee types




Printed on 5/20/2010                                                                                93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                      Page 54 of 79
Financial Systems Integration Office                                                                          Requirements Tested Matrix
                                                                                                            Core Requirements & Test Status

 Requirement                                                                                                                                                                                                          Requirement Short
    Year               Req. No.                                  Description                                            Status        Test Cycle     Test Status        Process              Test Notes                     Name
                                  Consolidate multiple payments to a single payee in accordance with
                                  TFM prescribed limitations (currently up to 14 lines of 55 characters
                                  each for check payments, up to 9,999 lines of 80 characters each for
                                  CTX payments). Itemize all payments covered by the one check or
                                  EFT (CTX only). Provide the option to issue separate checks to a                                                  Not                                                              Consolidate multiple
           2006 PMD-35            payee.                                                                            Mandatory       Pending         Scheduled      Disbursing                                        payments to payee
                                  Generate the following identification on each remittance, as allowed
                                  for by Treasury payment file formats and NACHA edits:                                                                                                                              Remittance
                                  •     Vendor invoice number(s) or account number                                                                                                                                   information on
                                  •     Obligating document number or other reference number                                                        Not                                                              Treasury payment
           2006 PMD-36            •     Discount, interest and offset amounts.                                      Mandatory       Pending         Scheduled      Disbursing                                        files
                                  Capture prompt payment information required by 5 CFR 1315,                                                        Not
           2006 PMD-37            including discounts taken, discounts lost, and interest paid.                     Mandatory       Pending         Scheduled      Disbursing                                        Prompt pay
                                  Query disbursement data. Parameters include accounting period
                                  range, disbursement type(s) to be included. Provide an option to
                                  exclude credit card transactions. Result is the total number of
                                  payments made on time by disbursement type. Query returns total                                                   Not                                                              Prompt Pay Metric
           2006 PMD-38            number of on-time and late payments made based on due date.                       Mandatory       Pending         Scheduled      Disbursing                                        Query
                                  Record the U.S. SGL prescribed general ledger entries for the                                                     Not
           2006 PMD-39            payment of advances, prepaid expenses, loans, and grants.                         Mandatory       Pending         Scheduled      Disbursing                                        Payments GL entries
                                                                                                                                                    Not
           2006 PMD-40            Record the establishment and replenishment of imprest funds.                      Mandatory       Pending         Scheduled      Disbursing                                        Imprest funds
                                                                                                                                                                                                                     Imprest funds and
                                  Record purchases made through the use of imprest funds and third-                                                 Not                                                              third party U.S. SGL
           2006 PMD-41            party drafts.                                                                     Mandatory       Pending         Scheduled      Disbursing                                        entries
                                                                                                                                                                                                                     Simultaneous
                                  Record "obligate and pay" transactions where obligation and payment                                               Not                                                              obligation and
           2006 PMD-42            occur simultaneously.                                               Mandatory                     Pending         Scheduled      Disbursing                                        payment
                                  Record payments made on behalf of another agency, citing the other                                                Not                                                              Payments for other
           2006 PMD-43            agency's funding information.                                       Mandatory                     Pending         Scheduled      Disbursing                                        agencies
                                  Record payment transactions from other systems, such as payroll and
                                  travel. Identify whether or not disbursement has already been made,
                                  and record the U.S. SGL prescribed general ledger entries. Schedule
                                  those disbursements not already made for payment through the Core                                                 Not                                                              Interfaced payment
           2006 PMD-44            financial system.                                                   Mandatory                     Pending         Scheduled      Disbursing                                        entries
                                                                                                                                                                                  Clarification: Made requirement
2006                              Capture all mandatory and optional bulk file data for IPAC payment, collection,                                   Not                           wording generic instead listing
Clarification     PMD-45          zero dollar, adjustment and SGL posting transactions.                             Mandatory       Pending         Scheduled      Disbursing     required data elements.            IPAC transactions
                                  Capture the following additional information with IPAC
                                  reclassifications:                                                                                                                              Clarification: Deleted this
2006                              •    Original DO symbol                                                                           Not                                           requirement favor of revision to
Clarification     PMD-46          •    Voucher number.                                                              Mandatory       Applicable      Deleted        Disbursing     requirement PMD-45.                IPAC reclassifications
                                                                                                                                                                                  Clarification: Deleted this
2006                              Capture SGL comments with IPAC disbursement and collection                                        Not                                           requirement favor of revision to   IPAC posted SGL
Clarification     PMD-47          transactions.                                                                     Mandatory       Applicable      Deleted        Disbursing     requirement PMD-45.                transactions
                                  Export a bulk file in the currently required format for uploading the
                                  following interagency transactions to IPAC:
                                  •     Payment
                                  •     Collection
                                  •     Adjustment
                                  •     Zero dollar                                                                                                 Not
           2006 PMD-48            •     SGL posting.                                                                Mandatory       Pending         Scheduled      Disbursing                                        IPAC bulk file export
                                  Record transactions to reflect disbursement activity initiated by other                                           Not
           2006 PMD-49            agencies and recorded in IPAC.                                                    Mandatory       Pending         Scheduled      Disbursing                                        IPAC GL entries
                                  Record vendor credit memoranda as accounts receivable or negative                                                 Not                                                              Credit memo
           2006 PMD-50            accounts payable.                                                                 Mandatory       Pending         Scheduled      Disbursing                                        processing




Printed on 5/20/2010                                                                                          93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                             Page 55 of 79
Financial Systems Integration Office                                                                    Requirements Tested Matrix
                                                                                                      Core Requirements & Test Status

 Requirement                                                                                                                                                                                  Requirement Short
    Year               Req. No.                                   Description                                    Status        Test Cycle     Test Status        Process        Test Notes          Name
                                  Reduce payments to vendors to satisfy outstanding credit memos.
                                  Record the collection for the amount offset and reduce expenditures
                                  under the related obligation. If a credit is not fully liquidated by one
                                  payment, maintain the balance of the credit for application against a                                      Not                                             Process credit
           2006 PMD-51            future payment.                                                            Mandatory       Pending         Scheduled      Disbursing                       memoranda offsets
                                  Record credit memo offsets against subsequent payments to the                                              Not                                             Credit memoranda
           2006 PMD-52            same vendor from the same or a different funding source.                   Mandatory       Pending         Scheduled      Disbursing                       offsets across funds
                                  Notify vendors of payments that have been offset by credit memos.                                                                                          Notify vendors of
                                  Specify the invoice number, invoice amount, offset amount, payment                                         Not                                             credit memoranda
           2006 PMD-53            amount and payment date.                                                   Mandatory       Pending         Scheduled      Disbursing                       offsets
                                  Prevent agency offset of vendor payments based on agency-defined
                                  criteria such as accounting classification elements, vendor number,                                        Not                                             Credit memo offset
           2006 PMD-54            and vendor CCR business type.                                              Mandatory       Pending         Scheduled      Disbursing                       exclusions

                                  Generate the reversal of an entire payment schedule or a single
                                  payment within a payment schedule based on a single, online action.
                                  Generate disbursement-in-transit reversal entries, record the re-                                          Not                                             Reverse scheduled
           2006 PMD-55            established accounts payable, and update related payment records.          Mandatory       Pending         Scheduled      Disbursing                       payments
                                  For payments that reference obligations in cancelled funds, bring                                                                                          Payments
                                  forward accounting and non-financial information from the original                                         Not                                             Referencing
           2006 PMD-56            obligation document to an invoice in the current year.                     Mandatory       Pending         Scheduled    Disbursing                         Cancelled Funds
                                                                                                                                             Not
                                  Calculate payments to foreign vendors based on current exchange                        Not                 Tested/Value                                    Calculate foreign
           2006 PMD-57            rates.                                                                     Value Added Applicable          Added        Disbursing                         payment amounts
                                                                                                                                             Not
                                  Generate foreign payment file formats, including International Direct              Not                     Tested/Value                                    Foreign payment file
           2006 PMD-58            Deposit (IDD).                                                         Value Added Applicable              Added        Disbursing                         formats
                                  Query invoice status information. Parameters include: vendor number,
                                  vendor name (legal, DBA or division), TIN, DUNS number and vendor
                                  invoice number. List the selected invoices, their due dates, the dates
                                  that the following stages were reached and the number of days
                                  between each date:
                                  •     Invoice received
                                  •     Invoice suspended due to validation errors
                                  •     Invoice held
                                  •     Invoice returned to vendor
                                  •     Invoice resubmitted by vendor
                                  •     Invoice approved and warehoused
                                  •     Invoice scheduled for payment (disbursement-in-transit)                                              Not
           2006 PME-01            •     Invoice paid.                                                    Mandatory   Pending                 Scheduled      Payment Follow-up                Invoice Status Query




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                            Page 56 of 79
Financial Systems Integration Office                                                                    Requirements Tested Matrix
                                                                                                      Core Requirements & Test Status

 Requirement                                                                                                                                                                                                     Requirement Short
    Year               Req. No.                                  Description                                      Status        Test Cycle     Test Status        Process                  Test Notes                  Name

                                  Maintain a history of the following information for each payment voucher:
                                  •   Accounting classification information
                                  •   ALC
                                  •   TAS/BETC
                                  •   Referenced obligation document number(s)
                                  •   Source document number(s) (reimbursable agreement number, BPA and
                                  associated BPA call number, Contract and associated delivery/task order
                                  number, and grant number)
                                  •   Total invoice amount
                                  •   Payment voucher document number
                                  •   Vendor invoice number
                                  •   Vendor information (number, name, address, TIN, and DUNS (BPN)
                                  number                                                                                                                                         Clarifications:
                                  •   DUNS+4 number for CCR and FedReg vendors                                                                                                   1-Added required FedReg data.
                                  •   Payment address(es) and/or bank account number(s) and routing                                                                              2-Changed payment to payment
                                  number(s)                                                                                                                                      voucher in requirement short name
                                  •   Payment method(s) (e.g., check, EFT)                                                                                                       and text.
                                  •   Payment amounts                                                                                                                            3-Changed requirement to allow for
                                  •   Interest paid                                                                                                                              the capture of data for multiple
                                  •   Discount(s) taken                                                                                                                          payments from one payment
                                  •   Internal offset(s) made                                                                                                                    voucher.
2006                              •   Date(s) due                                                                                             Not                                4-Added of DUNS (BPN) number as Payment voucher
Clarification     PME-02          •   Date(s) paid.                                                           Mandatory       Pending         Scheduled      Payment Follow-up   required data.                     history
                                  Query payment data. Parameter is accounting period range. Result is
                                  number of payments and percent of total by payment method (EFT vs.                                          Not
           2006 PME-03            check).                                                             Mandatory               Pending         Scheduled      Payment Follow-up                                 EFT Metric Query



                                  Generate the Unmatched Invoice Document Lines Report. Result is a
                                  list of selected invoice document numbers with document lines not
                                  matched to obligations, receipts, and/or acceptance, as required by
                                  the matching terms of the obligation (2, 3 or 4-way matching). Report
                                  the following information for each invoice document listed:
                                  •      Vendor number and name
                                  •      Invoice number
                                  •      Invoice date
                                  •      Invoice receipt date
                                  •      Invoice amount
                                  •      Referenced obligation number
                                  •      Document number
                                  •      Document line number(s)
                                  •      Document line amount(s)
                                  •      Document line accounting classification
                                  •      Unmatched document(s) (obligation, receipt and/or acceptance)
                                  •      Age, in days, that invoice document line has been unmatched.                                                                                                          Unmatched Invoice
                                  Sorting options include document number, vendor number, vendor                                              Not                                                              Document Lines
           2006 PME-04            name, accounting classification and unmatched age.                    Mandatory             Pending         Scheduled      Payment Follow-up                                 Report
                                  Generate a report of payment vouchers past their due date, as of
                                  current system date. List the selected payment vouchers with the
                                  following information:
                                  •      Payment voucher number
                                  •      Referenced obligation number
                                  •      Vendor invoice number
                                  •      Vendor number and name
                                  •      Invoice date
                                  •      Invoice amount
                                  •      Invoice due date
                                  •      Number of days late.                                                                                 Not                                                              Late Payments
           2006 PME-05            Sort options include number of days late and vendor number.           Mandatory             Pending         Scheduled      Payment Follow-up                                 Pending Report


Printed on 5/20/2010                                                                                    93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                            Page 57 of 79
Financial Systems Integration Office                                                               Requirements Tested Matrix
                                                                                                 Core Requirements & Test Status

 Requirement                                                                                                                                                                                                Requirement Short
    Year               Req. No.                                  Description                               Status          Test Cycle     Test Status        Process                  Test Notes                  Name
                                  Generate IRS Forms 1099-MISC, 1099-INT and 1099-G in accordance
                                  with IRS regulations and in current IRS acceptable format, including
                                  hard copy and electronic form (i.e., bulk file). For example, produce
                                  an IRS Form 1099-MISC for payments of $600 or more to a sole                                           Not
           2006 PME-06            proprietor for services rendered.                                     Mandatory        Pending         Scheduled      Payment Follow-up                                  IRS 1099 Forms

                                                                                                                                                                                                           IRS 1099-MISC
                                  Report third-party payments on the principal vendors' IRS 1099-MISC                                    Not                                                               reporting of payments
           2006 PME-07            forms.                                                                  Mandatory      Pending         Scheduled      Payment Follow-up                                  to third parties
                                  Query IRS 1099-MISC information. Parameters include calendar year,
                                  vendor name (legal or DBA), TIN and DUNS+4 number. Result is                                           Not
           2006 PME-08            details supporting IRS 1099-MISC reporting.                             Mandatory      Pending         Scheduled      Payment Follow-up                                  IRS 1099-MISC query
                                  Query payments data. Identify a sample of payments for review based
                                  on agency-defined sampling criteria and the date(s) of payment.
                                  Result is a list of invoice document numbers with drill down to invoice
                                  details, including data required on a proper vendor invoice per 5 CFR                                  Not                                                               Statistical sample of
           2006 PME-09            1315.                                                                   Mandatory      Pending         Scheduled    Payment Follow-up                                    payments query
                                                                                                                                         Not
                                  Generate e-mail notification to employees of travel payments made by             Not                   Tested/Value                                                      Travel payment
           2006 PME-10            disbursing offices.                                                  Value Added Applicable            Added        Payment Follow-up                                    notification
                                  Maintain customer information to support receivable management
                                  processes including the following:
                                  •    Customer name
                                  •    Customer ID number
                                  •    Customer type (Federal agency, foreign/sovereign, state/local
                                  government, commercial, or consumer)
                                  •    DUNS (BPN) number
                                  •    DUNS+4 number
                                  •    Billing method (IPAC, 1081, paper bill, or other)
                                  •    TIN
                                  •    Customer address
                                  •    Customer contact name
                                  •    Customer contact telephone number
                                  •    Customer contact e-mail address
                                  •    Federal vs. Non-Federal indicator
                                  •    GFRS and FACTS I Trading Partner codes (for Federal
                                  customers)
                                  •    ALC (for Federal customers)
                                  •    IRS 1099-C indicator
                                  •    Third-party payer name
                                  •    Third-party payer address
                                  •    Third-party payer contact name
                                  •    Third-party payer contact telephone number                                                                       Customer
2006                              •    Comment field                                                                                     Not            Information         Clarification:Added DUNS (BPN)
Clarification     RMA-01          •    Active/Inactive indicator.                                      Mandatory   Pending               Scheduled      Maintenance         number as required data.       Customer information




Printed on 5/20/2010                                                                               93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                              Page 58 of 79
Financial Systems Integration Office                                                                          Requirements Tested Matrix
                                                                                                            Core Requirements & Test Status

 Requirement                                                                                                                                                                                       Requirement Short
    Year               Req. No.                                     Description                                         Status        Test Cycle     Test Status        Process      Test Notes          Name
                                  Capture the following vendor information:
                                  •     Customer ID number (agency-assigned)
                                  •     Business Name
                                  •     Trading Style Name
                                  •     Customer name (Division)
                                  •     Physical address
                                  •     Business type (support FedReg published business rules for business
                                  type: Seller, Buyer, Buyer and Seller)
                                  •     Mailing address
                                  •     Headquarters DUNS (BPN) Number
                                  •     Headquarters Name
                                  •     Agency DUNS (BPN) Number
                                  •     Agency Name
                                  •     Hierarchy Code
                                  •     Status Code (0 - Not a subsidiary, 3 Subsidiary)
                                  •     Source
                                  •     Treasury Index (Treas Dept Code)
                                  •     Employer Identification Number
                                  •     ALC
                                  •     Disbursing Office
                                  •     POC email (registration, elimination, sales, accounts receivable, accounts
                                  payable)
                                  •     POC Name (First, Last, Middle Initial for POCs to include registration,
                                  elimination, sales, accounts receivable, accounts payable))
                                  •     POC Phone (area code, phone number, extension for POCs to include
                                  registration, elimination, sales, accounts receivable, accounts payable))
                                  •     POC Phone International (POCs to include registration, elimination, sales,
                                  accounts receivable, accounts payable)
                                  •     POC Fax (POCs to include registration, elimination, sales, accounts
                                  receivable, accounts payable)
                                  •     POC Address (POCs to include registration, elimination, sales, accounts
                                  receivable, accounts payable)
                                  •     Annual Revenue
                                  •     Merchant ID (ID1)                                                                                                          Customer
2006                              •     Product Service codes                                                                                       Not            Information                    Federal Customer
Addendum          RMA-01a         •     FSC code                                                                     Mandatory      Pending         Scheduled      Maintenance                    Information
                                  Validate TINs when adding or updating customer records. Notify the                                                               Customer
                                  agency when duplicate TINs are identified. Allow the error message to                                             Not            Information                    Validate Customer
           2006 RMA-02            be overridden.                                                        Mandatory                   Pending         Scheduled      Maintenance                    TINs
                                  Query customer file. Parameters include:
                                  •    Customer number
                                  •    Customer name
                                  •    Customer TIN
                                  •    DUNS+4 number                                                                                                               Customer
                                  •    IRS 1099-C indicator.                                                                                        Not            Information
           2006 RMA-03            Result is a display of all data for the specified customer.           Mandatory                   Pending         Scheduled      Maintenance                    Customer query
                                  Maintain a history of changes made to customer information. Capture                                                              Customer
                                  name of data item changed, before and after values, entry date and                                                Not            Information
           2006 RMA-04            time and ID of user who made the change.                              Mandatory                   Pending         Scheduled      Maintenance                    Customer file history

                                  Query customer history. Parameters include customer number,                                                                      Customer
                                  change date range. Results include date and time of change, ID of                                                 Not            Information                    Customer history
           2006 RMA-05            user who made the change, item name, before and after data values.                 Mandatory      Pending         Scheduled      Maintenance                    query
                                                                                                                                                                   Customer
                                  Deactivate customers on demand or based on agency-specified length                                                Not            Information                    Criteria for
           2006 RMA-06            of time with no activity.                                          Mandatory                      Pending         Scheduled      Maintenance                    deactivating customer
                                                                                                                                                                   Customer
                                  Prevent the deactivation of customers that have unliquidated                                                      Not            Information                    Customer deactivatio
           2006 RMA-07            receivables in the system.                                                         Mandatory      Pending         Scheduled      Maintenance                    n edit
                                  Record accounts receivable and corresponding revenues, expense                                                    Not            Receivables and
           2006 RMB-01            reductions, advance/prepayment reclassifications, or other offsets.                Mandatory      Pending         Scheduled      Billing                        Record receivables




Printed on 5/20/2010                                                                                          93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                          Page 59 of 79
Financial Systems Integration Office                                                                         Requirements Tested Matrix
                                                                                                           Core Requirements & Test Status

 Requirement                                                                                                                                                                                                            Requirement Short
    Year               Req. No.                                   Description                              Status                    Test Cycle     Test Status           Process              Test Notes                     Name
                                  Record adjustments to receivables and capture a reason and                                                       Not            Receivables and                                      Receivable
           2006 RMB-02            description on each adjustment.                                       Mandatory                  Pending         Scheduled      Billing                                              adjustments
                                  Capture an agency-defined receivable type on receivable documents
                                  to identify the activity which generated the receivable, such as: the
                                  sale of goods or services, overpayments, unused advances subject to                                              Not            Receivables and
           2006 RMB-03            refund, fees and fines.                                               Mandatory                  Pending         Scheduled      Billing                                              Receivable type

                                  Capture the following additional information on receivable documents:
                                  •    Baseline receivable date (used to properly age the receivable
                                  and determine the delinquency date)
                                  •    Customer ID number                                                                                          Not            Receivables and                                      Receivable document
           2006 RMB-04            •    Reimbursable agreement number.                                   Mandatory                  Pending         Scheduled      Billing                                              data
                                                                                                                                                                                    Clarification: Deleted this
2006                              Capture the original baseline receivable date on receivables converted                           Not                            Receivables and   duplicative requirement            Converted
Clarification     RMB-05          from legacy systems, in order to properly age the receivable.            Mandatory               Applicable      Deleted        Billing           (covered elsewhere).               receivables
                                  Generate bills to non-reimbursable customers based on receivables
                                  recorded. Include the following information on the bills:
                                  •    Customer name
                                  •    Customer address
                                  •    Customer contact name
                                  •    Agency contact name, office, address and telephone number                                                   Not            Receivables and                                      Non-reimbursable
           2006 RMB-06            •    Date due.                                                           Mandatory               Pending         Scheduled      Billing                                              billings
                                  Calculate billing amounts and generate bills to customers based on
                                  reimbursable agreement billing terms, such as:
                                  •    Percentage of work completed
                                  •    Accrued expenditures
                                  •    Actual costs incurred (direct and indirect using data from the cost
                                  management system).
                                  Include the following information on the bills:
                                  •    Customer name
                                  •    Customer address
                                  •    Customer contact name
                                  •    Agency contact name, office, address and telephone number;
                                  and                                                                                                              Not            Receivables and                                      Reimbursable
           2006 RMB-07            •    Date due.                                                           Mandatory               Pending         Scheduled      Billing                                              agreement billings
                                                                                                                                                                                                                       Reimbursable
                                  Monitor billing in excess of the billing limit on a reimbursable                                                 Not            Receivables and                                      agreement billing
           2006 RMB-08            agreement. Reject, warn or inform the agency when limit is exceeded. Mandatory                   Pending         Scheduled      Billing                                              limits
                                  Generate bills based on pre-defined fee schedules or payment                                                     Not            Receivables and
           2006 RMB-09            schedules.                                                           Mandatory                   Pending         Scheduled      Billing                                              Scheduled billings
                                                                                                                                                   Not            Receivables and                                      Bills to Third-party
           2006 RMB-10            Generate bills to third party payers as responsible debtors.                     Mandatory       Pending         Scheduled      Billing                                              payers
                                  Customize the text and data elements to be displayed on system-generated
                                  bills, by customer type, receivable type, or billing method. For example, a bill for
2006                              the sale of goods and services would need to contain different supporting text                                   Not            Receivables and   Clarification: Deleted the IPAC in
Clarification     RMB-11          than a bill to an employee for an overpayment.                                       Mandatory   Pending         Scheduled      Billing           bill example.                      Bill types
                                  List principal, interest, penalties, and administrative charges                                                  Not            Receivables and
           2006 RMB-12            separately on a bill and provide a description of each.                          Mandatory       Pending         Scheduled      Billing                                           Bill data
                                                                                                                                                   Not            Receivables and   This erroneous requirement will
           2006 RMB-13            Include advances and prior collections received on bills.                        Mandatory       Pending         Scheduled      Billing           eventually be deleted.          Additional bill data
                                  Generate bills in hard-copy format, including Standard Forms 1080                                                Not            Receivables and
           2006 RMB-14            and 1081.                                                                        Mandatory       Pending         Scheduled      Billing                                              Bill forms
                                                                                                                                                   Not            Receivables and
           2006 RMB-15            Derive the bill date from the system date. Allow for override.          Mandatory                Pending         Scheduled      Billing                                              Derive bill date
                                  Capture a unique bill number and a bill date on system-generated                                                 Not            Receivables and
           2006 RMB-16            bills.                                                                  Mandatory                Pending         Scheduled      Billing                                              Bill number and date
                                  Consolidate multiple receivables for a customer onto one bill retaining                                          Not            Receivables and                                      Consolidating
           2006 RMB-17            identification of each receivable separately within the bill.           Mandatory                Pending         Scheduled      Billing                                              receivables


Printed on 5/20/2010                                                                                         93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                 Page 60 of 79
Financial Systems Integration Office                                                                         Requirements Tested Matrix
                                                                                                           Core Requirements & Test Status

 Requirement                                                                                                                                                                                                                 Requirement Short
    Year               Req. No.                                    Description                                            Status        Test Cycle     Test Status        Process                  Test Notes                      Name

                                  Update receivable status from unbilled to billed when bills are                                                     Not            Receivables and
           2006 RMB-18            generated. Associate the receivable with the bill number and bill date. Mandatory                   Pending         Scheduled      Billing                                                Receivable status
                                  Capture information from manually prepared bills. Update receivable
                                  document (e.g., change status of receivable from unbilled to billed)                                                Not            Receivables and
           2006 RMB-19            with manual bill information.                                           Mandatory                   Pending         Scheduled      Billing                                                Manual bills
                                                                                                                                                                                       Clarification: Changed "update the
                                  Re-establish a receivable when a check collection is cancelled due to                                                                                receivable status from billed to
2006                              insufficient funds or a when a chargeback is recorded. Capture the original                                         Not            Receivables and   unbilled" to "ensure that the
Clarification     RMB-20          baseline receivable date and ensure that the receivable is rebilled.               Mandatory        Pending         Scheduled      Billing           receivable is rebilled."             Returned checks
                                                                                                                                                      Not            Receivables and                                        Reschedule
           2006 RMB-21            Reschedule existing receivables to be paid under installment plans.                Mandatory        Pending         Scheduled      Billing                                                receivables
                                                                                                                                                      Not            Receivables and
           2006 RMB-22            Reschedule a receivable multiple times.                                  Mandatory                  Pending         Scheduled      Billing                                                Multiple rescheduling
                                  Generate a Debt Repayment Amortization Schedule. Parameters
                                  include the receivable number, final due date, begin date, frequency of
                                  payments, and interest rate. Result is an amortization schedule that
                                  displays the original amount of debt, payment dates, amount of
                                  incremental payments, and balance remaining after each payment for                                                  Not            Receivables and
           2006 RMB-23            debt being paid under an installment plan or rescheduled debt.           Mandatory                  Pending         Scheduled      Billing                                                Amortization schedule
                                  Generate Customer Account Statements. Parameters include
                                  customer type, customer ID number, customer name, and time period
                                  (month, quarter, year-to-date). Result is a statement for each
                                  customer that includes:
                                  •     Statement date
                                  •     Customer ID number
                                  •     Customer name
                                  •     Customer address
                                  •     Customer contact name
                                  •     Agency name
                                  •     Agency contact name
                                  •     Agency contact phone number
                                  •     Agency contact email address
                                  •     Balance brought forward
                                  •     Receivables established (including due dates)
                                  •     Interest
                                  •     Penalties
                                  •     Administrative costs
                                  •     Adjustments made
                                  •     Collections received (identify principal, interest, penalties, and
                                  administrative charges separately to indicate how collections were
                                  applied)
                                  •     Outstanding receivable balance.
                                  Provide agency the option to generate customer statements in Excel
                                  format.                                                                                                             Not            Receivables and                                        Customer account
           2006 RMB-24                                                                                     Mandatory                  Pending         Scheduled      Billing                                                statements
                                  Query outstanding receivable balance. Parameter is the receivable
                                  document number. Result is the original amount of the receivable, the
                                  current outstanding amount of the receivable and a detailed list of all
                                  activity related to the receivable, including:
                                  •     Adjustments
                                  •     Interest
                                  •     Penalties
                                  •     Administrative charges
                                  •     Collections                                                                                                                                                                         Outstanding
                                  •     Waivers                                                                                                       Not            Receivables and                                        receivable balance
           2006 RMB-25            •     Write-offs.                                                        Mandatory                  Pending         Scheduled      Billing                                                query




Printed on 5/20/2010                                                                                            93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                   Page 61 of 79
Financial Systems Integration Office                                                                 Requirements Tested Matrix
                                                                                                   Core Requirements & Test Status

 Requirement                                                                                                                                                                              Requirement Short
    Year               Req. No.                                 Description                                    Status        Test Cycle     Test Status        Process      Test Notes          Name
                                  Query reimbursable agreements. Parameters include Reimbursable
                                  Agreement Number, Customer ID Number, Customer Name, Project,
                                  or Fund. Result is a display of the following information for each
                                  reimbursable agreement selected:
                                  •     Period of performance
                                  •     Billing terms
                                  •     Reimbursable agreement amount
                                  •     Billing limit
                                  •     Amount obligated
                                  •     Amount expended
                                  •     Unfilled customer order amount
                                  •     Advances collected
                                  •     Advances applied to earned revenue
                                  •     Remaining balance on advances
                                  •     Amount earned
                                  •     Amount billed
                                  •     Amount collected on receivables                                                                    Not            Receivables and                Reimbursable
           2006 RMB-26            •     Outstanding accounts receivable (billed and unbilled).              Mandatory      Pending         Scheduled      Billing                        agreement query
                                  Calculate and record late payment interest charges on overdue non-
                                  Federal receivables based on the Treasury Current Value of Funds                                         Not
           2006 RMC-01            Rate (CVFR) unless otherwise specified by the agency.                     Mandatory      Pending         Scheduled      Debt Management                Assessing interest
                                  Calculate and record late payment interest charges on overdue non-
                                  Federal receivables based on an agency-assigned interest rate
                                  different from the CVFR for a particular receivable, customer, or                                        Not                                           Interest assessment
           2006 RMC-02            customer type.                                                            Mandatory      Pending         Scheduled      Debt Management                rate

                                  Calculate and record penalties and administrative charges on overdue                                                                                   Penalties and
                                  receivables based on an agency-assigned rate or amount for a                                             Not                                           administrative
           2006 RMC-03            particular receivable, customer, customer type, or receivable type.       Mandatory      Pending         Scheduled      Debt Management                charges
                                  Optionally record interest, penalties, or administrative costs to                                                                                      Accounting
                                  accounting classification elements that are different from those to                                      Not                                           classification of
           2006 RMC-04            which the principal amount is recorded.                                   Mandatory      Pending         Scheduled      Debt Management                receivables
                                  Optionally cease or continue accruing interest on delinquent debts that                                  Not                                           Interest on referred
           2006 RMC-05            have been referred to Treasury or another agency.                         Mandatory      Pending         Scheduled      Debt Management                debt
                                  Generate dunning notices on overdue receivables at frequencies
                                  specified by the agency, including on-demand, and by agency-defined                                      Not
           2006 RMC-06            parameters, including customer type.                                      Mandatory      Pending         Scheduled      Debt Management                Dunning notices
                                  Customize text used on dunning notices based on receivable age                                           Not
           2006 RMC-07            categories and customer types.                                            Mandatory      Pending         Scheduled      Debt Management                Dunning notice text

                                  Generate an Accounts Receivable Aging Report. Parameters include:
                                  •   Accounting Period
                                  •   TAS or Internal Fund Code
                                  •   General Ledger Account
                                  •   Customer type
                                  •   Federal/Non Federal Indicator
                                  •   Customer ID number.
                                  Result is a report that displays the outstanding receivable balances in                                  Not                                           Accounts Receivable
           2006 RMC-08            each of the Delinquent Debt Age categories listed on the TROR.          Mandatory        Pending         Scheduled      Debt Management                Aging Report




Printed on 5/20/2010                                                                                 93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                          Page 62 of 79
Financial Systems Integration Office                                                                    Requirements Tested Matrix
                                                                                                      Core Requirements & Test Status

 Requirement                                                                                                                                                                                 Requirement Short
    Year               Req. No.                                  Description                                      Status        Test Cycle     Test Status        Process      Test Notes          Name

                                  Query accounts receivable by age categories. Parameters include:
                                  •     Accounting Period
                                  •     TAS or Internal Fund Code
                                  •     General Ledger Account
                                  •     Customer type
                                  •     Federal/Non Federal Indicator
                                  •     Customer ID number.
                                  Result is a display of the outstanding receivable balances in each of
                                  the Delinquent Debt Age categories listed on the TROR. Drill-down to                                        Not                                           Accounts Receivable
           2006 RMC-09            a detailed list of outstanding receivables within any one age category. Mandatory           Pending         Scheduled      Debt Management                Aging Query
                                  Identify receivables that may be eligible for write-off. Selection criteria
                                  is:
                                  •     Delinquent debt age category
                                  •     Customer type
                                  •     Receivable type.
                                  Display selected items on-line. Include the receivable number,
                                  outstanding amount, age of receivable, vendor or customer name, and
                                  vendor or customer ID number of each receivable. Provide the option
                                  to mark a receivable as eligible for write-off.                                                             Not                                           Receivables eligible
           2006 RMC-10                                                                                        Mandatory       Pending         Scheduled      Debt Management                for write-off
                                  Record the waiver and write-off of receivables, including interest,                                         Not                                           Waivers and write-
           2006 RMC-11            penalties, and administrative charges.                                      Mandatory       Pending         Scheduled      Debt Management                offs
                                  Classify receivables written off as "Currently not Collectible" or "Closed                                  Not
           2006 RMC-12            Out."                                                                       Mandatory       Pending         Scheduled      Debt Management                Classify write offs
                                                                                                                                              Not                                           Waived and written-
           2006 RMC-13            Maintain data on receivables that have been waived or written-off.           Mandatory      Pending         Scheduled      Debt Management                off receivables
                                  Identify receivables that may be eligible for referral. Selection criteria
                                  is:
                                  •     Delinquent debt age category
                                  •     Customer type
                                  •     Receivable type.
                                  Display selected items on-line. Include receivable number, receivable
                                  amount, age of receivable, vendor or customer name, and vendor or
                                  customer ID number of each receivable. Provide the option to mark                                           Not                                           Receivables eligible
           2006 RMC-14            receivables as eligible referral.                                            Mandatory      Pending         Scheduled      Debt Management                for referral
                                  Generate a delinquent debt referral file for transmission to Treasury in                                    Not                                           Delinquent debt
           2006 RMC-15            accordance with the Debt Collection Improvement Act (DCIA).                  Mandatory      Pending         Scheduled      Debt Management                referral file
                                  Update receivables with dunning notice dates, referral dates, and                                           Not
           2006 RMC-16            comments to support debt collection activities.                              Mandatory      Pending         Scheduled      Debt Management                Receivable updates
                                  Calculate and record the allowance for loss on accounts receivable
                                  based on agency-defined criteria, including percentage of gross book
                                  value of receivables within an age category, customer type, and                                             Not
           2006 RMC-17            receivable type.                                                             Mandatory      Pending         Scheduled      Debt Management                Allowance for loss
                                  Classify delinquent debt by the following categories needed for the
                                  TROR:
                                  •    In Bankruptcy
                                  •    In Forbearance or formal appeals process
                                  •    In Foreclosure
                                  •    At private collection agencies
                                  •    At DOJ
                                  •    Eligible for internal offset
                                  •    In wage garnishment
                                  •    At Treasury for cross-servicing
                                  •    At Treasury for Offset
                                  •    At Agency                                                                                              Not                                           Delinquent debt
           2006 RMC-18            •    Other.                                                                  Mandatory      Pending         Scheduled      Debt Management                categories




Printed on 5/20/2010                                                                                    93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                          Page 63 of 79
Financial Systems Integration Office                                                                  Requirements Tested Matrix
                                                                                                    Core Requirements & Test Status

 Requirement                                                                                                                                                                              Requirement Short
    Year               Req. No.                                 Description                                    Status        Test Cycle     Test Status         Process     Test Notes          Name
                                  Generate the Treasury Report on Receivables (TROR). Parameter is
                                  the fiscal year and quarter. Result is the TROR in accordance with
                                  Treasury form and instructions. Ensure reported totals agree with the                                    Not                                           Treasury Report on
           2006 RMC-19            general ledger.                                                          Mandatory       Pending         Scheduled      Debt Management                Receivables (TROR)


                                  Query customer receivables. Parameters include Customer ID
                                  Number, Customer Name, TIN, Trading partner codes. Result is a
                                  display of the customer's information (e.g., customer ID number,
                                  customer name, TIN, trading partner codes) and all receivable-related
                                  activity associated with the customer, including the following:
                                  •     Principal
                                  •     Interest
                                  •     Penalties
                                  •     Administrative charges
                                  •     Adjustments
                                  •     Collections
                                  •     Waivers
                                  •     Write-offs
                                  •     Receivable balance.
                                  Group interest, penalties, and administrative charges with their
                                  associated principal. Drill down to the detailed transactions,
                                  documents, and document details (e.g., document numbers,
                                  transaction dates, document reference numbers, receivable statuses
                                  (billed or unbilled), bill numbers (if billed), bill dates, dunning notice                               Not                                           Customer receivables
           2006 RMC-20            dates, referral dates, due dates, and delinquent debt statuses).           Mandatory     Pending         Scheduled      Debt Management                query
                                                                                                                                           Not
           2006 RMC-21            Generate IRS form 1099-C in accordance with IRS instructions.            Mandatory       Pending         Scheduled      Debt Management                IRS Form 1099-C
                                  Capture the following additional information on collections:
                                  •     Vendor/customer ID number and name
                                  •     Deposit number
                                  •     Deposit date
                                  •     Deposit confirmation date
                                  •     Obligation reference number
                                  •     Reimbursable agreement reference number
                                  •     Advance reference number
                                  •     Payment reference number
                                  •     Source (Cash, EFT, Check, Money order, Credit card, IPAC, SF
                                  1081, Electronic file from bank, or Treasury Offset Program)                                             Not            Collections and
           2006 RMD-01            •     Comments.                                                          Mandatory       Pending         Scheduled      Offsets                        Collection data
                                  Record collections against receivables. Reference the receivable
                                  document and update customer records and related billing                                                 Not            Collections and                Collections against
           2006 RMD-02            information.                                                             Mandatory       Pending         Scheduled      Offsets                        receivables
                                  Record collections with corresponding revenues, expenditure
                                  reductions, advance/prepayment reclassifications or other offsets,                                       Not            Collections and                Collections without
           2006 RMD-03            when receivables were not previously established.                        Mandatory       Pending         Scheduled      Offsets                        receivables
                                  Apply collections against receivables in the following order: first to
                                  penalty and administrative costs, second to interest receivable, and
                                  third to outstanding debt principal, in accordance with the DCIA,                                        Not            Collections and                Order for applying
           2006 RMD-04            unless otherwise stated in program statute.                              Mandatory       Pending         Scheduled      Offsets                        collections
                                  Record collections received against receivables that were waived or                                      Not            Collections and                Collections on closed
           2006 RMD-05            written off.                                                             Mandatory       Pending         Scheduled      Offsets                        receivables
                                  Record collections of refunds of previous overpayments or erroneous
                                  payments. If a receivable was not previously established, reference
                                  the obligation. Reduce cumulative payments and expenditures under                                        Not            Collections and                Collections of
           2006 RMD-06            the obligation.                                                          Mandatory       Pending         Scheduled      Offsets                        overpayments




Printed on 5/20/2010                                                                                 93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                          Page 64 of 79
Financial Systems Integration Office                                                                         Requirements Tested Matrix
                                                                                                           Core Requirements & Test Status

 Requirement                                                                                                                                                                                                                Requirement Short
    Year               Req. No.                                    Description                                         Status        Test Cycle     Test Status         Process                 Test Notes                        Name

                                  Record collections of refunds of advance payments or prepayments. If
                                  a receivable was not previously established, reference the advance                                               Not            Collections and                                         Collections of
           2006 RMD-07            obligation. Reduce cumulative advances under the obligation.         Mandatory                   Pending         Scheduled      Offsets                                                 advance payments
                                  Record advances (unearned revenue) received under reimbursable                                                                                                                          Reimbursable
                                  agreements. Update the advance balances on the reimbursable                                                      Not            Collections and                                         agreement advances
           2006 RMD-08            agreements.                                                          Mandatory                   Pending         Scheduled      Offsets                                                 received

                                                                                                                                                                                    Clarification: Changed requirement    Reimbursable
2006                              Record revenue collected under reimbursable agreements. Update the earned                                        Not            Collections and   short name and text from revenue      agreement revenue
Clarification     RMD-09          revenue balances on the reimbursable agreements.                                Mandatory        Pending         Scheduled      Offsets           received to revenue collected.        collected
                                  Generate a refund payable when collections of advances from others
                                  exceed the amount expended or billed on a reimbursable agreement
                                  after all work is performed. Update the advance balances on the                                                  Not            Collections and                                         Refund excess
           2006 RMD-10            reimbursable agreements.                                                        Mandatory        Pending         Scheduled      Offsets                                                 advance payments
                                  Generate a refund payable when collections of advances from others
                                  exceed the amount expended or billed on a reimbursable agreement
                                  after all work is performed. Update the advance balances on the                                                  Not            Collections and                                         Refund excess
           2006 RMD-11            reimbursable agreements.                                                        Mandatory        Pending         Scheduled      Offsets                                                 advance payments
                                  Maintain an accounting classification structure that includes the
                                  following elements:
                                  •     Treasury Account Symbol
                                  •     Budget fiscal year
                                  •     Internal fund code
                                  •     Organization
                                  •     Program
                                  •     Project
                                  •     Activity
                                  •     Cost center
                                  •     Object class
                                  •     Revenue source
                                  •     Budget function
                                  •     Budget sub-function code
                                  •     Accounting period.
                                  Maintain each classification element independently. For example,
                                  budget fiscal year must be maintained as a separate value from the
                                  period of availability component in the TAFS.                                                                    Not            Accounting                                              Accounting
           2006 SMA-01                                                                                            Mandatory        Pending         Scheduled      Classification                                          classification

                                  Define five additional accounting classifications elements, including                                            Not            Accounting                                              Additional accounting
           2006 SMA-02            element titles and valid values.                                                Mandatory        Pending         Scheduled      Classification                                          classifications
                                  Classify transactions by standard and agency-defined accounting                                                  Not            Accounting
           2006 SMA-03            classification elements.                                                        Mandatory        Pending         Scheduled      Classification                                          Classify transactions
                                  Derive full accounting classifications on transactions from abbreviated
                                  user input. Examples of methods include: entering shorthand codes,
                                  deriving elements from an entered field, or providing users with a list                                          Not            Accounting                                              Short classification
           2006 SMA-04            of values from which to choose.                                                 Mandatory        Pending         Scheduled      Classification                                          codes
                                  Add, change, or deactivate elements of the accounting classification
                                  structure and define valid ACE values without programming changes                                                Not            Accounting                                               Accounting
           2006 SMA-05            (e.g., through online table updates).                                           Mandatory        Pending         Scheduled      Classification                                           classification tables
                                  Capture an effective date for changes to accounting classification elements.                                                                      Clarification: Replaced "structure and Accounting
2006                              Activate or deactivate accounting classification changes based on effective                                      Not            Accounting        valid value" with the more generic     classification effective
Clarification     SMA-06          date.                                                                           Mandatory        Pending         Scheduled      Classification    "elements."                            date




Printed on 5/20/2010                                                                                         93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                      Page 65 of 79
Financial Systems Integration Office                                                                     Requirements Tested Matrix
                                                                                                       Core Requirements & Test Status

 Requirement                                                                                                                                                                                      Requirement Short
    Year               Req. No.                                 Description                                  Status              Test Cycle     Test Status         Process         Test Notes          Name
                                  Query document accounting data. Parameters include all standard
                                  and agency-defined accounting classification elements. Result is a list
                                  of selected document accounting lines. Display the document number,
                                  accounting classification elements and accounting line amounts. Drill
                                  down from accounting lines to GL transaction details, including
                                  transaction numbers, transaction and system dates and debits and                                             Not            Accounting                         Accounting activity
           2006 SMA-07            credits.                                                                Mandatory            Pending         Scheduled      Classification                     query

                                  Maintain a revenue source code structure to classify types of revenue
                                  and receipts as defined by the agency, such as rental income, sales                                          Not            Accounting                         Revenue source code
           2006 SMA-08            by product type and income by type of service performed.                     Mandatory       Pending         Scheduled      Classification                     structure
                                  Maintain a TAS structure that includes the following components
                                  defined by Treasury and OMB:
                                  •    Subclass
                                  •    Agency code
                                  •    Hyphen (when co-owner is not null)
                                  •    Transfer agency
                                  •    Fiscal year (period of availability)
                                  •    Main account number                                                                                     Not            Accounting                         Treasury Account
           2006 SMA-09            •    Sub-account symbol.                                                     Mandatory       Pending         Scheduled      Classification                     Symbol

                                  Accounting classification structure levels—Define additional (lower)
                                  levels in the fund, program, project, organization and object class                                                                                            Accounting
                                  structures (e.g. establish parent child relationships with the ability to                                    Not            Accounting                         classification structure
           2006 SMA-10            summarize, distribute funds, and report data at all defined levels).         Mandatory       Pending         Scheduled      Classification                     levels


                                  Maintain an accounting classification structure that can associate each
                                  element with multiple other elements and element values, including:
                                  •     TAS to multiple internal funds
                                  •     Internal fund to multiple organizations, programs, projects, and
                                  activities
                                  •     Organization to multiple programs, projects and activities
                                  •     Project code to multiple organizations, programs and activities                                        Not            Accounting
           2006 SMA-11            •     Program to multiple organizations, projects and activities.            Mandatory       Pending         Scheduled      Classification                     ACE associations
                                  Maintain an object class structure consistent with the standard object
                                  class codes defined in OMB Circular A-11. Accommodate additional
                                  (lower) levels in the object class structure, e.g., by establishing parent                                   Not            Accounting                         Object class code
           2006 SMA-12            child relationships.                                                         Mandatory       Pending         Scheduled      Classification                     structure
                                  Deliver the Core financial system software populated with the 3-digit
                                  Budget Object Classification codes specified in OMB Circular No. A-                                          Not            Accounting                         Pre-configured BOC
           2006 SMA-13            11.                                                                          Mandatory       Pending         Scheduled      Classification                     codes
                                  Capture a unique system-generated or agency-assigned document                                                Not            Document and
           2006 SMB-01            number for each document and document modification.                          Mandatory       Pending         Scheduled      Transaction Control                Document number
                                  Capture a unique system-generated number to identify each general
                                  ledger transaction. Associate one or more general ledger transactions                                        Not            Document and
           2006 SMB-02            with a document and document modifications.                                  Mandatory       Pending         Scheduled      Transaction Control                Transaction number
                                  Associate referenced documents in the processing chain, such as
                                  when an obligation document references one or more prior                                                     Not            Document and                       Referenced
           2006 SMB-03            commitment documents.                                                        Mandatory       Pending         Scheduled      Transaction Control                documents
                                  Capture a reimbursable agreement number and one other agency-
                                  assigned source document number in separate fields on all spending
                                  documents. The agency-assigned source document number may be a
                                  purchase requisition number, contract number and associated delivery
                                  /task order number, purchase order number, blanket purchase
                                  agreement number and associated call number, grant number, travel                                            Not            Document and                       Source document
           2006 SMB-04            order number, etc.                                                           Mandatory       Pending         Scheduled      Transaction Control                number




Printed on 5/20/2010                                                                                     93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                               Page 66 of 79
Financial Systems Integration Office                                                                         Requirements Tested Matrix
                                                                                                           Core Requirements & Test Status

 Requirement                                                                                                                                                                                                                       Requirement Short
    Year               Req. No.                                Description                                Status                     Test Cycle     Test Status        Process                       Test Notes                          Name
                                  Define document numbering as system-generated or agency-assigned                                                 Not            Document and                                                    Document number
           2006 SMB-05            by document type.                                                    Mandatory                   Pending         Scheduled      Transaction Control                                             source
                                  Validate that duplicate documents are not recorded, e.g., by editing
                                  document numbers or storing additional information that make the                                                 Not            Document and
           2006 SMB-06            document number unique (as in date stamp on a utility bill).         Mandatory                   Pending         Scheduled      Transaction Control                                             Duplicate documents
                                  Capture the source system and the source system document number                                                  Not            Document and
           2006 SMB-07            of each interfaced document.                                         Mandatory                   Pending         Scheduled      Transaction Control                                             Source system

                                  Capture goods delivery and service performance period start and end dates at
                                  the document and document line item level on documents where the period of
                                  performance is a validation for future processing, e.g.,
                                  •    Contracts
                                  •    Blanket purchase agreements                                                                                                                      Clarification: Specified that period of
                                  •    Reimbursable agreements                                                                                                                          performance dates are to be
2006                              •    Travel orders                                                                                               Not            Document and        captured at the document and                Period of
Clarification     SMB-08          •    Grants.                                                                     Mandatory       Pending         Scheduled      Transaction Control document line item level.                   performance
                                  Capture the following data elements when establishing reimbursable
                                  agreements:
                                  •    Reimbursable agreement number
                                  •    Reimbursable agreement amount                                                                                                                  Deleted the need to capture a
                                  •    Billing limit                                                                                                                                  source on a RA; can be derived Reimbursable
2006                              •    Billing terms                                                                                               Not            Document and        from information required on   agreement terms and
Clarification     SMB-09          •    Accounting classification information                                       Mandatory       Pending         Scheduled      Transaction Control customer record by RMA-01.     conditions

                                  Capture the following additional data elements when establishing reimbursable
                                  agreements between federal entities (intragovernmental):
                                  •    TAS for both Trading Partners
                                  •    BETC for both Trading Partners
                                  •    Method of payment (override of vendor default)
                                  •    DUNS (BPN) number for both Trading Partners
                                  •    DUNS+4 number for both Trading Partners
                                  •    Finance office point of contact information including name, location, and
                                  telephone number.
                                  •    Advance payment/liquidation provisions
                                  •    Performance (revenue and expenses) reporting method
                                  •    Performance reporting frequency                                                                                                                                                            Intragovernmental
                                  •    Right to modify indicator                                                                                                                                                                  Reimbursable
2006                              •    Right to cancel indicator                                                                                   Not            Document and                                                    agreement terms and
Addendum          SMB-09a         •    Right to terminate indicator.                                               Mandatory       Pending         Scheduled      Transaction Control                                             conditions
2006                              Validate TAS/BETCs captured on intragovernmental reimbursable                                                    Not            Document and
Addendum          SMB-09b         agreements.                                                                      Mandatory       Pending         Scheduled      Transaction Control                                             Validate TAS/BETC
                                  Define the level of fund control edits and tolerance checks as one of
                                  the following:
                                  •     Rejection
                                  •     Warning (override authority needed to post transaction)                                                    Not            Document and                                                    Funds control and
           2006 SMB-10            •     Information only (no override needed).                                     Mandatory       Pending         Scheduled      Transaction Control                                             tolerance levels
                                  Prevent the recording of erroneous transactions by rejecting                                                     Not            Document and
           2006 SMB-11            documents that fail transaction processing edits.                                Mandatory       Pending         Scheduled      Transaction Control                                             Reject documents

                                  Notify the user when online documents fail funds control edits,
                                  transaction processing edits, or tolerance checks. Provide the
                                  notification on the document entry screen, and include the nature of
                                  each error and the validation level (rejection, warning or information                                           Not            Document and
           2006 SMB-12            only). Retain errors with the document until they have been resolved.            Mandatory       Pending         Scheduled      Transaction Control                                             Failed edit notification
                                  Suspend documents that fail transaction processing edits, funds                                                  Not            Document and                                                    Suspended
           2006 SMB-13            control edits, or tolerance checks.                                              Mandatory       Pending         Scheduled      Transaction Control                                             documents
                                  Allow users to hold documents for completion or processing at a later                                            Not            Document and
           2006 SMB-14            date. Segregate held from suspended documents                                    Mandatory       Pending         Scheduled      Transaction Control                                             Hold documents




Printed on 5/20/2010                                                                                         93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                            Page 67 of 79
Financial Systems Integration Office                                                                         Requirements Tested Matrix
                                                                                                           Core Requirements & Test Status

 Requirement                                                                                                                                                                                                                  Requirement Short
    Year               Req. No.                                    Description                                         Status        Test Cycle     Test Status         Process                     Test Notes                      Name
                                  Re-validate suspended documents at least daily against changes in underlying
                                  data, such as CCR/FedReg vendor registration statuses, CCR/FedReg vendor                                                                            Clarification: Added that processing
                                  names, and available (allotted) funds. Process suspended documents when                                                                             of suspended documents can be          Re-validate
2006                              these data changes resolve validation errors, without additional action by the                                   Not            Document and        performed by periodic batch            suspended
Clarification     SMB-15          user.                                                                            Mandatory       Pending         Scheduled      Transaction Control processes.                             documents
                                  Allow users to select suspended and held documents for continued                                                 Not            Document and
           2006 SMB-16            processing.                                                                      Mandatory       Pending         Scheduled      Transaction Control                                        Failed edit corrections
                                                                                                                                                   Not            Document and                                               Cancel posted
           2006 SMB-17            Allow users to cancel (permanently close) posted documents.                      Mandatory       Pending         Scheduled      Transaction Control                                        documents
                                                                                                                                                   Not            Document and                                               Delete unposted
           2006 SMB-18            Allow users to delete held or suspended documents.                               Mandatory       Pending         Scheduled      Transaction Control                                        documents

                                  Define tolerances by percentage, "not-to-exceed" dollar amounts, or
                                  "not-to-exceed" quantities at the document line level, and use them to
                                  control overages by document line for the following relationships:
                                  •     Obligations to commitments
                                  •     Receipts to obligations                                                                                    Not            Document and
           2006 SMB-19            •     Invoices to obligations                                          Mandatory                 Pending         Scheduled      Transaction Control                                        Over tolerances
                                                                                                                                                   Not            Document and                                               Over tolerances by
           2006 SMB-20            Define tolerances for all obligations or by obligation type.                     Mandatory       Pending         Scheduled      Transaction Control                                        obligation type
                                  Capture the following accounting line item detail on all documents:
                                  •     Line item number
                                  •     Line item amount                                                                                           Not            Document and                                               Accounting line item
           2006 SMB-21            •     Line item accounting classification information.                           Mandatory       Pending         Scheduled      Transaction Control                                        detail
                                  Define the valid values for the following acquisition information:
                                  •    NAICS business codes
                                  •    SIC codes
                                  •    Product and service codes
                                  •    FOB shipping points                                                                                         Not            Document and                                               Define acquisition
           2006 SMB-22            •    Ship to locations (destination codes).                                      Mandatory       Pending         Scheduled      Transaction Control                                        information
                                  Validate that valid values for the following acquisition information are
                                  captured on spending documents:
                                  •    NAICS business codes
                                  •    Product service codes
2006                              •    FOB shipping points                                                                                         Not            Document and        Clarification: Deleed the SIC          Validate acquisition
Clarification     SMB-23          •    Ship to locations (destination codes).                                      Mandatory       Pending         Scheduled      Transaction Control code as required data.                 information
                                  Capture the following information at the document line item level on spending
                                  documents:
                                  •   Quantity
                                  •   Unit of measure
                                  •   Unit Price
                                  •   Extended Price
                                  •   Description                                                                                                                                       Clarification:
                                  •   Product service codes                                                                                                                             Changed obligation documents to      Document line item
2006                              •   FOB shipping points                                                                                          Not            Document and        spending documents in requirement      detail on spending
Clarification     SMB-24          •   Ship to locations (destination codes).                                       Mandatory       Pending         Scheduled      Transaction Control short name                             documents
                                  Validate that the sum of all document line items is equal to the                                                 Not            Document and                                               Line items to
           2006 SMB-25            document total.                                                                  Mandatory       Pending         Scheduled      Transaction Control                                        document total
                                                                                                                                                   Not            Document and                                               Default transaction
           2006 SMB-26            Derive the default transaction date from the current system date.       Mandatory                Pending         Scheduled      Transaction Control                                        date
                                  Derive the default accounting period from the transaction date.                                                  Not            Document and                                               Default accounting
           2006 SMB-27            Prevent user override.                                                  Mandatory                Pending         Scheduled      Transaction Control                                        period
                                  Capture an agency-specified transaction date (i.e., allow the agency to
                                  override the default transaction date with a date in any open                                                    Not            Document and                                               Override transaction
           2006 SMB-28            accounting period).                                                     Mandatory                Pending         Scheduled      Transaction Control                                        date

                                  Record subsequent activity against a document with the transaction
                                  date of that activity, e.g., the payment voucher, not the transaction                                            Not            Document and                                               Transaction date of
           2006 SMB-29            date of the original document, e.g., the referenced obligation.                  Mandatory       Pending         Scheduled      Transaction Control                                        subsequent activity


Printed on 5/20/2010                                                                                         93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                      Page 68 of 79
Financial Systems Integration Office                                                                  Requirements Tested Matrix
                                                                                                    Core Requirements & Test Status

 Requirement                                                                                                                                                                                   Requirement Short
    Year               Req. No.                                   Description                                   Status        Test Cycle     Test Status         Process         Test Notes          Name
                                  Validate transaction accounting classification elements. Prevent the
                                  recording of transactions with missing, invalid or inactive classification                                Not            Document and
           2006 SMB-30            elements or values.                                                        Mandatory      Pending         Scheduled      Transaction Control                Validate ACE
                                  Validate transaction-associated FACTS attributes. Prevent the
                                  recording of transactions with missing, invalid or inactive FACTS                                         Not            Document and                       Validate FACTS
           2006 SMB-31            attributes.                                                                Mandatory      Pending         Scheduled      Transaction Control                attributes
                                  Validate transactions that would post to U.S. SGL accounts (e.g.,
                                  borrowing authority, contract authority, or investments) to ensure that
                                  the associated fund code is designated as having the appropriate RT7                                      Not            Document and                       Record type 7
           2006 SMB-32            code.                                                                      Mandatory      Pending         Scheduled      Transaction Control                validation
                                  Capture the following dates on all transactions:
                                  •     Transaction date - The date a transaction is effective in the
                                  general ledger (i.e., the date a financial event is recognized).
                                  •     System date - The actual date a transaction is processed by the
                                  system. This date is assigned by the computer and may not be
                                  modified.                                                                                                 Not            Document and
           2006 SMB-33                                                                                       Mandatory      Pending         Scheduled      Transaction Control                Transaction dates
                                                                                                                                            Not
                                  Record transactions in both foreign currency and U.S. dollars in all                  Not                 Tested/Value   Document and                       Foreign currency
           2006 SMB-34            Core system modules.                                                      Value Added Applicable          Added          Transaction Control                transactions
                                  Define tolerances by percentage, dollar amount or quantity for final
                                  payments that are less than the referenced obligation document line                                       Not
                                  amounts, and use them to control erroneous de-obligations of the                      Not                 Tested/Value   Document and
           2006 SMB-35            funds.                                                                    Value Added Applicable          Added          Transaction Control                Under tolerances-
                                                                                                                                            Not
                                                                                                                        Not                 Tested/Value   Document and                       Over Tolerances by
           2006 SMB-36            Define under tolerances for all obligations or by obligation type.        Value Added Applicable          Added          Transaction Control                obligation type
                                  Associate documents in the processing chain, and bring forward
                                  accounting and non-financial information from one document to
                                  another, when the previously recorded document is referenced, (e.g.,                                                     Document                           Associate documents
                                  commitment to obligation, receivable to collection). This is to include                                   Not            Referencing and                    in the processing
           2006 SMC-01            accounting classification, vendor and customer information.               Mandatory       Pending         Scheduled      Modification                       chain
                                  Update the balance of open documents by accounting line item as
                                  they are referenced by subsequent documents in the processing
                                  chain. For example, reduce commitments when referenced by
                                  obligations, reduce obligations when referenced by expenditures,                                                         Document
                                  reclassify obligations when referenced by advances, reduce accounts                                       Not            Referencing and                    Update referenced
           2006 SMC-02            receivable when referenced by collections.                                Mandatory       Pending         Scheduled      Modification                       document balances
                                  Associate documents with related source documents (e.g.,
                                  reimbursable agreements, purchase orders, contracts and delivery                                                         Document                           Associate documents
                                  orders, BPAs and call numbers, and grants) so that queries show all                                       Not            Referencing and                    with source
           2006 SMC-03            related activity.                                                         Mandatory       Pending         Scheduled      Modification                       documents
                                  Capture document modifications at the accounting line item level that
                                  affect the general ledger, including changes to dollar amounts and                                                       Document                           Financial
                                  accounting classifications. Validate that funds are available prior to                                    Not            Referencing and                    modifications to
           2006 SMC-04            recording the modifications.                                              Mandatory       Pending         Scheduled      Modification                       documents
                                                                                                                                                           Document                           Non-financial
                                  Capture document modifications that do not affect the general ledger,                                     Not            Referencing and                    document
           2006 SMC-05            such as changes to vendor names, descriptions, etc.                       Mandatory       Pending         Scheduled      Mod.                               modifications
                                                                                                                                                           Document                           Associate
                                  Associate document modifications and cancellations with the original                                      Not            Referencing and                    modifications with
           2006 SMC-06            documents so that queries show all related activity.                      Mandatory       Pending         Scheduled      Mod.                               original documents
                                                                                                                                                           Document
                                  Re-open a closed document to allow further processing against it,                                         Not            Referencing and                    Re-open closed
           2006 SMC-07            without requiring a new or amended document number.                       Mandatory       Pending         Scheduled      Mod.                               document




Printed on 5/20/2010                                                                                  93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                Page 69 of 79
Financial Systems Integration Office                                                                Requirements Tested Matrix
                                                                                                  Core Requirements & Test Status

 Requirement                                                                                                                                                                             Requirement Short
    Year               Req. No.                                   Description                                 Status        Test Cycle     Test Status        Process      Test Notes          Name
                                  Reference multiple documents and document lines in the processing
                                  chain. For example, reference multiple commitments or commitment                                                       Document
                                  lines on an obligating document, or reference multiple receivable                                       Not            Referencing and                Reference multiple
           2006 SMC-08            documents or document lines on a collection. all documents.
                                  Capture the latest system processing status on                           Mandatory      Pending         Scheduled      Mod.                           prior documents
                                  •     Held: The user has decided to save (hold) the document and not
                                  allow the system to process it. (Note: This status is distinguished from
                                  invoices that are processed and warehoused, then ―held‖ from
                                  inclusion in the payment schedule.)
                                  •     Suspended: The document has failed one or more system
                                  validations (edits) and is prevented by the system from processing.
                                  The document is automatically stored for later processing. Suspended
                                  documents may be automatically processed by the system upon
                                  changes to underlying data, such as available funds.
                                  •     Pending Approval: The document has passed all system
                                  validations. The system will not process the document until all
                                  approvals required by the agency's workflow configuration have been
                                  applied. Not all documents require approvals.
                                  •     Approved: The document has passed all system validations
                                  (edits) and all required approvals have been applied. The document is
                                  available for processing.
                                  •     Processed: All related accounting events have been recorded
                                  and system tables have been updated.
                                  •     Open: The document has been processed but not liquidated or
                                  only partially liquidated. The document is available for further
                                  processing.
                                  •     Closed: The document has been processed and completely
                                  liquidated. The system will not allow further processing against the                                                   Document
                                  document unless it is reopened by the user.                                                             Not            Referencing and
           2006 SMC-09            •     Cancelled: The user has permanently closed a previously            Mandatory      Pending         Scheduled      Mod.                           Document status

                                  Query documents. Parameter includes any document number. Result
                                  is a list of all document numbers in the document's processing chain
                                  with document statuses and balances at the document level. Drill-                                                      Document
                                  down from each document number to its document details (e.g.,                                           Not            Referencing and                Related documents
           2006 SMC-10            vendor/customer name, description, amount).                          Mandatory          Pending         Scheduled      Mod.                           query
                                  Query transactions. Parameter is any document number. Result is a
                                  list of all general ledger transactions in the document's processing
                                  chain, including:
                                  •      Transaction numbers
                                  •      Amounts                                                                                                         Document
                                  •      GL debits and credits                                                                            Not            Referencing and                Standard document
           2006 SMC-11            •      Accounting classification elements.                           Mandatory          Pending         Scheduled      Mod.                           transactions query

                                  Query documents. Parameter(s) include any one or a combination of
                                  the following:
                                  •     Document type
                                  •     Document status (e.g., open, closed)
                                  •     Vendor number
                                  •     Vendor DUNS+4 number
                                  •     Customer number
                                  •     Accounting classification elements.
                                  Result is a list of selected document numbers with document statuses                                                   Document
                                  and balances at the document level. Drill-down from each document                                       Not            Referencing and                Standard document
           2006 SMC-12            number to its document lines and detailed GL transactions.           Mandatory          Pending         Scheduled      Mod.                           query




Printed on 5/20/2010                                                                                93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                         Page 70 of 79
Financial Systems Integration Office                                                                  Requirements Tested Matrix
                                                                                                    Core Requirements & Test Status

 Requirement                                                                                                                                                                                  Requirement Short
    Year               Req. No.                                 Description                                       Status        Test Cycle     Test Status        Process       Test Notes          Name
                                  Update accounting data at the accounting line level when accounting
                                  classification elements are restructured, i.e., by reversing GL and
                                  subsidiary ledger transactions and reposting them with the new                                              Not            Document
                                  values. Generate an audit trail from the original postings to the final                Not                  Tested/Value   Referencing and                 Update accounting
           2006 SMC-13            postings.                                                                  Value Added Applicable           Added          Mod.                            data
                                                                                                                                              Not            Document
                                  Reclassify accounting data from the beginning of the current fiscal                    Not                  Tested/Value   Referencing and                 Dating of accounting
           2006 SMC-14            year or fiscal month.                                                      Value Added Applicable           Added          Mod.                            data reclassification
                                                                                                                                              Not            Document
                                  Update related open documents when users modify classification                              Not             Tested/Value   Referencing and                 Update open
           2006 SMC-15            information on a document in a processing chain.                        Value added         Applicable      Added          Mod.                            documents
                                  Capture start and end dates and posting frequency (monthly, quarterly,
                                  or specified number of days) of recurring entries and reversals such as                                     Not            System-Generated                Parameters for
           2006 SMD-01            accruals and obligations.                                               Mandatory           Pending         Scheduled      Transactions                    recurring entries

                                  Generate recurring entries and reversals in future accounting periods
                                  (e.g., payroll and travel accruals), when the specified transaction dates                                   Not            System-Generated                Future-dated
           2006 SMD-02            are reached. This is to include entries that cross fiscal years.          Mandatory         Pending         Scheduled      Transactions                    recurring entries
                                  Future date transactions for processing in subsequent accounting
                                  periods, i.e., when the specified transaction dates are reached.
                                  Validate the transaction upon initial entry and re-validate the                                             Not            System-Generated                Future-dated
           2006 SMD-03            transaction at the point it is recorded.                                  Mandatory         Pending         Scheduled      Transactions                    transactions

                                  Generate batched reversal transactions by any one or a combination
                                  of the following parameters:
                                  •     Accounting period
                                  •     Transaction or document type
                                  •     Accounting classification elements
                                  •     System date
                                  •     Transaction date
                                  •     Source system ID.                                                                                     Not            System-Generated
           2006 SMD-04            For example, reverse payroll transactions posted on January 1, 2006.       Mandatory        Pending         Scheduled      Transactions                    Transaction reversals
                                  Validate that transaction reversals do not violate the integrity of the
                                  document chain. For example, do not reverse obligations that have                                           Not            System-Generated                Valid transaction
           2006 SMD-05            been liquidated by payments.                                               Mandatory        Pending         Scheduled      Transactions                    reversals
                                  Generate a report of posted and unposted reversal transactions.
                                  Parameters are:
                                  •     Accounting period
                                  •     Transaction or document type
                                  •     Accounting classification elements
                                  •     System date
                                  •     Transaction date
                                  •     Source system ID.
                                   Result is a list of transactions including:
                                  •     System date
                                  •     Transaction date
                                  •     Original document and accounting line numbers
                                  •     Status (posted or un-posted)
                                  •     Accounting classification elements
                                  •     GL transaction ID number
                                  •     GL debits and credits.                                                                                Not            System Generated                Transaction Reversal
           2006 SMD-06            Sorting options include document number and reversal status.               Mandatory        Pending         Scheduled      Transactions                    Report




Printed on 5/20/2010                                                                                    93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                            Page 71 of 79
Financial Systems Integration Office                                                                        Requirements Tested Matrix
                                                                                                          Core Requirements & Test Status

 Requirement                                                                                                                                                                                                                 Requirement Short
    Year               Req. No.                                    Description                                          Status        Test Cycle     Test Status         Process                    Test Notes                     Name
                                  Deliver the capability to send/receive financial data from Governmentwide
                                  mandated applications:
                                  •    Federal Agency Registration (FedReg)
                                  •    Central Contractor Registration (CCR)
                                  •    Electronic Certification System (ECS)
                                  •    Federal Agencies Centralized Trial Balance System I (FACTS I)
                                  •    Federal Agencies Centralized Trial Balance System II (FACTS II)
                                  •    Government Online Accounting Link System (GOALS II)                                                                                               Clarifications:
                                  •    Intra-governmental Payment and Collection System (IPAC)                                                                                           1-Added FedReg as an interfacing
2006                              •    Treasury Offset Program (TOP)                                                                                Not            System Generated      system.
Clarification     SMD-07          •    Secure Payment System (SPS).                                      Mandatory                  Pending         Scheduled      Transactions          2-Changed transactions to data.    System interfaces
                                  Deliver the capability to send/receive financial transactions from
                                  Government wide mandated applications:
                                  •     eTravel                                                                                                     Not
                                  •     CA$HLINK II                                                                                 Not             Tested/Value System Generated                                           Other system
           2006 SMD-08            •     GWA.                                                             Value Added                Applicable      Added        Transactions                                               interfaces
                                  Generate an audit trail of transactions recorded as a document moves
                                  from its source through all document statuses. The initial source may
                                  be documents that were entered online, system-generated, interfaced
                                  from other systems or modules, or converted during implementations                                                Not                                                                     Document processing
           2006 SME-01            or software upgrades.                                                  Mandatory                  Pending         Scheduled      Audit Trails                                             audit trail
                                  Capture all document change events (additions, modifications and                                                  Not                                                                     Document activity
           2006 SME-02            cancellations), including the date/time and User ID.                   Mandatory                  Pending         Scheduled      Audit Trails                                             logging
                                  Query document additions, modifications and cancellations.
                                  Parameters include:
                                  •     User ID
                                  •     Document number
                                  •     Document type
                                  •     Change type (add, modify, cancel)
                                  •     Transaction date range
                                  •     Accounting period.
                                  Results include all parameter values, document numbers, date and
                                  time stamps.                                                                                                      Not                                                                     Document activity
           2006 SME-03                                                                                   Mandatory                  Pending         Scheduled      Audit Trails                                             query
                                  Generate an audit trail of all accounting classification structure
                                  additions, changes and deactivations, including the effective dates of                                            Not                                                                     Accounting
           2006 SME-04            the changes.                                                           Mandatory                  Pending         Scheduled      Audit Trails                                             classification history

                                  Capture the following additional information on converted documents:
                                  •     Legacy system identifier                                                                                    Not
           2006 SME-05            •     Legacy system document number.                                             Mandatory        Pending         Scheduled      Audit Trails                                             Converted documents
                                  Delivered system must be modular, highly scalable and incorporate an                                              Not            General
           2006 TLA-01            open-systems architecture.                                                       Mandatory        Pending         Scheduled      Design/Architecture                                      General design
                                  Delivered system must be customizable to meet agency-defined
                                  business practices. Agency customizable features must be                                                          Not            General
           2006 TLA-02            table/parameter driven.                                                          Mandatory        Pending         Scheduled      Design/Architecture                                      Customization
                                  Delivered system must be upgradeable to accommodate changes in                                                    Not            General
           2006 TLA-03            laws, regulations, best practices or new technology.                             Mandatory        Pending         Scheduled      Design/Architecture                                      Upgradeability
                                  Delivered system must generate output reports, query results and data
                                  files using multiple formats as specified by functional requirements.
                                  Specified formats can include online display, printed report, Portable
                                  Document Format (PDF), MS Word, Excel, ASCII or delimited text file.
                                  In cases where an output format is not specified within a requirement,
                                  the requested information must be viewable to the agency online,                                                  Not            General
           2006 TLA-04            using the application user interface.                                            Mandatory        Pending         Scheduled      Design/Architecture                                      System outputs




Printed on 5/20/2010                                                                                          93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                                     Page 72 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                    Requirement Short
    Year               Req. No.                                  Description                                     Status        Test Cycle     Test Status         Process         Test Notes          Name

                                  Deliver fault-free performance in the processing of date and date-
                                  related data (including, calculating, comparing, and sequencing) by all
                                  hardware and software products included as part of the application                                         Not            General
           2006 TLA-05            both individually and in combination (i.e., be Y2K compliant).             Mandatory       Pending         Scheduled      Design/Architecture                Date handling
                                  Delivered system should be capable of processing online transactions,                                      Not
                                  batch jobs and transactions submitted via system interface                             Not                 Tested/Value   General                            Parallel transaction
           2006 TLA-06            simultaneously.                                                            Value Added Applicable          Added          Design/Architecture                processing
                                  Deliver a reports management capability to enable online retrieval,                                        Not
                                  viewing, re-printing, and permanent archiving of system-generated                      Not                 Tested/Value   General
           2006 TLA-07            reports.                                                                   Value Added Applicable          Added          Design/Architecture                Report spooling
                                  Delivered system must include a Structured Query Language (SQL)                                            Not
           2006 TLB-01            compliant relational database.                                             Mandatory       Pending         Scheduled      Infrastructure                     Relational database
                                                                                                                                             Not
                                  Operate in a mainframe environment (e.g., Multiple Virtual System                      Not                 Tested/Value
           2006 TLB-02            (MVS), Operating System (OS/) 390).                                        Value Added Applicable          Added          Infrastructure                     Mainframe operation
                                                                                                                                             Not
                                  Operate in a server computing environment running under UNIX,                          Not                 Tested/Value
           2006 TLB-03            LINUX, Windows Server 2000 or above.                                       Value Added Applicable          Added          Infrastructure                     UNIX/NT software
                                                                                                                                             Not
                                                                                                                         Not                 Tested/Value
           2006 TLB-04            Operate in an Apple Macintosh system environment.                          Value Added Applicable          Added          Infrastructure                     Apple/Mac
                                  Deliver an online graphical user interface (GUI). The GUI must provide
                                  consistent data entry, navigation and information presentation across                                      Not
           2006 TLC-01            all modules and sub-systems.                                               Mandatory       Pending         Scheduled      User Interfaces                    GUI interface
                                  Comply with Section 508 of the Rehabilitation Act, as detailed in 36                                       Not
           2006 TLC-02            CFR 1194, Subpart B.                                                       Mandatory       Pending         Scheduled      User Interfaces                    508 Compliance
                                  Deliver a context-sensitive, online help facility. This facility must be                                   Not
           2006 TLC-03            customizable by the agency.                                                Mandatory       Pending         Scheduled      User Interfaces                    Context-sensitive help
                                                                                                                                             Not                                               Error message
           2006 TLC-04            Deliver the capability to customize error message text.                      Mandatory     Pending         Scheduled      User Interfaces                    customization
                                  Incorporate user interface features designed to reduce the amount of
                                  direct keying required for transaction processing, such as:
                                  •     Default values based on system maintained transaction and user
                                  profiles
                                  •     Value look-up tables
                                  •     Highlighting or accentuating required fields
                                  •     Grayed data fields that are unavailable for user entry
                                  •     Auto tabs
                                  •     Automatic data recall
                                  •     Auto fill text
                                  •     Cut, copy and paste functionality
                                  •     Keyboard shortcuts (e.g., function keys to invoke help facility,
                                  clear screen,        etc.)
                                  •     Menu mode of screen navigation
                                  •     Undo/redo
                                  •     Disabling of non-supported function keys
                                  •     Ability to select records from a list by scrolling or typing only part
                                  of an entry.
                                  •     Ability to pass common data from field to field, screen to screen                                    Not
           2006 TLC-05            and transaction to transaction.                                              Mandatory     Pending         Scheduled    User Interfaces                      Data entry efficiencies
                                                                                                                                             Not
                                  Support integration with other common desktop applications (e.g.,                      Not                 Tested/Value
           2006 TLC-06            word processing, spreadsheets, data management).                           Value Added Applicable          Added        User Interfaces                      Desktop integration
                                  Deliver a capability to import and process standard transactions                                           Not                                               Application program
           2006 TLD-01            generated by other systems.                                                Mandatory       Pending         Scheduled    Interoperability                     interface




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                                Page 73 of 79
Financial Systems Integration Office                                                                  Requirements Tested Matrix
                                                                                                    Core Requirements & Test Status

 Requirement                                                                                                                                                                                Requirement Short
    Year               Req. No.                                  Description                                     Status       Test Cycle     Test Status         Process      Test Notes          Name
                                  Deliver data record layouts for all standard transactions that can be
                                  accepted by the application's API facility. Transactions must include
                                  sufficient data to enable complete validation and processing by the                                       Not
           2006 TLD-02            receiving system.                                                           Mandatory     Pending         Scheduled      Interoperability                API record layouts
                                  Process API transactions using the same business rules, program
                                  logic, and edits used by the system in processing transactions                                            Not                                            API transaction
           2006 TLD-03            submitted through the application client.                                   Mandatory     Pending         Scheduled      Interoperability                validation
                                  Deliver the capability to suspend erroneous API transactions.
                                  Suspense processing must include the ability to perform the following
                                  functions:
                                  •     Report suspended transactions
                                  •     Retrieve, view, correct and process, or cancel suspended
                                  transactions
                                  •     Automatically re-process transactions                                                               Not                                            API transaction
           2006 TLD-04            •     Report re-processed transactions.                                     Mandatory     Pending         Scheduled      Interoperability                suspension

                                  Deliver API processing controls to ensure real time transactions or
                                  batch transactions files are received from authorized sources,
                                  complete and not duplicates. In addition, the API must ensure that
                                  where batch files are used:
                                  •     The number of transactions in a received file matches a control
                                  record count
                                  •     The dollar total of transactions in a file matches a control amount
                                  •     The sender is notified of erroneous transactions
                                  •     The erroneous transactions are automatically returned to the                                        Not                                            API processing
           2006 TLD-05            sender.                                                                     Mandatory     Pending         Scheduled      Interoperability                controls
                                  Generate API transaction edit error records using a data layout defined                                   Not                                            API generated error
           2006 TLD-06            by the vendor (i.e., provide two-way interface support).                    Mandatory     Pending         Scheduled      Interoperability                notices
                                  Deliver the capability to connect to an agency operated e-mail system.
                                  This capability must include the ability to distribute application                                        Not
           2006 TLD-07            generated text messages with attached files.                                Mandatory     Pending         Scheduled      Interoperability                Agency e-mail
                                  EDI translationSupport direct EDI translation compliant with American                                     Not
                                  National Standards Institute (ANSI) X-12 standards to enable                            Not               Tested/Value
           2006 TLD-08            electronic data exchanges with designated trading partners.                 Value Added Applicable        Added          Interoperability                EDI transalation
                                                                                                                                            Not
                                  Deliver an integrated Extensible Markup Language (XML) parsing                          Not               Tested/Value
           2006 TLD-09            capability.                                                                 Value Added Applicable        Added          Interoperability                XML
                                                                                                                                            Not
                                  Deliver a capability to exchange data using the Extensible Business                     Not               Tested/Value
           2006 TLD-10            Reporting Language (XRBL).                                                  Value Added Applicable        Added          Interoperability                XRBL
                                  Deliver an integrated workflow management capability to automate
                                  internal routing of documents, transactions, forms or reports for online                                  Not            Workflow
           2006 TLE-01            approval processing.                                                        Mandatory     Pending         Scheduled      Messaging                       Integrated workflow
                                  Deliver the capability to customize workflow processes to automate
                                  agency-defined business rules, required approvers, pooled or proxy
                                  approving authorities and workload balancing. Agency customization
                                  must include the capability to apply start and end dates to approvers                                     Not            Workflow                        Workflow process
           2006 TLE-02            and their proxies.                                                          Mandatory     Pending         Scheduled      Messaging                       definition
                                  Deliver the capability to define multiple levels of document approvals
                                  based on agency-defined criteria, including dollar amounts, types of                                      Not            Workflow                        Document processing
           2006 TLE-03            items purchased, and document types.                                        Mandatory     Pending         Scheduled      Messaging                       approval

                                  Deliver the capability to define multiple approval levels to a single
                                  user. Prevent a user from applying more than one level of approval to
                                  the same document in order to conform to the principle of separation
                                  of duties. For example, a disbursing officer must not be allowed to
                                  certify payment of an invoice he/she entered, and a certifying officer                                    Not            Workflow
           2006 TLE-04            must not be allowed to schedule a payment he/she certified.                 Mandatory     Pending         Scheduled      Messaging                       Document approvals


Printed on 5/20/2010                                                                                  93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                           Page 74 of 79
Financial Systems Integration Office                                                                   Requirements Tested Matrix
                                                                                                     Core Requirements & Test Status

 Requirement                                                                                                                                                                                Requirement Short
    Year               Req. No.                                    Description                                   Status        Test Cycle     Test Status         Process     Test Notes          Name
                                  Deliver a workflow calendaring capability to generate date-based
                                  process exception reports and alerts. For example, notify an accounts
                                  payable office when invoices are held over 30 days with no matching                                        Not            Workflow                       Processing exception
           2006 TLE-05            receiving report.                                                           Mandatory      Pending         Scheduled      Messaging                      notices
                                  Deliver the capability to capture approval actions by transaction,                                         Not            Workflow                       Document approval
           2006 TLE-06            including the time/date and approving party.                                Mandatory      Pending         Scheduled      Messaging                      tracking
                                  Deliver the capability to route action requests/status messages
                                  internally to individuals, groups or external trading partners. Supported
                                  communications channels must include agency e-mail, Blackberry,                                            Not            Workflow
           2006 TLE-07            internal application messaging.                                             Mandatory      Pending         Scheduled      Messaging                      Document routing
                                  Deliver the capability to generate workflow event-based user alerts.
                                  For example, at the point an emergency travel voucher is approved,                                         Not            Workflow
           2006 TLE-08            electronically notify the affected traveler.                                Mandatory      Pending         Scheduled      Messaging                      User alerts

                                  Deliver the capability to generate user alerts based on agency-defined
                                  thresholds (i.e., trigger events). For example, electronically warn a                                      Not            Workflow
           2006 TLE-09            budget officer when available funds reach 50% of the allotment.        Mandatory           Pending         Scheduled      Messaging                      User notices
                                                                                                                                             Not
                                                                                                                          Not                Tested/Value   Workflow                       Workflow process
           2006 TLE-10            Deliver a business process modeling capability.                             Value Added Applicable         Added          Messaging                      modeling
                                                                                                                                             Not
                                  Generate auditable records of changes made to the workflow approval             Not                        Tested/Value   Workflow                       Workflow definition
           2006 TLE-11            routing design.                                                     Value Added Applicable                 Added          Messaging                      audits
                                                                                                                                             Not
                                  Delivered system should comply with the current Workflow                                Not                Tested/Value   Workflow
           2006 TLE-12            Management Coalition (WFMC) Workflow Standard - Interoperability.           Value Added Applicable         Added          Messaging                      Wf-XML
                                  Deliver the capability to index and store file reference materials                                         Not            Document                       Indexed Refeence
           2006 TLF-01            received or generated by the agency in electronic format.                   Mandatory      Pending         Scheduled      Management                     Materials
                                  Deliver the capability to electronically image, index and store file                                       Not
                                  reference materials delivered in a hard copy format (e.g., a signed                     Not                Tested/Value   Document
           2006 TLF-02            contract, bill of lading, vendor invoices).                                 Value Added Applicable         Added          Management                     Document imaging
                                                                                                                                             Not
                                  Deliver the capability to notify the user of the presence of associated                 Not                Tested/Value   Document                       Image availability
           2006 TLF-03            document images. Deliver on-screen display of imaged material.              Value Added Applicable         Added          Management                     notification

                                  Delivered system must support Transmission Control Protocol/Internet                                       Not
           2006 TLG-01            Protocol (TCP/IP) for application component connectivity.            Mandatory             Pending         Scheduled      Internet Access                TCP/IP
                                                                                                                                             Not
           2006 TLG-02            Deliver browser access to all system modules/functionality.                 Mandatory      Pending         Scheduled      Internet Access                Browser access
                                                                                                                                             Not
                                  Deliver the capability to receive vendor invoices and payments from                     Not                Tested/Value                                  Internet-originated
           2006 TLG-03            the public via the Internet.                                                Value Added Applicable         Added          Internet Access                transactions
                                                                                                                                             Not
                                  Support secure Internet access to the integrated ad hoc data query                      Not                Tested/Value                                  Internet access to ad
           2006 TLG-04            facility.                                                                   Value Added Applicable         Added          Internet Access                hoc queries
                                                                                                                                             Not
                                  Support operations via a Virtual Private Network (VPN) system                           Not                Tested/Value
           2006 TLG-05            capability for secure remote access.                                        Value Added Applicable         Added          Internet Access                VPN
                                                                                                                                             Not
                                  Deliver the capability to use Public Key Infrastructure technology to                   Not                Tested/Value
           2006 TLG-06            control system access.                                                      Value Added Applicable         Added          Internet Access                PKI
                                  Deliver integrated security functionality compliant with the National                                      Not
           2006 TLH-01            Institute of Standards and Technology (NIST) Security Standards.            Mandatory      Pending         Scheduled      Security                       NIST compliance




Printed on 5/20/2010                                                                                   93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                           Page 75 of 79
Financial Systems Integration Office                                                                 Requirements Tested Matrix
                                                                                                   Core Requirements & Test Status

 Requirement                                                                                                                                                                            Requirement Short
    Year               Req. No.                                    Description                                  Status       Test Cycle     Test Status         Process   Test Notes          Name
                                  Ensure that the management, operations and technical baseline
                                  security controls are implemented in accordance with Federal
                                  Information Processing Standards (FIPS) 199 Standards for Security
                                  Categorization of Federal Information and Information Systems and
                                  other current NIST guidance on selecting the appropriate security                                        Not
           2006 TLH-02            controls.                                                                  Mandatory     Pending         Scheduled      Security                     Security Controls
                                  Deliver the capability to control function access (e.g., system modules,
                                  transactions, approval authorities) and data access (i.e., create, read,
                                  update, delete) by assigned:
                                  •      User ID
                                  •      Functional role (e.g., payable technician) or
                                  •      Organization.
                                  Enable the agency to define access rules based on any combination of                                     Not
           2006 TLH-03            these attributes.                                                          Mandatory     Pending         Scheduled      Security                     Access control
                                  Ensure that the appropriate security controls are consistently enforced
                                  in all modules, including software used for ad-hoc data query/report                                     Not
           2006 TLH-04            generators.                                                                Mandatory     Pending         Scheduled      Security                     Security policy
                                  Sensitive data masking Deliver the capability to restrict access to
                                  sensitive data elements, such as social security numbers, banking                                        Not                                         Sensitive data
           2006 TLH-05            information by user ID, assigned role or organization.                     Mandatory     Pending         Scheduled      Security                     masking
                                  Deliver a process scheduling capability. Allow the agency to define,
                                  initiate, monitor and stop system processes (e.g., online availability,                                  Not
           2006 TLI-01            batch jobs, and system maintenance).                                       Mandatory     Pending         Scheduled      Operations                   Process scheduling

                                  Maintain internal database consistency at all times. In the event of a
                                  system failure the system must have the capability to:
                                  •    Back out incompletely processed transactions
                                  •    Restore the system to its last consistent state before the failure
                                  occurred
                                  •    Re-apply all incomplete transactions previously submitted by the
                                  user
                                  •    Validate internal database consistency to ensure duplicate
                                  postings are avoided                                                                                     Not                                         Internal database
           2006 TLI-02            •    Report any data or transactions that failed to process completely. Mandatory        Pending         Scheduled      Operations                   controls
                                  Generate online status messages to the operator. Include job or
                                  transaction type, name, when processing initiates, when it completes,                                    Not                                         Job processing
           2006 TLI-03            and any processing errors encountered.                                  Mandatory        Pending         Scheduled      Operations                   messages
                                  Deliver a restart capability for all application’s online and batch
                                  processing components. Batch jobs must be segmented to facilitate                                        Not
           2006 TLI-04            restart in the event of a system failure.                               Mandatory        Pending         Scheduled      Operations                   Job restart

                                  Deliver common error-handling routines across functional modules.
                                  Generate meaningful and traceable error messages that allow the                                          Not
           2006 TLI-05            user or system operator to identify and respond to reported problems. Mandatory          Pending         Scheduled      Operations                   Error handling
                                  Deliver a document archiving capability. Include the ability to define,
                                  establish, and maintain archival criteria, such as date, accounting
                                  period, closed items, and vendors/customers inactive for a specific
                                  time period. Archiving of closed or completed detail transactions must                                   Not
           2006 TLI-06            not affect related general ledger account balances.                     Mandatory        Pending         Scheduled      Operations                   Data archiving
                                  Support data archiving and record retention in accordance with rules
                                  published by the National Archives and Records Administration
                                  (NARA), GAO, and National Institute of Standards and Technology                                          Not                                         Data archive
           2006 TLI-07            (NIST).                                                                 Mandatory        Pending         Scheduled      Operations                   standards

                                  Deliver the capability to restore archived data based on agency-                                         Not                                         Archived data
           2006 TLI-08            defined criteria such as date, accounting period, or vendor/customer.      Mandatory     Pending         Scheduled      Operations                   retrieval




Printed on 5/20/2010                                                                                 93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                          Page 76 of 79
Financial Systems Integration Office                                                                    Requirements Tested Matrix
                                                                                                      Core Requirements & Test Status

 Requirement                                                                                                                                                                              Requirement Short
    Year               Req. No.                                  Description                                      Status        Test Cycle     Test Status        Process   Test Notes          Name

                                  Deliver an event logging capability for systems, transactions, tables,
                                  and system parameters. The logs must include the following:
                                  •    User ID
                                  •    System date
                                  •    Time
                                  •    Type of activity (i.e., add, modify, delete)
                                  •    Old value
                                  •    New value.
                                  (For example, provide a log of all attempts to log onto the system or                                       Not
           2006 TLI-09            track changes to the prompt pay interest rate value.)                       Mandatory       Pending         Scheduled      Operations                  Event logging
                                  Maintain and report application usage statistics. Productivity statistics
                                  should include concurrent users, job submissions, transactions                                              Not
           2006 TLI-10            throughput, and system availability.                                        Mandatory       Pending         Scheduled      Operations                  Productivity reporting

                                  Deliver a capability to override the system date value used to
                                  automatically default document effective date and related transaction                                       Not                                        System date for
           2006 TLI-11            posting date/period. This capability is intended for system testing.        Mandatory       Pending         Scheduled      Operations                  testing
                                  Deliver the capability to process queued jobs (i.e. reports, transaction                                    Not
                                  files from interfacing systems, bulk record updates) with no online                     Not                 Tested/Value
           2006 TLI-12            performance degradation.                                                    Value Added Applicable          Added          Operations                  Queued jobs
                                  Deliver the capability to customize system logging features. Allow the                                      Not
                                  agency to specify which parameters (or tables) to log. Allow the                        Not                 Tested/Value                               User selected access
           2006 TLI-13            agency to turn logging feature on or off as needed).                        Value Added Applicable          Added          Operations                  logging
                                  Deliver an integrated ad hoc query capability to support agency access                                      Not
           2006 TLJ-01            to and analysis of system maintained financial data.                        Mandatory       Pending         Scheduled      Ad Hoc Query                Ad hoc query
                                  Deliver the capability to define parameter-based query scripts that can
                                  be queued for execution, stored for re-use and shared with other                                            Not                                        Ad hoc query
           2006 TLJ-02            authorized agency users.                                                    Mandatory       Pending         Scheduled      Ad Hoc Query                origination
                                  Process submitted queries and queue output on-line for access by                                            Not                                        Ad hoc query
           2006 TLJ-03            authorized users.                                                           Mandatory       Pending         Scheduled      Ad Hoc Query                execution
                                  Ad hoc query results Distribute query results or notifications of online                                    Not
           2006 TLJ-04            query result availability to pre-defined individuals or groups.             Mandatory       Pending         Scheduled      Ad Hoc Query                Ad hoc query results
                                  Deliver run-time controls to prevent "run-away" queries and to restrict                                     Not
           2006 TLJ-05            very large data download requests.                                          Mandatory       Pending         Scheduled      Ad Hoc Query                Run-time controls
                                  Deliver the capability to display graphical output on the desktop with                                      Not
           2006 TLJ-06            dynamic report reformatting.                                                Mandatory       Pending         Scheduled      Ad Hoc Query                Graphical output
                                  Deliver an on-line "drill-down" capability from summary amounts in                                          Not
           2006 TLJ-07            queries to supporting detail records.                                       Mandatory       Pending         Scheduled      Ad Hoc Query                Drill-down
                                  Deliver the capability to download selected query data. Reformat
                                  downloaded query information for direct access by common desktop                                            Not
           2006 TLJ-08            applications (e.g., spreadsheet, ASCII text, "," delimited).                Mandatory       Pending         Scheduled      Ad Hoc Query                Data downloading
                                  Deliver the capability to preview a query, form, report, or other result                                    Not
           2006 TLJ-09            before printing.                                                            Mandatory       Pending         Scheduled      Ad Hoc Query                Query/Report preview
                                                                                                                                              Not
           2006 TLJ-10            Deliver capability to access current year and historical financial data.    Mandatory       Pending         Scheduled      Ad Hoc Query                Available data

                                  Deliver the following ad hoc query interface features:
                                  •    Graphical display of data sources
                                  •    The ability to "point and click" on selectable table, data, and link
                                  objects for inclusion in a custom query, and                                                                Not                                        Ad hoc query
           2006 TLJ-11            •    An active data dictionary to provide users with object definitions.    Mandatory       Pending         Scheduled    Ad Hoc Query                  interface
                                                                                                                                              Not
                                                                                                                          Not                 Tested/Value
           2006 TLJ-12            Deliver the capability to optimize queries.                                 Value Added Applicable          Added        Ad Hoc Query                  Query optimization




Printed on 5/20/2010                                                                                    93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                         Page 77 of 79
Financial Systems Integration Office                                                                  Requirements Tested Matrix
                                                                                                    Core Requirements & Test Status

 Requirement                                                                                                                                                                            Requirement Short
    Year               Req. No.                                  Description                                   Status        Test Cycle     Test Status        Process    Test Notes          Name
                                  Deliver a "dashboard" reporting capability that can be used to
                                  continuously display agency-defined performance metrics on a                                             Not
                                  managers desktop (e.g., a graphical view of the agency's budget                      Not                 Tested/Value
           2006 TLJ-13            status).                                                                 Value Added Applicable          Added        Ad Hoc Query                   Dashboard output
                                  Deliver documentation that identifies all software and hardware
                                  products needed by an agency to install, operate, access, and
                                  maintain the application. Delivered hardware and software
                                  documentation must specifically identify those products that are
                                  intended to be purchased or licensed as part of the product licensing
                                  agreement, and those products needed to meet any technical and
                                  functional requirement that must be acquired separately by the                                           Not                                         Hardware and
           2006 TLK-01            agency.                                                                  Mandatory       Pending         Scheduled      Documentation                software

                                  Deliver application design documentation. This documentation must
                                  include the following:
                                  •      Description of the application's design/architecture and integrated
                                         technologies
                                  •      Database specifications
                                  •      Data dictionary
                                  •      Entity relationship diagrams
                                  •      Internal file record layouts
                                  •      Cross references between internal files, database tables and
                                  data-entry screens
                                  •      Program module specifications including firmware and program
                                  source code
                                  •      System flowcharts.
                                  Application documentation must identify known problems (software                                         Not
           2006 TLK-02            bugs) and recommended work around.                                         Mandatory     Pending         Scheduled      Documentation                Application design
                                  Software installation and maintenanceDeliver product installation and
                                  maintenance documentation. Installation documentation must
                                  describe the following items:
                                  •      Product release content
                                  •      Third party software configuration requirements
                                  •      Database installation steps
                                  •      The directory structure for locating application data, programs,
                                  files, tables including drive mappings
                                      •     Hardware driver installation and configuration
                                  •      Application security set-up and maintenance
                                  •      Software configuration instructions
                                  •      Operating parameter definitions and any other required set-up
                                  data
                                  •      Software build instructions
                                  •      Vendor supplied configuration tools
                                  •      Interface processes to be installed
                                  •      Startup scripts needed to initiate the software                                                   Not
           2006 TLK-03            •      Test steps needed to verify correct installation.                   Mandatory     Pending         Scheduled      Documentation




Printed on 5/20/2010                                                                                 93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                       Page 78 of 79
Financial Systems Integration Office                                                                 Requirements Tested Matrix
                                                                                                   Core Requirements & Test Status

 Requirement                                                                                                                                                                            Requirement Short
    Year               Req. No.                                   Description                              Status            Test Cycle     Test Status        Process    Test Notes          Name
                                  Deliver system operations and user manuals. Documentation must
                                  explain the following system operations:
                                  •     System start-up
                                  •     Shutdown
                                  •     Monitoring
                                  •     Recovery/re-start
                                  •     Internal processing controls
                                  •     Archiving and application security.
                                  User documentation must explain in detail how to execute available
                                  functionality in each application component and must cover
                                  instructions for the following:
                                  •     Access procedures
                                  •     User screen layout
                                  •     Standard report layout and content
                                  •     Transaction entry
                                  •     Workflow
                                  •     Batch job initiation
                                  •     GL and transaction maintenance
                                  •     Yearend processing
                                  •     Error codes with descriptions
                                  •     Recovery steps                                                                                     Not                                         User and operating
           2006 TLK-04            •     Trouble shooting procedures.                                    Mandatory          Pending         Scheduled      Documentation                documentation
                                  Deliver documentation updates concurrent with the distribution of new
                                  software releases. Release notes must clearly identify all changes                                                                                   Updated release
                                  made to the system's functionality, operation or required computing                                      Not                                         specific
           2006 TLK-05            hardware and software.                                                Mandatory          Pending         Scheduled      Documentation                documentation
                                  Process the agency’s specified accounting workload without adversely                                     Not            System
           2006 TLL-01            impacting projected online response time.                             Mandatory          Pending         Scheduled      Performance
                                  Process scheduled work (e.g., batch jobs) within an agency specified
                                  batch-processing window. Scheduled work can include:
                                  •     Daily systems assurance reports
                                  •     Daily backups
                                  •     Daily interface processing
                                  •     Core GL posting
                                  •     Table updates
                                  •     Standard reporting.                                                                                Not            System                       Batch processing
           2006 TLL-02                                                                                  Mandatory          Pending         Scheduled      Performance                  workload
                                  Maintain the agency’s specified current and historical financial data
                                  (e.g. general ledger records, documents, transactions, lines, and
                                  vendor records) storage needs with no degradation to online or batch                                     Not            System
           2006 TLL-03            processing performance.                                               Mandatory          Pending         Scheduled      Performance                  Data volume
                                  Support concurrent access to functional modules for the agency's                                         Not            System                       Concurrent user
           2006 TLL-04            specified user community.                                             Mandatory          Pending         Scheduled      Performance                  access

                                  Deliver computing performance metrics for platforms and systems
                                  environments that the application is certified to run on. Performance
                                  metrics provided by the vendor should describe:
                                  •    Transaction processing throughput capacity,
                                  •    Expected workstation client response time by transaction type,                                      Not
                                  •    Data storage capacity, and                                                     Not                  Tested/Value System
           2006 TLL-05            •    Limitations on concurrent user connectivity.                       Value Added Applicable           Added        Performance                    Performance metrics




Printed on 5/20/2010                                                                                 93acfe11-a1a0-4bda-b2f7-5eb59b621a91.xls                                                       Page 79 of 79

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:20
posted:5/20/2010
language:English
pages:79