Fix Billing Software Data Issues
Budget: ₹1,500 – ₹12,500 INR
Our in-house desktop billing application has started showing serious data problems—duplicate records pop up, figures drift between screens, and every so often a line item appears that nobody entered. My priority is to uncover the root cause of these inconsistencies, then clean up the database and stop the duplicates for good.
What you can expect when you come in: I will give you remote or on-site access to the application, its executables, and the current database dump. The codebase is legacy; language, framework, and DB engine still have to be confirmed, so part of the assignment is to inspect the binaries, identify the tech stack, and map out the architecture before any fixes are applied.
Deliverables
• Detailed diagnostic report pinpointing why duplicates and mismatches occur, including any schema or transaction-level issues
• Action plan for repairing the existing dataset without data loss
• Implemented fix that removes current duplicates, prevents new ones, and logs any inconsistent input attempts
• Integrity audit results with tests or scripts I can rerun after future updates
Acceptance criteria: no duplicate record can be reproduced under normal user workflows; cross-checked fields (totals, item counts, timestamps) must stay in sync across every module; and the audit script returns a clean result on two consecutive business days.
If you have solid experience reverse-engineering desktop business apps and tightening database integrity, I’m ready to start as soon as you are.
What you can expect when you come in: I will give you remote or on-site access to the application, its executables, and the current database dump. The codebase is legacy; language, framework, and DB engine still have to be confirmed, so part of the assignment is to inspect the binaries, identify the tech stack, and map out the architecture before any fixes are applied.
Deliverables
• Detailed diagnostic report pinpointing why duplicates and mismatches occur, including any schema or transaction-level issues
• Action plan for repairing the existing dataset without data loss
• Implemented fix that removes current duplicates, prevents new ones, and logs any inconsistent input attempts
• Integrity audit results with tests or scripts I can rerun after future updates
Acceptance criteria: no duplicate record can be reproduced under normal user workflows; cross-checked fields (totals, item counts, timestamps) must stay in sync across every module; and the audit script returns a clean result on two consecutive business days.
If you have solid experience reverse-engineering desktop business apps and tightening database integrity, I’m ready to start as soon as you are.