ABSS is modeled as the Air Force Automated Business Services System, a business-services/request workflow surface for requirements, approvals, funding support, and procurement handoff.
ABSS blueprint for Air Force business services and request-to-procurement workflow
ABSS / Automated Business Services System Blueprint
Explore ABSS as an Air Force business-services workflow surface for requirements, funding validation, approval routing, purchase-request or GPC handoff, contracting evidence, receipt/acceptance, AP/accrual support, reporting, and audit traceability.
4
Core ABSS lineage scenarios
Request -> Approve -> Handoff -> AccountSystem profile
What it is, who uses it, and why it matters
Air Force requirement owners, resource advisors, budget/funds certifiers, contracting support users, GPC participants, approving officials, finance/reporting teams, and auditors may rely on ABSS records.
It captures requirement packages, routes funding and approval reviews, supports PR/MIPR/GPC or contracting handoff, tracks status/evidence, and connects request activity to accounting and audit support.
Public ABSS implementation details are limited; this page models the business process and marks exact platform, interfaces, and current operational footprint as requiring Air Force authority.
It gives Air Force organizations a controlled request-to-procurement trail so mission needs, funding, approvals, award support, receipt, payment, and audit evidence can be connected.
The blueprint models 5 ABSS feeder/source categories; authoritative interface counts require Air Force ABSS documentation.
Requirement Owner InputsFunding / LOA SourceContracting / Market InputsPIEE / WAWFGPC / Bank / Micro-Purchase
Clickable architecture map
End-to-end flow: business event to financial statement
Cards in the selected ABSS scenario path are highlighted. Click any card to inspect fields, T-codes, audit questions, and risks.
Source
Source / Requirement Inputs
Air Force requirement owners, funding officials, contracting inputs, vendor/payment evidence, card activity, and source documents that initiate business-service requests.
ABSS
ABSS Workflow / Business Services
Automated Business Services System workflow for request intake, funding validation, package routing, approval status, procurement handoff, and audit evidence.
Detail
Procurement / Request Detail
Requirement package, purchase request, MIPR, GPC, award, receipt, acceptance, invoice, ULO, deobligation, and closeout detail.
Accounting
Accounting Layer
Commitment, obligation, expense, accrual, AP, payment, GL, budgetary USSGL, proprietary USSGL, and close accounting, typically downstream in DEAMS or related accounting environments.
Reporting
Reporting / Treasury Layer
ABSS status reports, acquisition metrics, DEAMS/GL reporting, DDRS, GTAS, Treasury/CARS/FBwT, IPAC/G-Invoicing, and audit extracts.
Statements
Financial Statement Support
SBR, Net Cost, Balance Sheet/AP, ULO, obligation aging, accrual, note schedule, and audit support tied back to request and award evidence.
Scenario lineage explorer
ABSS Services Requirement to Award Path
Shows how an Air Force service requirement moves from mission owner package through ABSS funding, approval, procurement handoff, award, accounting, and statement support.
->
->
->
->
->
->
->
Business flow
- A mission owner builds the requirement package and submits it into ABSS.
- ABSS captures category, estimate, attachments, priority, organization, and routing needs.
- Resource management validates LOA, funds availability, purpose, amount, and certification.
- Required reviewers approve, reject, or return the package for correction.
- The approved request is handed off to PR, MIPR, GPC, or contracting execution.
- Award and obligation activity is reconciled back to the ABSS request and supports SBR reporting.
AI / audit exception tests
- request package incomplete
- funding not certified
- approval skipped
- handoff loses request ID
- award amount differs from certified funding
Audit lens
Where the AI UoT analyzer should watch
These are the places where completeness, accuracy, timeliness, and traceability commonly break.
Completeness
Source events missing from the ERP, subledger items not posted to GL, or financial statement balances without supporting populations.
Traceability
Broken reference keys across feeder, interface, subledger object, GL document, trial balance, and statement line item.
Timing
Authorization, receipt, invoice, voucher, payment, and GL posting dates crossing accounting periods without appropriate accrual or adjustment.
Supportability
Transactions posted to GL without valid approval, contract, receipt, invoice, voucher, asset record, or other audit evidence.
Enterprise infrastructure
Support services that make the blueprint work
Workflow Governance
Request intake, package checklist, status trail, reviewer sequence, role authorization, comments, attachments, and closeout evidence.
Funding Controls
LOA validation, funds certification, commitment support, fiscal-year controls, funding revisions, amount reconciliation, and deobligation tracking.
Contracting Integration
PR, MIPR, GPC, SPS/contract writing, award, modification, PIID, CLIN, vendor, and contracting-officer decision evidence.
Receipt & Payment Evidence
PIEE/WAWF invoice, receipt, acceptance, COR review, bank/card statements, AP, accrual, payment, and clearing support.
Reporting & Audit
ABSS status reports, approval aging, open request populations, source-to-award reconciliation, DEAMS tie-outs, ULO review, and audit extracts.
Data Governance
Request ID, organization, fund cite, vendor, PIID, CLIN, invoice, obligation, TAS, USSGL, period, amount, status, and evidence retention rules.