Track outstanding invoices and bills by vendor with due dates, aging categories, and payment scheduling for cash flow management.
You type in each unpaid bill - vendor, invoice number, amount, and due date - and the tracker measures every due date against today's date to sort invoices into aging buckets: current, 1-30, 31-60, 61-90, and 90-plus days past due. It then totals what you owe by vendor and by bucket, so you can see both total exposure per supplier and how much of your payables are overdue. The thing people miss most: aging recalculates off the date on their own device, so a wrong system clock or a typo in a due date silently reshuffles every bucket without any error message.
A concrete input and expected output from the current implementation.
Input
Vendor A, INV-101, $1,200.00, due 2026-07-01 Vendor B, INV-102, $450.00, due 2026-08-10 Vendor C, INV-103, $3,000.00, due 2026-09-05
Expected output
As of 2026-08-15: INV-101 (Vendor A): 45 days past due -> 31-60 bucket INV-102 (Vendor B): 5 days past due -> 1-30 bucket INV-103 (Vendor C): due in 21 days -> Current By bucket: Current $3,000.00 | 1-30 $450.00 | 31-60 $1,200.00 | 61-90 $0.00 | 90+ $0.00 By vendor: Vendor A $1,200.00 | Vendor B $450.00 | Vendor C $3,000.00 Total outstanding: $4,650.00
July 1 to August 15 is 45 days, placing INV-101 in the 31-60 bucket; August 10 to August 15 is 5 days, placing INV-102 in the 1-30 bucket; September 5 is still 21 days away, so INV-103 sits in Current. The three amounts sum to $4,650.00.
Each invoice's due date is compared against the current date to get days past due, or days remaining if it isn't due yet. That figure places the invoice into a bucket - current, 1-30, 31-60, 61-90, or 90-plus days overdue - the same bracket structure used in standard AP aging reports, and it recalculates every time the page is loaded or a date is edited.
Invoice amounts are summed two ways: by vendor, so you can see total exposure to any single supplier, and by aging bucket, so you can see how much of total payables is current versus overdue. Payment scheduling draws on the same due-date field to surface what's coming due soonest.
No. It only works from whatever invoices you enter in the browser during that session. There's no integration with accounting platforms, so it won't reflect payments or new bills recorded elsewhere until you update the entries here yourself.
Calendar days. The gap between a due date and today includes weekends and holidays, which matches the standard convention for AP aging schedules, but it means an invoice due right before a weekend can look more urgent than it is by Monday.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Calculate gross, operating, and net profit margins from cost and revenue with breakeven analysis.
Convert between annual salary and hourly rate with adjustments for work hours, overtime, and benefits.
Calculate sales tax amounts, tax-inclusive and tax-exclusive prices for any tax rate or jurisdiction.
Calculate return on investment from initial cost and final value with annualized ROI and comparison tables.
Convert between markup and margin percentages, calculate selling price, and compare pricing strategies.
Convert numeric amounts to written words for invoices, checks, and legal documents in multiple currencies.