How does a small business track who owes money (an AR tracker)?

The short answer

A small business tracks who owes money with an accounts receivable tracker: one list of every open invoice with the customer, amount, due date, days overdue, the last contact and the next follow-up date, grouped into aging buckets. Each overdue invoice gets an owner and a follow-up step on a fixed schedule, and promises to pay and disputes are logged so nothing is chased twice or forgotten.

A small business tracks who owes it money with an accounts receivable tracker: one list of every open invoice, showing the customer, invoice number, amount, due date, days overdue, who owns the follow-up, the last contact, and the next follow-up date, grouped into aging buckets so the late money is impossible to miss. Each overdue invoice moves through the same follow-up steps on a fixed schedule, from a friendly reminder to a call to an owner's escalation, and every promise to pay and every dispute is logged so nobody chases a customer who already paid or forgets one who said "next Friday." Your accounting software stays the record of what was invoiced and paid. The tracker is where the collecting happens.

Most small businesses collect today from a printed aging report, a bookkeeper's memory and an inbox. The work gets done in bursts, usually when cash is tight, which is the worst possible time to discover that a big invoice went out to the wrong contact six weeks ago.

Why money stays out longer than it should

Nobody owns the follow-up. The bookkeeper thinks the project manager will mention it; the project manager thinks the bookkeeper is on it.
Follow-up happens in bursts. Invoices get chased at month-end, not on a schedule, so a late invoice can sit for weeks.
Context is scattered. The customer said the invoice was short a PO number. That conversation is in one person's email.
Promises are not tracked. "We'll pay on the 15th" is worth something only if someone checks on the 16th.
Disputes block payment silently. A customer who disagrees with a charge often just does not pay, and nobody fixes the charge.
It is tedious. A Zapier survey of businesses with up to 250 people found repetitive tasks take an average of 17.3 hours a week. Chasing payments is among the most repetitive work in any office.

What the tracker should contain

Each open invoice

Customer and billing contact (name, email, phone).
Invoice number, invoice date, due date and amount.
Amount paid so far and balance due.
Days overdue and aging bucket, calculated automatically.
Job, project or order the invoice relates to.
Owner of the follow-up.
Status (see below).
Next follow-up date.
Promise-to-pay date and amount, if any.
Dispute reason and resolution, if any.
A log of every contact: date, method, who, and what was said.

Each customer

Payment terms.
Billing contact and any accounts payable contact on their side.
Required details for their invoices, such as PO numbers.
Total balance and oldest open invoice.
Payment history: average days to pay, broken promises.
A hold flag: whether new work requires payment first.

Aging buckets

Bucket	What it usually means	Typical next step
Not yet due	Sent, inside terms	Friendly reminder a few days before the due date
1 to 30 days	Late, often an oversight	Email the day after due; call at two weeks
31 to 60 days	Late enough to be a pattern or a problem	Call the billing contact and their payables team; confirm there is no dispute
61 to 90 days	Serious	Owner or manager contacts the customer; consider holding new work
Over 90 days	At risk of never being collected	Owner decides next steps with your accountant or attorney

Adjust the buckets to your terms. A company on net 15 will want tighter steps than one on net 60.

Statuses

Open: sent, not yet due.
Reminder sent: the pre-due or day-after note went out.
In follow-up: someone is actively chasing.
Promised: the customer committed to a date and amount.
Disputed: the customer disagrees with part or all of the invoice.
Escalated: handed to the owner or a manager.
Paid: balance is zero; kept for history.
Written off: your accountant has advised removing it from receivables.

The follow-up schedule

Write it once and apply it to every invoice.

Three days before the due date: a friendly reminder with a copy of the invoice and how to pay.
The day after the due date: a short note that the invoice is now past due.
Day 14: a phone call. Ask whether there is anything preventing payment.
Day 30: a call to the customer's payables contact, and a check that the invoice reached them with everything they require.
Day 45: the owner or a manager is alerted if the balance is over your threshold.
Day 60: decide whether new work for this customer is on hold until the balance is cleared.

A broken promise resets the clock: the day after a missed promise date, the invoice goes straight to a call, and a second broken promise alerts the owner.

Handling disputes

Disputes are where receivables quietly rot. Treat them as their own small workflow.

Log the reason in the customer's words.
Assign an owner who can fix it: the project manager for a scope question, the office for a missing PO number.
Set a resolution date.
Split if you can. If only one line is disputed, ask for payment on the rest.
Close it with a note of what was agreed, so it never comes back.

Roles

Office or AR staff see every open invoice, log contacts and promises, and send reminders.
Project or account managers see their customers' balances and disputes, and are asked to help when a dispute is about the work.
Owner sees everything, including escalations and the weekly summary.
Sales may see whether a customer is on hold before quoting new work, without seeing every balance.

Receivables are sensitive. A customer's balance, a dispute note or a promise to pay is not something every employee should see, so set roles deliberately.

Trusting the numbers

Owners rightly ask whether numbers in a tool built by someone other than an accountant can be trusted. Three rules keep the tracker honest:

One source for invoices and payments. Your accounting system remains the record of what was invoiced and paid. The tracker reads from it or is updated from it on a schedule; it does not invent balances.
Check totals against the accounting system weekly. The tracker's open total and the accounting aging total should match. If they do not, find out why before you chase anyone.
Test the calculations before launch. Pick ten invoices and confirm days overdue, buckets and balances by hand. In the 2025 Stack Overflow Developer Survey, 66% of developers named "AI solutions that are almost right, but not quite" as their top frustration with AI tools. Almost right is not good enough for money.

Connecting systems is where most small companies struggle. In MuleSoft's 2022 Connectivity Benchmark, only 37% of IT leaders said they completed every project asked of them the year before. Keeping the tracker's job narrow, the follow-up work, makes the connection simple.

Reports

Aging summary by bucket, with totals.
Promises due this week and broken promises.
Disputes open, by owner and age.
Top ten balances and oldest invoices.
Days to pay by customer, to spot who is getting slower.
Weekly owner summary: total open, total over 60, collected this week, escalations.

Example request

Example request: "Build an accounts receivable tracker for our 30-person landscaping and snow removal company. Each open invoice has customer, billing contact, email, phone, invoice number, invoice date, due date, amount, amount paid, balance, job, follow-up owner, status, next follow-up date, promise date and amount, dispute reason and resolution, and a contact log with date, method, person and notes. Calculate days overdue and aging bucket automatically: not yet due, 1 to 30, 31 to 60, 61 to 90, over 90. Statuses are open, reminder sent, in follow-up, promised, disputed, escalated, paid and written off. Remind the follow-up owner of each step: three days before due, the day after due, day 14, day 30. Alert the owner when an invoice over $2,500 reaches 45 days, or when a customer breaks a promise twice. Each customer has terms, required invoice details, total balance, average days to pay and a hold flag. Office staff see everything; account managers see only their customers; sales sees only whether a customer is on hold. Email the owner a summary every Monday. Roles are owner, office, account manager and sales. Only invited people can sign in. We will load open invoices from a CSV export of our accounting system each morning."

How to roll it out

Load every open invoice from your accounting system.
Assign an owner to every invoice over 30 days.
Set the next follow-up date on each one. The first week will be busy.
Agree the schedule with whoever does the chasing, and write the reminder templates together.
Run it for a month, checking totals against the accounting system weekly.
Add account managers for disputes once the office is comfortable.

Mistakes to avoid

Treating the tracker as the books. It is the follow-up tool. The accounting system is the record.
No owner on an invoice. Unowned invoices age.
Chasing without context. Read the contact log before every call.
Ignoring disputes. A disputed invoice is not going to pay itself.
Holding work too late. Decide the hold rule in advance, not in the middle of an argument.

How to measure that it works

Compare with the three months before launch:

Average days to collect (sometimes called DSO).
Total over 60 days, and over 90.
Promises kept versus broken.
Disputes resolved within two weeks.
Office hours spent on collections.

How FORGE handles it

On FORGE, your office manager or bookkeeper describes the tracker in plain words, like the example above, and FORGE builds it. A panel of top AI models plans the tool, a dedicated AI crew builds it, and every piece is checked for quality and security before it is saved. Most teams have their first real tool the same day, and the follow-up schedule starts working on the first morning's list.

Every app lives inside your company and people join only by invite. Office staff, account managers and sales each see only what their role allows, and there is a complete record of every contact, promise and status change. Staff who only work the list are $10 a user a month, builders are $49 a seat a month with 3 builds included, and nothing extra is ever charged without your OK. Our team onboards every company, starting with a workflow workshop to find where your cash is waiting longest. Talk to us or see pricing.

Questions people ask

What is accounts receivable?

Accounts receivable is the money customers owe you for work or goods you have already delivered and invoiced. It sits on your books as an asset, but it only helps cash flow once it is collected.

What is an AR aging report?

An aging report groups unpaid invoices by how long they are overdue, usually current, 1 to 30 days, 31 to 60, 61 to 90 and over 90. It shows at a glance how much is late and how late, so you know where to focus.

Doesn't our accounting software already do this?

Your accounting software holds the invoices and the aging report. What it usually does not hold well is the follow-up work: who called, what the customer said, the promised payment date, the dispute, and the next step. An AR tracker keeps that work in one place, while your accounting system stays the record of what was invoiced and paid.

How often should we follow up on overdue invoices?

On a fixed rhythm, such as a friendly reminder a few days before the due date, a note on the day after, a call at two weeks and an escalation at 30 days. The exact schedule matters less than applying it to every invoice, every time.

When should an owner get involved in collections?

Set a rule, such as any invoice over a set amount that is more than 45 days late, or any customer who breaks a promise to pay twice. A short weekly look at the over-60 list keeps big problems from becoming bad debt.

How does FORGE help with receivables?

Your office or finance lead describes the tracker in plain words and FORGE builds it, with follow-up dates, promises to pay, dispute notes and weekly reports. Roles keep amounts visible only to the people who should see them, and there is a complete record of every contact.

See what FORGE builds for your team

We onboard every team ourselves, starting with the work that costs you the most time.

Talk to us