Inspiration Exporters often have to compare invoices, shipment paperwork, and incoming payments by hand. When amounts or quantities differ, finance teams can spend hours tracking down the reason. I wanted to build a tool that makes this review easier and keeps the supporting evidence visible. What it does ProcureMind is a prototype for reviewing export documents and payment discrepancies. Users can upload documents, inspect extracted fields, and correct values for human review. A reconciliation worklist demonstrates how a reviewer can investigate a payment difference, inspect its supporting evidence, and record a decision with notes. A PayPal Sandbox flow demonstrates approval-gated checkout and payment receipts without moving real money.
The current demo shows document extraction and a seeded reconciliation scenario separately; linking newly uploaded documents directly into reconciliation is a next step. How I built it I built the frontend with Next.js, TypeScript, Tailwind CSS, and shadcn/ui. AG Grid presents the reconciliation worklist, while TanStack Query handles API data. The backend uses Python, FastAPI, Pydantic, and SQLAlchemy, with PostgreSQL as the source of truth for records and reconciliation results.
For document processing, I used tools such as PyMuPDF, pdfplumber, openpyxl, and pandas, alongside structured extraction and validation. PayPal Sandbox provides the test payment flow. I designed the system to keep human review in the loop for corrections and financial decisions. Challenges I ran into A major challenge was keeping financial comparisons precise and explainable. Extracted values need to be reviewed against their source documents, and payment amounts must be compared carefully with currency and fees taken into account. I also had to distinguish a real payment workflow from a Sandbox demonstration and avoid presenting seeded data as if it came from a user’s uploaded documents. Accomplishments I’m proud of I brought document review, reconciliation evidence, human decision recording, and a Sandbox payment demonstration into one product experience. I’m especially proud of making discrepancies reviewable: users can see the figures being compared and the evidence behind the result. What I learned I learned that document extraction alone doesn’t complete a reconciliation workflow. Documents, trade records, and payment records must be linked before their values can be compared meaningfully. I also learned that financial software should make uncertainty visible and leave approval decisions to people. What’s next for ProcureMind I plan to connect uploaded commercial invoices and supporting shipment documents to reconciliation records, add more payment evidence sources, and explore an accounting integration such as Zoho Books. I also plan to improve OCR reliability, expand evaluation with representative sample documents, and prepare a deployed demo for reviewers.
