Record keeping

Track Actual Maintenance Costs Across Vehicles and Machines

The estimate, final invoice, and card charge can show different numbers. Keep the source trail, then record one supported cost for the completed job.

By Sebastian, founder and builder · Published · 4 minute read

Pick the final number, not the first number

A cost log is useful only when each number answers the same question: what did this completed job cost for this asset?

An estimate describes proposed work. The final invoice or completed repair order is the better source for the amount tied to completed shop work.

The FTC says a completed repair order should list the repairs, supplied parts and charges, labor charges, and odometer readings.

Do not add the estimate and invoice together. Keep the estimate as context, but place only one supported amount on the completed record. The repair-shop paperwork guide explains the full document trail.

One job, one asset, one amount

Start with the asset, service date, and work completed. Add mileage or hours when the source provides them.

For a shop visit, use the final total that belongs to that record. For DIY work, use the documented cost of parts and fluids used for that job.

If one invoice covers several jobs on one asset, keep one visit record with the invoice total. Split the jobs only when the invoice gives reliable line-item costs.

Do not copy one full invoice total into several records. That makes a useful history look more expensive every time it is summarized.

A shared receipt may cover supplies for several machines. If the document does not support a clean split, keep the receipt and leave the individual costs blank.

Unknown, zero, and estimated are different

Blank means the cost is unknown or not recorded. Zero means you verified that the completed job had no owner-paid cost. Do not use zero as a placeholder.

Planning ranges belong in planning, not history. A projected amount should not become the saved cost for a completed job unless the final source confirms it.

California and New York guidance both keep estimates and final invoices distinct. Those requirements apply in their states, so check the rules where the repair happened.

This guide does not calculate refunds, reimbursements, credits, warranty coverage, financing costs, taxes, or total cost of ownership. Keep those questions with the source that controls them.

Across the garage, consistency matters

Use the same definition of cost across vehicles and machines. Copy the final supported total, then apply that rule consistently.

Compare records within the same currency. If records use different currencies, review them separately unless you have a dated, verified conversion method.

Total recorded spend, average cost per priced job, and changes between similar services can be useful. They are ledger summaries, not forecasts, savings claims, or repair advice.

The full maintenance-log guide shows where cost fits beside the date, reading, work, provider, proof, and next reminder.

Five checks before saving a cost

A short check keeps the ledger honest. If one answer is no, keep the source and leave the cost blank until the number can be supported.

  • Was the work completed?
  • Is the amount final?
  • Does it belong to this asset?
  • Will it be counted once?
  • Is the currency clear?

What ServiceVault records today

In the current iPhone build, a service record can hold one optional cost and one currency beside its date, mileage or hours, provider, notes, and attachments.

The saved amount appears on the record and feeds recorded-spend summaries. The math reflects what you entered. It does not verify the invoice or decide which number is final.

ServiceVault does not turn estimates into actual costs, allocate a shared invoice, convert currencies, or reconcile a later payment. You review and enter the number.

When several sources describe the same job, the record-reconciliation guide shows how to count the completed work once without deleting the proof.

Sources and further reading

See how the Journal is checked or report a correction.

Sources checked .