How to manage accounts receivable early

Accounts receivable for startups is the money customers owe you on invoices that are Sent but not fully Paid. Managing it early means a named owner, an aging board you open every week, and honest Record Payment entries so cash stories stay true. Nautis Invoices tracks status, due dates, and aging; it does not send dunning email automatically. This is operating practice, not accounting or legal advice. Confirm revenue recognition and collections wording with your CPA or counsel when deals get complex.

What accounts receivable for startups actually covers

AR is not "we have pipeline." It is open invoice balances after you Mark as Sent or send from Invoices. Draft invoices are not AR yet. Cancelled invoices leave the working set. Paid means the balance is zero after Record Payment entries.

Early teams mix three clocks:

1. Booked revenue stories from CRM.
2. Invoices Sent with a Due Date.
3. Cash that hit the business bank account.

Accounts receivable for startups lives on clock two and only becomes cash on clock three. Treat the gap as a work queue, not a vanity total. Write the definition on the aging Note: AR equals open balances on Sent or Overdue invoices in Invoices, nothing else. That sentence stops sales from arguing that verbal commitments belong on the board.

Illustrative miss (composite only): a founder quoted "we're fine on cash" from Sent invoices totaling $40,000 while $28,000 sat Overdue. Runway math used hope. After Record Payment hygiene and a collection week, real cash was half the slide.

Build an aging board before you chase anyone

Sort open invoices by how late they are relative to Due Date. Keep buckets simple.

Use Invoices filters and the overdue count badge in the sidebar to find the queue. Analytics can show aging analysis; still paste the board into a Note so the owner cannot hide behind charts.

Name one human owner for the board. Shared "someone will chase" ownership is how 61+ rows grow quietly. Give the owner authority to send the first reminder without a meeting. Escalations that need a founder should be listed in the 31-60 playbook so Tuesday does not become a debate club. If the owner is out, name a deputy on the same Note.

Rules that keep the board honest

• Every open invoice has a Due Date you meant.
• Partial payments are recorded with Record Payment the day cash arrives; do not wait for a full Paid flip to log money.
• Promises from customers get a dated Note on the invoice trail, not a memory in Slack.
• Do not delete Overdue invoices to clean the badge. Cancel only when the deal is truly void.

Weekly collection cadence (thirty minutes)

Same day each week. Same agenda.

Minute 0-5: open Invoices, filter to Sent and Overdue, refresh the aging board counts. Minute 5-15: send reminders from the invoice page for every 1-30 item without a promise date. Nautis does not dunning-email automatically; you choose when to remind. Minute 15-25: work 31-60 and 61+ with escalations already written in a short template. Minute 25-30: Record Payment for any cash that landed; confirm statuses moved toward Paid.

Carry unfinished escalations as the first lines next week. Do not open new customer work in the same thirty minutes; the cadence fails when it becomes a general sales meeting.

If the queue is empty, still open the view. Empty is a result worth seeing. Track two numbers each Tuesday: overdue count from the sidebar badge, and total open AR dollars from the filtered list. Put both on the Note. Dollar total without age lies; age without dollars hides material risk.

When a customer asks for a PDF again, download it from the invoice rather than exporting a side copy that drifts. One system of record keeps Record Payment and status aligned.

Illustrative cadence (composite only): Tuesday 9:00, ops lead, twelve open invoices, three Overdue. Two reminders go out, one partial Record Payment lands from a wire that arrived Monday, one 61+ account gets a stop-work note pending founder approval.

Tie AR to cash without double counting

When you update Startup Health, Cash Balance is month-end bank cash, not open AR. Do not pad runway with unpaid invoices. For burn and runway definitions, see How to calculate startup burn rate and runway.

Accounts receivable for startups still belongs next to cash planning: list expected collections for the next four weeks with probability only if you have a written promise date. Unpromised Overdue amounts stay at zero in that forecast. If fundraising decks need a collections outlook, show promised amounts separately from unpromised Overdue. Mixing them recreates the illustrative miss above. Investors who care about cash will ask which invoices already cleared the bank.

Partials and credits

Recording a payment reduces the balance; full payment flips status to Paid. Partial payments stay visible in the invoice activity timeline. If you issue a credit note, follow the invoice credit flow rather than editing history in a spreadsheet that diverges from Invoices.

Terms and stop-work that prevent new debt

Write payment terms on the invoice before Mark as Sent. Net-30 that nobody reads still becomes AR. For early startups, shorter terms on first invoices often beat heroic collections later.

Stop-work policy (plain language):

1. Who can pause delivery when an invoice hits 31-60.
2. What the customer hears in one short paragraph.
3. Who must approve exceptions.

Illustrative policy line (composite only): "At 45 days Overdue we pause non-critical roadmap work for that account until Record Payment covers the balance or a founder signs a dated exception."

Without a stop-work rule, collections become optional manners. With one, AR stays a queue with consequences. Sales must see the rule before they discount terms in email. Changing Due Dates after Mark as Sent to dodge Overdue badges is not a strategy; it breaks the aging board. If terms genuinely change, edit with a Note saying why and who approved.

Illustrative eight weeks at Maple Metrics

Illustrative Maple Metrics (composite only): B2B SaaS, founder-led sales, invoices from Nautis.

Week 1: aging board created; nine invoices Current, two in 1-30. Week 2: weekly cadence starts; both Overdue get reminders from the invoice page. Week 3: one customer pays in full (Record Payment to Paid); one promises Friday (dated Note). Week 4: promise slips; move to 31-60 playbook; pause a non-critical integration task. Week 5: partial wire recorded; balance remains visible. Week 6: remainder Paid; stop-work lifted. Week 7: new invoices ship with clearer Due Dates and shorter terms for first-time buyers. Week 8: overdue badge stays at zero for two Tuesdays; Cash Balance in Startup Health finally matches the story founders tell.

They did not buy a separate AR suite. Accounts receivable for startups here was the board, the cadence, and Record Payment discipline. Maple also stopped creating invoices in Draft and leaving them for weeks. Draft is for preparation; AR starts when the invoice is Sent or marked as Sent after delivery outside the email path. That single habit cut fake urgency on the board.

Failure modes and when to get help

• Calling CRM "Commit" amounts AR.
• Leaving payments in the bank unrecorded so invoices stay Overdue forever.
• Sending soft reminders forever with no stop-work.
• Letting sales mark invoices Paid in chat without Record Payment.
• Building a parallel spreadsheet that disagrees with Invoices statuses (Draft, Sent, Paid, Overdue, Cancelled).

Bring a bookkeeper or CPA into collections wording, revenue recognition, and bad-debt decisions when balances get material. The product still needs a founder-owned weekly cadence so the queue does not wait on month-end archaeology.

If you outsource chasing later, hand the vendor the aging board, the stop-work rule, and view access to Invoices. Do not hand them a private sheet that disagrees with statuses. Their first Tuesday should look like yours: badge, board, reminders, Record Payment.

International invoices may add tax lines and currency. Keep Tax Name and Tax Rate aligned with advisor notes, and still age by Due Date in the same board so collections does not fragment into special cases that never get owned.

Accounts receivable for startups stays healthy when Current stays dull, Overdue stays small, and every dollar that arrives shows up as Record Payment the same day. Revisit the board design when you add your first reseller or annual prepaid deal. Prepaid that is fully paid up front should hit Paid quickly; usage true-ups need their own Due Dates so they do not sit unmarked. Keep the weekly thirty minutes even when the badge is green. Green weeks are how you notice the first slip.