What Is Chase This First? A Rule-Based Way to Rank Overdue Freelance Invoices

TL;DR. Chase This First is the rule-based ranker on FreelancerFlow's Money tab that orders every outstanding item — overdue invoices, accepted-but-unbilled quotes, unpaid invoices, due-soon invoices, and drafts you forgot to send — by a single multiplicative score: amount × ageCoeff × bucketWeight. The top five surface with a suggested action. Rules, not predictive AI. The 90-second Friday read is: open Money tab, glance at the top of the list, take the suggested action on item one, leave the rest until next week.

By FreelancerFlow · 8-min read

The Monday-morning problem

It is Monday, 8:47 a.m. A solo designer opens Gmail and sees three overdue invoices waiting: $5,400 sent 38 days ago, $620 sent 28 days ago, $1,200 sent 12 days ago. She freezes for a moment, then reaches for the client who emailed last Friday — the $1,200 one. By 9:15 the email is sent. By Friday the $5,400 invoice has aged another week with no follow-up.

That default move — chasing the loudest invoice — is what most solo freelancers do under pressure. The loudest is the client most recently in your inbox, not the one whose unpaid balance is doing the most damage to your cashflow. The data backs this up indirectly: the Freelancers Union Freelance Isn't Free research [3] documents how often payment culture, not freelancer effort, decides when invoices land — and the structural fix is process, not nagging.

<a id="chase-this-first-definition"></a>Chase This First is the rule-based ranker FreelancerFlow ships on the Money tab to make this decision for you. It scores every outstanding item by three factors, sorts descending, surfaces the top five, and tells you what to send. No prediction. No language model. Arithmetic you can recreate on paper.

The rest of this article walks through what the three factors are, how they combine, the five buckets the ranker runs across, a worked example with five real invoices, the 90-second Friday workflow, and what the article is honest enough not to claim. The companion KPI on the same Money tab — Coverage Percentage — measures whether your collection rhythm is matching your billing rhythm; Chase This First is the daily action layer that keeps Coverage healthy.

Why "chase the oldest" and "chase the biggest" both miss

Two naïve heuristics circulate in freelance advice columns. Both lose more often than they win.

Chase the oldest. Seductive because aging feels like a clean signal. The problem: time alone doesn't capture leverage. A $200 invoice 45 days overdue carries less cashflow consequence than a $5,000 invoice 22 days overdue, but the oldest-first rule sends you chasing the smaller one first. Worse, it lumps unsent drafts into the same queue as overdue sent invoices, which is a different conversation entirely.

Chase the biggest. Equally seductive because dollars feel like a clean signal. The problem: amount alone doesn't capture urgency. A $5,000 invoice due tomorrow is not yet a collection problem; a $1,200 invoice 41 days overdue with the same client almost certainly is. The biggest-first rule chases the wrong frame.

The fix is to multiply both factors and add a third — the invoice's status. That is the Chase This First formula.

The three factors behind Chase This First

The ranker shipped in Build 11 multiplies three factors per outstanding item. The factors come from the actual iOS code path in MoneyAIPrioritizer.swift; the values below are the shipped numbers, not editorial inventions.

Factor 1 — Invoice amount (the leverage factor)

The raw dollar size of the outstanding balance, in your primary currency. Larger invoices contribute proportionally larger scores — a $4,000 invoice contributes twice as much as a $2,000 one at equal age and equal bucket. Amount enters linearly; there is no log-scaling or amount tier.

Edge case worth knowing: a small invoice can still top the list if it's old enough. A $200 invoice 60+ days overdue with the overdue bucket weight (1.5) often beats a fresh $2,500 draft (bucket weight 0.5) once the age coefficient compounds. Small-and-old is not automatically safe.

Factor 2 — Age coefficient (the time-decay factor)

A multiplier that grows linearly with days past due, capped at day 60.

ageCoeff = 1.0 + min(daysOverdue, 60) ÷ 30

At day 0 (just due) the coefficient is 1.0. At day 30 it's 2.0. At day 60 it's 3.0. After day 60 it stops growing — a 90-day invoice scores the same on the age dimension as a 60-day one. The reasoning: by day 60 you've already crossed into escalation territory; the formula isn't pushing you to escalate harder. That decision has moved off the score and onto your judgement.

For invoices that aren't yet overdue (due-soon and unpaid), daysOverdue is treated as zero, so the age coefficient stays at 1.0. The bucket weight (Factor 3) carries those items through the ranker.

Factor 3 — Bucket weight (the urgency factor)

A status-based multiplier across the five Outstanding buckets:

Overdue is the heaviest bucket because the deadline has passed; the freelancer's leverage is also at its highest there. Accepted-but-unbilled sits just below — an accepted quote you forgot to convert is silent revenue evaporating, and the ranker treats it almost as seriously as an overdue invoice. Drafts get the lightest weight because the freelancer is the only blocker; the action there is "send the invoice you forgot to send."

The formula in one line

Score = amount × ageCoeff × bucketWeight
ageCoeff = 1.0 + min(daysOverdue, 60) ÷ 30

Multiplicative, not additive. None of the three factors is zero-sum — large amounts and old ages and overdue status compound. That is the lift the formula provides over picking one rule.

The in-app reasoning sheet says it verbatim: "Items are ranked by amount × age, weighted by status. Overdue and accepted-unbilled outweigh due-soon and drafts." If you ever want the one-sentence version, that is it.

How we analysed this. The three factors and the bucket weights in this article are read directly from the Build 11 iOS source — MoneyAIPrioritizer.swift lines 60–77. The age coefficient and the 60-day cap come from the same file. The 30-day overdue → escalate threshold comes from the bucket+age → action mapping in lines 80–89. This article does not editorialise the math; it documents what ships. Version 1.0, 2026-06-24.

The 5 buckets the ranking runs across

A common misread of Chase This First is that it's an overdue-only list. It isn't. The ranker scores every item in every bucket and sorts them together. That matters because the top of the list often surprises you — an accepted-but-unbilled quote can beat a fresh overdue invoice; a draft you forgot can outrank a small overdue one.

The five buckets above are the actual scope. They mirror the Outstanding bucket explained Help article one-for-one. The Outstanding bucket on the Money tab shows the full list grouped by bucket; the Chase This First card above shows the top five ranked across all buckets. Both surfaces share the same underlying outstanding-item array — the difference is presentation: bucket-grouped versus score-ranked-top-5.

The reason for the top-5 cap: this is a Monday-morning decision, not a queue. Five is roughly the upper bound of what a solo freelancer can act on in one sitting without spreading the day's collection energy too thin. The other items live in the Outstanding bucket below, waiting for next Friday's review.

A worked example: five invoices ranked

Maya, a solo designer (the same protagonist from the Coverage Percentage worked example), opens her Money tab at 4 p.m. Friday. Five items in Outstanding. The numbers are real; the score is computed exactly as Build 11 computes it.

The ranking output: Studio Bright → NorthBuild → Quill & Co → Indigo Labs → Patchwork.

The Studio Bright #1 is unsurprising — it dominates on every factor — and that is the point. The framework doesn't manufacture novelty; it stops you missing the obvious answer when the loudest invoice (Quill & Co, the most recent one to email) tries to jump the queue.

The interesting positions are #2 and #3. NorthBuild ($3,800, not yet due) beats Quill ($1,200, 12 days overdue) because amount × bucket-weight on NorthBuild — $3,800 × 0.7 = $2,660 — narrowly edges Quill's $1,200 × 1.5 × 1.4 = $2,520. The multiplicative structure is the reason: status alone doesn't decide, amount alone doesn't decide, both compound. A freelancer who relied on "chase the overdue ones first" would put Quill ahead of NorthBuild and lose roughly equal leverage on a much bigger balance.

The other counter-intuitive move is Patchwork — a $2,100 draft — ranking below Indigo Labs' $620 overdue. The age coefficient and the overdue bucket-weight together more than compensate for the smaller amount. The Draft bucket-weight (0.5) is the framework's way of saying "you forgot to send this, fix it" — but not at the expense of the actually-overdue items.

What Maya does first. Studio Bright is 38 days overdue — past the 30-day threshold — so the suggested action is Escalate: schedule a call, don't just send another reminder. She taps the suggested-action capsule, the Share Sheet opens with a pre-written message asking for a call window. She sends it via Mail in twenty seconds. NorthBuild and Quill (positions 2 and 3) each show Send reminder; Maya can take both, or stop at #1 and revisit next Friday. The whole sitting is less than 90 seconds. Indigo and Patchwork wait.

Chase This First vs. chase-the-oldest vs. chase-the-biggest vs. chase-the-loudest

The accepting hand goes to chase-the-loudest, because it does happen — there are weeks where a client emails about an invoice and the right move is to handle it on the spot. The honest framing: that's a relationship decision, not a prioritisation one. Chase This First handles the prioritisation question; the relationship question is yours.

How to rank your overdue invoices on Friday in 90 seconds

A repeatable weekly ritual. The whole thing is one screen on the Money tab.

How FreelancerFlow handles this. Chase This First is the section header inside the Money tab in Build 11 — the card sits directly above the Outstanding bucket. The three factors combine into a single rank with fixed weighting; there are no sliders or user-editable rules in the current build. Tap any row to open the invoice, share a reminder, escalate, or convert an accepted quote. The full screen-by-screen walkthrough lives at Outstanding bucket explained.

Step 1 — Open the Money tab and find the Chase this first card

The card sits at the top of the Outstanding section. The in-app label is the verbatim lowercase "Chase this first" — the title-case Chase This First is the entity name used throughout this article, and the article's title; they refer to the same surface. Below the title sits a single-sentence summary that names the action to take first (for example: "Send a reminder to chase the highest-impact balance first"). Underneath, the top five ranked items.

Step 2 — Read the suggested action on the top row

Each row carries a suggested-action capsule. The capsule label is one of five:

• Send reminder — opens the iOS Share Sheet with a pre-written reminder. Most overdue (≤ 30 days) and due-soon items.
• Schedule a call — same Share Sheet, different copy. Surfaced when the item is overdue past 30 days.
• Escalate — for items 30+ days overdue when Send reminder has already fired this week.
• Convert to invoice — appears on accepted-but-unbilled quotes; opens the invoice creation flow seeded from the quote.
• Mark uncollectible — manual status change; surfaced only when other actions have been exhausted.

The 30-day Send reminder → Schedule a call shift is the only escalation threshold the formula triggers automatically; everything past day 60 is on you.

Step 3 — Tap to act, then leave the rest until next Friday

Tapping the capsule opens the Share Sheet (for reminders and calls) or the invoice flow (for accepted quotes). The pre-written copy is neutral — "Hi [client], just a note that invoice #123 for $5,400 is currently 38 days past due..." — not accusatory. You pick the channel and send.

After you share a reminder, the capsule dims for seven days on that row. The item still scores and still ranks — the dim is a soft anti-double-send guard, not a hard suppression. The other four items wait until next Friday.

If the suggested action feels wrong — say, you'd rather call than email a long-time client — the score is just telling you the order. The relationship call is yours.

Build 11 quirks worth knowing

Four behaviours that aren't obvious from the card alone and that surprise readers who think the ranker is doing more (or less) than it does.

The age coefficient caps at day 60. A 90-day invoice scores the same on age as a 60-day one. Past day 60, you've already escalated; the formula is no longer the right tool to push harder.

The ranker is currency-blind. Build 11 multiplies the raw amount field; a $3,000 USD invoice and a €3,000 EUR invoice score identically in the formula. If you bill in multiple currencies, the ranking ignores FX exposure as a separate dimension. The Outstanding bucket below displays the native currency per row; the score itself does not normalise.

Drafts appear in the rank with 0.5 weight. An invoice you saved but never sent shows up in the ranker. The suggested action is Send reminder, but the practical meaning is "send the invoice you forgot." It's the framework's way of surfacing your own bottleneck without yelling.

The card hides when nothing is outstanding. Unlike the Coverage Percentage card, which always shows (em-dash when empty), the Chase this first card is conditionally rendered. Empty Outstanding bucket = no card. There is no "all caught up" celebration screen — just absence, which is honest enough.

What this article does not promise

Chase This First ranks overdue invoices; it does not chase them. FreelancerFlow does not send the reminder email, predict which client will pay first, or replace your judgement about which relationships to protect. The three factors ship at fixed weighting in Build 11 — the score is visible and consistent, but not user-tuneable. The app does not draft your dunning copy from scratch, escalate to a collection agency, or advise on late-fee enforcement, which varies by jurisdiction. Chase This First is rule-based, not predictive — the ranker does not learn from your client history, does not predict which clients are likely to pay, and does not auto-send reminders; you tap, you send, you decide. It is a ranker for your Friday review, not a substitute for the conversation.

How FreelancerFlow handles this

In FreelancerFlow, Chase This First lives inside the Chase this first card on the Money tab, directly above the Outstanding bucket, on iPhone and iPad. The score combines three factors — amount, age coefficient, and status bucket weight — and surfaces the top five outstanding items by leverage. Tap a row to open the invoice or share a reminder; the app remembers when you last reminded and dims the action for seven days to stop accidental double-sends. The companion KPI on the same Money tab — Coverage Percentage — measures whether the chase is working. See Outstanding bucket explained for the screen-by-screen walkthrough and Money tab overview for where Chase This First sits in the wider tab.

Try FreelancerFlow free on iPhone and iPad. Seven-day Apple trial — no card required at signup, charged through the App Store after the trial ends.

If the in-app card doesn't fit your workflow, the three factors still apply. You can rank by hand on a notebook: for each outstanding invoice, write down the amount, the days overdue, the status, look up the bucket weight from the table earlier in this article, multiply the three numbers, sort descending. The result is the same ranking, computed the same way. The arithmetic is the framework; the app just saves you the calculator.

Frequently asked questions

How do I decide which freelance invoice to chase first?

Multiply three numbers per invoice: the amount, an age coefficient that grows from 1.0 to 3.0 over 60 days, and a bucket weight that depends on status (overdue 1.5, accepted-but-unbilled 1.2, unpaid 1.0, due-soon 0.7, draft 0.5). The highest score is what to chase first. Picking by amount alone or age alone loses — both rules compound.

Should I chase the biggest or the oldest invoice?

Neither alone. A small invoice that has aged past 30 days can outrank a fresh large one once the age coefficient compounds with the overdue bucket weight. Conversely, a large unpaid invoice that isn't due yet can outrank a smaller overdue one. The multiplicative score resolves the trade-off — that is what Chase This First does.

Is Chase This First an AI feature?

No. Chase This First is rule-based. The three factors — amount, age coefficient, bucket weight — combine into a single fixed-weight score in Build 11. No model is predicting which client will pay. The math is arithmetic you can recreate on paper in two minutes. The app's reasoning sheet labels the panel "AI reasoning" for UI consistency, but the implementation is the deterministic ranker.

How do I prioritise overdue invoices as a freelancer?

Open the Money tab, scroll to the Chase this first card above the Outstanding bucket, and act on the top item only. The card surfaces the top five outstanding items by score. The suggested-action capsule on each row tells you whether to send a reminder, schedule a call, escalate, convert a quote to an invoice, or mark something uncollectible. Move on to next Friday for the rest.

How often should I send a payment reminder?

After you share a reminder for an item, the action capsule dims for seven days on that row — a soft anti-double-send guard. The score still updates as the invoice ages, so the item may resurface at the top of the list next week. Past 30 days overdue, the suggested action escalates from a reminder to a call automatically.

Does FreelancerFlow automatically send invoice reminders?

No. FreelancerFlow does not auto-send anything to your clients. Tapping the suggested-action capsule opens the iOS Share Sheet with a pre-written message; you choose the channel — WhatsApp, Mail, iMessage — and send it yourself. The app ranks; you decide what to send and when.

How do I chase a long-time client without damaging the relationship?

Honest cadence is the relationship preserver, not silence. Use the Send reminder action; the pre-written copy is neutral, not accusatory. Past day 30, switch from email to a call — the suggested action changes from Send reminder to Schedule call for a reason. If the same client surfaces at rank 1 three Fridays running, the relationship is already strained, and the conversation is no longer about a single invoice.

Sources

1. Investopedia, Days Sales Outstanding (DSO) — the corporate-finance lineage of time-decay metrics on accounts receivable. The age coefficient in Chase This First is the freelance-shaped variant of the same time-decay idea. https://www.investopedia.com/terms/d/dso.asp (accessed 2026-06-24).
2. AccountingTools, Collection Effectiveness Index (CEI) — the corporate-finance benchmark for "what share of what you billed has been collected." Chase This First's bucket-weight schedule borrows from the same lineage; the 80% Coverage Percentage benchmark in the sibling article comes from the same source. https://www.accountingtools.com/articles/collection-effectiveness-index (accessed 2026-06-24).
3. Freelancers Union, Freelance Isn't Free — research documenting how often payment culture, not freelancer effort, decides when invoices land. Anchors the article's structural-not-personal framing. https://www.freelancersunion.org/resources/freelance-isnt-free/ (accessed 2026-06-24).