#G INVOICING MIPR MAC#

#G INVOICING MIPR MAC#

Management support directly related to supporting customer-funded efforts (IAC MAC Task Orders and Specialized Task Orders). This percentage amount is paid to DTIC to cover the costs of processing customer orders. This is a percentage of the amount of funding that will be placed on contract. This is the amount of funding that will be placed on contract and used by the contractor to perform the tasks in the performance work statement. IAC MAC Task Order or BCO Task Order funding.MIPRs submitted to DTIC should contain two line items in section 7b: CSDC is the additional amount paid by customers for MIPR processing and accounting support, contracting office support, and program. The customer shared direct cost (CSDC) is not a fee paid to DTIC.

At no time should it be expected that the CSDC is 0% for the life of the project. DTIC’s CSDC is assessed each year by the IAC Reimbursable Review Board in consultation with general counsel and the OUSD comptroller and will be adjusted annually as such, the CSDC rate may fluctuate during the course of the delivery order. The FY 2023 Provisional customer shared direct cost (CSDC) rate is 1.00%.

A transaction broker may be used to reduce the number of interfaces, thereby reducing the cost to maintain the interfaces and minimizing the number of interfaces subject to changes in interface controls to support auditability. A transaction broker and translation service may be used for legacy systems with a retirement plan and date to translate non-SFIS data elements to SFIS data elements. Supporting transactions are required to be posted to the target accounting system using proper USSGL accounts and accounting standards. Systems that support the financial management purchasing process such as contracts, intergovernmental orders, and payroll for audit readiness purposes must be interoperable with SLOA/Accounting Classification data elements.For legacy accounting systems and legacy financial business feeder systems that have a retirement plan and date, the implementation of SFIS and SLOA/Accounting Classification is considered on a case-by-case basis depending upon its impact on audit readiness.Ġ40303.Further, systems must meet all applicable SFIS Business Rules. Target systems must send, receive, capture, store, and maintain the SLOA/Accounting Classification data constructed as discrete data. This includes, but is not limited to, accounting, contract writing, logistics, civilian pay, military pay, travel, medical, and transportation. The SLOA/Accounting Classification requirement is applicable for all systems that process business events with accounting impacts between the time of commitment through disbursement. The DoD SLOA/Accounting Classification is a subset of SFIS data elements that is used to ensure accurate accounting transactions and interoperability between systems.DoD Component program managers are required to use the SFIS checklist to determine SFIS compliance and to guide implementation and configuration efforts.

SFIS data element transactions are required to be posted to the financial accounting system using the required USSGL accounts and accounting standards.

SFIS compliance means a target system must send, receive, capture, store, and maintain the SFIS data constructed as discrete data.

SFIS provides an enterprise-wide standard for categorizing financial information along several dimensions to support financial management and financial reporting functions enable decision-makers to efficiently compare similar programs and activities across DoD and provide a level of detail required for information retrieval and auditability. SFIS is also considered for legacy accounting systems and legacy financial business feeder systems on a case-by-case basis.

SFIS compliance is required for all target accounting systems and target financial business feeder systems that comprise the target environment, as identified in the Enterprise Transition Plan, that support financial transactions.

G invoicing mipr