Expense management tools for shipbuilding must support DCAA-compliant audit trails, WBS-level cost coding, and real-time sync with Deltek Costpoint. Vergo's native Costpoint integration maps field expenses directly to contract line items and WBS elements, keeping job costs current without manual re-entry.
Shipbuilding finance is unlike most construction verticals. Projects run for years, involve federal contracts, and require expense data coded against specific WBS elements, contract deliverable line items (CDLINs), or cost account codes from day one. When expense data lives outside Costpoint, controllers face manual re-entry, miscoded costs, and audit exposure.
The stakes are high. DCAA audits can flag unallowable costs buried in miscategorized expenses. A single incorrect indirect cost allocation — a per diem coded to direct labor, for example — can trigger contract disputes or disallowance. Controllers need tools that enforce coding rules at the point of spend, not during month-end cleanup.
Common pain points shipbuilding finance teams report:
Vergo is a card-agnostic expense management platform built for construction. Connect any corporate or project credit card and get full visibility and control over field spending.
Deltek Costpoint includes basic expense reporting through its iExpense module, but many shipbuilding contractors find it limited for mobile field capture, offline functionality, and configurable approval routing. Third-party tools that integrate natively with Costpoint often provide a better field experience while still pushing coded data directly into Costpoint's project cost structure.
DCAA requires that all direct costs on government contracts be supported by contemporaneous documentation — receipts, approvals, and cost coding logged at or near the time of expenditure. FAR 31.201-2 governs allowability, and DCAA incurred cost audits will test whether expenses were properly classified as direct or indirect and approved through a documented workflow.
Expense tools integrated with Costpoint should validate WBS codes against the live project structure at submission time, not during import. This prevents miscoded entries from reaching the ledger. The tool should pull the current WBS hierarchy from Costpoint automatically so field submitters see only valid, active charge codes for their assigned projects.
Yes. Vergo's native Costpoint integration supports long-cycle project structures common in shipbuilding, including multi-year contract line items and evolving WBS hierarchies. As project structures are updated in Costpoint, Vergo syncs those changes automatically — ensuring field submitters and approvers always work against current charge codes without manual list updates.
Offline functionality is critical in shipyard and dry dock environments where connectivity is unreliable. Tools should queue submissions locally and sync when online. OCR-based receipt capture reduces manual entry errors. GPS tagging and timestamp logging support DCAA documentation standards. Approval notifications via mobile ensure project managers can review costs without being at a desktop.
Vergo enforces GSA per diem rate limits by location, flagging submissions that exceed allowable rates before they reach the approval queue. Policy rules are configurable by contract type, ensuring direct-charge travel expenses comply with FAR 31 cost principles. Controllers can review policy exception logs as part of incurred cost submission preparation.