Contact

Document control

Vehicle Sales Documentation

In production Integrated with dealership data

Centralizes the documentation for each vehicle sale, creating the file automatically from invoiced sales and extracting data from uploaded documents.

Problem

Each vehicle sale requires a complete document package. Every dealership prepared its files locally and entered the data manually, so corporate staff had no consolidated view of documentation status by reporting period.

Solution

The application synchronizes invoiced sales from all dealership locations every night and creates the corresponding sales file. Each document is uploaded once, and automatic text recognition extracts its data, eliminating manual entry.

Outcome

Corporate staff can review files created from invoiced sales in one place without entering document data more than once.

My role

I rebuilt version 2 and implemented daily DMS synchronization, data extraction, and automatic document generation.

How it works

Every night, invoiced sales create their corresponding files, and the documentation moves through the process until it is available for corporate review.

Scroll horizontally to view the full diagram.

Vehicle sales file creation and review workflow Invoiced sales are synchronized nightly, with CSV upload as an alternate path. After the document is uploaded, the application determines whether a PLD document required under Mexico's anti-money-laundering rules must be generated before enabling review. DMS SOURCE DEALERSHIP / ENTRY PLATFORM CORPORATE REVIEW SALES NEW SALES BATCH CREATION CREATED UPLOAD PDF VALIDATE YES NO PLD READY NIGHTLY DMS Invoiced sales Records by location PLATFORM Synchronize Nightly · 11:00 PM ADMINISTRATOR Bulk CSV upload Alternate batch creation PLATFORM Create sales file Initial status: Created DEALERSHIP Upload document Transaction PDF PLATFORM Store file S3 · status: Uploaded ANNUAL RULE Requires PLD? Threshold vs. base price PLATFORM Generate PLD Finds section and creates PDF CORPORATE TEAM Review sales file Status and file access PRIMARY FLOW SCHEDULED RUN COMPLIANCE RULE
Nightly synchronization or a bulk upload creates the sales file. The PLD document required under Mexico's anti-money-laundering rules is generated only when the annual threshold applies; the file is then available according to permissions.

Key functions

Product evolution

Version 2 rebuilt the interface in React while preserving the original data model. It added automatic sales synchronization, text-recognition data extraction, and automatic generation of supporting documentation—tasks that were manual in the first version.

Technical details

Backend
NestJS 10 · TypeORM · PostgreSQL 15 · scheduled jobs
Frontend
React 18 · Vite · Tailwind CSS · TanStack Query
Infrastructure
Elastic Beanstalk · RDS PostgreSQL · S3 · Amazon Textract
Data source
DMS invoiced sales records