[18.0][ADD]fleet_traffic_infraction: new module Replaces #185#217
Open
[18.0][ADD]fleet_traffic_infraction: new module Replaces #185#217
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Depends on #184?
Motivation
This module introduces a framework for the comprehensive management of traffic infractions within a vehicle fleet. Many companies struggle to track fines, identify the responsible driver, and manage the lifecycle of an infraction from notification to resolution.
The primary motivation is to create a foundational module that focuses exclusively on the operational aspects of infraction management. It provides the necessary tools to record infractions accurately, link them to the correct vehicle, and, most importantly, suggest the driver who was in charge of the vehicle at the time of the incident.
This module intentionally separates the operational tracking from the financial transactions. This approach creates a lean and focused base module, fleet_traffic_infractions, upon which financial modules, such as an accounting integration, can be built.
Implementation
To achieve this, the module implements the following:
This module serves as the definitive record for what happened, who was responsible, and the operational status of the fine. All accounting-related features, such as creating bills or invoices, are explicitly out of scope.
Roadmap
This module is the first step in a two-part plan for complete traffic infraction management. The next step will be the creation of the fleet_traffic_infractions_account module, which will build directly on this foundation.
The future accounting module will be responsible for:
Creating a Vendor Bill from an infraction (or a generic accout.move), payable to the "Issuing Agency."
Creating a Customer Invoice to charge the fine and any administrative fees to the responsible driver or a third party.
Tracking the payment status of fines.
Linking infractions directly to their corresponding journal entries for full financial traceability.