How Unsupported Costs Arise
Unsupported costs can originate at different points in the transaction lifecycle. A purchase may lack an approved requisition or supporting invoice, a labor charge may not have adequate timekeeping records, or an indirect cost allocation may lack the schedules needed to reproduce the calculation. The accounting entry may be accurate while the supporting evidence is insufficient to demonstrate that accuracy.
- Missing source documents: Receipts, invoices, contracts, timesheets, or other primary records are unavailable.
- Incomplete approvals: Required authorization is not documented or cannot be connected to the transaction.
- Unclear allocation: Records do not adequately explain how a cost was assigned to a contract or cost objective.
- Insufficient calculations: Schedules or assumptions supporting an amount cannot be independently reconciled.
- Weak transaction linkage: The relationship between the source transaction and general ledger entry is not readily traceable.
Unsupported Costs in Procurement
Procurement documentation is particularly important because purchasing transactions typically pass through requisitions, sourcing, approvals, receiving, invoicing, and payment. A properly documented purchase order can connect the approved requirement to the supplier, quantities, pricing, receipt information, and subsequent invoice.
Strong procurement controls also establish who authorized spending and which cost objective should receive the expense. When an auditor reviews a transaction, this evidence helps demonstrate that the expenditure followed the organization's purchasing procedures and can be traced through the procure-to-pay process.
Organizations reviewing purchasing controls can also examine the Manual Purchase Order Process vs Automated: Cut 80% Costs discussion for context on purchase-order processing, approvals, error reduction, and transaction consistency.
Accounting Treatment and Supporting Evidence
Finance teams should connect each material cost to the records necessary to explain its accounting treatment. For contract-related expenditures, this can include the agreement, invoice, receipt, approval, allocation methodology, journal entry, and reconciliation supporting the reported amount.
Amortization Of Contract Costs illustrates why supporting schedules matter. When qualifying contract-related costs are recognized over an applicable period, the accounting record should be supported by documentation explaining the underlying cost, recognition period, calculation, and resulting entries.
Other valuation concepts require their own supporting evidence. Fair Value Less Costs To Sell uses fair value and directly attributable selling costs as components of a valuation measurement, so the records supporting those inputs should be retained and reconcilable.
Similarly, Incremental Costs Of Obtaining A Contract describes qualifying costs that arise specifically from obtaining a contract. Finance teams should retain evidence establishing the nature of the cost and the basis for its accounting treatment.
ERP Traceability and Cost Documentation
An ERP can connect purchasing, accounts payable, project accounting, general ledger, and contract information so that finance teams can trace a transaction from its source through approval and posting. Effective integration also helps preserve the relationships among source documents, accounting classifications, and financial reports.
Organizations evaluating ERP integration or migration can review How Hyperbots Helped Avoid Millions in ERP Migration Costs for an example of how finance teams can approach ERP migration, AI-driven workflows, and finance process optimization while maintaining structured accounting information.
For unsupported-cost reviews, the key requirement is traceability. A reviewer should be able to move from the reported amount to the underlying transaction, supporting evidence, accounting entry, and applicable cost objective without relying on undocumented assumptions.
How to Resolve Unsupported Costs
Resolution begins by identifying the exact amount and reason the supporting evidence is considered insufficient. Finance teams can then reconstruct the transaction history, obtain missing documentation where available, reconcile the amount to the accounting records, and document the conclusion reached.
- Identify each unsupported transaction and its affected contract or cost objective.
- Gather invoices, receipts, approvals, time records, contracts, calculations, and reconciliations.
- Reconcile supporting documentation to the general ledger and relevant subsidiary records.
- Document the explanation for any remaining evidence gap and the resulting accounting treatment.
- Establish ownership and retention requirements for supporting records going forward.
For example, if $18,000 of indirect costs lacks an allocation schedule, management can reconstruct the calculation using approved source records and reconcile the result to the ledger. If the reconstructed schedule supports the full $18,000, it provides evidence explaining the original accounting treatment and strengthens the audit record.
Summary
Unsupported Costs are expenditures for which the available records do not sufficiently substantiate the amount, purpose, classification, allocation, or accounting treatment. Strong procurement controls, complete source documentation, traceable ERP records, and reproducible calculations help finance teams substantiate costs and support reliable financial reporting.