Freight Invoice Format
Last Updated: August 2026
Use as a field checklist when designing invoices or migrating from paper.
Summary
Reference fields every freight invoice should carry for Indian transporters. Use as a field checklist when designing invoices or migrating from paper.
What is this?
Freight Invoice Format
Who is it for?
Transport office teams standardizing paperwork.
Why use it?
Consistent fields reduce disputes and speed software adoption.
Key takeaways
- Copy into Sheets or enforce in TruckBill
- Use as branch SOP
- Link to Knowledge Hub
Recommended fields
- Party / document identifiers
- Trip or LR reference
- Amounts and tax lines (where applicable)
- Proof attachments
- Approver / date stamps
How to use
Copy this structure into Excel/Google Sheets or enforce it inside TruckBill. Related: Knowledge templates pillar · transport glossary.
Minimum invoice blocks to keep
A freight invoice should be easy for customers, accounts, and auditors to reconcile against LR and trip logs. Keep these core blocks even if your design changes.
- Header: invoice number/date, supplier GST details, customer GST details
- Trip reference: LR number, vehicle, route, loading/unloading dates
- Charges: freight, detention, loading/unloading, taxable amount, GST breakup
- Payment terms: due date, bank details, and supporting document references
Frequently asked questions
Why should invoice and LR references stay together? Keeping LR references on the invoice reduces billing disputes and speeds party confirmation during collection follow-ups.
Can we use one format for all branches? Yes. Start with one standard format and allow only controlled branch-specific fields so consolidation remains consistent.