DRAFT - GL Feeder System Requirements

Item
The feeder system creates files in the KFS file format, and uploads the file to the KFS SFTP server.
Transactions posted to the ledger are summarized at the appropriate level. Example: if a department is being recharged for buying 10 computers, one ledger entry is created for the total cost of 10 computers, instead of 10 ledger entries for one computer.
The feeder system inputs, outputs, stores, and displays all KFS accounting attributes. The feeder system will collect these attributes in a data model compatible with the KFS data model for these attributes. Note: "required" on the aforementioned web page refers to whether that attribute is required in every transaction. The feeder system must support all attributes, required or not.
The feeder system uses KFS web services to validate accounting attribute information during data entry and immediately before ledger file creation. Individual accounting attribute fields must be validated (e.g. verify account code exists and has right size/format), and combinations of accounting attribute fields must be validated (e.g. verify that object code can be used with account).
The feeder system allows for a drill-down capability to view the justification for the ledger charges. KFS can generate a hyperlink to a feeder system to view the justification for the ledger entry.
The feeder system is able to generate entries to reverse charges sent to the ledger.
The feeder system is able to perform split funding.