10 U.S.C. § 4601 — Electronic submission and processing of claims for contract payments
submitted 26 years ago by Pub. L. 106-398 to r/title-10-ARMED-FORCES · 309 words · no verdicts yet
(a) The Secretary of Defense must require every claim for payment under a Department of Defense contract to be submitted electronically. (b) A Defense Department contracting officer, contract administrator, certifying official, or other employee who receives such an electronic claim and must send it to another Defense Department official for processing must send the claim and all additional documents needed to decide and pay it electronically. (c) If the Secretary finds electronic submission or transmission too burdensome for a category of cases, the Secretary may exempt that category.
(a) The Secretary of Defense must require every claim for payment under a Department of Defense contract to be submitted electronically.
(b) A Defense Department contracting officer*, contract administrator, certifying official, or other employee who receives such an electronic claim and must send it to another Defense Department official for processing must send the claim and all additional documents needed to decide and pay* it electronically.
(c) If the Secretary finds electronic submission or transmission too burdensome for a category of cases, the Secretary may exempt that category.
(d) The Secretary must provide (1) electronic-claim policies, requirements, and procedures, including for supporting receiving reports, contracts and changes, and certifications; (2) the format accepted by the Defense Finance and Accounting Service corporate database; and (3) contract requirements for contractors’ electronic claims.
(e) “Claim for payment” means an invoice or any other demand or request for payment.
The Secretary of Defense shall require that any claim for payment under a Department of Defense contract shall be submitted to the Department of Defense in electronic form.
A contracting officer*, contract administrator, certifying official, or other officer or employee of the Department of Defense who receives a claim for payment in electronic form in accordance with subsection (a) and is required to transmit the claim to any other officer or employee of the Department of Defense for processing under procedures of the department shall transmit the claim and any additional documentation necessary to support the determination and payment of the claim to such other officer or employee electronically.
If the Secretary of Defense determines that the requirement for using electronic means for submitting claims under subsection (a), or for transmitting claims and supporting documentation under subsection (b), is unduly burdensome in any category of cases, the Secretary may exempt the cases in that category from the application of the requirement.
In implementing subsections (a) and (b), the Secretary of Defense shall provide for the following:
Policies, requirements, and procedures for using electronic means for the submission of claims for payment to the Department of Defense and for the transmission, between Department of Defense officials, of claims for payment received in electronic form, together with supporting documentation (such as receiving reports, contracts and contract modifications, and required certifications).
The format in which information can be accepted by the corporate database of the Defense Finance and Accounting Service.
The requirements to be included in contracts regarding the electronic submission of claims for payment by contractors.
In this section, the term “claim for payment” means an invoice or any other demand or request for payment.
Source credit: (Added Pub. L. 106–398, § 1 [[div. A], title X, § 1008(a)(1)], Oct. 30, 2000, 114 Stat. 1654, 1654A–249, § 2227; renumbered § 4601, Pub. L. 116–283, div. A, title XVIII, § 1861(b), Jan. 1, 2021, 134 Stat. 4277.)
- 2000Enacted · Pub. L. 106-398 · 114 Stat. 1654, 1654
- 2021Amended · Pub. L. 116-283 · 134 Stat. 4277
A history note hasn’t been published yet. The record shows enactment by Pub. L. 106-398 on 2000-10-30.
all 0 arguments · sorted by: best
no arguments yet — make the first case