# Beancount for Vehicle Maintenance Records

Use Beancount to track vehicle maintenance records: service notes, parts, labor and mileage in a plain-text ledger you can query and report on.

Beancount records vehicle maintenance as plain-text transactions, so every service, part and repair cost sits in one searchable file. A beancount ledger pairs money movements with dated notes, which makes it a practical home for service history. You write the entries once and query them later with beancount reports. 

- Open the ledger with account directives for your vehicle's maintenance expense and the account that pays for it.
- Record each service as a transaction entry dated to the day the work happened, with the shop or part in the narration.
- Keep mileage and service notes in the same entry so the cost and the reason stay together.
- Use a separate maintenance expense account per vehicle to keep reports readable.
- Query the ledger with beancount reports to see spending by vehicle, category or period.
 

## What Beancount does for vehicle records 

Beancount is a plain-text accounting tool that stores every entry in a ledger file you own and edit. Vehicle maintenance fits this model because each service is a dated money movement with a short description. The ledger keeps the cost and the service note on the same line of text. 

A beancount ledger holds account directives that name your accounts before any entries use them. Transaction entries then post amounts between those accounts, such as a maintenance expense account and the card or bank account that paid. Every posting balances, which keeps the arithmetic honest across years of records. 

Records stay readable in any text editor and can be versioned like code. A query tool reads the same file and produces spending reports without a separate database. That combination suits a fleet manager who wants service history and cost history in one place. 

## Set up maintenance expense accounts 

Vehicle maintenance expense accounts belong under an expenses branch of your chart of accounts. Give each vehicle its own account, such as a maintenance expense account named for the unit, so reports separate one unit from another. Account directives declare these names once at the top of the ledger. 

Split the expense by type when you need detail. Tires, fluids, scheduled service and repairs can each take a subaccount under the vehicle. A coarser setup with one account per vehicle works too and keeps entry writing fast. 

Name the paying account as well, whether that is a business card, a bank account or a cash account. Every transaction entry needs at least two postings, and the second posting is the source of the money. Consistent account names keep beancount reports accurate later. 

## Write a maintenance transaction entry 

A maintenance transaction entry starts with a date, a flag and a narration that names the service. Post the amount to the vehicle's maintenance expense account and the offset to the account that paid. The narration is the place for the shop name, the part and the odometer reading. 

Keep the narration short and specific, such as 'Oil change and filter, unit 12, odometer noted'. Add metadata lines under the transaction for details that do not belong in the narration. Metadata like a mileage tag or a work order number keeps the entry clean and still searchable. 

Record the entry on the date the work happened, not the date the invoice arrived. That choice keeps the service history in the right order when you review a vehicle's timeline. If the invoice arrives later, the payment date can be its own entry or a metadata note. 

## Capture service notes with the cost 

Service notes make a maintenance record useful beyond the total spent. Put the symptom, the work performed and any parts replaced in the transaction narration or in metadata lines. A future reader then sees why the money was spent, not only how much. 

A short tag for the service type lets you group entries later, such as a tag for scheduled work or a tag for a breakdown. Tags sit in metadata and do not disturb the accounting. Reports and text searches can both filter on them. 

Keep warranty or inspection notes as text in the same entry when they affect the work. Do not put sensitive personal details in the ledger if the file is shared. A plain description of the job and the parts is enough for a fleet record. 

## Track mileage and intervals in the ledger 

Mileage gives maintenance records their context, because service intervals depend on distance traveled. Record the odometer reading as metadata on the maintenance transaction entry. A consistent tag for mileage lets you pull the reading for any service date. 

You can also log fuel and mileage as their own entries to build a distance history. Those entries post to a fuel expense account and carry the odometer reading in metadata. Together with service entries, the ledger shows which work happened at which distance. 

Beancount does not calculate service intervals for you. It stores the readings and lets you query them, and the interval decision stays with your maintenance schedule. Naming what each reading depends on keeps the record honest. 

## Report on vehicle costs 

Beancount reports turn the ledger into spending views for each vehicle. A report filtered to one maintenance expense account shows the total and the entries behind it. Running the same report for two periods shows how cost moved. 

Group spending by vehicle to compare units, and group by service type to see where money goes. Reports read the same entries you wrote, so no extra data entry is needed. Save the report commands you use so the same view is repeatable. 

Export report output to a spreadsheet when a manager wants a table. The ledger stays the source of truth and the export is a snapshot. Keep the export dated so it is clear which ledger state it reflects. 

## Steps for a clean maintenance record 

A clean vehicle maintenance record follows a short routine each time work is done. The steps below apply whether you write entries by hand or paste them from a template. Consistency matters more than detail volume. 

Write the entry close to the service date while the details are fresh. Attach the odometer reading and the service note in the same transaction. Then check that the posting balances before you move on. 

Review the vehicle accounts at a set interval and look for missing entries. A gap in dates or mileage often points to a service you forgot to record. Fix the gap in the same ledger rather than in a separate note. 

- Confirm the account directives exist for the vehicle before writing.
- Write the transaction entry on the service date with a clear narration.
- Add metadata for odometer reading, work order and service type.
- Check that the two postings balance to zero.
- Run a report on the vehicle account and scan for gaps.
- Add any missing entry to the same ledger file.
 

## Where the plain-text approach fits 

A plain-text ledger suits a fleet manager who wants records they can read without special software. The file works in any editor, diffs cleanly in version control and survives tool changes. Beancount adds double-entry accounting on top of that plain text. 

The approach asks you to learn a small syntax and to write entries yourself. It does not replace a dealership service system or a workshop's own records. Use it as your cost and service ledger alongside those sources. 

Jobs that need a trained specialist still go to that specialist, and the ledger records the outcome. Brake, tire and structural work belongs with a qualified technician. The ledger's role is to keep the date, the cost and the note together. 

## Questions about Beancount vehicle records 

### Can Beancount hold vehicle maintenance records? 

Yes, Beancount holds vehicle maintenance records as dated transaction entries in a plain-text ledger. Each entry posts the service cost to a maintenance expense account and names the service in the narration. Mileage and service notes fit in metadata on the same entry. 

### How do I record a vehicle service in a beancount ledger? 

Write a transaction entry dated to the service day with a narration naming the work and the vehicle. Post the amount to the vehicle's maintenance expense account and the offset to the paying account. Add metadata lines for the odometer reading and work order number. 

### Should each vehicle get its own maintenance expense account? 

Yes, a separate maintenance expense account per vehicle keeps beancount reports readable. Reports filtered to one account then show that unit's service cost and history. The account directives at the top of the ledger declare each name once. 

### Can Beancount track mileage along with maintenance costs? 

Yes, Beancount tracks mileage when you store the odometer reading as metadata on a transaction entry. A consistent mileage tag lets you query the reading for any service date. Beancount stores the readings but does not calculate service intervals for you. 

### What reports can I run on vehicle maintenance costs? 

Beancount reports can total spending on a maintenance expense account, compare vehicles and group cost by service type. Reports read the same entries you wrote, so no separate data entry is needed. Export the output to a spreadsheet when a manager wants a table.
