MOCAS is modeled as the Mechanization of Contract Administration Services, a legacy DoD contract administration and payment-support environment for administered contracts and complex payment activity.
MOCAS blueprint for administered contracts and contract-payment lineage
MOCAS / Mechanization of Contract Administration Services Blueprint
Explore MOCAS as a legacy contract administration and payment-support environment, connecting contract award, DCMA administration, WAWF invoice/acceptance, contract financing, DFAS payment, ERP accounting, Treasury reporting, FBWT, ULOs, and contract audit support.
3
Core MOCAS lineage scenarios
Award -> Admin -> Pay -> OutlaySystem profile
What it is, who uses it, and why it matters
DCMA contract administration personnel, DFAS payment offices, contracting and acquisition stakeholders, component ERP/accounting teams, vendors, program offices, and auditors rely on MOCAS-related contract/payment records.
It supports contract-payment administration, line/funding detail, invoice and acceptance linkage, progress or financing payments, liquidation, DFAS payment, accounting feeds, reconciliation, and contract-file audit traceability.
Legacy/operationally sensitive public detail is limited; this page models the business process accurately but does not claim a certified current platform or interface inventory.
Administered defense contracts require a controlled trail from award and funding to delivery, invoice, acceptance, payment, obligation liquidation, Treasury outlay, and audit evidence.
The blueprint models 7 MOCAS feeder/partner categories; authoritative counts require DCMA/DFAS system documentation.
Contract Award / Modification SourcesComponent ERP Obligation RecordsPIEE / WAWF Invoice and AcceptanceDCMA Contract AdministrationDFAS Payment / DisbursingCARS / Treasury ReportingContract Reporting / Audit Support
Clickable architecture map
End-to-end flow: business event to financial statement
Cards in the selected MOCAS scenario path are highlighted. Click any card to inspect fields, T-codes, audit questions, and risks.
Source
Contract, Funding, and Acceptance Sources
Contract awards, modifications, funding lines, DCMA administration, receipt/acceptance, invoices, and ERP obligation records.
Core
MOCAS and Contract Administration Capabilities
MOCAS legacy contract administration/payment support, DCMA administration controls, DFAS payment, and contract financing support.
Detail
Contract Payment Detail
PIID, CLIN, ACRN, invoice, receiving, acceptance, progress payment, liquidation, financing, and voucher detail.
Accounting
Accounting and Control Layer
Funds control, obligation/liquidation accounting, AP, expense, outlay, payment certification, and contract reconciliation.
Reporting
Treasury, ERP, and Contract Reporting
DFAS payment outputs, accounting feeds, Treasury/CARS, contract administration reports, and close/audit outputs.
Statements
Contract Liability, Outlay, and Audit Outputs
Obligation and ULO support, advances/contract financing, expenses, outlays, FBWT, and contract-file audit packages.
Scenario lineage explorer
Contract Award to Invoice, MOCAS/DFAS Payment, and Outlay
Traces an administered contract payment from award/funding through WAWF evidence, MOCAS, DFAS payment, ERP accounting, Treasury reporting, and outlay support.
->
->
->
->
->
->
->
Business flow
- Award, modification, funding, and ERP obligation records establish the contract payment baseline.
- PIEE/WAWF evidence provides invoice, receiving, and acceptance support.
- MOCAS contract/payment detail supports the payment record for administered contracts.
- DFAS executes the certified payment and accounting feeds liquidate the obligation and record outlay.
- Treasury/CARS and statement support tie the payment to FBWT, SBR, and audit evidence.
AI / audit exception tests
- payment without acceptance
- award/mod not reflected in ERP
- MOCAS/DFAS mismatch
- wrong obligation liquidated
- outlay unsupported
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
Contract Administration
Award/modification support, DCMA administration evidence, delivery/performance surveillance, and contract payment status.
Invoice and Acceptance Control
PIEE/WAWF invoice, receipt, acceptance, three-way match, duplicate prevention, and payment certification support.
MOCAS Payment Support
Legacy contract payment detail, PIID/CLIN/ACRN, progress payment, financing, liquidation, voucher support, and balance tracking.
DFAS Payment and Disbursing
Certified voucher, disbursement, payment status, accounting interface, Treasury classification, and cash/outlay reporting.
Contract Reconciliation
Award, MOCAS, WAWF, DFAS, ERP, Treasury, ULO, contract financing, and exception/difference reconciliation.
Audit Evidence
Contract file, funding, modifications, invoices, acceptance, payments, accounting postings, CARS/FBWT, and statement-support packages.