FAMIS-GF and FAMIS-WCF blueprint for legacy accounting and reporting

FAMIS / Financial Accounting Management Information System Blueprint

Explore FAMIS as a legacy/core accounting family with FAMIS-GF for general fund budget execution and FAMIS-WCF for working capital fund cost recovery, customer orders, AP/AR/GL, Treasury reconciliation, DDRS/GTAS reporting, and source-to-statement audit support.

4

Core FAMIS lineage scenarios

GF / WCF -> GL -> GTAS -> Statement

System profile

What it is, who uses it, and why it matters

What it is

FAMIS is modeled as the Financial Accounting Management Information System family, with FAMIS-GF for general fund accounting and FAMIS-WCF for working capital fund accounting, cost recovery, billing, and reporting support.

Who uses it

Legacy accounting users, budget execution users, WCF business offices, resource managers, AP/AR and close teams, DFAS or shared-service partners, Treasury/reporting teams, and auditors may rely on FAMIS data or outputs.

How it is used

It supports fund cite validation, commitments, obligations, expenditures, AP, AR, GL, WCF customer orders, billing, collections, cost recovery, inventory/cost support, suspense, JVs, trial balance, DDRS/GTAS, and statement schedules.

Current status

Modeled as a legacy/core accounting family. Public FAMIS-GF/WCF technical documentation is thin, so exact platform, interface inventory, owners, and modernization or archival status require authoritative documentation.

Why it is used

It preserves budget-to-reporting lineage for general fund execution and working-capital operations, helping users reconcile source transactions, GL balances, Treasury reporting, and audit evidence.

Modeled feeder systems7

The blueprint models 7 FAMIS source/partner categories; authoritative interface counts require agency/DFAS records.

GF Funding / LOA InputsWCF Customer Orders / OperationsProcure-to-Pay SourcesPayroll / Labor / TravelTreasury / Disbursing / IPACInventory / Cost SourcesManual JV / Suspense Inputs

Clickable architecture map

End-to-end flow: business event to financial statement

Cards in the selected FAMIS scenario path are highlighted. Click any card to inspect fields, T-codes, audit questions, and risks.

Source

Source / Interface Events

Funding, procurement, payroll, travel, logistics, WCF operating, disbursing, Treasury, and intragovernmental events that drive FAMIS accounting.

FAMIS

FAMIS-GF / FAMIS-WCF Processing

General Fund and Working Capital Fund accounting, budgeting, cost recovery, AP, AR, GL, suspense, and close processing.

Detail

Transaction Detail

Fund cite, order, obligation, invoice, payment, customer order, billing, collection, inventory/cost, JV, and suspense detail.

Accounting

Accounting and Control Layer

Budgetary GL, proprietary GL, WCF cost/revenue, AP/AR, FBWT, trial-balance, Treasury, and reconciliation controls.

Reporting

Execution and External Reporting

Status of funds, WCF operating reports, trial balance, DDRS, GTAS, Treasury, audit extracts, and management reporting.

Statements

Financial Statement Support

SBR, net cost, WCF inventory/revenue/cost recovery, FBWT, AP/AR, ULO, suspense, notes, and audit assertions.

Scenario lineage explorer

FAMIS-GF Funding to Obligation and SBR

Traces general fund authority through budget execution, obligation detail, budgetary accounting, trial balance, and SBR support.

->
->
->
->
->

Business flow

  1. General fund authority, allotment, and LOA data establish available resources.
  2. FAMIS-GF records commitments, obligations, expenditures, outlays, and status-of-funds updates.
  3. Fund cite and obligation detail preserve the transaction population and open-balance history.
  4. Budgetary accounting classifies authority, obligations, delivered orders, expenditures, and outlays.
  5. SBR support traces reported budgetary resources and ULO balances back to source detail.

AI / audit exception tests

  • invalid LOA
  • obligation exceeds authority
  • stale ULO
  • outlay not tied to disbursing
  • SBR amount lacks detail

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

FAMIS-GF Controls

Budget authority, LOA validation, availability, commitments, obligations, deobligations, ULO review, expenditures, outlays, and SBR support.

FAMIS-WCF Controls

Customer orders, rates, inventory/service delivery, cost allocation, billing, AR, revenue, collections, operating results, and WCF statement support.

AP / AR / GL Close

Invoice, receipt, acceptance, AP, AR, expense, revenue, accrual, reversal, GL journal, close package, and subledger reconciliation controls.

Treasury and IGT Reconciliation

FBWT, TAS/BETC, IPAC, G-Invoicing, trading partner, disbursing, collections, GTAS, and Treasury difference research.

Suspense and JV Governance

Reject queues, unmatched items, suspense aging, manual adjustment support, approvals, reversals, clearing evidence, and root-cause tracking.

Audit Evidence

Universe of Transactions extracts, source documents, customer orders, invoices, payments, billing, collections, reconciliations, trial balances, and statement schedules.