Defense Financial Management Improvement Guidance
(Includes FFMIA Rules)

Rule Name Rule Description Primary Reference Rule Type Rule Indicator CBM(s) BPM Process(es)
Accounts _Payable _Maintain _and _Update _Payee _Information _001
The system must have the functionality to submit payments for the following invoices and vouchers only after ACO approval:
1. Completion vouchers under cost-plus fixed-fee or other cost-reimbursement contracts. 2. Vouchers and invoices for termination costs under supplemental agreements unless the termination modification specifies the costs to be paid. 3. Completion vouchers under T&M and LH contracts. 4. Invoices for progress payments under fixed-price type contracts. 5. Vouchers and invoices where the contract requires approval by the ACO before payment. 6. Invoices for the release of "withhold" amounts previously instituted by the ACO. 7. Any payment request where a disbursing officer requires an ACO signature.
DFMIR Mandatory FM
  • Manage Disbursements

  • Manage Liabilities

  • Monitor Payment

  • Accounts _Payable _Reporting _013
    To support the closeout process, the agency's single integrated financial management system must provide a receiving report containing a final indicator, with acceptance acknowledged by a designated agency official including:
    • contract number and all associated delivery order numbers or task order numbers (including modification number, if any); PO number (including modification number, if any); BPA number and all associated BPA call numbers (including modification number, if any);
    • date of receipt;
    • date of acceptance; and
    • final acceptance indicator.
    FFMIA Mandatory MSSM
  • Monitor Contract or Order Performance

  • Accounts _Payable _Reporting _014
    To support the closeout process, the agency's single integrated financial management system must access or provide evidence that the contractor's final invoice has been submitted. FFMIA Mandatory MSSM
  • Monitor Contract or Order Performance

  • Monitor Payment

  • Accounts _Payable _Reporting _015
    To support the closeout process, the agency's single integrated financial management system must provide evidence that a final invoice payment has taken place with the following:
    • final payment indicator (including any resolution of contract withholds);
    • invoice number; and
    • total amount paid.
    FFMIA Mandatory MSSM
  • Monitor Contract or Order Performance

  • Monitor Payment

  • Accounts _Payable _Reporting _016
    To support the closeout process, the agency's single integrated financial management system must provide where excess funds have been identified, provide the document number under which the funds were obligated, the amount of the de-obligation, and the date of the de-obligation. FFMIA Mandatory FM
    MSSM
  • Manage Execution Fund Account

  • Monitor Contract or Order Performance

  • Accounts _Payable _Reporting _017
    To support the closeout process, the agency's single integrated financial management system should provide an accounting document number. FFMIA Value Added MSSM
  • Execute Contract Closeout

  • Accounts _Payable _Reporting _018
    To support the closeout process, the agency's single integrated financial management system should enable electronic contracting, obligation of funds, approvals and signatures, and notification alerts for pending actions. FFMIA Value Added FM
    MSSM
  • Manage Execution Fund Account

  • Manage Sales and Procurement

  • Accounts _Payable _Reporting _019
    Agency systems must maintain, store, and permit ready retrieval of financial information. The time frames for various parts of this requirement differ depending on the subject matter. The single integrated financial management system must be sufficiently flexible to retain and purge information consistent with varying record keeping requirements. FFMIA Mandatory FM
  • Post to General Ledger

  • Accounts _Payable _Reporting _020
    Based on the report requirements established in the participation agreement with the network bank, reports of the merchant's plastic card activity will be made available electronically by the network bank to the participating DoD activity (merchant). The summary will detail dates of deposits, dollar amounts of deposits, number of transactions processed, adjustment charges, and chargebacks. This report shall be used to reconcile any differences which may occur between the report and entries into the accounting system. The report shall also be reconciled with the Cash Collection Voucher (Department of Defense (DD) Form 1131), submitted to the DO or DDO, and Standard Form (SF) 215 information posted in the Transaction Reporting System (TRS) and/or CA$HLINK II. DFMIR Mandatory FM
    HRM
    MSSM
    RPILM
  • Manage Execution with Treasury

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Perform Financial Reporting

  • Post to General Ledger

  • Acquired _Loan _Account _Status _Maintenance _001
    A guaranteed loan system must identify accounts that should be written-off. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Account _Status _Maintenance _002
    A guaranteed loan system must identify accounts for which collection is to be pursued. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Account _Status _Maintenance _003
    A guaranteed loan system must calculate outstanding balances for each loan account invoiced, including principal, interest, late charges, and other amounts due. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Account _Status _Maintenance _004
    A guaranteed loan system must identify loan accounts to be invoiced based on agency program invoicing criteria and loan account information. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Account _Status _Maintenance _005
    A guaranteed loan system must generate and transmit an invoice to each borrower. At a minimum, the invoice must include borrower ID, amount due, date due, the date after which the payment will be considered late, and the current balance. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Account _Status _Maintenance _006
    A guaranteed loan system must provide for automatic acceleration of delinquent installment payment notes based on an acceleration clause indicator. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Account _Status _Maintenance _007
    A guaranteed loan system must track and age receivables by type. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Account _Status _Maintenance _008
    A guaranteed loan system must provide an automated interface with the Core Financial System to record accrual of interest, administrative charges, and penalties for delinquent loan accounts. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Account _Status _Maintenance _009
    A guaranteed loan system must apply collections according to agency program receipt application rules to the appropriate liquidating or financing account. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Account _Status _Maintenance _010
    A guaranteed loan system must include a partial, full, or late payment indicator. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Account _Status _Maintenance _011
    A guaranteed loan system must identify payments that cannot be applied and document the reasons why the payments cannot be applied. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Account _Status _Maintenance _012
    A guaranteed loan system must provide an automated interface with the Core Financial System to record the collection. If the guaranteed loan system processes collections, it must meet the requirements in the Core Financial System Requirements related to collections and send summary data to the Core Financial System. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Claim _Processing _001
    A guaranteed loan system must record key claim data, maintain data on original and if applicable, final claims. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Claim _Processing _002
    A guaranteed loan system must compare the claim application information to the agency's program claim application evaluation criteria. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Claim _Processing _003
    A guaranteed loan system must suspend processing for claims that are incomplete; and the claims should remain in suspension until they are corrected. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Claim _Processing _004
    A guaranteed loan system must identify claims not meeting agency program requirements and notify the lender of the rejection. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Claim _Processing _005
    A guaranteed loan system must document and track information on accepted and rejected claims and the reason for the rejections. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Claim _Processing _006
    A guaranteed loan system must reflect the status of the claim. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Claim _Processing _007
    A guaranteed loan system must calculate the claim payment to be made, making adjustments for any disallowed amounts or authorized debt collection activities. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Claim _Processing _008
    A guaranteed loan system must provide an automated interface with the Core Financial System to initiate a disbursement of the claim payment to the lender. If the guaranteed loan system processes payments, it must meet the requirements in the Core Financial System Requirements related to payments data to the Core Financial System. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Claim _Processing _009
    A guaranteed loan system must record acquired loan information and establish appropriate accounting entries such as receivables. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Claim _Processing _010
    A guaranteed loan system must have the capability to develop edits to address claims issues. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Claim _Processing _011
    A guaranteed loan system must have the capability to record or track claims errors. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquired _Loan _Claim _Processing _012
    A guaranteed loan system must have the capability to support underlying details. FFMIA Mandatory FM
  • Record Loans and Grants

  • Acquisition _001
    Purchase Orders shall specify the quantity of supplies or scope of services ordered. FFMIA Mandatory FM
    MSSM
    RPILM
  • Manage Disbursements

  • Manage Liabilities

  • Manage Supply Chain Entitlement

  • Acquisition _002
    Purchase Orders shall contain a determinable date by which delivery of the supplies or performance of the services is required. FFMIA Mandatory FM
    MSSM
    RPILM
  • Manage Disbursements

  • Manage Liabilities

  • Manage Supply Chain Entitlement

  • Acquisition _003
    Purchase Orders shall specify free on board (f.o.b.) destination for supplies to be delivered within the United States, except Alaska or Hawaii, unless there are valid reasons to the contrary. FFMIA Mandatory FM
    MSSM
    RPILM
  • Manage Disbursements

  • Manage Liabilities

  • Manage Supply Chain Entitlement

  • Acquisition _004
    Purchase Orders shall include any trade and prompt payment discounts that are offered. FFMIA Mandatory FM
    MSSM
    RPILM
  • Manage Disbursements

  • Manage Liabilities

  • Manage Supply Chain Entitlement

  • Audit _Trails _System _Controls _001
    DFAS shall maintain or create controls to ensure that transactions that occur during a reporting period are uniquely identified with the reporting period and processed in order to meet the reporting schedule due dates. DFMIR Mandatory FM
  • Define Cost Performance Model

  • Manage Financial Management Policy

  • Post to General Ledger

  • Audit _Trails _System _Controls _002
    Documentation must be available to provide an audit trail and support accomplished reconciliations and resulting adjustments. Such documentation should be available for auditors and management for proper oversight. DFMIR Mandatory FM
    MSSM
  • Archive Asset Record

  • Manage Financial Management Policy

  • Post to General Ledger

  • Audit _Trails _System _Controls _003
    DoD Component sytems must ensure that all financial transactions are submitted to DFAS. These controls should include tools to identify and track the numbers, types, and dollar amounts of transactions submitted to DFAS. DFMIR Mandatory FM
  • Manage Disbursements

  • Populate Cost Performance Model

  • Post to General Ledger

  • Audit _Trails _System _Controls _004
    For all programs that acquire IT, including an NSS, at any ACAT level, the MDA shall not initiate a program or an increment of a program, or approve entry into any phase of the acquisition process; and the DoD Component shall not award a contract until: (1) The sponsoring DoD Component or PM has satisfied the requirements of Title 40/CCA; (2) The DoD Component CIO, or designee, confirms Title 40/CCA compliance; and (3) For MDAPs and MAIS programs only, the DoD CIO also confirms Title 40/CCA compliance. DFMIR Mandatory WSLM
  • Define Program

  • Benefit _Claim _Acceptance _And _Tracking _001
    The benefit system must capture all applicable mandatory data elements (i.e., universal and appropriate categorical), which include:
    - Name and address of claim holder (person on whose record benefit is earned/due)
    - SSN of claim holder
    - Birth date of the claim holder
    • Date of initial claim.
    • Claimant information, if other than claim holder, including:
    • name, address and SSN, and birth date; and
    • the claimant's relationship to claim holder, when different from the claim holder (e.g., self, spouse, child, dependent parent).
    • Name and relationship of a representative payee, including estate executors or legal guardians, when applicable.
    • The specific benefit(s) for which the claim is made.
    • Claimant address.
    • Bank information for direct deposit, if applicable including American Bank Association routing number, claimant bank account number, and account type.
    • Type of evidence/proofs required and submitted when applicable.
    • Status of the claim (e.g. approved, pending, denied).
    • For benefit systems relating to taxable programs, information needed to determine withholding amount such as: withholding status (e.g., married, single, or exempt); tax number of withholding allowances, back-up withholding, and additional voluntary amount of tax withholding.
    FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Acceptance _And _Tracking _002
    The benefit system must maintain all of the data elements specified in the "Application Information Stores" (reference listing in 16.01.01) so Information is readily accessible through standard online queries or reports, until the claim is approved and a master record is established, or until a final determination is made denying the claim. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Acceptance _And _Tracking _003
    The benefit system must provide for electronic acceptance of benefit applications by fiscal year 2003. If an agency anticipates receipt by electronic means of 50,000 or more submittals of a particular form, the system must allow multiple methods of electronic signatures for the submittal of such form, whenever feasible and appropriate. The system must provide for the electronic acknowledgement of electronic forms that are successfully submitted. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Acceptance _And _Tracking _004
    The benefit system must capture various correspondence, including due process requests submitted by various electronic mediums and automatically associate the correspondence with the specific claim for the required action. For manually submitted correspondence, provide for associating the correspondence with the specific application or existing claimant master record for the required action. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefit _Claim _Acceptance _And _Tracking _005
    The benefit system must incorporate input and completeness controls to ensure only complete applications are accepted by the system when electronic methods (e.g., web based, telecommunications) are used to facilitate claim form acceptance. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Acceptance _And _Tracking _006
    The benefit system must provide the capability to flag a claimant's paper based application as incomplete and to suspend further processing of the application until it is properly completed as specified by program requirements. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Acceptance _And _Tracking _007
    The benefit system must store incomplete applications in accordance with agency policies, and provide for automatic purging of incomplete applications after a time period specified by the agency. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Acceptance _And _Tracking _008
    For each claim, the benefit system must associate a unique identifier (e.g., initials or user code) of the employee assigned to review the claim. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefit _Claim _Acceptance _And _Tracking _009
    The benefit system must utilize an alternative application procedure that accommodates persons with disabilities (e.g., blind, missing limbs). FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefit _Claim _Acceptance _And _Tracking _010
    The benefit system must provide the capability to track the status of due process or other appeal proceedings when applicable, after an initial claim has been denied. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Acceptance _And _Tracking _011
    The benefit system should maintain a system record of pending claims and the status of other information including:
    - where in the process an ongoing claim is located,
    - who is holding claim,
    - what actions are needed to complete the claim,
    - whether additional information is needed; and
    - accommodation of explanation codes to indicate the reason why the claim is pending.
    FFMIA Value Added HRM
  • Manage Benefits

  • Benefit _Claim _Acceptance _And _Tracking _012
    The benefit system should allow the user to update the status of the following items:
    - where in the process an ongoing claim is located,
    - who is holding claim,
    - what actions are needed to complete the claim,
    - whether additional information is needed; and
    - accommodation of explanation codes to indicate the reason why the claim is pending.
    FFMIA Value Added HRM
  • Manage Benefits

  • Benefit _Claim _Processing _001
    The benefit system must utilize claimant data that has been submitted electronically in an automated fashion without manual intervention (i.e., avoid re-entering data from one component to another). FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefit _Claim _Processing _002
    The benefit system must have the ability to date and time stamp due process requests and other time sensitive correspondence (incoming and outgoing) that has been received/sent through electronic mediums. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _003
    The benefit system must accommodate automated case workload distribution by providing for various claim routing options as determined and maintained by the system administrator. For example, provide for the ability to route claims for manual validation. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _004
    The benefit system must indicate if the benefit payment calculation or verification thereof occurred manually. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _005
    The benefit system must provide the user the ability to update a claimant's master record with the results of a manual claim validation or manual verification of the benefit payment amount, or create a new master record if none exists. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Processing _006
    The benefit system must have the ability to capture what information is needed from the claimant in order to complete an incomplete claim. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefit _Claim _Processing _007
    The benefit system should provide for electronic approvals of claims at all levels of the approval process, whenever feasible. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _008
    The benefit system must incorporate a notification mechanism that informs users (claim evaluators and supervisors) when an application(s) has not completed processing within a time frame that can be specified by the agency. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _009
    The benefit system should allow the user to update the status of pending claims and other information. FFMIA Value Added HRM
  • Manage Benefits

  • Benefit _Claim _Processing _010
    The benefit system must facilitate user queries on individual claims. Specifically, for all claims that have been received and recorded in the system, the system must be able to retrieve data maintained in the application information information stores by querying the claim holders’ (or claimant if different) information. For example, data must be retrievable by query on full name, and Social Security Number (SSN) or taxpayer ID number. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefit _Claim _Processing _011
    The benefit system must support the benefit recovery receivable servicing process by allowing for the waiver of charges with appropriate authority. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _012
    The benefit system must support the benefit recovery receivable servicing process by matching receipts to the appropriate receivables and updating system balances. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Collections

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _013
    The benefit system must support the benefit recovery receivable servicing process by providing the ability to apply receipts to more than one receivable. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Collections

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _014
    The benefit system must support the benefit recovery receivable servicing process by updating receivable balances document by document, classifying and posting against principal, interest, administrative fees, etc., required by OMB Circular A-129, "Managing Federal Credit Programs. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _015
    The benefit system must support the benefit recovery receivable servicing process by identifying receivables that have been reduced by some means other than cash collections, such as waivers or write-offs. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _016
    The benefit system must support the benefit collection process by recording complete and partial receipts according to the Debt Collection Act (DCA) of 1982 and the Debt Collection Improvement Act (DCIA) of 1996 and other applicable regulations. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Collections

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _017
    The benefit system must support the benefit collection process by recording deposits and related debit vouchers for reconciliation to deposit confirmation information provided by Treasury or the banking system. Specifically, providing the capability for a user to record the deposit ticket or debit voucher document amount, number, and date. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Collections

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _018
    The benefit system must support the benefit collection process by providing the capability to associate the collection of funds to the claimant's master record if a master record exists if the user is not able locate an existing receivable in the master record of the person making a payment, and the document being recorded is a deposit ticket item. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Collections

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Sustain Human Resources

  • Benefit _Claim _Processing _019
    The benefit system must support the benefit collection process by providing features to record method of recovery (i.e., payment; internal offset; TOP, compromise settlement; civil suit; etc.). FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Collections

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _020
    The benefit system must support the benefit collection process by providing the capability to flag a claimant's receivable record to reflect "due process" status, in order to suspend collection activities associated with the receivable. Additionally, the system must automatically allow collection activities to resume when due process has expired or the flag has been reversed. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Collections

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _021
    For denied claims, the benefit system must accommodate explanation codes to indicate the reason why the claim has been denied. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _022
    The benefit system should support the benefit collection process by providing for the processing of cash or credit card receipts against outstanding receivables. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Collections

  • Manage Receivables

  • Benefit _Claim _Processing _023
    The benefit system must support the benefit offset process by allowing for offset of funds due to delinquent indebtedness through administrative offset, Federal employee salary offset, and income tax refund offset. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefit _Claim _Processing _024
    The benefit system must support the benefit offset process by providing the capability for a user to record the effective date of the offset plan. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _025
    The benefit system must support the benefit offset process by incorporating logic to reflect the legal authority as to whether the payment type may be reduced by offset, or is exempt from the TOP or other offsets. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _026
    The benefit system must support the benefit offset process by providing the capability to automatically exclude certain receivables from the offset function. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefit _Claim _Processing _027
    The benefit system must support the benefit offset process by automatically subjecting receivables to offset which had been previously excluded because of due process or bankruptcy status once status has been resolved. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefit _Claim _Processing _028
    The benefit system must comply with the requirements of the IRS Tax Refund Offset Program and TOP requirements. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _029
    The benefit system should support the benefit offset process by providing the capability for a user to select from a domain of offset program participants (i.e., the recipient of the amount to be offset against a claimant's benefit payment). FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _030
    The benefit system should support the benefit offset process by providing the capability for a user to create a participant record if the desired offset program recipient does not exist as a participant. FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _031
    The benefit system should support the benefit offset process in connection with paying retirement benefits, by uniquely identifying bankruptcy debt so that a bankruptcy debt is bypassed when computing the legally mandated 65 percent maximum deduction amount, when an account has both garnishment and former spouse deductions. FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Benefit _Claim _Processing _032
    The benefit system must automatically create a claimant master record using the claimant information for initial claims that are approved, when a master record for the claimant did not previously exist. The master record must contain all of the mandatory data elements as specified in the Claimant Master Record Information Store: • All applicable mandatory data elements (Universal and appropriate categorical) specified within the application information data stores;
    • General information such as: case status, benefit type, chronology of key dates;
    • award data such as: total award, gross and or net monthly payment as appropriate;
    • payment history such as: prior disbursements, collections including principal and interest, accruals;
    • special Collection Activity Data such as: delinquent debt collection activity and status.
    FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Processing _033
    The benefit system must support the funds control process within the benefit recovery receivable management process by properly recording the budgetary affect on U.S. SGL balances for all transactions typically involved with receivable management. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Collections

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _034
    The benefit system must support the benefit entity definition process by allowing for recording transactions in multiple TAFS and various fund types including annual, multi-year, and no-year appropriations, and trust funds. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Post to General Ledger

  • Benefit _Claim _Processing _035
    The benefit system must support the benefit entity definition process by accommodating reporting for multiple programs within a TAFS, based on the accounting classification elements (e.g., organization level, cost center). FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Perform Financial Reporting

  • Benefit _Claim _Processing _036
    The benefit system must support the benefit account definition process by using account titles consistent with the account titles provided in the U.S. SGL. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Financial Management Policy

  • Benefit _Claim _Processing _037
    The benefit system must support the benefit account definition process by using account definitions consistent with the account definitions provided in the U.S. SGL. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Financial Management Policy

  • Benefit _Claim _Processing _038
    The benefit system must support the benefit account definition process by providing subsidiary ledger support for U.S. SGL accounts and supporting reconciliation of U.S. SGL control accounts to their respective subsidiary records by accounting period. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Financial Management Policy

  • Benefit _Claim _Processing _039
    The benefit system must support the benefit transaction definition and processing activities by allowing standard transactions, including system-generated transactions, to be established, modified, or deleted by authorized personnel and providing for traceability of changes. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefit _Claim _Processing _040
    The benefit system must support the benefit transaction definition and processing activities by generating and posting compound debit and credit entries to the U.S. SGL accounts and updating both budgetary and proprietary U.S. SGL accounts based on a single input transaction. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefit _Claim _Processing _041
    The benefit system must support the benefit transaction definition and processing activities by providing the capability to add, modify, and maintain editing and posting rules through systems tables controlled by authorized personnel. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefit _Claim _Processing _042
    The benefit system must support the benefit transaction definition and processing activities by processing transactions consistent with U.S. SGL account descriptions and postings. Use of other than U.S. SGL account numbers (i.e., a pseudo code) is acceptable providing the account descriptions and posting rules are the same as those used in the U.S. SGL for relevant transactions. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefit _Claim _Processing _043
    The benefit system must automatically update an existing claimant master record (i.e., claimant already receives a different type of benefit administered by the agency) to reflect the status (pending, approved, or rejected) of additional claims for other benefits the agency administers that are sought by the claimant. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefit _Claim _Processing _044
    The benefit system must have any expansion to the chart of accounts that roll up to the accounts as defined in the SGL. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Financial Management Policy

  • Benefit _Claim _Processing _045
    The benefit system must perform integrity checks on batches received via interfaces. Checks should include a batch number to detect duplicate or skipped batches, and validity of header and trailer records to ensure counts and amount in trailer agree with records in the batch. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _046
    The benefit system must provide this capability when balancing of preceding documents when entering dependent documents used in the liquidation of commitments, obligations, payables, receivables, or other items, as appropriate. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Post to General Ledger

  • Benefit _Claim _Processing _047
    The benefit system must support the benefit transaction definition and processing activities by processing system-generated transactions, such as automated payment scheduling, accruals, closing entries, recurring payments, and transactions that generate other transactions in those cases where a single transaction is not sufficient. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefit _Claim _Processing _048
    The benefit system must support the benefit transaction definition and processing activities by automatically liquidating, partially or in full, balances of preceding documents when entering dependent documents. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _049
    The benefit system should support the benefit transaction definition and processing activities by providing the capability to enter and store for future processing any transactions in the current month for processing in the subsequent month. FFMIA Value Added HRM
  • Manage Benefits

  • Benefit _Claim _Processing _050
    The benefit system must provide features to record death information provided from voluntary sources (e.g. returned check, funeral home notification, and next of kin). FFMIA Mandatory HRM
  • Manage Benefits

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefit _Claim _Processing _051
    The benefit system must provide all users the capability to perform a "Print Screen" function. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _052
    The benefit system must allow users to input parameters required to run batch jobs in a production mode either daily, monthly, quarterly or yearly. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _053
    The benefit system should Provide for self-service claimant initiated Web browser requests pertaining to account specific matters. For example:
    - enable the claimant to request the reissuance of a misplaced payment using a Web browser;
    - enable the claimant to access decision tree functions to help guide them through self-service transactions through a Web browser;
    - have pop-up windows to help annuitants when making changes to files through a Web browser;
    - enable the claimant to complete forms using a Web browser;
    - have the ability to verify the claimant security information through a Web browser;
    - provide access to claimant retirement related data through Interactive Voice Response (IVR);
    - make IVR available for claimant inquiries 24 hours a day, 7 days a week with the exception of scheduled outages;
    - allow the claimant to initiate changes to his/her account through the IVR;
    - have the ability to support multiple languages (e.g., English and Spanish).
    FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefit _Claim _Processing _054
    The benefit system must automatically merge the mandatory claimant data maintained in the application information stores into the appropriate master record after a claim has been approved and a claimant master record has been established. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefit _Claim _Processing _055
    The benefit system must support the data entry technical function by utilizing various automated input devices when hard copy applications and correspondence are received. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _056
    The benefit system must support the data entry technical function by supporting both batch and real-time on-line data entry and use the same edit and update rules as appropriate for each mode. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _057
    The benefit system must support the data entry technical function by supporting simultaneous data entry/access by multiple users in a variety of access modes. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _058
    The benefit system must support the data entry technical function by providing user entry and query screens that support validation of codes entered on the screen, assisting users in determining correct codes if an invalid code is entered, and providing for inquiry by the user to verify valid codes during the data entry process. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _059
    The benefit system must support the data entry technical function by providing the capability to display inputs required to complete transactions by a user based on the selection of transaction type. Whenever possible, keystroke reducing tools such as drop down menus should be utilized to reduce chance of data entry error. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _060
    The benefit system must support the data entry technical function by displaying a message to the user notifying them of the acceptance or rejection of each transaction once all inputs are completed. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _061
    The benefit system should support the data entry technical function by identifying erroneous inputs with corrective recommendations. FFMIA Value Added HRM
  • Manage Benefits

  • Benefit _Claim _Processing _062
    The benefit system should support the data entry technical function by providing the capability for financial users to create comments relating to all types of transactions using free-form text. FFMIA Value Added HRM
  • Manage Benefits

  • Benefit _Claim _Processing _063
    The benefit system must maintain general data such as demographic data other than that specified in the application information stores that has been historically used by the agency in preparing actuarial estimates, for purposes such as forecasting and complying with financial statement reporting requirements (e.g. SFFAS No. 5 and No. 17). FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefit _Claim _Processing _064
    The benefit system must provide the capability to generate statistics on approved and rejected claim applications. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _065
    The benefit system must provide the capability to accept, identify, track, and report manual overrides of system-generated acceptance/rejection recommendations. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _066
    The benefit system must allow a user who has the proper access to reverse or affirm an initial decision regarding the denial of a benefit, and process the claim accordingly. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _067
    The benefit system must provide the capability to review all prior employee notations or decisions made while processing a benefit claim. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _068
    The benefit system should provide the capability to record an estimated completion date for pending claims. FFMIA Value Added HRM
  • Manage Benefits

  • Benefit _Claim _Processing _069
    The benefit system should have the ability, where multiple claims exist for the same claimant, to process the claims sequentially based on order of precedence. FFMIA Value Added HRM
  • Manage Benefits

  • Benefit _Claim _Processing _070
    The benefit system must have the ability to automatically compare information contained in application(s) that have been submitted by claimants against agency program eligibility criteria (i.e., screen applications for eligibility). FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefit _Claim _Processing _071
    The benefit system must have the ability to accept the manual validation of a claim. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _072
    The benefit system must provide for maintaining separate eligibility criteria and processing routines by type of claim. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _073
    The benefit system must provide for establishment of various age limitations depending on the type of benefit for automatic verification of program eligibility. For example, the system should allow for age attainment verification (e.g., generally a claimant must be at least 60 years of age to be eligible for SSA retirement benefits). FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefit _Claim _Processing _074
    The benefit system must provide the ability to cross-validate applicant information against data maintained for other benefit payment programs which are internal to the administering agency to ensure compliance with all program requirements (e.g., ensure that applicant has not filed for multiple conflicting benefits). FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Processing _075
    The benefit system must provide features to indicate that the applicant submitted required evidence. For example, allow user to record receipt of a school certification pertaining to a claimant or his/her dependent child. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Processing _076
    The benefit system must provide features to create and maintain a system record of accepted and rejected claim applications. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _077
    The benefit system must provide tools to check the appropriate data files to determine whether the applicant has submitted a duplicate application or had a recent benefit application rejected. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefit _Claim _Processing _078
    The benefit system must provide features to determine whether payments being made to the claimant in relation to other internal benefit payment programs affect the claimant's eligibility or payment amount for the benefit under consideration, whenever legally permitted (i.e., permitted by statute or regulation). FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Processing _079
    The benefit system must allow the user to put the processing of a claim on hold (suspend) while verifying questionable information, and to release hold (suspended) status as appropriate. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefit _Claim _Processing _080
    The benefit system should provide ability to inform applicant of potential eligibility for other internal benefit payment programs. FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _081
    The benefit system should have the ability to automatically validate survivor applicant information against information about the deceased or former spouse or related former guardian that is maintained in a master record database. FFMIA Value Added HRM
  • Manage Benefits

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefit _Claim _Processing _082
    The benefit system should automatically validate dates of employment, earnings and other claimant-specific data provided on the application for benefits against the work history and earnings information reported to central agencies such as the Internal Revenue Service (IRS), SSA, and OPM when permitted by statute, or against other verified claimant-specific information maintained by the agency. FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Processing _083
    The benefit system must have the ability to determine if the effective date of the claim has been reached (e.g., the effective date of a retirement claim), and initiate subsequent processing. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefit _Claim _Processing _084
    The benefit system must provide features to compute the amount of both recurring and non-recurring benefit payments based on all available information (e.g., applicant data, and specific benefit program criteria). FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Processing _085
    The benefit system must determine the ending date for recurring payments of limited duration. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _086
    The benefit system when processing an approved claim for benefits such as retirement, disability, death, survivor, and other claims, calculate the amount of recurring payment, or capture the amount of the claimant’s recurring payment that has been determined externally. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefit _Claim _Processing _087
    The benefit system must provide flexibility in maintaining pay rates. For example, use tables that are easily maintained by the user. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _088
    The benefit system must provide for adjusting the amount of payment when the claimant is receiving offsetting monetary amounts. For example, military retired pay is offset on a dollar for dollar basis against veterans compensation payments, and for indiviuals under age 65, Social Security benefits are offset at a predetermined ratio for every dollar earned by claimants above the established threshold amount. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _089
    The benefit system must identify whether the claimant retired under provisions of voluntary separation incentive and capture the amount of the incentive, for Federal and Uniformed Service retirement systems. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefit _Claim _Processing _090
    The benefit system must compute the base amount of retirement pay by determining the "highest paid 36 months (or other number as required by law, regulation or statute) of paid service, for Federal and Uniformed Service retirement systems. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefit _Claim _Processing _091
    The benefit system must determine the creditable years of service based on dates of employment or active military service. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Record Time and Attendance

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefit _Claim _Processing _092
    The benefit system must provide features to calculate the claimant's and/or related dependent's age based on the birth date provided in an application or other verified source for subsequent use in determining claimant eligibility. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefit _Claim _Processing _093
    The benefit system must provide for user defined reasonableness/tolerable limit checks on the amounts of benefit payments that are calculated by the system. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _094
    The benefit system must flag or suspend processing of a claim that fails reasonableness edits to facilitate manual verification of the amount computed. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _095
    The benefit system must enable approved users to have the ability to resume the processing of a claim that was suspended for failing a reasonableness edit, and subsequently verified as accurate. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _096
    The benefit system must allow a user to initiate the calculation of a claimant's benefit amount, at any time, based on claimant data that exists when the request is made. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _097
    The benefit system must have the ability to record the amount of manually computed benefit payments. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _098
    The benefit system must provide for automatic system initiated calculation and or recalculation of benefit amount by claim type, based on a specific user defined event such as claim validation and approval, court order, claimant initiated withholding change, etc. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _099
    The benefit system must provide features to calculate and send overpayment information (date of occurrence, claimant name, and overpayment amount) to Receivables/Collections subsidiary ledger. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Sustain Human Resources

  • Benefit _Claim _Processing _100
    The benefit system must provide for automated routines that access claimant master record data to facilitate calculating the amount of benefits due claimants. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Processing _101
    The benefit system must, at a minimum, accumulate actual payments for each payee annually. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Processing _102
    The benefit system must support the benefit payment execution process by reporting all disbursements made under the delegation in the agency's payment accounting reports to the Financial Management Service (FMS), using the appropriate agency accounting codes, as authorized by FMS. As stated in Section 10025, the agency must submit immediately to the Chief Disbursing Officer (CDO) any irregularity in accounts involving disbursement activity. Furthermore, the agency is responsible for resolving any irregularities or discrepancies associated with such reports. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Perform Financial Reporting

  • Benefit _Claim _Processing _103
    The benefit system must support the benefit payment execution process by submitting check issuance data in a timely and accurate manner to FMS no later than the close of business of the week in which the issue dates occur and at month's end. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Perform Financial Reporting

  • Benefit _Claim _Processing _104
    The benefit system must support the benefit payment execution process by complying with the Financial Management Service (FMS) guidelines concerning applicable requirements to include a payee's taxpayer identifying number on payment vouchers in accordance with 31 U.S.C. § 3325(d). FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Processing _105
    The benefit system must support the benefit payment execution process by complying with all applicable EFT system requirements including those related to message authentication and enhanced security, unless explicitly waived in writing by the CDO. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Disbursements

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _106
    The benefit system must support the benefit payment execution process by automatically identifying and selecting payments to be disbursed in a particular payment cycle based on their due dates. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _107
    The benefit system must support the benefit payment execution process by allowing changes to payment schedules by authorized staff prior to acceptance by the disbursing office. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _108
    The benefit system must support the benefit payment execution process by allowing specific payments selected for disbursement to be excluded from the payment cycle and held for later payment. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _109
    The benefit system must support the benefit payment execution process by automatically computing net amounts to be disbursed, after taking into account withholdings, interest, garnishments, or other offsets as needed, in accordance with applicable regulations. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Post to General Ledger

  • Benefit _Claim _Processing _110
    The benefit system must support the benefit payment execution process by automatically determining taxable benefit payments from non-taxable payments. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _111
    The benefit system must support the benefit payment execution process by collecting information on interest paid if applicable, and recording the amounts to the proper ledger account. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefit _Claim _Processing _112
    The benefit system must support the benefit payment execution process by calculating totals by Agency Location Code (ALC) and TAFS for inclusion on the payment schedule. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Financial Management Policy

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _113
    The benefit system must support the benefit payment execution process by sorting individual payment detail by TAFS to enable SF-224 reconciliation. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefit _Claim _Processing _114
    The benefit system must support the benefit payment execution process by providing for various forms of payment to be used, (i.e., check or electronic funds transfer). FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Collections

  • Manage Disbursements

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _115
    The benefit system must support the benefit payment execution process by supporting Treasury-specific standards for format of check and EFT payment requests. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefit _Claim _Processing _116
    The benefit system must support the benefit payment execution process by automatically updating payment records based on updates recorded in the payee's master record, such as change of address, changes in deposit account information, etc. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Processing _117
    The benefit system must support the benefit payment execution process by allowing a payment request to be removed from the automated scheduling stream and scheduled as a manual payment by an authorized official. FFMIA Mandatory FM
    HRM
  • Calculate Payment Adjustments

  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _118
    The benefit system must support the benefit payment execution process by allowing the user to trigger an immediate benefit payment for "emergency" situations. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _119
    The benefit system must support the benefit payment execution process by providing the capability to schedule and make payments in various forms (e.g., ACH, SF-1166) as required by an agency's disbursing offices, including physical media (e.g., tape, electronic transfer). FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefit _Claim _Processing _120
    The benefit system must support the benefit payment execution process by allowing for cancellation of an entire payment schedule or a single payment within a payment schedule after payments are scheduled and prior to actual disbursement by Treasury. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefit _Claim _Processing _121
    The benefit system must support the benefit payment execution process by providing features to reduce the payment amount due a claimant, in order to offset an outstanding receivable owed by the claimant, in accordance with applicable laws, regulations, and provisions of the Treasury Offset Program (TOP). However, the system must properly record the impact of the entire amount of the transaction in both budgetary and proprietary (i.e., entire amount is expensed, payables or cash accounts reflect net outlay, budgetary resources increased by amount of nonfederal receivable collected, etc.). FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefit _Claim _Processing _122
    The benefit system must provide a function for review and certification by an authorized certifying officer. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _123
    The benefit system must generate the appropriate transactions to reflect the computed deductions and additions. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Post to General Ledger

  • Benefit _Claim _Processing _124
    The benefit system must support the benefit payment execution process by providing for reissuing payments for misplaced payments, lost or stolen checks. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefit _Claim _Processing _125
    The benefit system should support the benefit payment execution process by automatically consolidating amounts due benefit claimants when the claimant is entitled to more than one benefit administered by the same agency, and itemizing all payments covered by the one check or EFT on a payment advice or addendum to the EFT file per Treasury specifications. FFMIA Value Added FM
    HRM
  • Manage Benefits

  • Manage Disbursements

  • Manage Human Resources Compensation and Reimbursements

  • Post to General Ledger

  • Benefit _Claim _Processing _126
    The benefit system should support the benefit payment execution process by allowing for the splitting of a single benefit payment into separate bank accounts (i.e., allotments) as indicated on the claimants direct deposit request form. Allow for a minimum of one allotment in addition to the primary deposit account. FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefit _Claim _Processing _127
    The benefit system should support the benefit payment execution process by providing for making payments in a foreign currency. FFMIA Value Added FM
    HRM
  • Manage Benefits

  • Manage Collections

  • Manage Disbursements

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _128
    The benefit system must support the benefit payment confirmation and follow-up process by updating master record information resulting from payments made by the core system (if applicable). FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _129
    The benefit system must support the benefit payment confirmation and follow-up process by allowing the user to record the outcome of the Treasury search when recertified checks are issued because original checks are lost, stolen, or destroyed. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefit _Claim _Processing _130
    The benefit system must support the benefit payment confirmation and follow-up process by providing 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 scheduled;
    - schedule sent to appropriate disbursing office; and
    - payment issued by appropriate disbursing office.
    FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefit _Claim _Processing _131
    The benefit system must support the benefit payment confirmation and follow-up process by providing for comparison of the agency's payment schedule and the disbursing office's accomplished payment schedule. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Disbursements

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _132
    The benefit system must support the benefit payment confirmation and follow-up process by updating payment information when confirmation is received from the disbursing office, including the paid schedule number, check numbers or trace numbers, date, amount of payment, and payment method (e.g., check or EFT). FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Disbursements

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _133
    The benefit system must support the benefit payment confirmation and follow-up process by automatically liquidating the related liability or the in-transit amount when payment confirmation updates the system. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Disbursements

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _134
    The benefit system must support the benefit recovery receivable establishment process by recording the establishment of receivables in the claimant's master record. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Collections

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Sustain Human Resources

  • Benefit _Claim _Processing _135
    The benefit system must support the benefit recovery receivable establishment process by providing for the establishment of receivables in other systems such as centralized accounts receivable systems, based on individual claim holder debts. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Collections

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _136
    The benefit system must support the benefit recovery receivable establishment process by providing the capability for a user to select the reason the receivable is being recorded from a domain of recognized reasons. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _137
    The benefit system must support the benefit recovery receivable establishment process by supporting the establishment and tracking of receivables to be paid under installment plans, including plans for which payments have been rescheduled. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _138
    The benefit system must support the benefit recovery receivable establishment process by calculating, generating and posting the required ledger entries for receivables resulting from duplicate payments or erroneous payments, and the corresponding expenditure reductions, or other offsets. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _139
    The benefit system must support the benefit recovery receivable establishment process providing the capability to print bills, accommodating the generation of standard forms and turnaround documents to be used as a remittance advice. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _140
    The benefit system must provide the capability for a user to record the beginning and ending dates of the payment period as well as the frequency and amount of each payment. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _141
    The benefit system must allow customized text in generated billing documents. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefit _Claim _Processing _142
    The benefit system must support the benefit recovery receivable establishment process by providing features to notify overpaid individuals (or claimant's estate) of:
    the amount overpaid and how and when overpayment occurred;
    - the right to appeal the overpayment determination;
    - the required recovery; and
    - the right to request a waiver of recovery.
    FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefit _Claim _Processing _143
    The benefit system must support the benefit recovery receivable establishment process by recording adjustments, both increases and decreases (i.e., non-cash credits) and post to a claimant's master record. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Sustain Human Resources

  • Benefit _Claim _Processing _144
    The benefit system must support the benefit recovery receivable establishment process by dating the bills with the system-generated date or with the date supplied by an authorized user. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _145
    The benefit system must support the benefit recovery receivable establishment process by accepting transactions that generate receivables from other systems in a standard format for entry into the benefits system. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _146
    The benefit system must support the benefit recovery receivable establishment process by printing statements as well as bills. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _147
    The benefit system must support the benefit recovery receivable servicing process by updating each master record when billing documents are generated and collections are received. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefit _Claim _Processing _148
    The benefit system must support the benefit recovery receivable servicing process by providing automatic calculation and assessment of interest, administrative charges, and penalty charges as applicable on overdue receivables. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefits _Archiving _And _Purging _001
    The benefit system must support the benefit archiving and purging process by providing an automated means for permanently storing electronic data. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Archiving _And _Purging _002
    The benefit system must support the benefit archiving and purging process by archiving transactions and related information needed for audit trails in a format accessible by audit software. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Archiving _And _Purging _003
    The benefit system must support the benefit archiving and purging process by providing the authorized system administrator the flexibility to determine whether records are to be archived or purged. Of those documents that meet the criteria the system must include the capability to establish and maintain user defined archival criteria. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Archiving _And _Purging _004
    The benefit system must support the benefit archiving and purging process by retaining system records in accordance with Federal regulations established by the National Archives and Records Administration (NARA), GAO, and others. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefits _Archiving _And _Purging _005
    The benefit system must prevent the purging of transactions prior to the proper period in accordance with regulations governing the retention of documents and transactions. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Interface _Requirements _001
    The benefit system should support the benefit internal reporting process by providing the capability for a two-way interface with the core system for purposes of funds control and funds availability verification. FFMIA Value Added FM
    HRM
  • Manage Benefits

  • Perform Financial Reporting

  • Benefits _Interface _Requirements _002
    The benefit system must support the benefit external interface function by providing capabilities allowing interface with central agency financial systems such as Department of the Treasury FMS and IRS Systems, OMB, and OPM systems according to the standards established by these oversight and regulatory agencies. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Perform Financial Reporting

  • Benefits _Interface _Requirements _003
    The benefit system should support the benefit external interface function by receiving information from SSA records to verify applicant's name, SSN, and income information, when legally permitted. FFMIA Value Added HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefits _Interface _Requirements _004
    The benefit system should support the benefit external interface function by providing features to verify applicant's income against Civil Service Annuity, Military Retirement, and IRS earnings records, when legally permitted. FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Interface _Requirements _005
    The benefit system must allow an interface with central agency financial systems for example, systems that interface with the Department of the Treasury must include the capability to: - receive and read the deposit reconciliation file from Treasury, and to produce a report of the matched data and differences;
    - produce a file of all hold check transactions as they are created, and to periodically transmit the hold check file to Treasury;
    - produce and transfer a file of changes to EFT payments previously forwarded to Treasury for release;
    - produce and transfer a file of changes to be made to the Home Address file in Treasury;
    - receive and process the data on the returned check file sent by Treasury’s Recertification system, including generating returned check transactions and updating account data; and
    - receive and automatically process an ACH update file (containing changes to EFT information) from Treasury or other sources on a recurring basis.
    FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Disbursements

  • Manage Human Resources Compensation and Reimbursements

  • Benefits _Payment _Warehousing _001
    The benefit system must support the benefit payment warehousing process by having the ability to determine whether the benefit payment is a non-recurring payment. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefits _Payment _Warehousing _002
    The benefit system must support the benefit payment warehousing process by automatically determining the due date and amount of benefit payments. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefits _Payment _Warehousing _003
    The benefit system must support the benefit payment warehousing process by reestablishing payables for voided checks, or EFTs that were not successful and allowing for reversing the accounting transaction leading to the disbursement and reestablishment of a payable, as appropriate. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefits _Payment _Warehousing _004
    The benefit system must support the benefit payment warehousing process by allowing anticipated obligation or expenditure transactions so that documents may be entered early, stored, and posted at the appropriate date. The benefit system must also subject these documents to edit and validation procedures prior to posting. If the anticipated obligation does not occur, permit the user to delete the transaction without posting it. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _001
    The benefit system must provide capabilities to select benefit claims based on agency program evaluation criteria (such as attainment of certain dollar thresholds - cumulative and per payment, excessive length of benefit payment life) for subsequent review. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _002
    The benefit system must provide the ability to monitor and update a claimant's master records to reflect changes in circumstances affecting a claimant's eligibility or the amount of payment. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _003
    The benefit system must provide capabilities to capture claimant (or relative) reported matters such as:
    - death
    - change in amount of earned/unearned income
    - change of residence
    - marriage, divorce, or separation
    - absence from the U.S.
    - change in disability condition;
    - eligibility for other benefits;
    - changes in net worth/resources of claimant;
    - change in school attendance;
    - change in composition of household; and
    - change in citizenship or alien status.
    FFMIA Mandatory HRM
  • Manage Benefits

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _004
    The benefit system must provide for the recording of notes or comments by customer service representatives and associate with the claimant's master record, and maintain a history of notes taken. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _005
    The benefit system must provide capabilities to record the method used to independently verify the death of a claimant before terminating benefits (phone contact, signature verification, or personal contact with next of kin). FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _006
    The benefit system must provide the ability to maintain a schedule of continuing disability reviews (when applicable) at the individual claim holder level, and maintain the status of the schedule within the claimant's master record. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _007
    The benefit system must provide capabilities to track the status of appeal proceedings when a change is made affecting a current claimant's level of benefits. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _008
    The benefit system must provide features to record termination of benefit payment including:
    - event/reason for termination (e.g., death, increase in income)
    - date of event (thus effective date of benefit cessation)
    FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _009
    The benefit system should provide features to determine if benefits are commensurate with claimant's gender. FFMIA Value Added HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _010
    The benefit system should have the ability to select benefit payment calculations based on statistical sampling techniques for the purpose of verifying calculations. FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefits _Quality _Assurance _And _Maintenance _011
    The benefit system should provide the ability to generate a random sample of claimants to periodically survey regarding their satisfaction with the agency's benefit payment claims process (from initial contact with agency to receipt of benefit payment). FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefits _Quality _Assurance _And _Maintenance _012
    The benefit system should allow users to suspend payment to claimants, when fraud is suspected, or death has been reported but not yet verified by an authoritative source (e.g., SSA). FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefits _Quality _Assurance _And _Maintenance _013
    The benefit system must support the benefit offset process by providing ability to report overdue receivables with associated SSN or TIN data to Treasury for possible offset. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Perform Financial Reporting

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _014
    The benefit system should allow users to cancel a previously recorded suspected death on a claimant, and place the claimant back in a payment status if appropriate. FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _015
    The benefit system must support the benefit payee information maintenance process by maintaining payee information that includes data to support obligation, accounts payable, and disbursement processes. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _016
    The benefit system must support the benefit payee information maintenance process by supporting payments made to parties that act as an agent for the payee without changing permanent claimant information that is maintained in the claimant's master record such as the claimant’s name, address or financial institution. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _017
    The benefit system must support the benefit payee information maintenance process by allowing the user to capture the current tax status, number of exemptions, and other information requested on applicable IRS withholding forms (i.e., W-4P, W-4S, and W-4V). FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _018
    The benefit system must support the benefit payee information maintenance process by maintaining detailed information for each payee to comply with IRS reporting requirements. In cases where payments are made to third parties who are serving in a fiduciary capacity, maintain 1099 information for the principal party rather than the agent. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _019
    The benefit system must support the benefit payee information maintenance process by providing the capability to automatically update payee records to reflect automated clearinghouse (ACH) or electronic funds transfer (EFT) related changes. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _020
    The benefit system must support the benefit payee information maintenance process by providing search capability for payee information (e.g., payee name). FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _021
    The benefit system must support the benefit payee information maintenance process by producing payee listings based on agency-defined criteria, (e.g., payee name and SSN.) FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _022
    The benefit system must support the benefits payee maintenance process by maintaining as part of the claimant’s master record a complete history, of all financial transactions executed for each payee receiving benefits under the claim holder’s master record. This includes payments, and collections, waivers , or offsets resulting from overpayments. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _023
    The benefit system must support the benefit payee maintenance process by making the financial transaction history data of the most recent 18 months available for online query and review for all active "payees". FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _024
    The benefit system should support the benefit payee information maintenance process by maintaining deposit account information on at least two financial institutions for a single payee. FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefits _Quality _Assurance _And _Maintenance _025
    The benefit system must support the benefit funds availability editing process by allowing for recording of funding transactions including recording internal allocations or allotments from within the agency. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _026
    The benefit system must support the benefit funds availability editing process by including adequate controls to prevent the recording of obligations or expenditure transactions that exceed available balances. The system must also support recording obligations or expenditures that exceed available balances based on proper management approval (i.e., provide the capabilities and controls for authorized users to override funds availability edits). FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Execution Fund Account

  • Benefits _Quality _Assurance _And _Maintenance _027
    The benefit system must support the benefit funds availability editing process by providing for designated authorities to establish and modify the system's response (either reject transaction or provide warning) to the failure of a funds availability edit. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Execution Fund Account

  • Benefits _Quality _Assurance _And _Maintenance _028
    The benefit system must support the benefit funds availability editing process by recording the financial impact of all transactions that affect the availability of funds, such as commitments, obligations, expenditures and the establishment of, and collections against recovery receivables. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _029
    The benefit system must support the benefit funds availability editing process by automatically updating all appropriate budgetary tables and ledger account balances (when applicable) to ensure that the system always maintains and reports the current status of funds for all open accounting periods. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _030
    The benefit system should support the benefit funds availability editing process by providing for designated authorities to establish and modify the level of funds control using elements of the classification structure, including object class, program, organization, project, and fund. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _031
    The benefit system should support the benefit funds availability editing process by providing the ability to produce an on-line status of funds report down to the lowest level of the organizational structure. The report should include: amounts available/allotted, open commitments, open obligations, expenditures, and balance available. FFMIA Value Added FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _032
    The benefit system should support the benefit commitment process by allowing commitment transactions to be entered on-line and from multiple locations. FFMIA Value Added FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _033
    The benefit system should support the benefit commitment process by maintaining information related to each commitment transaction. At a minimum, the system should capture accounting classification elements, and estimated amounts. FFMIA Value Added FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _034
    The benefit system should support the benefit commitment process by providing for modifications to commitment transactions, including ones that change the dollar amount or the accounting classification elements cited. FFMIA Value Added FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _035
    The benefit system should support the benefit commitment process by allowing for commitment transactions to be future-dated, stored, and posted at the appropriate date. FFMIA Value Added FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _036
    The benefit system should support the benefit commitment process by closing open commitments under the following circumstances: (1) by the system upon issuance of an obligating document, (2) by an authorized user, and (3) as part of the year-end closing if the commitment is in an annual appropriation or in the last year of a multi-year appropriation. FFMIA Value Added FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _037
    The benefit system should support the benefit commitment process by providing the capability to support commitment accounting based on agency needs. FFMIA Value Added FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _038
    The benefit system must support the benefit obligation and expenditure activity by updating budgetary tables to reflect obligations based on obligating documents and liquidate, at the user's request, the related commitments, either partially or fully. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _039
    The benefit system must support the benefit obligation and expenditure activity by updating budgetary tables to reflect obligations for which there is no related commitment. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Liabilities

  • Benefits _Quality _Assurance _And _Maintenance _040
    The benefit system must support the benefit obligation and expenditure activity by maintaining information related to each obligation document, including amendments. At a minimum, the system must capture the obligating document number and type; and other identification, including benefit payee SSN or TIN, accounting classification elements as appropriate; referenced commitment (if applicable); and dollar amounts. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Liabilities

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _041
    The benefit system must support the benefit obligation and expenditure activity by allowing obligation documents to be entered on-line and from multiple locations. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Execution Fund Account

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _042
    The benefit system must support the benefit obligation and expenditure activity by allowing authorized modifications and cancellations of posted obligation documents. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Execution Fund Account

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _043
    The benefit system must support the benefit obligation and expenditure activity by providing on-line access to all unliquidated obligations by selection criteria, (e.g., document number.) FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Execution Fund Account

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _044
    The benefit system must support the benefit obligation and expenditure activity by maintaining an on-line history file of closed-out documents for a user-defined period of time. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Post to General Ledger

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _045
    The benefit system must support the benefit obligation and expenditure activity by closing open obligating documents to accommodate both of the following circumstances: (1) automatically when reclassifying an unliquidated obligation to an expenditure, or (2) by an authorized user. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Execution Fund Account

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _046
    The benefit system should support the benefit obligation and expenditure activity by allowing multiple commitments to be combined into one obligation or expenditure document and one commitment document to be split into various obligating or expenditure documents. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Execution Fund Account

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _047
    The benefit system must support the benefit payment confirmation and follow-up process by maintaining history of every payment by the benefits system, including authorizing document number, payment schedule number, payment date, payment address, and TAFS charged. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _048
    The benefit system must support the benefit payment confirmation and follow-up process by providing on-line access to claimant and payment information. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _049
    The benefit system must support the benefit payment confirmation and follow-up process by providing on-line access to open documents based on agency selection criteria (e.g., SSN). FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _050
    The benefit system must support the benefit payment confirmation and follow-up process by producing IRS 1099s in IRS acceptable form (hard copy or magnetic tape) when required by IRS regulations (e.g., miscellaneous payments to individuals over $600). FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _051
    The benefit system must support the benefit recovery receivable servicing process by maintaining detailed information by account (i.e., individual) sufficient to provide audit trails and to support billing and research activities. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _052
    The benefit system must support the benefit recovery receivable servicing process by providing on-line query capability to receivable and account information. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _053
    The benefit system must support the benefit recovery receivable servicing process by providing information, on a summary basis and on individual receivables, on the age of receivables to allow for management and prioritization of collection activities. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _054
    The benefit system must support the benefit recovery receivable servicing process by maintaining data for receivables referred to other Federal agencies and or outside organizations for collections. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefits _Quality _Assurance _And _Maintenance _055
    The benefit system must support the benefit recovery receivable servicing process by automatically initiating transactions to record the write-off of delinquent or uncollectible receivables (including interest, penalties, and administrative charges) based on user defined criteria, and maintain data to monitor closed accounts. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefits _Quality _Assurance _And _Maintenance _056
    The benefit system must support the benefit recovery receivable servicing process by producing dunning (collection) letters for overdue receivables in accordance with Treasury requirements and existing legislation. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefits _Quality _Assurance _And _Maintenance _057
    The benefit system must support the benefit recovery receivable servicing process by providing authorized users with the ability to customize the dunning process parameters and dunning letter text. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefits _Quality _Assurance _And _Maintenance _058
    The benefit system must support the benefit recovery receivable servicing process by maintaining information needed to support reporting required by IRS. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefits _Quality _Assurance _And _Maintenance _059
    The benefit system must support the benefit recovery receivable servicing process by maintaining a history of billings and receipts for each receivable and account in accordance with agency requirements. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefits _Quality _Assurance _And _Maintenance _060
    The benefit system must support the benefit recovery receivable servicing process by providing for re-establishment of a receivable for checks returned due to insufficient funds. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefits _Quality _Assurance _And _Maintenance _061
    The benefit system must support the benefit collection process by providing the capability to display all active receivable accounts of record for the relative to the claimant in connection with recording deposits if a claimant's master record is located. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _062
    The benefit system must support the benefit collection process by capturing whether the receivable has been petitioned and or discharged in connection with bankruptcy proceedings to facilitate compliance collection restrictions pertaining to such debts. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefits _Quality _Assurance _And _Maintenance _063
    The benefit system must support the benefit account definition process by providing the capability to create additional sub-accounts to the general ledger for agency specific tracking and control. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Post to General Ledger

  • Benefits _Quality _Assurance _And _Maintenance _064
    The benefit system must support the benefit transaction definition and processing activities by using standard transactions to record accounting events and to control the related updating of other information maintained in the system, such as values in tables (e.g., available funding). FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Post to General Ledger

  • Benefits _Quality _Assurance _And _Maintenance _065
    The benefit system must support the benefit transaction definition and processing activities by performing integrity checks on batches received via interfaces. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Disbursements

  • Benefits _Quality _Assurance _And _Maintenance _066
    The benefit system must support the benefit transaction definition and processing activities by providing control over the correction and reprocessing of all erroneous transactions through the use of error file(s) and or suspense accounts. Erroneous transactions must be maintained and tracked until either corrected or posted or deleted at the specific request of an authorized user. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Disbursements

  • Benefits _Quality _Assurance _And _Maintenance _067
    The benefit system must support the benefit transaction definition and processing activities by supporting management controls to ensure that transactions are processed in accordance with Government and agency-prescribed standards and procedures, the integrity of data in the system is maintained, and access is restricted to authorized users. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Disbursements

  • Benefits _Quality _Assurance _And _Maintenance _068
    The benefit system must support the benefit transaction definition and processing activities by providing transaction edits that control, at a minimum, fund availability, account structure, and tolerance levels between related transactions, such as between an obligation and its related accrual. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Disbursements

  • Benefits _Quality _Assurance _And _Maintenance _069
    The benefit system must support the benefit transaction definition and processing activities by providing controls to prevent the creation of duplicate transactions. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Disbursements

  • Benefits _Quality _Assurance _And _Maintenance _070
    The benefit system should support the benefit audit trails process by providing audit trails to trace transactions from source documents, original input, other systems, system-generated transactions, and internal assignment transactions through the system. Provide transaction details to support account balances. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Post to General Ledger

  • Benefits _Quality _Assurance _And _Maintenance _071
    The benefit system must support the benefit audit trails process by providing audit trails to trace source documents and transactions through successive levels of summarization to the financial statements and the reverse. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Post to General Ledger

  • Benefits _Quality _Assurance _And _Maintenance _072
    The benefit system must support the benefit audit trails process by providing audit trails to identify changes made to system parameters and tables that would affect the processing or reprocessing of any financial transactions. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Post to General Ledger

  • Benefits _Quality _Assurance _And _Maintenance _073
    The benefit system must support the benefit audit trails process by providing audit trails that identify document input, change, approval, and deletions by originator. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Post to General Ledger

  • Benefits _Quality _Assurance _And _Maintenance _074
    The benefit system must support the benefit audit trails process by providing the capability to record the user ID, date, and time updated for each transaction affecting the general and subsidiary ledger accounts. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Post to General Ledger

  • Sustain Human Resources

  • Benefits _Quality _Assurance _And _Maintenance _075
    The benefit system must provide for back up and recovery of the system per relevant OMB Circulars. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Quality _Assurance _And _Maintenance _076
    The benefit system must maintain the present interest rate per the Department of the Treasury. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Benefits _Quality _Assurance _And _Maintenance _077
    The benefit system should maintain the daily exchange rate for relevant currencies. FFMIA Value Added FM
    HRM
  • Calculate Payment Adjustments

  • Manage Benefits

  • Benefits _Reporting _001
    The benefit system must provide features to compute and maintain performance trends such as:
    - number and dollar value of benefit payments made,
    - average benefit payment,
    - benefit payments made by operating levels and geographic region.
    FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefits _Reporting _002
    The benefit system must provide features to compute and maintain efficiency measures to help determine the effectiveness of use of agency resources (at the local level and the national level) such as:
    - number of applications processed
    - number of awards; and
    - number of denials.
    FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Reporting _003
    The benefit system must provide features to compute the length of time claimants have received benefits (average number of months and years, and report(s) showing the number of individuals receiving benefits for by duration (e.g., 1-5 years, 6-10 years) for the entire claimant population. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefits _Reporting _004
    The benefit system should provide features to automatically compute and maintain efficiency measures to help determine the effectiveness of use of agency resources (at the local level and the national level) such as:
    - administrative cost per application approved, and
    - time required to process a claim application.
    FFMIA Value Added HRM
  • Manage Benefits

  • Record Time and Attendance

  • Benefits _Reporting _005
    The benefit system must provide for issuing standard notices for a variety of user defined events. For example, the benefit system must provide capabilities to notify claimant of decisions affecting payment amount or cessation of payments. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefits _Reporting _006
    The benefit system must allow the user to add custom text for each standard correspondence type. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Reporting _007
    The benefit system must allow user to record that the U.S. Postal Service has returned correspondence as undeliverable. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Reporting _008
    The benefit system must have the ability to capture or record the date on which a request for information is received from a claimant or an authorized representative, relative to an appeals case. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefits _Reporting _009
    The benefit system must support the benefit funds analysis process by maintaining current information on obligations according to the classification elements established by the agency, on a fund by fund basis. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Post to General Ledger

  • Benefits _Reporting _010
    The benefit system must support the benefit funds analysis process by sorting and providing on-line access to both summary level and detailed information, based on the defined level of funds control for those transactions that represent obligations and expenditures. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Execution Fund Account

  • Benefits _Reporting _011
    The benefit system must support the benefit funds analysis process by providing control features that ensure the amounts reflected in the fund control structure agree with the general ledger account balances at the end of each update cycle. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Execution Fund Account

  • Benefits _Reporting _012
    The benefit system should support the benefit funds analysis process by tracking the use of funds against operating or financial plans. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Execution Fund Account

  • Benefits _Reporting _013
    The benefit system must support the benefit recovery receivable servicing process by identifying and reporting receivables that meet predetermined criteria for bad debt provisions or write-off. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Manage Receivables

  • Benefits _Reporting _014
    The benefit system must support the benefit recovery receivable servicing process by providing information to allow either manual or automated reporting of delinquent accounts to commercial credit bureaus and referral to collection agencies or other appropriate governmental organizations. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Perform Financial Reporting

  • Benefits _Reporting _015
    The benefit system must support the benefit transaction definition and processing activities by posting to the current and prior accounting months concurrently until the prior month closing; maintain and provide 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 prior month closing. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Post to General Ledger

  • Benefits _Reporting _016
    The benefit system must support the benefit external reporting process by maintaining accounting data to support reporting in accordance with accounting standards pronounced by FASAB, and with other reporting requirements issued by the Director of OMB and the Secretary of the Treasury (some examples are listed in Appendix A). Of particular significance is data that is needed when preparing actuarial estimates for financial statement presentation, in compliance with the reporting requirements specified by SFFAS No. 5 and No. 17. For example, the system should facilitate historical trend analysis of various data elements as determined by the agency. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Perform Financial Reporting

  • Benefits _Reporting _017
    The benefit system must support the benefit external reporting process by providing summarized data electronically to systems used by the agency for decision support and provide for the preparation of external reports such as those required by the Department of the Treasury and OMB. For example, the system must pass the data needed to prepare reports for required by the Federal Agencies’ Centralized Trial-Balance System (FACTS) I, FACTS II, SF-224 (when appropriate) and financial statements to the Core financial system. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Perform Financial Reporting

  • Benefits _Reporting _018
    The benefit system must support the benefit external reporting process by reporting events and transactions according to the accounting classification elements established and within a given accounting period including providing the ability to automatically assign costs by a major program to facilitate preparation of the Statement of Net Costs in accordance with OMB’s current Bulletin on “Form and Content of Agency Financial Statements. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Perform Financial Reporting

  • Benefits _Reporting _019
    The benefit system must support the benefit external reporting process by maintaining the information required for program performance, financial performance, and financial management performance measures needed for budgeting, program management, and financial statement presentation. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Perform Financial Reporting

  • Benefits _Reporting _020
    The benefit system must support the benefit external reporting process by providing the capability to produce all relevant reports, statements, or returns required by the IRS, including producing year-end 1099 statements. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Perform Financial Reporting

  • Benefits _Reporting _021
    The benefit system must support the benefit external reporting process by allowing a user to request a reissued tax statement for current or previous year. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefits _Reporting _022
    The benefit system should support the benefit external reporting process by providing for an automated methodology of data manipulation and data exportation. FFMIA Value Added HRM
  • Manage Benefits

  • Benefits _Reporting _023
    The benefit system should support the benefit external reporting process by providing for automatic translation of foreign currency payments based on the exchange rate specified by the user. FFMIA Value Added FM
    HRM
  • Manage Benefits

  • Manage Disbursements

  • Manage Human Resources Compensation and Reimbursements

  • Perform Financial Reporting

  • Benefits _Reporting _024
    The benefit system should support the benefit external reporting process by allowing a user to request a reissued tax statement for previous 3 prior years. FFMIA Value Added HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefits _Reporting _025
    The benefit system must support the benefit internal reporting process by providing for the production of formatted reports. The system must allow for the reformatting of reports to present different sorts of information, the presentation of only specific information in the format selected, the summarization of data, and the modification of report formats to tailor the reports to the specific requirements of the user. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Reporting _026
    The benefit system must support the benefit internal reporting process by providing for program cost accounting data to support reporting requirements specified in OMB's "Form and Content of Agency Financial Statements," and the decision-making process in managing agency programs. This will include:
    - cost reports to be utilized in the analysis of programmatic activities;
    - schedules and operating statements based on the accounting classification elements and agency criteria;
    - meaningful cost information needed to support performance measures; and
    - ability to transfer cost information directly to and from other systems.
    FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Perform Financial Reporting

  • Benefits _Reporting _027
    The benefit system should support the benefit internal reporting process by providing cost information for comparison to other program data to determine compliance with planned budgeted activities. FFMIA Value Added FM
    HRM
  • Manage Benefits

  • Populate Cost Performance Model

  • Benefits _Reporting _028
    The benefit system should support the benefit internal reporting process by supporting the use of historical data to conduct variance analysis. FFMIA Value Added FM
    HRM
  • Manage Benefits

  • Perform Financial Reporting

  • Benefits _Reporting _029
    The benefit system must support the benefit internal interface if an agency’s financial management system architecture is configured so that the major functions described herein are performed entirely by the benefit module, provide capability to interface with agency core accounting system to record the accounting impact of all financial activity at the U.S. SGL level, on a daily basis, to support consolidated financial reporting. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Perform Financial Reporting

  • Benefits _Reporting _030
    The benefit system must support the benefit internal interface by providing standard input record format(s) for interface of transactions from other systems to the benefits system and subject all transactions from interfacing systems to the benefits financial system edits, validations, and error correction procedures. Erroneous transactions must be maintained and tracked until corrected, posted, or deleted by an authorized user. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Perform Financial Reporting

  • Benefits _Reporting _031
    The benefit system must support the benefit internal interface when a major benefit system function(s) such as payment administration or recovery receivable management is performed by the core system, the benefit system must provide capability to interface with agency’s core accounting system to automatically update detailed claimant related information (e.g. individual payable and receivable records) that is maintained in the core system. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Perform Financial Reporting

  • Sustain Human Resources

  • Benefits _Reporting _032
    The benefit system must support the benefit internal interfacing process by providing the capability to interface to the agency's cost accounting system. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Perform Financial Reporting

  • Benefits _Reporting _033
    The benefit system must support the access to benefit information process by allowing for the information contained in the system to be queried and present detailed data as requested. This will include user-defined criteria to access data for open or closed accounting periods. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Reporting _034
    The benefit system must support the access to benefit information process by providing users with access to on-line guidance or help for performing system functions. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Reporting _035
    The benefit system must support the access to benefit information process by displaying a message indicating the transaction cannot be completed and further research is required if a claimant's or claim holder's record is not located via query. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefits _Reporting _036
    The benefit system must support the access to benefit information process by presenting information resulting from system queries in a formatted fashion to facilitate the understanding of the information by non-technical users, and unformatted for more technically proficient users. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Reporting _037
    The benefit system must support the access to benefit information process by providing the capability to access historical data records that are removed from on-line viewing, including items such as individual benefit payments, receivable, and collection data. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Benefits _Reporting _038
    The benefit system must support the access to benefit information process by allowing users to design extract files for their specific requirements, and perform table look-ups and expansion of codes when needed to clarify the information contained within the results of system queries or reports. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Reporting _039
    The benefit system must support the access to benefit information process by providing features to facilitate verification (i.e., matching programs) using information extracted (see above) from the benefit system for comparison against benefit programs administered by other agencies when legally permitted. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Reporting _040
    The benefit system must support the access to benefit information process by facilitating the analysis of information contained in the system by allowing analysts to obtain report information and the results of system queries in data files that can be transferred to other applications or analytical tools. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Reporting _041
    The benefit system must support the access to benefit information process by providing for easy access to historical files for comparative, analytical, and trend information. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Reporting _042
    The benefit system should support the access to benefit information process by providing for self-service claimant initiated Web browser requests pertaining to account specific matters. FFMIA Value Added HRM
  • Manage Benefits

  • Benefits _Security _Internal _Controls _001
    The benefit system must adhere to the applicable final "Electronic and Information Technology Accessibility Standards" issued by the Architectural and Transportation Barriers Compliance Board, which address technical and functional performance criteria necessary for such technology to comply with section 508 of the Rehabilitation Act Amendments of 1998. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Security _Internal _Controls _002
    The benefit system must support the benefit security and internal controls activities by providing flexible security facilities to control user access at varying degrees including: overall system access, capability to perform specific functions (inquiry, update), access to certain functionality. FFMIA Mandatory HRM
  • Manage Benefits

  • Benefits _Security _Internal _Controls _003
    The benefit system must support the benefit security and internal controls activities by providing the capability to define access to specific functions by named user, class of user, and position. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefits _Security _Internal _Controls _004
    The benefit system must support the benefit security and internal controls activities by providing for multiple levels of approvals based on user-defined criteria including dollar limits, type of document processed, etc. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Benefits _Security _Internal _Controls _005
    The benefit system must support the benefit security and internal controls activities by providing the capability to perform reconciliation routines for internal participant accounts, ledgers, and funds, and to identify unsuccessful reconciliations via error log or error report. FFMIA Mandatory FM
    HRM
  • Manage Benefits

  • Post to General Ledger

  • Benefits _Security _Internal _Controls _006
    The benefit system must support the benefit security and internal controls activities by establishing the appropriate administrative, technical and physical safeguards to ensure the security and confidentiality of records and to protect against anticipated threats or hazards to their security or integrity which could result in substantial harm, embarrassment, inconvenience, or unfairness to any individual on whom information is maintained. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefits _Security _Internal _Controls _007
    The benefit system must support the benefit security and internal controls activities by providing a mechanism to monitor changes to software coding and the responsible individual (authorized user). FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Benefits _Security _Internal _Controls _008
    The benefit system must support the access to benefit information process by complying with the disclosure provisions of the Privacy Act of 1974 (5 U.S.C. 552A) as amended. FFMIA Mandatory HRM
  • Manage Benefits

  • Sustain Human Resources

  • Budgetary _Accounting _001
    To support the Document and Transaction Control process, the Core financial system must provide automated functionality to 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
    • Invoices to obligations.
    FFMIA Mandatory FM
  • Manage Execution Fund Account

  • Budgetary _Accounting _002
    To support the Funds Distribution process, the Core financial system must provide automated functionality to record allotments, sub-allotments, allocations and allowances (i.e. distribute funds) to multiple organizational levels or other elements of accounting classification. FFMIA Mandatory FM
  • Execute Apportionment and Allocate Funds

  • Manage Execution Fund Account

  • Post to General Ledger

  • Budgetary _Accounting _003
    To support the Funds Control/Funds Availability Editing activity, the Core financial system must provide automated functionality to record transactions against prior year funds, both expired and unexpired, in the current year. FFMIA Mandatory FM
  • Manage Execution Fund Account

  • Post to General Ledger

  • Budgetary _Accounting _004
    To support the Funds Control/Funds Availability Editing activity, the Core financial system must provide automated functionality to monitor amounts paid out of current year funds to cover obligations made against a cancelled account Treasury Appropriation Fund Symbol (TAFS)). Prevent payments that cumulatively exceed 1 percent of the current year appropriation or the total amount available prior to close of the original appropriation. FFMIA Mandatory FM
  • Manage Execution Fund Account

  • Budgetary _Accounting _005
    To support the Financial Reporting process, the Core financial system must provide automated functionality to 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 Office of Management and Budget (OMB) Circular A-11 instructions and the USSGL crosswalk to the SF-133 report. FFMIA Mandatory FM
  • Perform Financial Reporting

  • Post to General Ledger

  • Cashier _Function _001
    To support the Cashier Function, the Revenue System must provide the capability to identify the TAFS for which the deposit is being made. FFMIA Mandatory FM
  • Manage Receivables

  • Cashier _Function _002
    To support the Cashier Function, the Revenue System must provide the capability to recognize and classify collections in the proper budgetary categories. Record and control all prescribed types of budgetary authorities relative to earned and unearned revenue or cash collections (both cash and accrual basis), including spending authority from offsetting collections. FFMIA Mandatory FM
  • Manage Receivables

  • Post to General Ledger

  • Cashier _Function _003
    To support the Cashier Function, the Revenue System must provide the capability to recognize and record advance payments received. FFMIA Mandatory FM
  • Manage Receivables

  • Post to General Ledger

  • Cashier _Function _004
    To support the Cashier Function, the Revenue System must provide the capability to recognize and record cash donations as non-exchange revenue. FFMIA Mandatory FM
  • Manage Collections

  • Post to General Ledger

  • Cashier _Function _005
    To support the Cashier Function, the Revenue System must provide the capability to perform transaction cross-referencing in which a user can perform a query to locate the details of associated transactions in the processing "chain" (e.g., querying on a receivable would provide any associated cash receipts). FFMIA Mandatory FM
  • Manage Receivables

  • Cashier _Function _006
    To support the Cashier Function, the Revenue System must provide the capability to track funds at various levels based on required elements of the accounting classification and project/program accounting structure. FFMIA Mandatory FM
  • Manage Receivables

  • Common _Requirements _For _Inventory _Classification _001
    The Inventory, Supplies and Materials system must record beginning balances (on-hand), acquisitions, withdrawals (dispositions), and calculate ending balances (on-hand) expressed in dollar values and physical units. FFMIA Mandatory FM
    MSSM
  • Post to General Ledger

  • Common _Requirements _For _Inventory _Classification _002
    The Inventory, Supplies and Materials system must record item identification, classification (e.g., nomenclature, quantity, description, Federal stock classification or national stock number), initial cost, and subsequent costs related to acquisition (i.e. holding/handling cost). FFMIA Mandatory FM
    MSSM
  • Perform Financial Reporting

  • Post to General Ledger

  • Common _Requirements _For _Inventory _Classification _003
    The Inventory, Supplies and Materials system must record the condition of the inventory. FFMIA Mandatory FM
    MSSM
  • Post to General Ledger

  • Common _Requirements _For _Inventory _Classification _004
    The Inventory, Supplies and Materials system must record changes in value of Inventory, Supplies and Materials due to changes in condition or other impacting circumstances. FFMIA Mandatory FM
    MSSM
  • Post to General Ledger

  • Common _Requirements _For _Inventory _Classification _005
    The Inventory, Supplies and Materials system must record whether material received is hazardous, classified, requires special handling, requires special packaging, requires munitions list controls, requires trade security controls, or has a shelf life. FFMIA Mandatory FM
    MSSM
  • Post to General Ledger

  • Common _Requirements _For _Inventory _Classification _006
    The Inventory, Supplies and Materials system must identify the type of transaction affecting the item; e.g., initial acquisition, location, change in location, and disposal. FFMIA Mandatory FM
    MSSM
  • Post to General Ledger

  • Common _Requirements _For _Inventory _Classification _007
    The Inventory, Supplies and Materials system must provide edits (controls) to prevent duplicate entries and reduce the likelihood of creating erroneous inventory documents/records, thereby ensuring the integrity of data recorded in the system. FFMIA Mandatory FM
    MSSM
  • Post to General Ledger

  • Common _Requirements _For _Inventory _Classification _008
    The Inventory, Supplies and Materials system must permit only authorized users to enter, modify, or otherwise alter inventory records (See section on Security and Internal Controls). FFMIA Mandatory MSSM
  • Post to General Ledger

  • Common _Requirements _For _Inventory _Classification _009
    The Inventory, Supplies and Materials system must provide audit trails to trace transactions from source documents, original input, other systems, and system-generated transactions. FFMIA Mandatory FM
    MSSM
  • Post to General Ledger

  • Common _Requirements _For _Inventory _Classification _010
    The Inventory, Supplies and Materials system must enable and account for the transfer of responsibility for inventory from one authorized manager to another authorized manager, ensuring that sufficient information is transferred to provide an audit trail at the gaining management activity. FFMIA Mandatory MSSM
  • Post to General Ledger

  • Common _Requirements _For _Inventory _Classification _011
    The Inventory, Supplies and Materials system must provide the capability to relate data elements to each other as discussed, through an integrated data query facility that supports ad hoc query access to financial information described in the document and provides reporting tools for data analysis. FFMIA Mandatory MSSM
  • Post to General Ledger

  • Common _Requirements _For _Inventory _Classification _012
    The Inventory, Supplies and Materials system must comply with the Government Paperwork Elimination Act (GPEA) of 1998; requiring Federal agencies to allow, by October 21, 2003, individuals or entities, as an option, to interact with them electronically where practicable. FFMIA Mandatory MSSM
  • Post to General Ledger

  • Common _Requirements _For _Inventory _Classification _013
    The Inventory, Supplies and Materials system must adhere to the applicable final "Electronic and Information Technology Accessibility Standards" issued by the Architectural and Transportation Barriers Compliance Board, which address technical and functional performance criteria necessary for such technology to comply with section 508 of the Rehabilitation Act Amendments of 1998. FFMIA Mandatory MSSM
  • Post to General Ledger

  • Common _Requirements _For _Inventory _Classification _014
    The system must provide a field for a Unique Item Identifier (UID). A UID is a unique, unambiguous string of alpha numeric characters that enable the identification of a specific item from any other like or unlike it in compliance with ISOs 15434 and 15418. (ISO 5434:2005 defines the manner in which data is transferred to high-capacity ADC media from a supplier's information system and the manner in which data is transferred to the recipient's information system. ISO 15418 is Information technology -- EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance.) (Inventory, Supplies, and Materials systems are required to have this field function at all steps in the process from acquisition to disposal. Use of the field is at the discretion of agency management. However, if an agency decides to enable this field, the data in the field must be maintained throughout the lifecycle of the inventoried item.) FFMIA Mandatory MSSM
  • Post to General Ledger

  • Computing _Gross _Pay _001
    The payroll system must process both current period and prior period adjustments as an integral part of the payroll cycle. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Sustain Human Resources

  • Computing _Gross _Pay _002
    The payroll system must compute pay for various types of employees, e.g., firefighters, law enforcement officers, emergency medical technicians, teachers, etc. FFMIA Mandatory HRM
  • Manage Human Resources Compensation and Reimbursements

  • Computing _Gross _Pay _003
    The payroll system must (1) compute earnings amounts or rates for partial pay periods when entitlement dates do not coincide with the pay period's beginning and ending dates, and (2) process earnings adjustments on a begin-date/end-date basis. FFMIA Mandatory HRM
  • Manage Human Resources Compensation and Reimbursements

  • Computing _Gross _Pay _004
    The payroll system must calculate pay at the end of each period after properly authorized inputs have been received from the Time and Attendance Processing Function, and after personnel action processing is completed. FFMIA Mandatory HRM
  • Acquire Human Resources

  • Assign Human Resources

  • Develop Human Resources

  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Record Time and Attendance

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Computing _Gross _Pay _005
    The payroll system must calculate overtime based on FLSA or Title 5 requirements. FFMIA Mandatory HRM
  • Manage Human Resources Compensation and Reimbursements

  • Record Time and Attendance

  • Computing _Gross _Pay _006
    The human resources and payroll systems must calculate current and/or retroactive adjustments for allowances, premiums and differentials as defined by law or regulation. These may be set dollar amounts or computed as a percentage of pay, applying caps or other limitations when applicable. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Computing _Gross _Pay _007
    The payroll system must accommodate information requirements to support supplemental pay actions and recertified checks. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Computing _Gross _Pay _008
    To support pay processing, the payroll system must perform statutory limit and reasonableness tests on gross pay. FFMIA Mandatory HRM
  • Manage Human Resources Compensation and Reimbursements

  • Computing _Gross _Pay _009
    The payroll system must compute gross pay as the sum of each rate of pay times the number of units related to it, minus retirement annuity offsets, if applicable, plus all appropriate allowances and/or other gross pay components. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Computing _Gross _Pay _010
    The payroll system must classify and total deductions, subtract total deductions from gross pay, and apply formulas or utilize tables to determine employer contributions required for certain payroll taxes and benefits. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Computing _Gross _Pay _011
    The system must process and compute pay and deductions for multiple positions under different appointment authorities, and different pay, leave, and benefit entitlements. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Record Time and Attendance

  • Computing _Gross _Pay _012
    The human resources and payroll systems must support retirement calculations for all categories of employees under all applicable retirement programs to the agency. FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Confirm _And _Followup _On _Payments _001
    To support the Payment Confirmation process, the Core financial system must provide automated functionality to update payments with paid schedule number, confirmed date, and check number or trace number upon receipt of confirmation data from the Government Online Accounting Link System (GOALS) II Information Access System (IAS) Regional Financial Center (RFC) Agency Link. FFMIA Mandatory MSSM
  • Monitor Contract or Order Performance

  • Confirm _And _Followup _On _Payments _002
    To support the Payment Follow-Up process, the Core financial system must provide automated functionality to maintain a history of the following information for each payment made:
    • Accounting classification information
    • Agency Locator Code (ALC)
    • Treasury Account Symbol (TAS) / Business Event Type Code (BETC)
    • Referenced obligation document number(s)
    • Source document number(s) (reimbursable agreement number, Blanket Purchase Agreement (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, Taxpayer Identification Number (TIN), and Data Universal Numbering System (DUNS)+4 number for Central Contractor Registration (CCR) vendors)
    • Payment address or bank account number and routing number
    • Payment method (e.g., check, Electronic Fund Transfer (EFT))
    • Payment amount
    • Interest paid
    • Discount taken
    • Internal offset made
    • Date due
    • Date paid.
    FFMIA Mandatory FM
    MSSM
  • Manage Collections

  • Manage Supply Chain Entitlement

  • Monitor Contract or Order Performance

  • Confirm _And _Followup _On _Payments _004
    To support the Reconciliation and Reporting process, the Core financial system must provide automated functionality to 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 formats required by the Department of the Treasury. FFMIA Mandatory FM
  • Manage Execution with Treasury

  • Confirm _And _Followup _On _Payments _005
    The system must provide the Statement of Transactions According to Appropriations, Funds, and Receipt Accounts, FMS Form 1220, data in hard copy format required by the Department of the Treasury. FFMIA Mandatory FM
    MSSM
  • Manage Sales and Procurement

  • Perform Financial Reporting

  • Confirm _And _Followup _On _Payments _007
    To support the Payment Confirmation process, the Core financial system must provide automated functionality to liquidate individual disbursement-in-transit transactions and record confirmed disbursements upon receipt of payment confirmation from the Government Online Accounting Link System (GOALS) II Information Access System (IAS) Regional Financial Center (RFC) Agency Link. FFMIA Mandatory FM
  • Manage Disbursements

  • Post to General Ledger

  • Confirm _And _Followup _On _Payments _008
    To support the Disbursing process, the Core financial system must provide automated functionality to record transactions to reflect disbursement activity initiated by other agencies and recorded in Intra-governmental Payment and Collection (IPAC). FFMIA Mandatory FM
    MSSM
  • Manage Supply Chain Entitlement

  • Monitor Contract or Order Performance

  • Post to General Ledger

  • Confirm _And _Followup _On _Payments _009
    To support the Payment Confirmation process, the Core financial system must provide automated functionality to assign check numbers to individual payment records when a payment schedule has multiple check ranges or a break in check numbers. FFMIA Mandatory MSSM
  • Monitor Payment

  • Confirm _And _Followup _On _Payments _010
    To support the Payment Follow-Up process, the Core financial system must provide automated functionality to 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 proprietor for services rendered. FFMIA Mandatory MSSM
  • Monitor Payment

  • Confirm _And _Followup _On _Payments _011
    To support the Reconciliation and Reporting process, the Core financial system must provide automated functionality to import the Agency Confirmation Report (ACR) support listing from the GOALS II/IAS RFC Agency Link to facilitate reconciliation of agency recorded disbursements and cancellations with Treasury. FFMIA Mandatory FM
  • Manage Execution with Treasury

  • Confirm _And _Followup _On _Payments _012
    To support the Treasury Information Maintenance process, the Core financial system must provide automated functionality to capture the TAS/BETC on all transactions that impact the FBWT and are reported through the Government wide Accounting (GWA) system. FFMIA Mandatory FM
  • Manage Execution with Treasury

  • Confirm _And _Followup _On _Payments _013
    To support the Payment Confirmation process, the Core financial system must provide automated functionality to import payment confirmation data from the GOALS II/IAS RFC Agency Link. FFMIA Mandatory FM
  • Manage Execution with Treasury

  • Confirm _And _Followup _On _Payments _014
    To add value to the Payment Follow-Up process, the Core financial system should provide automated functionality to generate e-mail notification to employees of travel payments made by disbursing offices. FFMIA Value Added MSSM
  • Monitor Payment

  • Confirm _And _Followup _On _Payments _015
    To support the Payment Follow-Up process, the Core financial system must provide automated functionality to 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.
    Sorting options include document number, vendor number, vendor name, accounting classification and unmatched age.
    FFMIA Mandatory FM
  • Post to General Ledger

  • Confirm _And _Followup _On _Payments _016
    To support the Payment Confirmation process, the Core financial system must provide automated functionality to assign check numbers to individual payments, based upon the payment schedule's check range received from the GOALS II IAS RFC Agency Link. FFMIA Mandatory FM
  • Manage Collections

  • Confirm _And _Followup _On _Payments _017
    To support the Reconciliation and Reporting process, the Core financial system must provide automated functionality to 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 used for financial reporting purposes. FFMIA Mandatory FM
  • Post to General Ledger

  • Confirm _And _Followup _On _Payments _018
    To support the Reconciliation and Reporting process, the Core financial system must provide automated functionality to 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
    • Items in the agency's general ledger and not on the ACR listing.
    FFMIA Mandatory MSSM
  • Process Contract Clauses

  • Confirm _And _Followup _On _Payments _020
    To support the Reconciliation and Reporting process, the Core financial system must provide automated functionality to import IPAC support listing from the GOALS II/IAS to facilitate reconciliation of agency recorded IPAC transactions with Treasury. FFMIA Mandatory FM
  • Manage Execution with Treasury

  • Confirm _And _Followup _On _Payments _022
    To support the Reconciliation and Reporting process, the Core financial system must provide automated functionality to compare IPAC transactions on the IPAC support listing with IPAC transactions recorded in the agency's general ledger. FFMIA Mandatory FM
  • Post to General Ledger

  • Confirm _And _Followup _On _Payments _023
    To support the Reconciliation and Reporting process, the Core financial system must provide automated functionality to generate the General Ledger (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 listing.
    FFMIA Mandatory FM
  • Manage Execution with Treasury

  • Confirm _And _Followup _On _Payments _024
    To support the Payment Follow-Up process, the Core financial system must provide automated functionality to query payment data. Parameter is accounting period range. Result is number of payments and percent of total by payment method (EFT vs. check). FFMIA Mandatory FM
  • Manage Disbursements

  • Confirm _And _Followup _On _Payments _025
    To support the Payment Follow-Up process, the Core financial system must provide automated functionality to 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.
    Sort options include number of days late and vendor number.
    FFMIA Mandatory FM
  • Manage Collections

  • Confirm _And _Followup _On _Payments _026
    To support the Payment Follow-Up process, the Core financial system must provide automated functionality to query IRS 1099-MISC information. Parameters include calendar year, vendor name (legal or Doing Business As (DBA)), TIN and DUNS+4 number. Result is details supporting IRS 1099-MISC reporting. FFMIA Mandatory FM
  • Manage Disbursements

  • Confirm _And _Followup _On _Payments _027
    To support the Payment Follow-Up process, the Core financial system must provide automated functionality to 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 Part 1315. FFMIA Mandatory FM
  • Manage Disbursements

  • Confirm _And _Followup _On _Payments _028
    To support the Treasury Information Maintenance process, the Core financial system must provide automated functionality to maintain GWA Reporter Categories. FFMIA Mandatory FM
  • Manage Execution with Treasury

  • Confirm _And _Followup _On _Payments _029
    To support the Treasury Information Maintenance process, the Core financial system must provide automated functionality to define the GWA Reporter Category for GWA reporter ALCs as
    • IPAC Only
    • CA$HLINK II Only
    • Treasury Disbursing Office (TDO) Payments Only
    • IPAC and CA$HLINK II
    • IPAC and TDO Payments
    • TDO Payments and CA$HLINK II, or
    • IPAC, CA$HLINK II and TDO Payments.
    FFMIA Mandatory FM
  • Manage Collections

  • Confirm _And _Followup _On _Payments _030
    To support the Payment Confirmation process, the Core financial system must provide automated functionality to correct system-assigned check numbers on payment records that do not match the actual check number assigned by Treasury. FFMIA Mandatory FM
  • Manage Collections

  • Cost _And _Revenue _Accumulation _001
    The managerial cost accounting system must send cost data to the appropriate system to calculate exchange revenue for goods or services made or produced to order under a contract. FFMIA Mandatory FM
    MSSM
  • Monitor Contract or Order Performance

  • Populate Cost Performance Model

  • Cost _And _Revenue _Accumulation _002
    The managerial cost accounting system should support the inventory system (or other property system) by accumulating costs from multiple sources for inventory and related property that has been acquired, is undergoing repair, or is in production (work-in-process). FFMIA Value Added FM
  • Populate Cost Performance Model

  • Cost _And _Revenue _Accumulation _003
    The managerial cost accounting system should provide accumulated costs, including applicable indirect costs, to the appropriate system for recording as the appropriate asset or expense type. FFMIA Value Added FM
  • Manage Liabilities

  • Populate Cost Performance Model

  • Post to General Ledger

  • Cost _And _Revenue _Accumulation _004
    The managerial cost accounting system should accumulate and determine the full cost of general property, plant and equipment (PP&E) under construction. FFMIA Value Added FM
  • Populate Cost Performance Model

  • Cost _And _Revenue _Accumulation _005
    The managerial cost accounting system should transfer the completed project construction in progress cost to the appropriate asset account and passed the information to the core financial system and property management system(s) for asset valuation purposes. FFMIA Value Added FM
  • Populate Cost Performance Model

  • Cost _And _Revenue _Accumulation _006
    The managerial cost accounting system shall recognize the cost of acquiring, improving, reconstructing, or renovating heritage assets, other than multi-use heritage assets, on the statement of net cost for the period in which the cost is incurred. The cost shall include all costs incurred during the period to bring the item to its current condition at its initial location. FFMIA Mandatory FM
  • Populate Cost Performance Model

  • Cost _And _Revenue _Accumulation _007
    The managerial cost accounting system must accumulate and maintain Stewardship Investment cost (investment in human capital, research and development, and non-federal physical property), on an annual basis for stewardship reporting, for a period of five years FFMIA Mandatory FM
  • Populate Cost Performance Model

  • Cost _And _Revenue _Accumulation _008
    The job order cost system must calculate actual shop rates from the cost obtained from the same database used to prepare general ledger control account entries. DFMIR Mandatory FM
  • Populate Cost Performance Model

  • Cost _And _Revenue _Accumulation _009
    The managerial cost accounting system should be capable of supporting cost management by accumulating costs in agency defined cost centers that are associated with agency-defined performance measures FFMIA Value Added FM
  • Populate Cost Performance Model

  • Cost _And _Revenue _Accumulation _010
    The managerial cost accounting system must be capable of supporting cost management by accumulating numerically valued agency-defined output information. FFMIA Mandatory FM
  • Populate Cost Performance Model

  • Cost _And _Revenue _Accumulation _011
    The managerial cost accounting system must be capable of supporting cost management by calculating the unit cost of outputs. FFMIA Mandatory FM
  • Populate Cost Performance Model

  • Cost _Assignment _001
    The managerial cost accounting system must support one or more of the following costing methodologies:
    • Activity Based Costing (ABC),
    • Job Order Costing,
    • Process Costing and
    • Standard Costing.
    FFMIA Mandatory FM
  • Define Cost Performance Model

  • Cost _Assignment _002
    If the cost assignment process affects the values of Standard General Ledger (SGL) accounts in the core financial system's general ledger, such as inventory or fixed asset accounts, the managerial cost accounting system must send the summarized impact of cost assignments to the core financial system for posting to the general ledger and external reporting. FFMIA Mandatory FM
  • Populate Cost Performance Model

  • Post to General Ledger

  • Cost _Assignment _003
    Costs of supporting services and intermediate products should be assigned to the segments that receive the services and products. This is referred to as the intra-entity cost assignments. FFMIA Mandatory FM
  • Populate Cost Performance Model

  • Cost _Assignment _004
    With respect to each responsibility segment, the costs that are to be assigned to outputs: (a) direct and indirect costs incurred within the responsibility segment, (b) costs of other responsibility segments that are assigned to the segment, and (c) inter-entity costs recognized by the receiving entity and assigned to the segment. If a responsibility segment produces one kind of output only, costs of resources used to produce the output are assigned to the output. FFMIA Mandatory FM
  • Define Cost Performance Model

  • Populate Cost Performance Model

  • Cost _Assignment _005
    The costs that can be traced to each of the activities (or outputs) shall be assigned to the activities (or outputs) directly. FFMIA Mandatory FM
  • Populate Cost Performance Model

  • Cost _Assignment _006
    To determine the full cost of each of the activities or outputs that share resources, indirect common costs shall be assigned to those activities. Common costs shall be assigned to activities either on a cause-and-effect basis, if feasible, or through reasonable allocations. FFMIA Mandatory FM
  • Populate Cost Performance Model

  • Cost _Assignment _019
    Unfunded cost financed by other organizations or by prior appropriations should be added to the shop rate charges and billed to non-DoD ordering activities or considered in making cost effectiveness comparisons. DFMIR Mandatory FM
  • Populate Cost Performance Model

  • Post to General Ledger

  • Cost _Assignment _020
    The general and administrative (G&A) expenses are accumulated in the activities indirect cost centers and charged to customers by equitably prorating the expense to job orders. DFMIR Mandatory FM
  • Populate Cost Performance Model

  • Cost _Monitoring _And _Reporting _001
    The managerial cost accounting system should be able to provide cost data needed to produce the Statement of Net Costs for the agency's financial statements FFMIA Value Added FM
  • Perform Financial Reporting

  • Populate Cost Performance Model

  • Cost _Monitoring _And _Reporting _002
    The managerial cost accounting system should assist in the reporting of financial data related to stewardship resources. FFMIA Value Added FM
  • Populate Cost Performance Model

  • Cost _Monitoring _And _Reporting _003
    The managerial cost accounting system must be capable of supporting cost management by producing unit cost reports by output. FFMIA Mandatory FM
  • Populate Cost Performance Model

  • Cost _Monitoring _And _Reporting _004
    The managerial cost accounting system must be capable of supporting cost management by producing project, job order, and work order reports showing costs for a project from its inception up to the current date. FFMIA Mandatory FM
  • Populate Cost Performance Model

  • Cost _Monitoring _And _Reporting _005
    The managerial cost accounting system must be capable of supporting cost management by producing contract reports showing the revenues and costs associated with each contract (i.e. customer orders). FFMIA Mandatory FM
  • Populate Cost Performance Model

  • Cost _Monitoring _And _Reporting _006
    A reporting entity and its responsibility segments may incur general management and administrative support costs that cannot be traced, assigned, or allocated to segments and their outputs. These unassigned costs are part of the organization costs, and they shall be reported on the entity's financial statements (such as the Statement of Net Costs) as costs not assigned to programs. FFMIA Mandatory FM
  • Define Cost Performance Model

  • Perform Financial Reporting

  • Populate Cost Performance Model

  • Cost _Monitoring _And _Reporting _007
    Inter-entity expenses/assets and financing sources shall be eliminated for any consolidated financial statements covering both entities. FFMIA Mandatory FM
  • Populate Cost Performance Model

  • Cost _Monitoring _And _Reporting _008
    The managerial cost accounting system must be able to provide cost data needed to produce the Statement of Net Cost for the agency's financial statements. FFMIA Mandatory FM
  • Perform Financial Reporting

  • Populate Cost Performance Model

  • Cost _Monitoring _And _Reporting _009
    The process cost accounting system must update the appropriate general ledger control accounts: Inventory - Finished Goods and the Work-in-Process accounts. Detailed DoD-specific transactions are available in the USSGL Transaction Library, reference Volume 4, Chapter 2, subparagraph 020101. Using standardized transactions, post entries reflecting consumption of supplies and labor, followed by entries reallocating expenses to "in-process" accounts. DFMIR Mandatory FM
    HRM
    MSSM
    RPILM
  • Associate Project Identification to Appropriate CIP Account

  • Associate Project Identification to Appropriate WIP Account

  • Create CIP and or WIP Account

  • Determine If CIP and or WIP Account is Required

  • Establish CIP and or WIP Account

  • Populate Cost Performance Model

  • Post to General Ledger

  • Record CIP and or WIP Financial Transactions

  • Relieve CIP and or WIP Account

  • Update CIP and or WIP Account

  • Cost _Of _Post _1991 _Direct _Loans _001
    An automated direct loan system must record Post-1991 direct loans as assets at the present value of their estimated net cash inflows. The difference between the outstanding principal of the loans and the present value of their net cash inflows is recognized as a subsidy cost allowance. FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _002
    An automated direct loan system must record a subsidy expense for Post-1991 direct loans disbursed during a fiscal year. The amount of the subsidy expense equals the present value of estimated cash outflows over the life of the loans minus the present value of estimated cash inflows, discounted at the interest rate of on marketable United States (U.S.) Treasury securities of similar maturity to the cash flow of the direct loan or loan guarantee for which the estimate is being made (hereinafter referred to as the applicable Department of the Treasury interest rate). FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _003
    During the fiscal year in which new direct loans are disbursed, an automated direct loan system must recognize the components of subsidy expense (of those new direct loans) separately from interest subsidy costs, default costs, fees and other collections, and other subsidy costs. FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _004
    An automated direct loan system must record the present value of fees and other collections as a deduction from subsidy costs. FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _005
    An automated direct loan system must amortize the subsidy cost allowance for direct loans by the interest method using the interest rate that was used to calculate the present value of the direct loans when the direct loans were disbursed, after adjusting for the interest rate re-estimate. The amortized amount is recognized as an increase or decrease in interest income FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _006
    An automated direct loan system must re-estimate the following subsidy cost allowance, for direct loans, as of the date of the financial statements:
    interest rate re-estimates and
    technical/default re-estimates.
    Each program re-estimate should be measured and disclosed in these two components separately.
    FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _007
    An automated direct loan system must recognize any increase or decrease in the subsidy cost allowance resulting from the re-estimates as an increase or decrease in subsidy expense for the current reporting period. FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _008
    An automated direct loan system must recognize interest accrued on direct loans, including amortized interest, as interest income. FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _009
    An automated direct loan system must recognize interest due from the U.S. Treasury on un-invested funds as interest income. FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _010
    An automated direct loan system must recognize interest accrued on debt to the U.S. Treasury as interest expense. FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _011
    An automated direct loan system must recognize losses and liabilities of direct loans, obligated before October 1, 1992, when it is more likely than not that the direct loans will not be totally collected. FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _012
    An automated direct loan system must re-estimate the allowance of the uncollectible amounts, for pre-1992 direct loans, each year as of the date of the financial statements. FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _013
    An automated direct loan system must recognize the amount of the modification cost of direct loans as a modification expense when pre 1992 or post 1991 direct the loans are modified. FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _014
    An automated direct loan system must recognize any difference between the change in book value and the cost of modification of both pre 1992 and post 1991 direct loans as a gain or loss. FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _015
    For post-1991 direct loans, an automated direct loan system must recognize as a financing source (or a reduction in financing source) the modification adjustment transfer paid or received to offset any gain or loss. FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _016
    An automated direct loan system must recognize any difference between the book value loss (or gain) and the cost of modification on a sale of a pre 1992 and post 1991 direct loan as a gain or loss. FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _018
    The actual historical experience for the performance of a risk category is a primary factor upon which an estimation of default cost is based. To document actual experience, a database shall be maintained to provide historical information on actual payments, prepayments, late payments, defaults, recoveries, and amounts written off. DFMIR Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _019
    When a post-1991 direct loan is modified, an automated direct loan system must change the existing book value of that loan to an amount equal to the present value of the net cash inflows projected under the modified terms from the time of modification to the loan's maturity. That amount is discounted at the original discount rate (the rate that was originally used to calculate the present value of the direct loan, when the direct loan was disbursed, after adjusting for the interest rate re-estimate). FFMIA Mandatory FM
  • Record Loans and Grants

  • Cost _Of _Post _1991 _Direct _Loans _020
    When property is transferred from borrowers to a federal credit program through foreclosure or other means, in partial or full settlement of post-1991 direct loans or as a compensation for losses that the government sustained under post-1991 loan guarantees, an automated direct loan system must recognized the foreclosed property as an asset and record the asset at the present value of its estimated future net cash inflows discounted at the original discount rate adjusted for the interest rate re-estimate. FFMIA Mandatory FM
  • Record Loans and Grants

  • Customer _Order _Options _001
    To support Customer Order Options, the Revenue System must provide the capability to process and track orders to determine order status and allow for detailed (by customer) and batched information required in RO-1 (see requirement 05.08.01). In a non-exchange revenue transaction, collect the same data a customer order provides in an exchange revenue transaction (see examples of non-exchange revenues). Customer order data is to be retained to capture an order's entire history for handling inquiries and providing an audit trail. OMB's Business Rules for Intragovernmental Transactions, (M-07-03), requirements must also be supported (i.e., providing DUNS numbers, order numbers, standard data elements for billing records, and others). Also, customer order data is to be filed in accordance with National Archives and Records Administration (NARA) regulations for the required time frames based on the type of record and activity. FFMIA Mandatory MSSM
  • Monitor Contract or Order Performance

  • Customer _Order _Options _002
    To support Customer Order Options, the Revenue System must provide the capability to ensure that order fulfillment and revenue can be associated with a specific Intragovernmental order, the seller must capture the buyer's Intragovernmental order number in the seller's order fulfillment or revenue system to associate the buyer's order number with any agreement or control number assigned by the seller's system. FFMIA Mandatory MSSM
  • Monitor Contract or Order Performance

  • Customer _Order _Options _003
    To support Customer Order Options, the Revenue System should provide the capability to receive customer orders via Internet. FFMIA Value Added FM
  • Manage Receivables

  • Customer _Order _Options _004
    To support Customer Order Options, the Revenue System should provide an integrated customer management relationship to establish a single view of account information. FFMIA Value Added FM
  • Manage Receivables

  • Death _Benefits _001
    To support the Application Information Store data requirements relative to systems used in administering death benefit programs, the benefit system must capture:
    - Claimant’s relation to claim holder.
    - Dates of creditable employment of the claim holder (and military service when used in determining eligibility and the amount of benefits).
    - Claimant dependency information, when such affects the benefit amount.
    - Date married, when applicable.
    - Date divorced when applicable.
    - Date of claim holder death.
    FFMIA Mandatory HRM
  • Manage Benefits

  • Manage Human Resources Compensation and Reimbursements

  • Separate or Terminate Human Resources

  • Sustain Human Resources

  • Deferred _Maintenance _And _Cleanup _Costs _001
    The system shall recognize and record the following total estimated cost of environmental liabilities associated with General PP&E placed in service prior to October 1, 1997:
    (a) In the initial year the liability is recorded, unless the costs are intended to be recovered through user charges.
    (b) If the costs are intended to be recovered through user charges, then the DoD Components shall recognize a liability for that portion of the asset that has passed since the PP&E was placed into service in the initial year the liability is recorded. The remaining liability shall be systematically recognized over the remaining useful life.
    The property system must recognize the estimated environmental liabilities associated with General PP&E placed in service after September 30, 1997, that have future environmental closure and/or environmental cleanup requirements, over the useful life. The accumulation of the liability and the recognition of the related expense shall commence when it is placed in service, continue in each period that operation continues, and be completed when the General PP&E ceases operation.
    FFMIA Mandatory FM
    RPILM
  • Manage Liabilities

  • Post to General Ledger

  • Prepare Environmental Liabilities Information for Financial Reporting

  • Deferred _Maintenance _And _Cleanup _Costs _002
    Environmental cost estimates shall be reviewed annually and revised when there is evidence that significant changes in the cost measurement have occurred, such as changes in scope, ownership, regulation, or technology. As a minimum, long-term cost estimates shall be adjusted upward or downward annually, through indexing, to maintain them on a current cost basis as if acquired in the current period. FFMIA Mandatory RPILM
  • Prepare Environmental Liabilities Information for Financial Reporting

  • Deferred _Maintenance _And _Cleanup _Costs _003
    During each period that general PP&E is in operation, the system must record a portion of the estimated total cleanup costs as an expense. This expense allocation must be done in a systematic and rational manner based on the use or physical capacity of the associated PP&E, whenever possible. If physical capacity is not applicable or estimable, the estimated useful life of the associated PP&E may serve as the basis for systematic and rational recognition of expenses and accumulation of the liability. Recognition of the expense and accumulation of the liability shall begin on the date that the PP&E is placed into service, continue in each period that operation continues, and be completed when the PP&E ceases operation. FFMIA Mandatory FM
    RPILM
  • Post to General Ledger

  • Prepare Environmental Liabilities Information for Financial Reporting

  • Deferred _Maintenance _And _Cleanup _Costs _004
    The system should allow estimated environmental liabilities to be reduced by the costs that are paid to reflect the total remaining cleanup costs less any unrecognized portions of a systematically recognized cost estimate. Further, the DoD Component should be able to distinguish between the current and non-current portions of the liability estimate. FFMIA Mandatory FM
    RPILM
  • Manage Liabilities

  • Perform Financial Reporting

  • Post to General Ledger

  • Prepare Environmental Liabilities Information for Financial Reporting

  • Deferred _Maintenance _And _Cleanup _Costs _005
    The system must recognize the estimated environmental liabilities associated with cleanup cost for Stewardship PP&E in the period that the asset is placed into service. FFMIA Mandatory FM
    RPILM
  • Manage Liabilities

  • Post to General Ledger

  • Prepare Environmental Liabilities Information for Financial Reporting

  • Deferred _Maintenance _And _Cleanup _Costs _006
    The property system must record the cumulative effect of changes in cost estimates by recognizing an expense in the current accounting period and adjusting the corresponding liability. Additionally, the related cleanup cost for the current period shall be expensed and accrued as an environmental liability. FFMIA Mandatory FM
    RPILM
  • Manage Liabilities

  • Post to General Ledger

  • Deferred _Maintenance _And _Cleanup _Costs _011
    For stewardship PP&E that are in service at the effective date of SFFAS-6 (beginning after September 30, 1997), the system must recognize a liability for cleanup costs and an adjustment must be made to the Net Position of the entity. The amount of the adjustment shall be shown as a "prior period adjustment" in any statement of changes in net position that may be required. No amounts should be recognized as expense in the period of implementation. The amounts involved should be disclosed and, to the extent possible, the amount associated with current and prior periods should be noted. FFMIA Mandatory FM
    RPILM
  • Perform Financial Reporting

  • Post to General Ledger

  • Deferred _Maintenance _And _Cleanup _Costs _012
    The system shall allow an entity to record an offsetting charge, for any General PP&E Cleanup Cost liability recognized upon implementation, to its' Statement of Changes in Net Position. FFMIA Mandatory FM
  • Perform Financial Reporting

  • Post to General Ledger

  • Deferred _Maintenance _And _Cleanup _Costs _013
    An entity must show, as a prior period adjustment in its Statement of Changes in Net Position, the amount of the liability due to implementing the cleanup costs standard in SFFAS-6. The amounts involved shall be disclosed and, to the extent possible, the amount associated with current and prior periods should be noted. The system shall not recognize any amount as an expense in the period of implementation. FFMIA Mandatory FM
  • Perform Financial Reporting

  • Deferred _Maintenance _And _Cleanup _Costs _014
    The property management system may provide the capability to forecast or schedule maintenance requirements for future periods. FFMIA Value Added RPILM
    WSLM
  • Maintain Asset Information

  • Deferred _Maintenance _And _Cleanup _Costs _015
    At a minimum, the system must present deferred maintenance in the financial statements as required supplementary information for all General PP&E including identification of each major class of asset for which maintenance has been deferred and the method of measuring deferred maintenance for each major class of PP&E. FFMIA Mandatory FM
    RPILM
    WSLM
  • Maintain Asset Information

  • Perform Financial Reporting

  • Deferred _Maintenance _And _Cleanup _Costs _016
    The system must capture management's estimate of deferred maintenance. This may be accomplished through a process or system other than in a property system. FFMIA Mandatory RPILM
    WSLM
  • Maintain Asset Information

  • Perform Installations Support

  • Deferred _Maintenance _And _Cleanup _Costs _017
    The property management system must capture management's assessment of property condition. This may be accomplished through a process or system other than in a property system. FFMIA Mandatory RPILM
    WSLM
  • Maintain Asset Information

  • Deferred _Maintenance _And _Cleanup _Costs _019
    The system must capture the total estimated clean-up cost when the item is placed in service if the PP&E meets the criteria established in paragraph 88 of SFFAS No. 6. This may be accomplished through a process or system other than in a property system. FFMIA Mandatory FM
    RPILM
  • Manage Liabilities

  • Post to General Ledger

  • Prepare Environmental Liabilities Information for Financial Reporting

  • Deferred _Maintenance _And _Cleanup _Costs _020
    The system must capture environmental liabilities associated with PP&E when an event has occurred and the liability is probable and estimable. This may be accomplished through a process or system other than in a property system. FFMIA Mandatory FM
    RPILM
  • Manage Liabilities

  • Post to General Ledger

  • Prepare Environmental Liabilities Information for Financial Reporting

  • Deferred _Maintenance _And _Cleanup _Costs _021
    The system must calculate the annual amortization of estimated material, clean-up costs, and the unamortized balance for general PP&E. FFMIA Mandatory FM
    RPILM
  • Manage Liabilities

  • Post to General Ledger

  • Prepare Environmental Liabilities Information for Financial Reporting

  • Deferred _Maintenance _And _Cleanup _Costs _022
    The system must estimate environmental liability cost measurements for each environmental site located at an installation or organizational level. The liability cost estimates should include the anticipated costs of the level of effort required to cleanup hazardous wastes, as well as the costs of complying with associated applicable legal and/or regulatory requirements. Such cost estimates are calculated on a current cost basis and based on a current decontamination and/or disposal plan, existing laws, and technology. The cost estimates for both the environmental and non-environmental portion of the liability should include the following cost elements, as applicable:
    1. Compensation and benefits of government personnel expected to devote significant time directly to a disposal effort to include security and surveillance.
    2. Efforts to tear down, remove, and dispose of the item(s) to include transportation, demilitarization, and dismantlement.
    3. Planning and design efforts to include contract advertisement and document reproduction.
    4. Landscaping costs.
    5. Permits, licenses, and approval to include State Historic Preservation Officer concurrence and documentation. Also included are screening costs of suitable property for the homeless as established by the McKinney Act in Public Law 101-645.
    6. Repair costs if disposed without being demolished.
    7. Cost of employing contractors, engineers, and consultants.
    8. Cost of dedicated facilities, machinery, and equipment and the related operating and maintenance costs.
    9. Research and development costs for alternative remediation technologies.
    10. Grants to state and local governments.
    11. Payments to state, tribal, and local governments.
    12. Payments to regulatory agencies to provide technical support, e.g. document review of planned studies.
    DFMIR Mandatory RPILM
  • Prepare Environmental Liabilities Information for Financial Reporting

  • Deferred _Maintenance _And _Cleanup _Costs _023
    The system shall maintain an inventory of environmental sites and reconcile it with PP&E records at least annually. DFMIR Mandatory RPILM
  • Prepare Environmental Liabilities Information for Financial Reporting

  • Deposit _Account _Function _001
    To support the Deposit Account Function, the Revenue System must provide the capability to create a new deposit account (escrow account) record with data element fields required in RO-1 (see requirement 05.08.01) to record account history and activity. FFMIA Mandatory FM
  • Manage Receivables

  • Post to General Ledger

  • Deposit _Account _Function _002
    To support the Deposit Account Function, the Revenue System must provide the capability to provide access to update deposit account records for both active and inactive deposit accounts. Modifications to any deposit account data will be date effective. FFMIA Mandatory FM
  • Manage Receivables

  • Post to General Ledger

  • Deposit _Account _Function _003
    To support the Deposit Account Function, the Revenue System must provide the capability to close a deposit account. The system will record the disposition of any remaining balance. Closed deposit account records will be archived. FFMIA Mandatory FM
  • Manage Receivables

  • Post to General Ledger

  • Deposit _Account _Function _004
    To support the Deposit Account Function, the Revenue System must provide the capability to process remittances to and charges against a deposit account. Remittances will be processed in the same record format as a payment. FFMIA Mandatory FM
  • Manage Receivables

  • Post to General Ledger

  • Deposit _Account _Function _005
    To support the Deposit Account Function, the Revenue System must provide the capability to provide monthly statements of transaction activity in paper and/or electronic form. FFMIA Mandatory FM
  • Manage Receivables

  • Perform Financial Reporting

  • Deposit _Account _Function _006
    To support the Deposit Account Function, the Revenue System must provide the capability to notify customers (if specified) if their deposit account balance drops below a certain dollar amount. FFMIA Mandatory FM
  • Manage Receivables

  • Deposit _Account _Function _007
    To support the Deposit Account Function, the Revenue System must provide the capability to validate accounts by not accepting a transaction for a charge against a deposit account until the system has determined that the account number is valid, not delinquent, and has a sufficient balance to cover the charge. If the balance is not sufficient to cover the charge, the system must send notification to the customer and a notice permitting/delaying service to be rendered. Any deposit account transaction that causes an overdrawn balance without notification shall be rejected by the system. FFMIA Mandatory FM
  • Manage Receivables

  • Deposit _Account _Function _008
    To support the Deposit Account Function, the Revenue System must provide the capability to apply penalty charges for deposit account balances that fall below a predetermined level at any point in time or at a predetermined point, such as at the end of a month. The predetermined level and assessment date may vary by deposit account type. These penalty charges shall be automatically assigned by the system. FFMIA Mandatory FM
  • Manage Receivables

  • Depreciate _Amortize _Deplete _Asset _002
    The property system must capture the estimated useful life, depreciation/amortization/depletion method, and salvage/residual value for each capitalized asset or group of assets, for capitalized property. FFMIA Mandatory RPILM
    WSLM
  • Maintain Asset Information

  • Depreciate _Amortize _Deplete _Asset _003
    The property system must accumulate depreciation expense in a contra asset account: accumulated depreciation. It must also accumulate amortization expense in a contra asset account: accumulated amortization FFMIA Mandatory FM
    RPILM
    WSLM
  • Maintain Asset Information

  • Post to General Ledger

  • Depreciate _Amortize _Deplete _Asset _004
    The property system should calculate and record accumulated depreciation/ amortization (contra asset) based on the recorded estimated cost and the number of years the general PP&E has been in use relative to its estimated useful live FFMIA Mandatory FM
    RPILM
    WSLM
  • Maintain Asset Information

  • Post to General Ledger

  • Depreciate _Amortize _Deplete _Asset _005
    For accountability and financial reporting purposes, the property system must recognize the proper accounting treatment (expense or capitalization and depreciation or amortization) and the reporting of capitalized amounts and accumulated depreciation or amortization on the appropriate DoD Component's financial statements. DFMIR Mandatory FM
    RPILM
    WSLM
  • Maintain Asset Information

  • Perform Financial Reporting

  • Depreciate _Amortize _Deplete _Asset _006
    The property system must be able to depreciate capital lease assets for those activities authorized to enter into capital lease agreements. DFMIR Mandatory FM
    RPILM
    WSLM
  • Maintain Asset Information

  • Post to General Ledger

  • Depreciate _Amortize _Deplete _Asset _007
    The property management system may calculate depreciation on asset pools. FFMIA Mandatory WSLM
  • Maintain Asset Information

  • Depreciate _Amortize _Deplete _Asset _008
    The property management system shall capitalize the costs to improve a General PP&E asset when the costs of the improvement increase the General PP&E asset's capability, size, efficiency, or useful life or modifies functionality. In addition, the cost of an improvement shall be capitalized only when the cost of the improvement equals or exceeds DoD capitalization threshold FFMIA Mandatory FM
    RPILM
    WSLM
  • Maintain Asset Information

  • Post to General Ledger

  • Depreciate _Amortize _Deplete _Asset _009
    The system must record as capital leases the lease that meet the following four criteria. Otherwise, it should be classified as an operating lease
    1. The lease transfers ownership of the property to the lessee by the end of the lease term.
    2. The lease contains an option to purchase the leased property at a bargain price..
    3. The lease term is equal to or greater than 75 percent of the estimated economic life of the leased property.
    4. The present value of rental and other minimum lease payments, excluding that portion of the payments representing executory cost, equals or exceeds 90 percent of the fair value of the leased property.
    The last two criteria (numbers 3 and 4) are not applicable when the beginning of the lease term falls within the last 25 percent of the total estimated economic life of the leased property.
    FFMIA Mandatory FM
    RPILM
    WSLM
  • Maintain Asset Information

  • Post to General Ledger

  • Depreciate _Amortize _Deplete _Asset _010
    The property system must provide an audit trail for amortization, depletion and depreciation expense. FFMIA Mandatory RPILM
    WSLM
  • Maintain Asset Information

  • Depreciate _Amortize _Deplete _Asset _011
    The property system must calculate depreciation/ amortization expense through the systematic and rational allocation of the cost of general PP&E, less its estimated salvage/residual value, over the estimated useful life of the general PP&E. Depreciation expense shall be recognized on all general PP&E, except land and land rights of unlimited duration. Estimates of useful life of military equipment must consider factors such as usage, physical wear and tear and technological change. FFMIA Mandatory FM
    MSSM
    RPILM
  • Maintain Asset Information

  • Post to General Ledger

  • Depreciate _Amortize _Deplete _Asset _012
    Department of Defense policy permits the use only of the straight-line method of depreciation, except for military equipment. For military equipment, an activity-based method of depreciation, which recognizes the change in an asset's value as a result of use rather than time, may also be used. FFMIA Mandatory FM
    MSSM
    RPILM
  • Maintain Asset Information

  • Post to General Ledger

  • Depreciate _Amortize _Deplete _Asset _014
    The property system shall recognize computer software that is integrated into (embedded) and necessary to operate equipment (rather than perform an application) as part of the equipment of which it is an integral part and capitalized and depreciated as part of the cost of equipment. The aggregate cost of the hardware and software shall be used to determine whether to capitalize or expense the costs. DFMIR Mandatory FM
    RPILM
  • Populate Cost Performance Model

  • Direct _Loan _Account _Billing _And _Collection _001
    The direct loan system must calculate outstanding balances for each loan account invoiced. The calculation must include principal, interest, late charges, and other amounts due. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _002
    The direct loan system must identify loan accounts to be invoiced based on agency program invoicing criteria and other loan account information, such as amount outstanding, most recent payment, payment amount due, and date due. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _003
    The direct loan system must provide the capability to analyze escrow balances to adjust required deposit amounts. This will help prevent deficiencies in tax and insurance deposits and payments for housing and other long-term real estate loans. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _004
    The direct loan system must generate and transmit a bill, payment coupon, invoice or other document that shows the borrower ID, amount due, date due, the date after which the payment will be considered late, and the current balance. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _005
    The direct loan system must apply any collections, using the agency's program receipt application rules, to the appropriate liquidating or financing account. Collection sources could include cash, pre-authorized debit, check, or credit card. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _006
    The direct loan system must record a prepayment (the early payoff of the entire loan balance or paying more than the scheduled monthly payment), a partial, full, or late payment indicator. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _007
    The direct loan system must identify payments that cannot be applied and document why the payments cannot be applied. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _008
    The direct loan system must be able to compare a borrower's preauthorized debits, received from financial institutions and other external sources, to expected collections. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _009
    The direct loan system must provide an automated interface with the Core Financial System to record the collection. If the direct loan system itself handles the collection processing, it must meet the requirements in the "Core Financial System Requirements" related to this activity and send summary data to the Core Financial System. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _010
    The direct loan system must be able to provide a means for debtors to inquire into their account status such as electronic inquiry using a secure internet WEB site or an automated telephone program such as a voice response unit. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _011
    The direct loan system must be able to apply components of payment (principle, interest, late fees) in accordance with established business rules. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _012
    The direct loan system must be capable of automatically capitalizing interest in accordance with established policy. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _013
    The direct loan system must be able to provide an electronic means to receive payments such as Automated Clearing-house (ACH) and Electronic Debit Account (EDA). FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _014
    For reporting collections, an automated direct loan system must be able to prepare and mail to borrowers by January 31 of each year:
    Internal Revenue Service (IRS) Form 1098, Mortgage Interest Statements;
    IRS Form 1099-A, Acquisition or Abandonments of Secured Property;
    IRS Form 1099-C, Cancellation of Debt;
    IRS Form 1099-G, Certain Government Payments and
    other IRS Forms as required.
    FFMIA Mandatory FM
  • Manage Collections

  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _015
    The direct loan system must be capable of interfacing with other financial management systems. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Billing _And _Collection _016
    The direct loan system must be capable of supporting managerial cost accounting. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _001
    The direct loan system must support evaluation of accounts proposed for modification by the agency or borrower by comparing loan data to the agency's program loan modification criteria. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _002
    The direct loan system must calculate rescheduled loan terms, including repayment amounts and schedules, where appropriate. It must also calculate any change in the subsidy amount as a result of the loan modifications. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _003
    The direct loan system must perform a funds control check through an automated interface with the Core Financial System to verify the availability of a subsidy. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _004
    The direct loan system must produce selected loan account information listings for review by internal modification groups. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _005
    The direct loan system must establish a new loan account and collateral record for each new debt instrument and assign a unique loan account number to the new account record. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _006
    The direct loan system must update the loan information store to reflect the modified status of the loan, including changes in the value or status of any collateral. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _007
    The direct loan system must provide an automated interface with the Core Financial System to record pre-1992 and post 1991 direct loan modifications. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _008
    The direct loan system must be able to generate a new loan document, which displays information concerning both the original and modified direct loan. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _011
    The direct loan system must be able to maintain a link between the new loan account established for the new debt instrument and the old loan account records. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _012
    For internal management information requirements for the account servicing function, an automated direct loan system must allow an agency to determine whether the following financial accounting information (at appropriate levels of summary for computational and reporting purposes) should be provided as a hard copy or through system queries:
    transactions,
    loan history, risk category,
    cohort, and
    account
    FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _013
    For collateral requirements, an automated direct loan system must document significant changes to the condition and value of any collateral. FFMIA Mandatory FM
  • Manage Liabilities

  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _014
    The automated direct loan system must use Configuration Management (CM) that will establish and maintain the security and integrity of the direct loan system throughout its development life cycle. FFMIA Mandatory FM
  • Manage Financial Management Policy

  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _015
    The direct loan system shall be able to demonstrate that all development requirements are incorporated into the final system output through the use of requirements traceability matrices. FFMIA Mandatory FM
  • Manage Financial Management Policy

  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _016
    The direct loan system shall perform all work needed to accomplish the specified outcomes, achieve or exceed the specified performance standards, record and reconcile funds, and track and report activity. FFMIA Mandatory FM
  • Define Cost Performance Model

  • Perform Cost Analysis

  • Populate Cost Performance Model

  • Record Loans and Grants

  • Direct _Loan _Account _Status _Maintenance _017
    The direct loan system testing shall ensure that all related manual procedures perform according to system requirements. FFMIA Mandatory FM
  • Manage Financial Management Policy

  • Record Loans and Grants

  • Direct _Loan _Application _Screening _001
    The direct loan system must record critical credit application data needed to support application screening. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _002
    The direct loan system must provide access to application information to all agency staff participating in the screening and credit-granting decisions. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _003
    The direct loan system must process and record collections of fees remitted with the application in both the direct loan system and the Core Financial System. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _004
    The direct loan system must compare loan application information to agency program eligibility criteria. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _005
    The direct loan system must check the appropriate system data files to determine whether the applicant has submitted a duplicate application or has had a recent loan application rejected. These situations may indicate attempts by applicants to subvert agency credit policies. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _006
    The direct loan system must document that borrowers have certified that they have been unable to obtain credit from private financial sources, where such certification is a program requirement. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _007
    The direct loan system must provide an automated interface with credit bureaus that allows an agency to obtain applicant credit history information (credit bureau report). For credit bureaus that do not have the capability for an automated interface, record credit history information entered by agency staff. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _008
    The direct loan system must document that applicant financial data, repayment ability, and repayment history have been verified through the use of supplementary data sources such as employment and income data, financial statements, tax returns, and collateral appraisals, where this is a program requirement. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _009
    The direct loan system must compare the applicant's creditworthiness information to system-stored program creditworthiness criteria and, where a program requirement, calculate a credit risk rating for the applicant. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _010
    The direct loan system must document whether the Credit Alert Interactive Voice Response System (CAIVRS) identified the applicant as a borrower who is delinquent or has defaulted on a previous federal debt. The system should allow override if the agency determines that the account was referred to CAIVRS in error. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _011
    The direct loan system must provide the information needed to compute the credit subsidy amount associated with a loan. It must do this by using projected cash flows and the applicable U.S. Treasury interest rate, in accordance with OMB Circular A-11, A-34, and SFFAS No. 2. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _012
    The direct loan system must provide an automated interface with the Core Financial System to determine if sufficient funds are available in the Program Account to cover the subsidy cost. It must also determine if available lending limits in the Financing Account are sufficient to cover the face value of the proposed loan. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _013
    The direct loan system must provide an automated interface with the Core Financial System to be able to commit funds for the loan if funds control is not done within the DL system. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _014
    The direct loan system must update the application information store to reflect the status of the loan. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _015
    The direct loan system must accept, identify, track, and report supervisor overrides of system-generated acceptance/rejection recommendations. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _016
    The direct loan system must create and maintain a system record of accepted and rejected loan applications. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _017
    The direct loan system must generate a letter notifying the applicant of rejection or acceptance of the loan application. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Application _Screening _018
    The direct loan system must be able to provide for an electronic application process using various media, such as a secure internet application (WEB site). FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _001
    When using an agency authorized to cross-service, an automated direct loan system should identify the volume and type of debts serviced. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _002
    When using an agency authorized to cross-service, an automated direct loan system should identify the tools used by the agency to collect its own debt. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _003
    When using an agency authorized to cross-service, an automated direct loan system should provide one or more years of information on the average age of debt over 180 days. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _004
    When using an agency authorized to cross-service, an automated direct loan system should calculate the amount of debt collected using various collection tools. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _005
    When using an agency authorized to cross-service, an automated direct loan system should accrue late charges, as required by referring agency. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _006
    When using an agency authorized to cross-service, an automated direct loan system should provide information to referring agency sufficient for the referring agency to satisfactorily complete the Report on Receivables Due From the Public. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _007
    When using an agency authorized to cross-service, an automated direct loan system should track, by portfolio, age of debt referred, dollar and number of referrals, collections on referred debts and report to Treasury on a monthly basis. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _008
    When using an agency authorized to cross-service, an automated direct loan system should provide information to referring agency as needed, i.e. collections received. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _009
    When using an agency authorized to cross-service, an automated direct loan system should provide ad hoc reporting capability needed to satisfy referring agencies unique information requests such as, length of workout agreements, percent of debt that can be compromised, etc. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _010
    In identifying accounts to be selected for cross-servicing, an automated direct loan system should compare delinquent loan account information to statutory criteria to select delinquent loan accounts for possible referral. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _011
    In identifying accounts to be selected for cross-servicing, an automated direct loan system should generate notification to the debtor of the agency's intent to refer the debt to a debt collection center. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _012
    In identifying accounts to be selected for cross-servicing, an automated direct loan system should update the loan information store. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _013
    In identifying accounts to be selected for cross-servicing, an automated direct loan system should identify accounts that can no longer be serviced by agency personnel. FFMIA Mandatory FM
  • Record Loans and Grants

  • Direct _Loan _Cross _Servicing _014
    In monitoring accounts referred to the debt collection center, an automated direct loan system should identify accounts with monetary adjustments that must be reported to the debt collection center. FFMIA Mandatory FM
  • Record Loans and Grants