NEWFlash AI is live — meet your desk copilot. »
/docs/modules/bill-of-sale

Bill of Sale

Close with paperwork that pulls dealership legal block from Settings — human review required.

Purpose

The Bill of Sale (BOS) packages buyer, seller, unit, price, tax, and disclosure references for Ontario-oriented independents. It helps desks print consistent deals; it is not a certified UCDA form replacement.

Setup

  1. Settings → Business — legal name, address, dealer licence, HST number.
  2. Inventory — known-damage disclosure complete on Active unit.
  3. Deal — all fees, trade, and taxes entered before BOS generate.
  4. E-sign optional (E-signatures).

Daily workflow

  1. Move deal to ready to close status.
  2. Generate BOS — preview all pages; verify VIN, odometer, sale price, HST.
  3. Manager review — especially on as-is and known-damage units.
  4. Print or e-sign — buyer and seller signatures captured.
  5. Archive — PDF stored on deal; audit trail logs generation event.

Key fields

BlockSource
Seller businessSettings → Business
BuyerCustomer record on deal
VehicleInventory VIN, year/make/model, odometer
Purchase price & HSTDeal structure
Disclosure refsInventory known-damage notes
We-owe / accessoriesDeal lines

Permissions

  • Sales — draft BOS with manager approval gate (if configured).
  • Manager / admin — final generate and void/regenerate.
  • Read-only — view PDF only.

Canadian notes

  • Ontario MVDA — known damage must be disclosed before sale; guards on Active inventory help but do not replace counsel.
  • UCDA — FlashFender aligns field layout where possible; certified forms come from UCDA or your lawyer.
  • BC VSA — see British Columbia compliance for provincial differences.