FinanceWindows app
Monthly Order Reconciliation Helper
Auto-match order exports with bank statements by order ID. Cut monthly reconciliation from two days to one hour.
The problem
Every month, finance exports orders and compares them line-by-line to bank statements. Hundreds to thousands of rows, manual VLOOKUP, high error rate, and late-night follow-ups.
The solution approach
A local Windows app. Drop both Excel files in, click "Reconcile", and it matches by order ID and amount. Matched rows checked off; mismatches land in a separate table with the diff and likely reason. Seconds per run.
What you will end up with
- A clean Windows desktop app — double-click to launch.
- Two big buttons on the home screen: "Import order Excel" and "Import bank Excel". Drag-and-drop works too.
- Header preview after import so you can confirm correct columns.
- Reconcile triggers a progress bar; totals appear afterwards.
- Footer button exports mismatches as "diff-YYYY-MM.xlsx".
- Runs entirely on your PC. No data leaves the machine.
Ready-to-use prompt
You are a senior engineer experienced with Windows desktop apps. Build a local Windows desktop tool for the finance team at an e-commerce company. The user is a non-developer.
[Goal]
Replace 1-2 days of monthly manual reconciliation with a tool that matches orders to bank statements and exports mismatches in a few clicks.
[Platform & Stack]
- Platform: Windows 10 / 11 desktop app
- Framework: Electron + React + TypeScript
- Spreadsheet parsing: SheetJS
- No servers, no network required
- Deliver a Windows .exe installer
[Core Features]
1. Home screen with two prominent buttons: "Import Orders Excel" and "Import Bank Excel". Drag-and-drop works.
2. After import, show headers and first 5 rows. Let the user pick "Order ID" and "Amount" columns from dropdowns. Remember and pre-fill next time.
3. "Reconcile" button triggers a progress bar. Rule: order ID as key; difference <= 0.01 = match; else mismatch.
4. Results page has two panes. Left: matched count, mismatched count, match rate, total amount. Right: a mismatch table with order ID, order amount, bank amount, diff, reason (amounts differ / missing in bank / missing in orders).
5. "Export mismatches to Excel" with default filename "diff-YYYY-MM.xlsx".
6. Fully offline; no uploads.
[Visual Style]
- Minimal: white background, generous whitespace, rounded cards, large type.
- Primary button: muted dark. Secondary: light gray.
- Follows Windows light/dark setting.
- Use system fonts (Segoe UI / Microsoft YaHei). No web fonts.
[Robustness]
- On invalid file formats, show a friendly message, not a raw stack trace.
- If field auto-detection fails, prompt for manual selection instead of crashing.
- Handle tens of thousands of rows; batch processing for > 100k with progress.
- Ship 2–3 anonymized sample files so new users can see it work immediately.
[Delivery]
1. First, outline the project structure and a plain-text wireframe. Wait for my confirmation.
2. Deliver in modules; run each one and show me.
3. Final step:
- Package as a Windows .exe installer.
- Write a 500-word plain-language user guide covering Install -> First run -> Common issues.
- List known limitations and future improvements.
[Working Style]
- Advance one thing at a time. Ask me if unsure.
- Use placeholders like {{COMPANY_NAME}} for personal details; summarize items to replace at the end.
Please start with step 1: structure and wireframe.After copying
1
Open Codex Desktop and create a new project
2
Paste the prompt and send
3
Wait for Codex to finish; tweak company names, column names, button text as needed