AI Invoice Processing and Dealer Management System AutomationAI Invoice Processing and Dealer Management System Automation
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Built an AI system that reads supplier invoices and posts them straight into a dealer management system. No one retypes anything anymore. The problem: a group of car dealerships was getting hundreds of supplier invoices by email and WhatsApp photos, and staff were keying every line into their DMS by hand. What I built: • Email and WhatsApp intake, auto-matched to the right dealership • AI and vision extraction of vendor, tax details, and line items grouped by vehicle • Verification and duplicate detection before anything gets posted • A review dashboard for the few cases that need a human • Browser automation that posts approved invoices into the DMS • WhatsApp auto-replies that chase suppliers for missing details Result: 280+ invoices processed so far, with zero exceptions. Stack: Python, LLM and vision models, React, Selenium If your team is still copying data from documents into another system, that's usually very automatable. Happy to take a look at yours. #AI #Automation #AIAgents
Post image
Timothy's avatar
280+ invoices with zero exceptions is the number that sells this. The WhatsApp intake auto-matched to the right dealership is smart, and keeping a review dashboard for the edge cases shows you trust the system without being naive about it.
SHAH's avatar
Thanks, really appreciate that! The review dashboard was a deliberate choice. The AI handles the bulk with confidence, but blurry photos and odd supplier formats still happen, so a human signs off on those in seconds instead of bad data slipping into the books. Trust the system,...
Mojtaba's avatar
The duplicate detection and review dashboard are the right instincts. The failure I'd guard hardest is the confidently-wrong field: a total or tax that parses cleanly but reads the wrong number, since it never looks low-confidence enough to reach your dashboard. What saved me...
SHAH's avatar
Great point, and yes, that's exactly the failure that worries me most. A clean parse with the wrong number never looks risky. So we don't trust the model's field read alone. Before posting, line items have to sum to the subtotal, and the tax has to match rate times base. Any...
Kapil's avatar
I'd test a DMS timeout immediately after the invoice saves, since Selenium can lose the confirmation even when the entry exists. Before retrying, does your flow check the dealership, supplier and invoice number in the DMS so it can recover without posting twice?
SHAH's avatar
Spot on, that's exactly the failure that would bite. Before any retry, the flow searches the DMS for that dealership, supplier and invoice number. If the entry is already there, it marks the invoice as posted and moves on instead of posting it again. Only a confirmed miss...
Yonatan's avatar
The WhatsApp auto-replies that chase suppliers for missing details are the piece I like most, since that closes the loop instead of just flagging a gap. How do you decide when a missing field gets an automatic chase versus going to the review dashboard for a person?
SHAH's avatar
Thanks, that loop was the whole point. A flag nobody acts on just moves the backlog somewhere else. The rule is simple. If the supplier is the only one who can fix it, like a missing invoice number, tax ID or an unreadable photo, it gets an automatic WhatsApp chase. If it needs...
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started