Achieve consistency in budget and accounting classifications and synchronization between those classifications and the organizational structure.
Provide a fund structure that identifies TAS/TAFS established by OMB and Treasury.
Differentiate among the type of budgeting, accounting, and reporting treatments to be used based on various TAS/TAFS characteristics.
Provide a program structure with sufficient levels of detail to allow reporting for all categories
Establish an organizational structure based on responsibility segments, such as bureaus, divisions, and branches.
Support the management of multiple Agency Location Codes (ALC) and associate the appropriate ALC with each transaction
Provide a project structure that is independent of the other accounting classification elements
Provide an object class structure consistent with the standard object class codes contained in OMB Circular No. A-11
Process additions, changes and deletions to elements of the accounting classification design, and related valid domain
Allow the user to enter, edit, and store accounting classification table changes
Reject or suspend interfaced transactions that contain accounting classification elements or domain values
Value Added Requirements
Provide a revenue source code structure to identify and classify types of revenue and receipts as defined by the user.
Validate all transactions involving Treasury and other disbursing centers for valid combinations of ALC and TAS/TAFS
Derive the full accounting classifications from abbreviated user input
Provide for an automated method to reclassify accounting data at the document level
Transaction Control Process
Transaction Definition and Processing
Mandatory Requirements
Use standard transactions when recording accounting events.
Allow the user to include proprietary, budgetary and memorandum accounts in the definition of a standard transaction.
Record transactions consistent with U.S. SGL posting rules.
Reject a transaction or provide a warning message when attempting to post a transaction
Allow users to define and maintain standard rules that control general ledger account postings for all accounting events.
Enable users to selectively require, omit, or set a default value for individual accounting classification elements.
Update all applicable general ledger account balances based on a single input transaction.
Define, generate and post compound general ledger debit and credit entries for a single transaction.
Allow users to define and process system-generated transactions
Automatically liquidate, partially or in full, the balance of open documents by line item.
Automatically determine and record the amount of upward or downward adjustments to existing obligations
Automatically distinguish between upward and downward adjustments to unexpired and expired budget authority
Relative to expired funds, provide an overrideable error message when attempting to post
When recording adjustments to prior year obligations automatically classify upward and downward adjustments
Control the correction and reprocessing of all erroneous transactions through the use of error/suspense files.
Provide immediate, on-line notification to the user of erroneous transactions.
Provide controls to prevent the creation of duplicate transactions.
Provide a warning message when the user attempts to input an external vendor invoice number that has already been recorded for the related vendor.
Validate the fields for all accounting classification elements required to process the transaction prior to posting.
Enter, edit, and store transactions in the current accounting period for automatic processing in a future accounting period.
Put transactions in a hold status within the Core system.
Capture the six-digit trading partner code when processing all transactions that directly involve another Federal entity.
For all transactions, capture transaction dates and posting dates.
Automatically determine the posting date from the system date for all transactions.
Automatically reverse entries by the parameters: transaction or document type, date range, schedule numbers, and others.
Post to the current and prior months concurrently until the prior month closing is complete.
Provide and maintain on-line queries and reports on balances separately for the current and prior months.
Post to the current fiscal year and prior fiscal year concurrently until prior yearend closing is complete.
Provide and maintain on-line queries and reports on balances separately for the current and prior fiscal years.
Value Added Requirements
Perform validation checks for use of certain general ledger accounts associated with specific Record Type 7 authority
Have all functions of the system, process and track transactions in both foreign currency and U.S. dollars.
Calculate progress payments to foreign vendors based on current exchange rates.
Audit Trails
Mandatory Requirements
Provide audit trails to trace transactions from their initial source through all stages of related system processing.
Select items for review based on user-defined criteria by type of transaction.
Provide audit trails that identify document input, change, approval, and deletions by user.
General Ledger Management
General Ledger Account Definition Process
Mandatory Requirements
Allow users to define and maintain a chart of accounts consistent with the U.S. SGL
Incorporate proprietary, budgetary, and memorandum (credit reform) accounts in the system
Provide U.S. SGL control accounts for detailed subsidiary accounts in the Core or external systems.
Create additional sub-accounts to the U.S. SGL for agency specific tracking and control.
Capture U.S. SGL attribute information required for both FACTS I and FACTS II reporting as specified
Provide flexibility so that the system can adapt to changes in FACTS I and FACTS II reporting requirements.
Process additions, deletions, and changes to the chart of accounts without extensive program or system changes
Prohibit new transactions from posting to general ledger accounts that have been de-activated.
Accruals, Closing and Consolidation Process
Mandatory Requirements
Allow for accruals relating to contracts or other items that cross fiscal years.
Automatically generate selected recurring accrual entries and reversals in subsequent accounting periods
Close an accounting period and prohibit subsequent postings to the closed period.
Automatically determine an accounting period's opening balances based on the prior accounting period's closing balances
Perform multiple preliminary yearend closings, while maintaining the capability to post current and prior period data.
Automatically generate fiscal yearend pre-closing and closing entries as they relate to fund types.
Provide for an automated yearend rollover of appropriate system tables into the new fiscal year.
Value Added Requirements
General Ledger Analysis and Reconciliation Process
Mandatory Requirements
Compare amounts in the general ledger accounts with the amounts in the related subsidiary records and create reports
Perform on-line "drill downs" from general ledger summary balances to detail transactions and referenced documents
Record subsequent activity related to a closed document under a unique document ID and provide an audit trail
Value Added Requirements
Funds Management
Budget Preparation Process
Mandatory Requirements
Establish and maintain operating/financial plans at or below the level of funds control.
Establish operating/financial plans by month and quarter at any level of the organizational structure specified by the user.
Track and report on the use of funds against operating/financial plans.
Value Added Requirements
Prepare operating/financial plans based on multiple measures, including obligations, costs, labor hours, and full-time equivalents.
Modify/revise an existing operating/financial plan by line item.
Maintain original and modified operating/financial plans.
Identify legal and administrative limitations on funds in operating/financial plans.
Generate allotments and sub-allotments.
Enter operating/financial plans for future operating periods.
Roll future plans into active budget plans based on future date or retrieval function.
Budget Formulation Process
Mandatory Requirements
Value Added Requirements
Report information for all categories on which budgetary decisions are made, whether legally binding
Populate the budget formulation system with prior-year budgeted and actual amounts.
Perform projections of obligations, income, and expenditures at any level of the organizational structure (e.g., projecting obligations based on prior periods and applying these to a future period).
Adjust projection rates and exclude specified obligations from projection.
Create, store, and modify payroll forecasts, at the individual employee level.
Incorporate overhead distribution as part of budget formulation.
Develop budgets on-line and via upload from spreadsheets.
Distribute budget submission guidance to subordinate organizations electronically.
Establish and maintain multiple budget cycles.
Tie budget formulation to the agency's stated goals and objectives required by GPRA.
Funds Allocation Process
Mandatory Requirements
Record funding and related budget execution documents (e.g., warrants, apportionments, allotments) and limitations.
Control the use of funds against limitations consistent with appropriation and authorization language
Distribute, track, and control, funds at various levels, based on the elements of the accounting classification and project structure.
Verify that funds distributed do not exceed the amount of funds available for allotment or sub-allotment at each distribution level.
Support Public Law 101-510 (M-year legislation)
Record and control all types of budgetary authority.
Record the expiration and cancellation of appropriation authority in accordance with OMB Circular No. A-34 and the U.S. SGL.
Account for spending transactions at a lower level in the accounting classification than they are budgeted.
Account for budgetary resources at a lower level in the accounting classification than they are budgeted and controlled.
Prepare and electronically transmit SF-132s to OMB. Store prepared requests as submitted for future use.
Value Added Requirements
Generate budgetary data in format required by OMB's MAX system.
Automatically prepare the formal allotment and sub-allotment documents and electronically distribute them
Create continuing resolution funding levels based on a percentage of prior-year funding.
Budget Execution Process
Mandatory Requirements
Record budget authority at multiple levels of distribution (at least five).
Track and record all changes to budget authority.
Track actual amounts and verify commitments and obligations against the budget as revised
Modify funding distribution (including apportionments and allotments) at multiple organizational levels (at least five).
Manage and control prior-year funds in the current year.
Establish and maintain user-defined variance tolerances.
Automatically withdraw (or cancel) uncommitted and unobligated allotments and sub-allotments
Automatically withdraw (or cancel) uncommitted and unobligated allotments and sub-allotments
Distribute the annual budget in accordance with the latest SF-132 Apportionment and Reapportionment Schedule
Value Added Requirements
Request approval for reprogramming and request additional funds outside the periodic budget review process.
Funds Control Process
Funds Availability Editing
Mandatory Requirements
Establish and modify multiple levels of funds control using elements of defined accounting classifications
Establish and modify the system's response to the failure of funds availability edits for each transaction type.
Perform on-line inquiry of funds availability prior to the processing of spending transactions
Determine funds availability and record appropriate accounting entries when de-obligation of expired funding occurs.
Record transactions that affect the availability of funds, including commitments, obligations, and expenditures.
Provide for modification to spending documents including ones that change the dollar amount or the accounting classification cited.
Provide on-line notification to users of transactions failing funds availability edits
Override funds availability edits, including automatically releasing and processing transactions previously rejected
Automatically update all appropriate budgetary accounts and or tables
Check for funds availability when the obligation exceeds the commitment document
Allow for available fund balances to be based on reimbursable customer orders accepted.
Track all activity related to an individual reimbursable agreement.
Record and maintain reimbursable agreements, so that information can be presented.
Value Added Requirements
Automatically notify users when funds availability is reduced by transactions from external systems
Commitments
Mandatory Requirements
Maintain information related to each commitment document, including amendments.
Input line item detail for commitment documents, including item description, unit price, quantity of goods and services
Future-date, store, and automatically post commitment documents at the appropriate date.
Close commitments by document and line item under circumstances
Value Added Requirements
Obligations
Mandatory Requirements
Record obligations for which there is no related commitment.
Maintain information related to obligation documents and related amendments
Future-date, store, and automatically post obligation documents at the appropriate date.
Enter recurring obligation transactions that will be automatically posted at various time intervals
Allow multiple commitments to be combined into one obligating document.
Allow one commitment document to be split between multiple obligating documents.
Reference multiple funding sources on a single commitment or obligation.
Allow authorized modifications and cancellations of posted obligating documents.
Provide on-line access to all obligations by selection criteria
Maintain an on-line history file of closed-out documents for a user-defined period of time.
Allow the vendor used on an obligation to be different from suggested vendor recorded on the related commitment document.
Close obligation documents under circumstances:
Record and maintain contracts and grants and related financial activity
Record blanket purchase agreements, and record, control, and track records of call.
Record, control, and track delivery orders against a contract limitation.
Record advance payments made, such as travel advances, contract advances, and grants.
Record expenditures claimed against advance payments made, and automatically liquidate the advance
Automatically link transactions in the spending chain, and bring forward accounting and non-financial information
Value Added Requirements
Maintain additional data fields for each obligating document
Analysis
Mandatory Requirements
Maintain current information on commitments and obligations according to the required accounting classification elements
Produce detailed listings and summary reports of commitments, obligations and expenditures
Provide control features that ensure that the amounts reflected in the fund control structure agree with the related general ledger account balances at the end of each update cycle
Maintain historical data on all commitment, obligation, payment and collection transactions.
Maintain open documents to show the status of commitments, obligations, accruals, and disbursements by document line item.
Provide the ability to perform document cross-referencing in which a user can query on any document
Value Added Requirements
Payment Management
Payee Information Maintenance Process
Mandatory Requirements
Maintain payee (vendor) information to support obligation, accounts payable, and disbursement processes, including:
Support payments made to third parties (payees) that act as an agent for the payee (vendor).
Prevent the duplicate entry of vendor records (e.g., by editing vendor ID numbers or vendor names.)
Track and maintain a history of changes to the vendor file
Query and report on payee information by user-defined criteria,
Activate and deactivate vendors that meet user selected criteria
Value Added Requirements
Capture vendor information required when registering with the Central Contractor Registration (CCR)
Payment Warehousing Process
Mandatory Requirements
Record an accrued liability upon receipt and acceptance of goods and services
Record "full" or "partial" receipt and acceptance of goods and services by line item.
Automatically update the funds control and budget execution balances to reflect changes in the status of obligations
Warehouse payment vouchers for future scheduling.
Allow a warehoused payment to be modified, cancelled, and put on hold.
Automatically match invoices to obligations and receiving reports by document and line item.
Process "obligate and pay" transactions where payment scheduling and obligation occurs simultaneously.
Reference multiple obligations on a single invoice document.
Set up recurring payments in the system and automatically schedule items for payment on an interval determined by the user
Modify recurring payment information for changes in agreement terms, amounts, frequency, etc.
Capture, store and process the following information for each vendor invoice, for audit trail, research and query purposes:
Edit the TIN field to ensure that it is a nine digit numeric field, does not include dashes, and is not all zeroes.
Accommodate an invoice number field of up to 30 characters or the current requirement of I TFM-6-5000.
Determine the due date and amount of vendor payments in accordance with Title 5, Part 1315 of the CFR
Manually override a system-calculated payment due date.
Split an invoice into multiple payments on the appropriate due dates
Record discount terms and automatically determine whether taking the discount is economically justified as defined in I TFM-6-8040.
Record additional shipping and other charges to adjust the payment amount
Record obligations, expenses, assets, etc., associated with payments made through use of Imprest funds, third-party drafts, and Government credit cards.
Record detailed transactions associated with credit card purchases.
Schedule payments of advances, prepaid expenses, loans, and grants, with the appropriate accounting entries for each.
Establish payables and make payments on behalf of another agency, citing the other agency's funding information.
Record expense or assets when goods have been received, or services performed
Indicate if a payment is "partial" or "final." If "final," automatically de-obligate any unliquidated balances.
Value Added Requirements
Automatically generate a payment voucher if the purchase order matches the receiver information.
Use the Fast Payment clause indicator on the obligating document to determine whether or not an accelerated payment is to be made.
Compare discount terms on the invoice with discount terms on the related obligating document.
Provide a system-generated letter or e-mail to the vendor stating the reason for rejection
Payment Execution Process
Mandatory Requirements
Automatically identify and select payments to be disbursed in a particular payment cycle based on their due dates.
Automatically compute amounts to be disbursed, including discounts, interest, and penalties
Automatically apply interest and discount across multiple accounting lines on an invoice
Apply the appropriate Treasury interest rate tables (e.g., Prompt Pay rate and Current Value of Funds rate).
Capture prompt payment information required by Title 5, Part 1315 of the CFR
Automatically include relevant identification information on each remittance, including: vendor invoice number(s);
Record user comments for each voucher/invoice.
Provide for up to 9,999 line items per invoice.
Record reason codes for returned and adjusted invoices, lost discounts, and late payments.
Track the status of invoices in the payment process
Provide for various forms of payment to be used
Generate ACH payments in Corporate Trade Exchange
Ensure that employee ACH payments are generated only as PPD or PPD+ payments.
Ensure that vendor ACH payments are generated only as CCD, CCD+ or CTX formats.
Prohibit the creation of an ACH payment in any format that does not contain a RTN and an account number.
Consolidate multiple payments to a single payee in accordance with TFM prescribed limitations
Create check files and EFT payment files in all formats
Provide an edit on the RTN field.
Edit the invoice number field to ensure it is populated.
Generate multiple payments using the same invoice number, to accommodate recurring invoice number.
Edit the ALC field to ensure it is an eight digit numeric field.
Create one check file regardless of payee type (employee or vendor).
Combine payment files from multiple ALCs into a single file for transmission to Treasury.
Make CTX payments using a separate file. The transactions need to be balanced.
Schedule and disburse U.S. dollar payments (SF-1166) through the Treasury's ECS
Process payment transactions from other systems, such as payroll and travel.
Automatically generate transactions to reflect disbursement activity initiated by other agencies
Flag vouchers selected for payment that will disburse a fund into a negative cash position.
Process credit memoranda for returned goods or other adjustments.
Apply credits against subsequent disbursements to the same vendor regardless of the funding source.
Allow for the exclusion of payments from agency offset based on user-defined criteria
Provide, generate, and maintain a sequential numbering system for scheduling payments to the disbursing office.
On each payment schedule/file, report totals by TAS/TAFS.
Cancel an entire payment schedule or a single payment within a payment schedule, prior to transmission to Treasury.
Cancel an entire payment schedule prior to actual disbursement by or upon rejection by Treasury.
Value Added Requirements
When consolidating multiple payments to a single payee, include the TAS/TAFS associated with each payment in the payment file.
When combining payment files for multiple ALCs into a single file for transmission to Treasury, provide summary totals by TAS/TAFS.
Provide National Automated Clearing House Association (NACHA) payment formats for Non-Treasury Disbursing Offices.
Split a single payment into separate bank accounts (e.g., benefit payments to recipients).
Provide statistical sampling capabilities to support agency payment certification.
Identify and report payment and deposit amounts at a detail suitable for reporting large dollar notifications
Payment Confirmation and Follow-up Process
Mandatory Requirements
Provide information about each payment to reflect the stage of the scheduling process that the payment has reached
For each payment made by the Core financial system, maintain a history of information
Automatically update the payment information when confirmation is received from the disbursing office
Automatically liquidate the in-transit amount and reclassify budgetary accounts from unpaid to paid
Record more than one check range for a payment schedule, along with a break in check numbers.
Provide on-line access to vendor and payment information.
Provide on-line access to open documents based on agency selection criteria
Reverse disbursement transactions for voided checks or for other payments that have not been negotiated.
Produce IRS-1099s in accordance with IRS regulations and current IRS acceptable format
Electronically download monthly "Fund Balance with Treasury" and activity recorded by Treasury
Value Added Requirements
Include the TAS/TAFS charged and the associated amount(s) in the history of each payment made by the Core financial system.
Provide an automated interface to the Department of Treasury system containing paid schedule data
Provide written notification to payees of payments made by disbursing offices.
Provide e-mail notification to employees of travel payments made by disbursing offices.
Track and report on aged, unmatched vendor invoices.
Track and report on spending agency-wide by state and congressional district.
Receivable Management
Customer Information Maintenance Process
Mandatory Requirements
Maintain customer information to support receivable management processes, including:
Maintain customer account information for audit trail purposes and to support billing, reporting and research activities, including:
Value Added Requirements
Receivable Establishment Process
Mandatory Requirements
Record the establishment of receivables along with the corresponding revenues, expense reductions, or other offsets.
Accept transactions that generate receivables from other systems in a standard format for entry into the Core financial system.
Support the calculation and establishment of accounts receivable based upon billing source, event and time period, and type of claim.
Establish receivables and credit memos from vendors to whom the agency has made duplicate or erroneous payments.
Uniquely identify multiple types of bills and the supporting data used to verify the specific charges.
Automatically establish receivables to be paid under installment plans, including plans for which payments have been rescheduled.
Record billings and collections by line item in order to identify unique accounting classification codes.
Support bills and collections between Federal agencies through the use of electronic systems such as IPAC.
Print bills, accommodating the generation of standard forms,and turnaround documents to be used as a remittance advice.
Date the bills with the system-generated date or with the date supplied by the user.
Consolidate multiple accounts receivable for a customer onto one bill.
Allow transactions related to manually prepared bills to be entered by authorized personnel.
Record adjustments to bills and post to customer accounts.
Generate monthly statements to customers showing account activity.
Value Added Requirements
Debt Management Process
Mandatory Requirements
Maintain data on individual receivables and referenced transactions supporting the receivable.
Maintain accounts for reimbursable orders and identify Government and non-government accounts that are designated as advance funding.
Update each customer account when appropriate events occur.
Automatically calculate interest charges using the appropriate Treasury Late Payment Charge rate and user-defined criteria
Allow the user to specify administrative and penalty amounts and record these amounts
Automatically generate dunning (collection) letters for overdue receivables
Customize the dunning process parameters and dunning letter text.
Provide information on the age of receivables to allow for management and prioritization of collection activities.
Identify and report receivables that meet predetermined criteria for write-off, or referral and generate the appropriate entries.
Automatically calculate and record the allowance for loss on accounts receivable.
Provide information to allow for the automated reporting of delinquent accounts to commercial credit bureaus.
Automatically create files of delinquent accounts for electronic submission
Maintain data for receivables referred to other Federal agencies and outside organizations for collections.
Record the waiver and write-off of receivables, including interest, penalties, and administrative charges.
Track and report on the date and nature of a change in the status of an accounts receivable
Perform on-line queries of account activity (billing, collection, and adjustment) by customer and receivable.
Perform on-line queries of miscellaneous cash receipts by customer, when identified, and by accounting period.
Uniquely record, classify, and report on reimbursable funds
Automatically produce IRS-1099-C's in the amounts of debts forgiven which meet or exceed a user-defined dollar threshold
Value Added Requirements
Collection Process
Mandatory Requirements
Automatically record the application of complete and partial payments made by the debtor
Record revenues, expenditure reductions, or other appropriate offsets associated with collections for which no receivable was previously established.
Apply collections back to the specific contract or purchase order award to reduce cumulative payments and expenditures
Record the receipt of an advance repayment and an advance from others with a reference to the related reimbursable agreement
Process cash or credit card collections. Match collections to the appropriate receivables
Record information associated with a collection at the time funds are applied to an open receivable document
Support the receipt of collection files from banks for application to open receivables.
Record collections received against advance payments made.
Apply collections to more than one receivable.
Re-open closed accounts to record collections after a waiver or write-off of a receivable has been recorded.
Electronically download monthly deposit and debit voucher confirmation information
Support the receipt of payment offset information from Treasury.
Automatically offset payments to vendors for amounts due to the agency
Value Added Requirements
Record TAS/TAFS(s) associated with collections received on deposit tickets and debit vouchers.
When downloading monthly confirmation information include both the TAS/TAFS(s) and the associated amount(s).
Interface with CA$HLINK, in order to reconcile Treasury recorded collections
Cost Management
Cost Setup and Accumulation Process
Mandatory Requirements
Use the agency's accounting classification elements to identify and establish unique cost objects
Allocate and distribute the full cost and revenue of cost objects as defined in SFFAS No. 4.
Allocate and distribute the full cost of goods and services provided by one Federal entity to another.
Track current cost information against prior month and prior-year-to date cost data for selected cost objects
Identify all costs incurred by the agency in support of activities of revolving funds, trust funds, or commercial functions
Accumulate non-financial data relating to cost objects such as output units
Transfer (and trace) cost data directly to and from other cost systems/applications that produce or allocate cost information.
Calculate prices, fees, and user charges for reimbursable agreements and other purposes
Value Added Requirements
Cost Recognition Process
Mandatory Requirements
Use the accrual basis of accounting when recognizing costs and revenue.
Associate with the appropriate cost objects, the reductions of balances such as inventories
Identify and record costs incurred by each cost object, including input of costs from feeder systems
Assign indirect costs on a cause-and-effect basis, or allocate costs through any reasonable and consistent basis
Perform multi-layer overhead distributions that are user-defined using multiple rates
Value Added Requirements
Cost Distribution Process
Mandatory Requirements
Distribute information (such as income statements and status of funds reports) on costs and revenue associated with cost objects.
Provide consistent information on financial, budget, and program matters in different reports.
Use historical information to conduct variance and time-series analyses
Distribute costs to other cost objects regardless of how they were originally assigned.
Provide an audit trail that traces a transaction from its origin to the final cost object(s).
Value Added Requirements
Working Capital and Revolving Fund Process
Mandatory Requirements
Use cost management in revolving funds, including working capital programs.
Allocate working capital and revolving fund costs across organization and program lines
Create and track the funding associated with cost objects and provide funding status
Support the aggregation of project cost and funding information to a higher level
Verify funds availability for orders placed against a specific contract, work-order or agreement
Support funding of revolving fund contracts, work-orders, and projects
Value Added Requirements
Reporting
General Reporting Process
Mandatory Requirements
Produce reports and transmittable files using data maintained by the Core financial management system.
Report on financial activity by any element of accounting classification
Value Added Requirements
Report the financial information required for program management performance reporting.
External Reporting
Mandatory Requirements
Provide data in hard copy and electronic formats required by the Department of the Treasury
Provide data in the electronic formats required by the Department of the Treasury for FACTS I and FACTS II reporting.
Produce a monthly SF-133, Report on Budget Execution and Budgetary Resources, in the formats required by OMB.
Perform the validation edits specified by Treasury to ensure the accuracy of data transmitted for FACTS I and FACTS II reporting
Automate the preparation of consolidated financial statements as required
Value Added Requirements
Internal Reporting
Mandatory Requirements
Produce a report of transaction level details for the TAS/TAFS totals reported on the FMS Form 224
For each TAS/TAFS that is subject to FACTS II reporting requirements, produce a daily on-line Available Funds report(s).
Provide on-line summary trial balances at the internal fund, organization, and TAS/TAFS levels.
Grand totals for TAS/TAFS must be provided for beginning balance, current period activity and ending balance columns.
Support FACTS I and FACTS II reporting and analysis
Grand totals for each TAS/TAFS must be provided for beginning balance, current period activity, and ending balance columns.
Provide an on-line transaction register at the internal fund, organization, and TAS/TAFS level, for each accounting period
Value Added Requirements
Ad Hoc Query
Mandatory Requirements
Provide an integrated data query facility that supports ad hoc query access to agency financial data sources
Allow users to create and submit parameter-based query scripts or to store them in a common library for future use.
Allow users to run queries on-line or in batch mode and to stage output for later access by authorized users.
Allow users to automatically distribute copies of report/query results via e-mail to multiple pre-identified individuals or groups.
Provide run-time controls to limit "run-away" queries and large data download requests.
Support graphical output display on the desktop.
Allow authorized users to download selected financial data.
Provide the ability to preview a report, form, or other query result before printing.
Support access to current year and historical financial data.
Value Added Requirements
Provide ad hoc query interface features
Technical Requirements
General Design/Architecture
Mandatory Requirements
Be modular in design, utilize open-systems architecture, and be upgradeable
Be a commercially available product, subject to regular maintenance based on vendor developed and scheduled software releases.
Include internal transaction processing controls, including the capability in the event of a system failure to automatically
Enforce internal database consistency during all on-line and batch update operations, including distributed databases, if applicable.
Have fully documented restart capabilities for the application's on-line and batch processing components.
Include complete installation, operating, and system maintenance documentation covering:
Include revised documentation concurrent with the distribution of new software releases.
Employ common error-handling routines across functional modules and present error messages that allow the user or system operator to respond to reported problems.
Common error message text must be customizable by the agency.
Generate output information to formats specified by functional requirements.
Be customizable to meet agency specific business/accounting needs using agency supplied application configuration and operating parameters.
Provide fault-free performance in the processing of date and date-related data by all hardware and software products
Value Added Requirements
Include an integrated relational, Structured Query Language compliant database.
Simultaneously process on-line transactions and transactions submitted via system interface.
Infrastructure
Mandatory Requirements
Identify all software and hardware products needed by an agency to install, operate, access, and maintain the application.
Utilize transaction Control Protocol/Internet Protocol communications protocol for application, database, and workstation connectivity.
At a minimum, support application client operation on a 32-bit, Microsoft Windows compatible operating system.
Value Added Requirements
Operate in a mainframe environment (e.g., Multiple Virtual System (MVS), Operating System (OS/) 390).
Operate in a server-computing environment running under UNIX or NT (e.g., Windows Server 2000).
Support application client operation on an Apple Macintosh Windows compatible operating system.
Support application client operation on a UNIX operating system.
Support automated touch-tone telephone access for standardized, commonly requested, inquiries (such as payment status).
Support automated fax-back access for standardized, commonly requested, documents (such as account statements).
Provide the capability to accept bar-coded documents.
Include a report spooling capability to enable on-line viewing, re-printing, and permanent archiving of requested reports.
User Interfaces
Mandatory Requirements
Value Added Requirements
Provide a consistent, Windows-compatible, on-line user interface to all modules and integrated subsystems.
Incorporate common Graphical User Interface characteristics
Incorporate data entry features designed to reduce the amount of direct keying required to initiate transaction processing.
Support desktop integration with other common workstation applications
The application help facility should be customizable by the agency.
Provide an application user interface that complies with the software application standards required by the Rehabilitation Act
Interoperability
Mandatory Requirements
Include an application program interface (API) to accept financial data generated by external applications
Process API submitted transactions using the same business rules, program logic, and edit table entries as are used by the application
Hold API submitted transactions that do not pass required edits in suspense pending appropriate corrective action by the user.
Provide internal controls with the API to ensure the integrity of received and processed transactions.
For the API, generate transaction editing error records in a standard format defined by the vendor for return to the originating feeder application
Value Added Requirements
Support direct EDI translation compliant with American National Standards Institute (ANSI) X-12 standards to enable electronic data exchanges
Interface with the agency electronic communications system to distribute application generated documents and messages
Accept vendor invoices and other external originated transactions over the Internet
Support emerging XML-based specifications for the exchange of financial data
Workflow/Messaging
Mandatory Requirements
Provide an integrated workflow management capability, including generation and routing of internal forms, reports, and other financial documents
Value Added Requirements
Enable authorized users to define workflow processes and business rules, including approval levels, and to modify workflow
Provide the capability to establish multiple levels of document approvals based on user-defined criteria
Provide an internal calendar or user-defined routing tables to generate rule-based or exception reports
Provide the ability to track approval events on-line by transaction, including the time/date and approving party.
Provide the capability to automatically generate electronic routing and status messages to individuals or groups.
Support Workflow Management Coalition (WFMC) standards.
Support Messaging API-Workflow (MAPI-WF) standards.
Support Vendor Independent Messaging (VIM) standards.
Document Management
Mandatory Requirements
Value Added Requirements
Support Document Management Alliance (DMA) standards.
Support Open Document Management Architecture (ODMA) standards.
Support Open Document Architecture/Open Document Interface Format (ODA/ODIF) standards.
Support Portable Document Format standards.
Support Standard Generalized Markup Language (SGML) standards.
Provide the capability to electronically image, index, store, and retrieve document reference material
Notify the user of the presence of associated document images and allow an on-screen display of this material.
Internet Access
Mandatory Requirements
Value Added Requirements
Support secure web browser access to all financial management system modules
Support secure Internet access to the integrated ad hoc data query facility.
Provide the capability to receive public payment collections via the Internet (e.g., Web-based collections via credit card).
Support the use of standard Public Key Infrastructure technology to control access to sensitive data over the Internet.
Security
Mandatory Requirements
Have integrated security features that are configurable by the system administrator to control access
Ensure that the agency's access policies are consistently enforced against all attempts made by users or other integrated system resources
Require the use of unique user identifications and passwords for authentication purposes.
Enable the system administrator to define functional access rights and data access rights by assigned user ID, functional role and owner organization.
Permit the system administrator to assign multiple levels of approval to a single user
Allow the system administrator to restrict access to sensitive data elements such as social security numbers and banking information
Maintain an audit logging capability to record access activity
Provide the ability to query the audit log by type of access, date and time stamp range, user identification, or terminal ID.
Value Added Requirements
Operations and Computing Performance
Mandatory Requirements
Include a process scheduling capability that enables the operator to initiate, monitor, and stop scheduled processes
Provide online status messages indicating job or transaction type and name, when requested processing starts, completes, and system errors.
Allow reports to be produced in the background while other system processing takes place.
Provide the system administrator the ability to control the archiving process.
Retain archived data and system records in accordance with Federal regulations
Provide the ability to selectively retrieve archived data based on user-defined criteria such as date, accounting period, or vendor.
Maintain and report on productivity statistics about application usage.
Provide audit trails to identify changes made to system parameters and tables that would affect the processing or reprocessing of any financial transactions.
Value Added Requirements
Provide computing performance metrics, for platforms and systems environments that the application is certified to run on.
Process an agency's projected accounting activity without impacting projected on-line response time.
Complete routine batch processing within an agency defined batch-processing window.
Maintain the agency's current and historical financial data with no degradation to on-line or batch processing performance.
Support concurrent access to functional modules by the agency's defined user community.
Disclose processing jobs, steps, and dependencies that are required to operate the system on a daily, weekly, monthly, quarterly, and annual basis.
Provide the capability to process batched transactions during online hours and accept online transactions
[Edit footer.html to set your custom footer here]
Current URL: http://compliancemanager.com/ModelStore/ModelPreview?ModelStoreId=bb104529-1fed-46e3-b545-00bde3a96355 Base URL: http://compliancemanager.com/ Current URL Domain Name: compliancemanager.com
Core Financial Systems Management
Clasify Accounting Transactions