Build Accounts Receivable Module

I’m extending our existing web-based application to cover the full accounts-receivable cycle. The new module must sit inside the current web app, so please plan your code to use the same tech stack, database, and authentication flow that is already in place.

Core workflow
• Finance reviews each quotation request that the team already creates in the system.
• From that same screen Finance can produce a Invoice from system or from other application and upload the invoice against that quotation request and choose the due term (Net 0, 10, 30, 60, 90, 120). Support team will review it and click to send the invoice to client from application.
• Issued invoices appear in a master list; any request that is still “uninvoiced” lives on its own page for quick follow-up.
• A client-level aging page shows open balances bucketed by due days.
• The dashboard contains 13 summary cards (current month + 12-month look-ahead) that total the amounts we expect to collect each month.

Payment receipt flow
When a client pays, Finance / operations opens a simple form, enters the receipt details, uploads the receipt file, and submits. The system then emails all confirmation with the attachment of the day, directly to our finance mailbox.

Reports required (exportable to PDF and Excel)
• Aging report
• Monthly expected amount report
• Payment receipt report
• Statement of account
• Payment history

Acceptance criteria
1. All screens match the wireframes I’ll supply and are fully responsive.
2. Emails and PDFs use the company letterhead template I’ll provide.
3. Calculations for aging buckets and monthly forecasts reconcile with a sample data set I’ll share.
4. Code is clean, commented, and pushed to our private Git repo with a brief deployment read-me.