Case Study

QuickBooks IES
Data Auditor

View Source Live Demo View Gallery

The Discovery

Importing Data on QuickBooks is Problematic

While using Discord Webhooks to scan subreddit threads for key action words, I stumbled across a pattern of frustrated users on reddit complaining about Intuit Enterprise Suite (IES) migrations. Users were reporting corrupted data upon import, not realizing that specific fields had a hidden 41-character cap.

The documentation was sparse. People were manually checking thousands of rows in Excel. I figured I could build something to address this.

The Purpose

Preventing data loss in enterprise migrations.

The Friction

If a legacy database has 45 characters, QuickBooks simply cuts it off without warning. Without an auditor, you have no idea if your data migrated correctly.

The Solve

A Python engine that uses PRAW to scrape community-discovered constraints and runs a normalization pass on your data, flagging violations before the import ever happens.

Technical Snapshot

Language

Python 3.11

Scraper

Reddit PRAW

Logic

Pandas/Regex

Deployment

Streamlit