Skip to content

Vehicle Purchase/Acquisition - Product Requirements Document

Version: 2.0 | Status: Ready for Stakeholder Review | Last Updated: 2026-01-15


Change Log

VersionDateAuthorChanges
2.02026-01-15PRD ConversionConverted to business-focused format per checklist
1.02025-12-01Initial DraftOriginal technical specification

1. Executive Summary

1.1 Purpose

Enable fleet operators to track vehicle acquisition costs (purchase, lease, rental) with automated payment tracking and complete financial visibility.

1.2 Problem Statement

Fleet operators lose money and time due to:

  • Manual payment tracking causes missed lease expenses and incorrect financial reporting
  • No centralized acquisition records makes it impossible to calculate true cost of ownership
  • Backdated contracts require hours of manual retroactive payment entry
  • Disconnected systems prevent accurate vehicle profitability analysis

1.3 Business Value

OutcomeMetricTarget
Eliminate missed paymentsPercentage of lease/rent payments automatically captured100%
Reduce manual data entryHours saved per month on payment tracking8-12 hours
Improve financial accuracyReduction in acquisition cost discrepancies95% fewer errors
Enable cost visibilityVehicles with complete acquisition cost tracking100% coverage
Accelerate backdated contractsTime to enter retroactive payments<1 minute vs 30+ minutes manual

1.4 Target Users

RolePrimary NeedBusiness Impact
Fleet ManagersTrack acquisition strategy across fleetOptimize purchase vs lease decisions
Finance TeamsAccurate expense records and forecastingMonth-end close accuracy, audit readiness
Operations StaffRecord agreements and documentationMaintain compliance, reduce errors

1.5 Scope

In Scope:

  • Three acquisition types: Purchase (one-time), Lease (financial), Rental (operational)
  • Automated monthly payment generation for recurring agreements
  • Retroactive payment calculation for backdated contracts
  • Contract lifecycle management (start, pause, resume, expire)
  • Document attachment for agreements
  • Integration with vehicle economics and balance tracking

Out of Scope:

  • Depreciation calculations
  • Payment notifications/reminders
  • Multi-currency support
  • Accounting system integration
  • Lease buyout calculations
  • Early termination management

2. Success Metrics

MetricDefinitionBaselineTargetMeasurement MethodTimeframe
Payment Capture Rate% of recurring payments auto-generated0% (manual)100%Compare expected vs actual balance entries3 months
Data Entry TimeHours spent manually recording acquisition costs~15 hrs/month (estimate)<3 hrs/monthTime tracking survey of finance teams6 months
Financial Accuracy% of vehicles with correct acquisition cost totals~70% (estimate)99%Quarterly audit reconciliation6 months
Retroactive ProcessingTime to enter backdated contract with payments~30 min/contract<1 minSystem timestamp comparison3 months
Fleet Coverage% of vehicles with acquisition records~50% (estimate)95%Vehicle count with active purchase record6 months
Contract Compliance% of agreements with attached documentation~60% (estimate)90%File attachment audit6 months

Baseline Collection:

  • Pre-implementation survey of finance teams for manual effort estimates
  • Audit sample of 50 vehicles for current acquisition record completeness
  • Analysis of vehicle balance entries for payment accuracy

3. User Stories

P0 - Must Have

IDUser StoryAcceptance Criteria
US-01As a Fleet Manager, I want to record a vehicle purchase so the acquisition cost appears in vehicle economicsGIVEN a vehicle exists, WHEN I create a purchase record with amount, THEN the expense appears in vehicle balance within 5 seconds
US-02As a Finance Team member, I want lease payments to automatically generate monthly expenses so I don’t have to enter them manuallyGIVEN an active lease with due date = 15th, WHEN the 15th arrives, THEN a balance entry is created with the correct amount
US-03As a Fleet Manager, I want to create backdated agreements with automatic retroactive payments so historical records are completeGIVEN a lease starting 3 months ago, WHEN I create it with retroactive flag, THEN 3 monthly payment entries are created instantly
US-04As an Operator, I want to upload purchase documentation so agreements are stored with the vehicleGIVEN a purchase record, WHEN I attach a file, THEN the file is linked to the record and all generated payment entries

P1 - Should Have

IDUser StoryAcceptance Criteria
US-05As a Fleet Manager, I want to pause a lease during vehicle downtime so payments stop until resumedGIVEN an active lease, WHEN I pause it, THEN no payments generate until I resume it
US-06As a Finance Team member, I want to set different first-month payments (down payments) so initial costs are tracked separatelyGIVEN a lease with initial payment of $1000 and regular payment of $500, WHEN payments generate, THEN first is $1000 and subsequent are $500
US-07As a Fleet Manager, I want agreements to automatically expire at end date so no payments generate for ended contractsGIVEN a lease ending Jan 10, WHEN Jan 11 arrives, THEN the contract is marked inactive and no future payments generate
US-08As a Finance Team member, I want to see total acquisition cost per vehicle including all payments to dateGIVEN a vehicle with 12 months of lease payments, WHEN I view vehicle economics, THEN I see the sum of all acquisition-related expenses

P2 - Nice to Have

IDUser StoryAcceptance Criteria
US-09As a Fleet Manager, I want to track included kilometers and overage costs per lease so I can monitor complianceGIVEN a lease with 30,000 km included, WHEN I enter overage cost per km, THEN this data is stored for reporting
US-10As a Finance Team member, I want to distinguish purchase vs lease vs rental in reports so I can analyze acquisition strategyGIVEN multiple vehicles with different acquisition types, WHEN I filter expenses by category, THEN I see separate totals for each type
US-11As a Fleet Manager, I want to track security deposits separately so refundable amounts are not counted as expensesGIVEN a lease with security deposit, WHEN recorded, THEN the deposit is tracked separately from regular payments

4. Functional Requirements

4.1 Acquisition Type Management

RequirementBusiness Outcome
FR-01: Support three acquisition types (Purchase, Lease, Rental)Finance teams can categorize and report on acquisition strategy
FR-02: Purchase type creates single expense entry immediatelyOne-time costs reflected in vehicle economics instantly
FR-03: Lease and Rental types generate recurring monthly expensesEliminate manual payment entry for recurring agreements
FR-04: Each vehicle has only one active acquisition recordPrevent duplicate payments and conflicting records

4.2 Payment Automation

RequirementBusiness Outcome
FR-05: Generate payments automatically on configured due date each month100% payment capture without manual intervention
FR-06: Support different first payment amount (down payment)Accurate tracking of variable initial costs
FR-07: Handle months with fewer days than due date (e.g., Feb 28 for due date 31)No missed payments due to calendar variations
FR-08: Prevent duplicate payments for same monthFinancial accuracy and auditability
FR-09: Stop payments automatically when contract end date passesNo erroneous post-contract expenses

4.3 Retroactive Processing

RequirementBusiness Outcome
FR-10: Calculate and create all historical payments for backdated contractsInstant retroactive entry vs hours of manual work
FR-11: Apply first-payment amount to first retroactive entry when applicableAccurate historical records including down payments
FR-12: Create all retroactive entries in single transactionData consistency and rollback capability

4.4 Contract Lifecycle

RequirementBusiness Outcome
FR-13: Pause and resume contracts without losing configurationHandle vehicle downtime without losing agreement terms
FR-14: Preserve records of expired/superseded contractsComplete audit trail for compliance
FR-15: Support contract updates (price changes, term modifications)Reflect renegotiated terms without recreating agreements

4.5 Documentation & Integration

RequirementBusiness Outcome
FR-16: Attach agreement files to purchase recordsSingle source of truth for contract documentation
FR-17: Link all generated payments back to originating agreementTraceability for audit and reconciliation
FR-18: Include acquisition costs in vehicle profitability calculationsAccurate total cost of ownership analysis

5. Business Rules

RuleDescriptionBusiness Rationale
BR-01One active acquisition per vehiclePrevents duplicate payments and data inconsistency
BR-02New acquisition supersedes previous (soft delete)Maintains audit trail while ensuring single source of truth
BR-03Paused contracts do not backfill missed payments when resumedPrevents unexpected bulk expenses; pause means no charges
BR-04Payment due date 31 uses last day of short monthsEnsures predictable monthly payment timing
BR-05Retroactive payments only for Lease and Rental typesPurchases are one-time by definition
BR-06Contract expiration is automatic and irreversiblePrevents accidental charges beyond agreement terms

6. Acceptance Criteria

AC-01: Purchase Recording

  • GIVEN a vehicle with no acquisition record
  • WHEN admin creates purchase record with $50,000 amount
  • THEN expense entry of $50,000 appears in vehicle balance within 5 seconds
  • AND purchase record shows as active

AC-02: Monthly Payment Generation

  • GIVEN lease with due date = 15th, monthly amount = $500
  • WHEN system processes on January 15
  • THEN expense entry of $500 is created dated January 15
  • AND entry is linked to originating lease record

AC-03: Different First Payment

  • GIVEN lease with initial payment = $1,000, regular payment = $500
  • WHEN first payment generates
  • THEN amount is $1,000
  • WHEN second payment generates
  • THEN amount is $500

AC-04: Retroactive Payments

  • GIVEN lease starting October 15, 2025 with due date = 15, regular = $500, initial = $1,000
  • WHEN created on January 20, 2026 with retroactive flag
  • THEN 4 expense entries created: Oct 15 ($1,000), Nov 15 ($500), Dec 15 ($500), Jan 15 ($500)

AC-05: Contract Pause

  • GIVEN active lease with due date = 15
  • WHEN admin pauses contract on January 5
  • AND system processes on January 15
  • THEN no payment is generated
  • WHEN admin resumes on February 10
  • AND system processes on February 15
  • THEN February payment is generated (January is not backfilled)

AC-06: Contract Expiration

  • GIVEN lease ending January 10
  • WHEN system processes on January 11
  • THEN contract marked inactive
  • AND no future payments generated

7. Dependencies

Upstream Dependencies

SystemDependency TypeImpact if Unavailable
Vehicle ManagementRequiredCannot create acquisition records
Tenant SettingsRequiredCannot determine timezone for payment scheduling

Downstream Dependencies

SystemIntegrationImpact
Vehicle BalanceExpense entriesAcquisition costs appear in vehicle economics
Fleet ReportsData aggregationCost of ownership calculations

8. Non-Functional Requirements

RequirementTargetMeasurement
Payment ProcessingAll monthly payments generated within 10-minute daily windowSystem logs
Data IntegrityZero duplicate payments per monthBalance entry audit
Reliability99.9% uptime for payment generationMonitoring dashboard
Error IsolationFailure in one tenant does not affect othersError logs
Audit TrailAll records preserved with soft deleteDatabase query verification

9. Glossary

TermDefinition
PurchaseOne-time vehicle acquisition with immediate expense entry
LeaseFinancial lease with recurring monthly payments, typically with residual value
RentalOperational lease with recurring monthly payments, no residual value
Initial PaymentFirst payment amount (may differ from regular monthly amount for down payments)
Residual ValueFinal payment or buyout amount at lease end
Retroactive PaymentsHistorical payment entries auto-generated for backdated contracts
Security DepositRefundable upfront amount tracked separately from payments
Soft DeleteMarking record inactive while preserving for audit trail

10. Unresolved Questions

  1. Baseline data availability? Can finance teams provide actual current manual effort hours for comparison?
  2. Audit frequency? How often will reconciliation audits run to measure accuracy improvements?
  3. Notification need? Should payment generation failures trigger alerts to finance team?
  4. Multi-currency priority? How urgent is support for cross-border fleet operations?