A client fund balance should pay an invoice only after four checks pass: the money sits in its own account, the automatic setting matches the charge, the work-in-process it will pay is confirmed, and the deposit date is read against the statement date. Tabs3's own worked examples use a $10,000 fund with Automatic All and a $5,000 fund with Automatic Fee Payment; the four checks run in the order listed above.
Chief takeaways
- Keep client fund money in its own account so each deposit and its remaining balance can be traced before any payment runs.
- Read the automatic setting before the balance. The two examples in Tabs3's overview use different settings and different amounts, so a familiar figure should never stand in for the check.
- Confirm each work-in-process line on its own, since the overview lists fees and advances separately and a single total can hide a missing advance.
- Compare the deposit date with the statement date, because a deposit dated after the statement can still generate an automatic payment.
Why a client fund needs its own account
Start with the account, because every later check depends on it. Tabs3 says its client funds feature "can be used to maintain a separate accounting of client funds for non-refundable retainers" ( Tabs3, Client Funds Overview). The important word there is separate. Money that sits inside general billing is hard to read on its own. A reviewer cannot quickly tell how much of a client's deposit is left or which invoice drew on it.
Before any automatic payment runs, open the client's fund record and confirm three things: the client it belongs to, the deposit amount, and the balance still held. If those figures do not match the deposit slip, stop there. Tabs3's example says the deposit amount is used to generate an automatic payment, so a wrong fund record becomes a wrong invoice payment. Examples in a vendor guide can show you which questions to ask; check the fund record's balance on the day you run the check.
Partners should treat the fund account as the record that settles questions. When a client asks how much of a retainer remains, the answer should come from the fund record itself. A client who has made more than one deposit benefits most, because each deposit should be reviewed separately rather than as one blended figure. Separate accounting also makes later explanations easier. Keep a dated note of each check you run, so the file shows what was confirmed and when.
Automatic All against a $10,000 balance
The first worked example in Tabs3's overview starts with a client who has a $10,000 fund balance and is set up as Automatic All ( Tabs3, Client Funds Overview). That sentence holds the two facts that drive the first check: the size of the balance and the setting that governs how the balance is used for automatic payments. Read them together every time. The amount on its own does not tell you what an automatic payment will do.
Start with the setting. Open the client's billing configuration and find the automatic option before you look at the balance. If it reads Automatic All, reconcile the balance in the client's own fund account against the deposit slip. If the account shows a different number, resolve the difference before any invoice is paid from the balance.
A common error is treating a large balance as permission to pay large invoices in full. The example supports only a narrower check. Confirm that the balance matches the figure the client's fund record shows, that the setting is Automatic All, and that the client's profile shows both facts at the same time. Two correct facts shown on different screens can still disagree when an invoice is generated, so check them as a pair.
Automatic Fee Payment against a $5,000 balance
The second example in the same overview follows directly after the first. It reads: "As another example, let's say a client has a $5,000 client funds balance and is set up as Automatic Fee Payment" ( Tabs3, Client Funds Overview). The table compares the two examples on the same measures.
| Measure | Automatic All example | Automatic Fee Payment example |
|---|---|---|
| Client fund balance | $10,000 | $5,000 |
| Setting named in the example | Automatic All | Automatic Fee Payment |
| How Tabs3 introduces the example | "a client has a $10,000 fund balance" | "As another example, ... a $5,000 client funds balance" |
Read the rows side by side. The second balance is half the first, and the setting changes too, so the two cases should never share one checklist entry. A reviewer who has learned to check an Automatic All client may skip the setting check for a Fee Payment client because the balance looks familiar. Do not. For a Fee Payment client, confirm that the account balance matches the client's fund record, that the setting reads Automatic Fee Payment, and that neither value was copied from another client's profile.
For partners reviewing billing, the practical rule is to confirm the fund account first, then check the setting and the balance together. That order makes it harder for a familiar number to hide a different setting. The habit matters most when profiles are duplicated for new matters, so verify the setting after any profile is copied.
Work-in-process a deposit can cover
Tabs3 gives a concrete work-in-process example: "The client has work-in-process consisting of $1,000 in fees and $50 in advances" ( Tabs3, Client Funds Overview). The fund balance says what the client has deposited. Work-in-process is work performed for the client that has not yet been billed or paid from a fund; the Tabs3 example describes it as $1,000 in fees and $50 in advances. An automatic payment connects the two, so you need to know what the statement holds before a deposit pays anything.
The example describes the work-in-process as $1,000 in fees and $50 in advances. Those are different kinds of charge, so check each line rather than a single total. A check that only confirms that work-in-process exists will miss a $50 advance that has been left off the statement or filed under the wrong heading. Listing the two lines separately gives you something specific to compare against the deposit.
Practically, open the statement, list the fees and advances on separate lines, and compare that list with the deposit slip and the automatic setting you confirmed earlier. If a line is missing or sits in the wrong category, correct it before the payment runs. Then decide, for each line, whether the automatic setting is meant to draw on it. The example shows that work-in-process can contain more than one type of charge, so that decision should be made for each type rather than assumed.
Deposit dates and statement dates
The fourth check concerns dates, and the example here runs against a common instinct. Tabs3 writes: "For example, if a client funds deposit is entered with a date of 10/3 and a statement with work-in-process is generated with a date of 9/30, the deposit amount will still be used to generate an automatic payment" ( Tabs3, Client Funds Overview). The three items in that example are shown below.
| Date item in the example | Value | Result in the example |
|---|---|---|
| Client funds deposit entered with | 10/3 | The deposit amount is still used |
| Work-in-process statement generated with | 9/30 | The statement date is earlier than the deposit date |
| Automatic payment | Generated | The deposit amount generates the payment |
Read the table as the example's logic. A deposit entered after the statement date still counts toward the automatic payment. The natural reaction to a later date is to assume the deposit belongs to a later billing period and should wait. The example says otherwise, so do not block a deposit simply because its date falls after the statement date. Check the amount and the setting as usual, then let the payment run as the system generates it.
The example gives no year for either date, so do not add one when you compare them. Tabs3's example shows a deposit dated 10/3 still generating an automatic payment against a statement dated 9/30.
Receivables outstanding from four customers
Before a deposit pays anyone, it helps to know what other clients owe the firm. The ERPNext manual shows this with its example company, Nova: "Nova's Accounts Receivable report shows $249,212 outstanding from four customers as of 13 August 2026" ( Frappe, Accounting Reports).
Receivables are amounts customers owe. In the example, one outstanding total covers four customers and is dated 13 August 2026. That is the only full date the example gives, so it should lead any note you make about the figure. The three measures the example gives are listed below.
| Measure | Value | Date |
|---|---|---|
| Outstanding receivables | $249,212 | 13 August 2026 |
| Customers with an outstanding balance | Four | 13 August 2026 |
| Report used | Accounts Receivable | 13 August 2026 |
When you apply a deposit, compare it with the client's open receivables so you know which balance the automatic payment is reducing. A deposit applied against the wrong open amount produces a payment that looks correct on the invoice but misstates what the client still owes. Pull the receivables figure and its date at the same moment as the deposit, since figures taken on different dates describe different moments.
Why the ageing bucket matters
Frappe's accounting manual uses Nova, an example company, to show how receivables reports sort open amounts. One line reads: "The entire visible amount falls in the 0 to 30 day ageing bucket" ( Frappe, Accounting Reports). The sentence says that every amount in the view sits in the youngest band shown. An ageing bucket is a band that sorts an outstanding amount by how long it has been open, so reading the bucket tells you how old a balance is before you decide anything about it.
For billing staff applying a client fund deposit, this matters because a deposit should not be applied without knowing what the client owes. If the open amounts sit in the youngest band, the balance is recent. If older amounts appear in other bands, the reviewer should decide which invoice the deposit is meant to clear before the automatic payment runs. The bucket is a quick way to see which situation applies.
A bucket describes the moment the report was run, so the run date belongs with it. Without that date, the bucket could describe a picture that has already changed.
Payables in the 121 days and above bucket
The same manual shows the payables side of the firm's books. Nova's payables report tracks what the company owes, and it reads: "Nova's Accounts Payable report shows $184,293 outstanding to Summit Traders Ltd., Zuckerman Security Ltd., and MA Inc. in the 121 days and above bucket" ( Frappe, Accounting Reports). That line names three payees and places the full $184,293 in the oldest band the example shows.
Why does a payables example belong in a post about client funds? The two kinds of money are easy to confuse at the point of payment. Receivables are what others owe the firm, and payables are what the firm owes others. A client fund deposit relates to a client's matter, so a review note should not treat it as interchangeable with vendor balances. Reviewers who handle both sides should keep the reports separate and label every figure with its direction.
The 121 days and above band also shows what age means in practice. An amount that old has been open for a long time, so the useful question is why it has stayed open. The example gives no reason, and this post will not guess at one. What it does establish is the amount, the three payees, and the oldest band. Those are the facts to carry into any review.
Turning on Evergreen Retainers first
Smokeball's support article on evergreen retainers sets a sequencing rule that is easy to miss: "You will first need to activate Evergreen Retainers in Billing settings before using this feature" ( Smokeball, Set up an Evergreen Retainer). The word "first" carries the instruction. Activation is a precondition, and the feature depends on a setting being switched on in Billing settings.
For billing teams, the check comes before any client profile is touched. Open Billing settings, confirm whether Evergreen Retainers has been activated, and only then set up a client on that basis. A reviewer who finds an evergreen retainer on a client profile but cannot find the matching setting should suspect that the activation step was skipped.
The quote does not describe what an evergreen retainer does once it is active, and this section will not supply those details. Read the Smokeball article for the steps that follow activation. What the quote supports is narrow: activation comes first, before any client relies on the feature.
Billing the client for fund amounts
Tabs3's overview includes a line that gets less attention than its automatic examples: "Tabs3 Billing also allows you to bill the client for the client funds" ( Tabs3, Client Funds Overview). This describes a different path. Instead of a fund balance paying an invoice on its own through an automatic setting, the firm can bill the client for the client funds.
The distinction matters when you decide how a deposit should move. An automatic setting such as Automatic All or Automatic Fee Payment lets the system generate a payment from the balance. The quote does not say which path a given matter should use, so that choice belongs to the partner and billing staff who know the matter, and the review note should state it.
The two paths should not blur together. Before choosing a path, confirm the client's current setting and whether a bill has already gone out. If one has, the other path should not draw on the same balance.
Which one should you pick?
The table compares them using only the facts the sources give.
| Option | Fact from the source | Source |
|---|---|---|
| Automatic All | Worked example with a $10,000 fund balance | Tabs3 Client Funds Overview |
| Automatic Fee Payment | Worked example with a $5,000 fund balance | Tabs3 Client Funds Overview |
| Evergreen Retainers | Must be activated in Billing settings before use | Smokeball support article |
| Bill the client for fund amounts | Offered as an option in Tabs3 Billing | Tabs3 Client Funds Overview |
The first two rows are automatic settings, and their figures come from examples, not rules. Each pairs a balance with a setting, which is why the setting should be confirmed alongside the amount. The Evergreen row is a precondition rather than a competing setting, so it is settled before the others are considered. The names of the automatic settings may suggest how much of the work-in-process each one covers, but the quotes do not define that scope. Confirm it in the system before choosing.
The practical rule is to pick the path that matches the client's engagement terms and the setting the firm has verified, and to be able to say why. A choice made with its evidence in view is easier to defend later than one made from habit.
Related guides: Client bank reconciliation with 4 balance checks · 3 client payment types to sort at intake · 4 records a client may send with a payment.
Reader questions
Does a deposit dated after a statement still pay an automatic invoice? According to Tabs3's example, yes. A deposit entered as 10/3 still generated an automatic payment against a statement dated 9/30 ( Tabs3, Client Funds Overview).
Which balance and setting should I check first? Check the setting first, then the balance, and check them together. Tabs3's examples tie Automatic All to $10,000 and Automatic Fee Payment to $5,000 ( Tabs3, Client Funds Overview).
Why keep client funds in a separate account? Tabs3 describes its client funds feature as a way to maintain a separate accounting of client funds for non-refundable retainers ( Tabs3, Client Funds Overview). Separate records make each deposit traceable.
Should a fund balance be assumed to cover all work-in-process? The quotes do not say that. Tabs3's example describes fees and advances as two amounts, at $1,000 and $50 respectively ( Tabs3, Client Funds Overview), so check each amount on its own.
What must happen before I use evergreen retainers? Evergreen Retainers must be activated in Billing settings first ( Smokeball, Set up an Evergreen Retainer).
What does the ageing bucket tell me about receivables? It shows how long an amount has been open. In Frappe's Nova example, every visible amount sits in the youngest band shown ( Frappe, Accounting Reports).
Where does the oldest payables figure in the example sit? Nova's $184,293 owed to Summit Traders Ltd., Zuckerman Security Ltd., and MA Inc. falls in the 121 days and above bucket ( Frappe, Accounting Reports). That is the oldest band in the example.