Shipbuilding companies handle reimbursements by matching employee and subcontractor expenses to vessel contracts, cost codes, and project phases for accurate job-cost tracking. Platforms like Vergo address this by tying each reimbursement to a cost code and contract phase, keeping multi-year projects auditable and billable.
A reimbursement in shipbuilding is any out-of-pocket cost incurred by an employee, subcontractor, or trade partner that the company agrees to repay — and in most cases, subsequently bill back to a vessel contract or government program. These costs range from travel to drydock inspection sites, to specialty tooling purchased by a welder, to per diem expenses for crews working away from the home shipyard.
Unlike a typical office environment where reimbursements are simple expense reports, shipbuilding reimbursements must satisfy two requirements simultaneously: they must follow internal accounting controls, and they must map to an external billing structure. Federal shipbuilding contracts — particularly those under the Defense Federal Acquisition Regulation Supplement (DFARS) — require that reimbursable costs be allowable, allocable, and reasonable. Misclassifying a reimbursement can trigger a contract audit or result in disallowed costs during government review.
Shipyards typically organize costs around vessel hull numbers, work breakdown structure (WBS) codes, or contract line item numbers (CLINs). Every reimbursement must slot into this hierarchy. A port engineer expensing a flight to a vessel commissioning in Newport News is not simply submitting a travel receipt — that cost is being coded to a specific hull, a specific phase, and a specific CLIN that will appear on a progress billing.
Shipbuilding controllers face a reimbursement problem that most ERP systems weren't designed to solve: expenses arrive from dozens of sources (field engineers, superintendents, third-party inspectors, subcontractors), on inconsistent timelines, against contracts that may span five to ten years. A single missed reimbursement coded to the wrong hull number can distort job cost reports and trigger billing discrepancies worth thousands of dollars.
The practical implications for shipbuilding finance teams include:
For a controller, this means the reimbursement workflow can't be an afterthought. It must be a structured, code-enforced process that feeds directly into job costing and accounts payable without manual rekeying.
Scenario 1 — Before a structured process: A marine systems engineer submits a paper expense report for travel to a sea trial. The accounts payable clerk codes it to the general overhead account because the hull number field is blank. The cost never hits the vessel contract, the project manager's job cost report understates direct costs, and the billing to the Navy is short by $1,400. The error surfaces six weeks later during a contract reconciliation.
Scenario 2 — After a structured process: The same engineer submits expenses through a digital workflow that requires a hull number, WBS code, and cost category before submission. The system routes the request to the project manager for approval, then posts automatically to the correct job cost ledger. The cost is captured before the monthly progress billing cycle closes and is included in the next invoice to the client.
Scenario 3 — Subcontractor reimbursables: An insulation subcontractor purchases specialty firebrick materials and submits receipts for reimbursement under a cost-plus task order. The shipyard's finance team validates the purchase against the approved budget for that hull section, confirms the material is allowable under the contract, and processes the reimbursement tied to the subcontract line — not to a general material account.
Leading shipbuilding finance teams are moving away from spreadsheet-based expense tracking and paper approval chains toward purpose-built reimbursement workflows that enforce job cost coding at the point of submission. The goal is to eliminate the gap between when a cost is incurred and when it appears in the job cost ledger.
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.
Shipbuilding reimbursements should map to the same cost code structure used for direct labor and materials — typically organized by hull number, WBS element, or CLIN. Using a separate 'reimbursement' bucket obscures true job costs. Each expense should carry a phase code, cost category, and the vessel contract it supports.
Federal shipbuilding contracts governed by FAR and DFARS require that reimbursable costs be allowable, allocable, and reasonable. Certain costs — such as entertainment or unsubstantiated travel — are expressly disallowed. Controllers must enforce these standards at the point of approval, not during a post-submission audit, to avoid cost disallowances during contract closeout.
In shipbuilding environments without a structured workflow, reimbursement approval can take two to four weeks due to paper routing, missing documentation, and manual coding. Best-practice teams target three to five business days by using digital submission with required job cost fields, automated routing to the project manager, and direct posting to the accounting system upon approval.
Subcontractor reimbursables under cost-plus task orders require additional validation steps: confirming the cost is within the approved scope, checking allowability under the subcontract terms, and coding to a subcontract line rather than a general material account. The approval chain typically involves both a project manager and a contracts administrator before finance processes payment.
A reimbursement posted after a billing cycle closes is deferred to the next period's invoice. On cost-plus contracts, this delays cash recovery. On fixed-price contracts with progress billings, it understates costs incurred in that period, distorting both the job cost report and the earned value calculation for the vessel in question.
Vergo's reimbursements module requires submitters to assign a job and cost code before submission, preventing unallocated expenses from entering the ledger. It integrates natively with major construction ERPs — including Sage, Viewpoint, Foundation, CMiC, and others — so approved reimbursements post directly to the correct job cost record without manual rekeying.