Beyond FIAR: A Case Study in Enterprise Knowledge Engineering
Executive Summary
Every organization depends on its ability to demonstrate that work was performed correctly. In financial management, that evidence supports an audit. In maintenance, it supports airworthiness. In engineering, it supports configuration control. In cybersecurity, it supports compliance. Although the mission differs, the underlying challenge is remarkably consistent: organizations must transform operational activity into trusted evidence.
This paper examines that challenge through the Air Force’s L19 (Material Balance Sheet/Inventory Reconciliation Report), while building on ACC3’s earlier work in Enterprise Knowledge Engineering and Maintenance, Repair, and Overhaul (MRO) modernization. The L19 illustrates a challenge shared across the Department of Defense: although each Military Department employs different enterprise resource planning systems, reporting artifacts, and business processes, all must demonstrate inventory accountability, financial reconciliation, and sufficient audit evidence in accordance with Department-wide policy (DoDM 4140.01; DoD 7000.14-R). It is used here not as a universal DoD artifact, but as a representative example of a much broader challenge.
While the Department has invested heavily in modernizing business systems and improving audit readiness, independent assessments continue to identify inventory valuation, supporting documentation, and final reconciliation as consistent challenges in sustaining auditability (Department of Defense, 2024a; Government Accountability Office [GAO], 2023b).
The objective is not to automate auditing — it is to ensure auditors spend less time assembling evidence and more time evaluating it. Together with those earlier papers, this case study demonstrates a repeatable methodology for preserving institutional knowledge and transforming complex operational workflows into governed, evidence-driven capabilities.
This Paper in Context
This paper is the third in a series examining how organizations preserve operational knowledge and transform it into repeatable capability. The first paper, Enterprise Knowledge Engineering, introduced the methodology for capturing institutional knowledge before it is lost. The second applied that methodology to aircraft Maintenance, Repair, and Overhaul (MRO), demonstrating how decades of depot expertise can be transformed into governed operational workflows. This paper extends the same approach to Financial Improvement and Audit Remediation (FIAR), using the Air Force’s L19 reconciliation process as a representative case study. Together, the three papers demonstrate that the methodology is not specific to maintenance or financial management — it applies wherever organizations depend on experienced professionals to consistently transform operational activity into trusted evidence.
Every Audit Begins the Same Way
The work begins with a simple question:
Does this transaction accurately represent what happened?
Answering this question requires considerably more than comparing values between two reports. The auditor must determine if the inventory exists, if it is valued correctly, if the adjustment complies with applicable policy, and whether sufficient evidence exists to support the financial record. Historical reports are reviewed, regulations consulted, and supporting documentation gathered before a conclusion can be reached.
Supply planners, leads, contract monitors, and others capture and review this data daily — the challenge is not a lack of information. Operational systems already maintain the inventory records, financial transactions, maintenance history, and supporting documentation required to demonstrate accountability; organizations must simply assemble them into evidence that supports an audit conclusion (DoDM 4140.01; AFMAN 23-122).
Financial Improvement and Audit Remediation (FIAR) drives substantial progress toward strengthening financial accountability across the Department (Department of Defense, 2024c). Inventory valuation and financial reconciliation remain among the most technically demanding aspects of DoD financial reporting: they require organizations to demonstrate the existence, completeness, valuation, rights, and obligations associated with inventory while maintaining evidential support sufficient for independent audit (Federal Accounting Standards Advisory Board [FASAB], 2023; GAO, 2023a; Department of Defense, 2024a) — and they depend on experienced professionals who understand how operational events become financial evidence.
This dependency raises an important question. If experienced auditors spend much of their time assembling evidence before they can apply professional judgment, can that preparation be performed more consistently and repeatably?
To answer this question, it is helpful to first understand how an inventory transaction becomes an audit opinion or finding.
Following an L19
The L19 is often viewed as another inventory report, a snapshot in time taken at the end of the month. In reality, it is the point where operational activity intersects with financial accountability. The L19 is the financial record that holds inventory balances by National Item Identification Number (NIIN), the Condition Code (CC), and the DoDAAC where the items are located, supporting reconciliation between operational inventory activity and financial reporting (AFMAN 23-122). Every line on an L19 reflects a summation of business events that must ultimately withstand independent scrutiny.
Consider a pricing variance found during routine audit activity. The investigation rarely begins with the question, "Is the number correct?" Instead, the auditor asks, "What happened?"
The answer requires reconstructing the operational history behind the variance. Was the price change due to an inventory transfer, repair, revaluation or did the acquisition cost change? Was the adjustment the result of normal business activity or a process that requires additional investigation? Does supporting documentation exist, and does the resulting valuation comply with Department policy?
The auditor's workflow itself is remarkably consistent. The auditor identifies the affected inventory item, retrieves historical records, compares current values against earlier reporting periods, reviews applicable business rules, and assembles the evidence needed to support a conclusion. Only then can the auditor’s professional judgment be applied.
On paper, the process appears straightforward; in practice, the information needed to answer these questions often resides across multiple systems, reports, and locally maintained files. Much of an auditor’s time is therefore spent requesting additional information and assembling evidence rather than evaluating it.
This distinction reveals the true bottleneck in the audit process: the challenge is not understanding what a variance means once evidence has been collected, but collecting and organizing that evidence quickly enough to support consistent decision-making across thousands of transactions.
Figure 1. Two Approaches to Audit Conclusion. The side-by-side workflow contrasts today’s reconciliation-driven process with a continuous analysis model. The destination — professional judgment and the audit conclusion — remains the same; what changes is the manual effort required to reach it.
The rest of this paper examines how organizations can shift from assembling evidence after operational events occur to continuously producing it as part of normal business operations. That shift is more than a technology improvement — it changes how audit work is performed, letting experienced auditors focus on interpreting evidence rather than searching for it.
Where the Process Slows
The workflow illustrated in Figure 1 highlights an important distinction: every audit reaches the same destination — a professional judgment supported by sufficient evidence — but the difference lies in how that evidence is assembled.
In the traditional process, the majority of an auditor's effort occurs before the actual analysis begins. Time is spent acquiring historical reports, comparing inventory positions across reporting periods, identifying any additional supporting documentation, interpreting regulations, and deciding which records are authoritative. Only after that work is complete can the auditor evaluate whether a variance represents routine business activity or a condition requiring corrective action.
None of these activities are unnecessary — they are essential to a defensible audit conclusion. The core issue is redundancy: auditors continually reapply the same techniques, business rules, and regulation review to each variance, which inflates review time exponentially.
Consider a typical pricing variance. Before deciding whether additional action is required, an auditor may need to find whether the item has experienced similar changes previously, the adjustment aligns with the approved valuation method, supporting documentation exists, and if the variance exceeds established materiality thresholds. Each question contributes to the auditor’s conclusion, but answering these questions often requires navigating multiple systems and assembling information that already exists somewhere within the enterprise.
This is where the process begins to slow.
Experienced auditors are efficient because they know where information resides and which questions to ask first. They recognize familiar patterns, understand how inventory movements affect financial reporting, and move through investigations that would take considerably longer for someone with less experience. That expertise exposes one of the Department’s greatest modernization challenges.
Organizations have invested substantially in enterprise resource planning systems, data integration, and financial management modernization — yet GAO and DoD Inspector General reports continue to identify weaknesses in internal controls, documentation, and evidence, showing that improved access to information alone does not eliminate the manual effort required to produce audit-ready evidence (GAO, 2023b; DoD OIG, 2024). As experienced members of the federal workforce retire, organizations also face the challenge of preserving institutional knowledge historically transferred through experience rather than documented as repeatable process (Office of Personnel Management, 2024).
This observation reframes the modernization challenge. The primary issue is not access to data. Most organizations already have the information needed to complete an investigation. The challenge is organizing that information into meaningful evidence before a professional judgment can be applied.
Traditional modernization efforts often address this problem by improving visibility — new dashboards, more accessible reports, integrated data sources. Those improvements are valuable, but visibility alone does not explain a pricing variance, prove regulatory compliance, or decide whether more investigation is warranted. Information must still be interpreted, evidence gathered, and business rules applied before an auditor can reach an opinion.
The opportunity, therefore, is not simply to make information easier to find. It is to reduce the amount of manual effort needed before an experienced auditor can begin doing the work that only an experienced auditor can do. This distinction represents the difference between a reporting system and an audit intelligence capability. A reporting system presents information. An audit intelligence capability begins transforming that information into evidence before the investigation ever starts.
The next section examines how that transition changes the role of both the software and the auditor, shifting repetitive investigative work into governed processes while preserving the professional judgment that is still central to every audit conclusion.
The Broader Opportunity
If the greatest amount of effort in today's audit process is spent preparing the investigation, the next logical question is straightforward:
What if that preparation had already been completed?
That question marks the difference between a traditional reporting system and an audit intelligence capability.
Most enterprise systems are designed to answer a fundamental question: What happened? They record transactions, maintain inventory balances, and provide the reports that let auditors begin an investigation. These systems establish an official record of operational activity, but they were never intended to perform the investigative work needed to explain it — that responsibility still belongs to the auditor.
The auditor gathers historical information, compares reporting periods, applies business rules, evaluates supporting documentation against regulations and guidance, and determines whether the available evidence supports the financial record. These activities require experience, but not every step requires judgment — many are performed the same way regardless of the transaction under review. This is where audit intelligence changes the workflow.
Rather than waiting for an investigation to begin, an audit intelligence capability continuously evaluates operational activity as new transactions occur. Historical records are correlated automatically. Pricing changes are compared against established business rules. Materiality thresholds are evaluated consistently. Supporting documentation is associated with the transaction, and significant variances are identified long before an auditor opens the case. The objective is to ensure that, when professional judgment is required, the supporting evidence has already been assembled.
Returning to the L19 example: under a traditional workflow, an auditor receives the report and begins gathering information needed to understand the variance. Under an audit intelligence workflow, much of that preparation has already occurred — historical pricing retrieved, previous adjustments identified, business rules evaluated, and supporting records linked to the transaction. The auditor starts with context instead of data collection.
This seemingly minor change has significant operational implications.
Investigations become more consistent because the same business rules apply every time, and supervisors gain confidence that similar transactions receive similar treatment regardless of who performs the review. New auditors become productive faster because governed workflows reinforce the investigative process rather than relying solely on institutional memory. Most importantly, experienced auditors spend more time exercising judgment and less time on repetitive research. This is not a replacement for the auditor — in many respects, it is the opposite.
The value of an experienced auditor has never been the ability to locate reports or compare spreadsheets. The value lies in interpreting evidence, recognizing operational context, resolving ambiguity, and making decisions that affect financial accountability. Those responsibilities remain firmly in human hands. Audit intelligence simply reduces the repetitive work required before their responsibilities can begin.
The distinction is subtle but important. Reporting systems document operational history. Audit intelligence prepares operational history for human evaluation.
This same pattern held true earlier, when ACC3 applied Enterprise Knowledge Engineering to aircraft Maintenance, Repair, and Overhaul. Although the operational domains differ, the L19 effort and the MRO modernization effort followed the same sequence:
-
Understand the work
-
Capture institutional knowledge
-
Engineer repeatable business rules
-
Implement governed workflows
-
Continuously generate evidence
This repeatable pattern is the foundation of Enterprise Knowledge Engineering. Whether the objective is maintaining aircraft, reconciling inventory, demonstrating cybersecurity compliance, or managing complex engineering programs, organizations face the same fundamental challenge: preserving expertise while producing trustworthy evidence.
Figure 2. The Repeatable Methodology. Enterprise Knowledge Engineering captures institutional knowledge from parallel programs — MRO Modernization and FIAR/L19 — and converts it into a Repeatable Operational Capability applied across Engineering, Logistics, Cyber, Finance, Acquisition, Quality, and Manufacturing.
The L19 capability described here is not the destination — it is evidence: evidence that complex operational expertise can be preserved before it is lost, that governed workflows can replace inconsistent manual processes, and that trusted audit artifacts can be generated continuously rather than reconstructed after the fact. Most importantly, it demonstrates that the methodology introduced in Enterprise Knowledge Engineering, and validated through MRO modernization, applies equally well to financial management. Taken together, these three papers describe more than individual solutions: a repeatable modernization discipline that enables organizations to preserve expertise, strengthen operational consistency, and continuously generate the evidence required to support mission success.
References
Department of Defense. (2023). Department of Defense financial management regulation (DoD 7000.14-R). U.S. Department of Defense.
Department of Defense. (2024a). Department of Defense agency financial report: Fiscal year 2024. U.S. Department of Defense.
Department of Defense. (2024b). DoD Manual 4140.01, Volume 4: Supply chain materiel management procedures. U.S. Department of Defense.
Department of Defense. (2024c). Financial Improvement and Audit Remediation (FIAR) guidance. Office of the Under Secretary of Defense (Comptroller).
Department of the Air Force. (n.d.). AFMAN 23-122, Materiel management procedures (Current ed.). Department of the Air Force.
Federal Accounting Standards Advisory Board. (2023). Statement of Federal Financial Accounting Standards (SFFAS) No. 3: Accounting for inventory and related property.
Government Accountability Office. (2023a). DOD financial management: Efforts to address auditability and systems challenges need to continue (GAO-23-106941). U.S. Government Accountability Office.
Government Accountability Office. (2023b). High-risk series: Efforts made to achieve progress need to be maintained and expanded to fully address all areas (GAO-23-106203). U.S. Government Accountability Office.
Office of Personnel Management. (2024). Federal workforce priorities report. U.S. Office of Personnel Management.
U.S. Department of Defense Office of Inspector General. (2024). Audit reports and evaluations supporting the Department of Defense financial statement audit. U.S. Department of Defense.
