DHS · DHS-2467 · record R1847

Purchase Card Worksheet Analysis

Department of Homeland Security · ICE

Overview

Development stage: In development or acquisitionSource: a) Pre-deployment – The use case is in a development or acquisition status.
High-impact designation: Not high-impactSource: c) Not high-impact
Impact justification: Not reported
Start date: Not reported
Withheld from public reporting: Not reported

Mission

Topic area: Procurement and Financial Management
Operational functions: No function tag matched Derived by keyword rules; see methodology

Problem the AI is intended to solve

The AI is intended to solve the problem of reviewers having to manually check each purchase card line item against numerous laws, policies, and contract terms, which is time‑consuming and increases the risk of missed compliance issues.

Expected benefits

The AI module is expected to help accelerate compliance checks, streamline processes, and assist in identifying potential risks, while continuously improving through a human-in-the-loop feedback system. This integration is intended to help procurement actions better align with relevant legal and policy requirements.

System outputs

The outputs of the AI module will include a compliance status for each purchase line item (compliant or non-compliant) and detailed reasoning with citations to the specific policies or legal documents used in the evaluation. The Automated Purchase Card Approval System will use these AI-generated compliance statuses and explanations to help route items and flag potential issues within the approval workflow. AI outputs do not themselves approve or deny purchases. Compliant items may proceed through the workflow consistent with existing business rules, while non-compliant items will be flagged for human review. Human reviewers can access detailed reasoning for non-compliant determinations and may choose to correct requests, raise exceptions, or flag inaccuracies.

Technology

AI classification: Generative AISource: Generative AI: AI that generates new or synthetic content (e.g., images, videos, audio, text, code).
System name(s): Not reported
Custom-developed code: Not reported
Public source code: Not reported

Sourcing

How it was built: Not reported
Vendor (as reported): Not reported
Vendors (standardized): None on the standard list

A vendor is the supplier named by the agency. It does not identify the underlying model or AI technology.

Data and privacy

Involves PII: Not reported
Privacy Impact Assessment: Not reported
Authorization to Operate: Not reported
Demographic features: Not reported
Training and evaluation data: Not reported
Federal Data Catalog: Not reported

Governance

0 of 8 minimum-practice questions answered. A blank answer means the agency reported nothing; it does not mean the practice is absent.

Pre-deployment testingNo answer reported

AI impact assessmentNo answer reported

Independent reviewNo answer reported

Ongoing monitoringNo answer reported

Operator trainingNo answer reported

Fail-safeNo answer reported

Appeal processNo answer reported

User and public consultationNo answer reported

Potential impacts and how they were identified

Not reported