SOFTWARE AND SUBSCRIPTIONS · QUICKBOOKS ONLINE & XERO
How to Categorize Figma in QuickBooks and Xero
Last Updated: October 5, 2026Figma’s billing has a feature almost no other tool has, and it catches businesses out every month: seats are assigned automatically when someone edits a file. Invite a contractor to comment, they edit instead, and you are billed for a seat. The charge then varies month to month with no deliberate decision behind it — which looks like a billing error and is not.
The Short Answer
| What the charge actually is | A per-editor subscription, with seats potentially assigned automatically when a viewer edits, plus separate products such as FigJam or Dev Mode on some plans. |
| Where it belongs | Software subscriptions. For an agency billing clients, there is a case for treating it as a project or production cost. |
| QuickBooks Online default | Office Expenses or a custom Software and Subscriptions. |
| Xero default | Subscriptions. |
| Expense or balance sheet | An expense; an annual plan paid up front is a prepayment if material. |
| Bank feed descriptor | Commonly contains FIGMA. Mid-cycle seat additions can produce prorated charges that look like duplicates. |
Why the Amount Changes Every Month
Figma bills for editors, and in many configurations a viewer who edits is upgraded to an editor automatically — and billed, prorated, immediately.
For a design team working with external collaborators, that means the monthly charge genuinely varies, and prorated mid-cycle additions can look like duplicate charges. Both are legitimate.
The bookkeeping implication is to resist the instinct to query or reverse them, and instead note that variability is expected for this vendor. The control that actually helps is the quarterly seat review: Figma is one of the places it most often finds editors who should be viewers.
Agencies: Project Cost or Overhead
If you are a design agency, Figma is arguably a production cost rather than general overhead — particularly where seats exist for a specific client engagement or are rebilled.
That matters because a cost belonging to a job and recorded as overhead makes the job look more profitable than it was, and the next proposal is priced off the wrong margin. For agencies running on project profitability, pushing tool costs that are genuinely project-specific into project cost is worth the effort.
Where seats are permanent and shared, overhead is the honest answer. The test is whether the seat exists because of a particular client.
Figma Categorisation FAQs
Why does our Figma bill change every month?
Because Figma bills per editor and, in many setups, a viewer who edits a file is upgraded to an editor and billed immediately on a prorated basis. For teams working with external collaborators the charge genuinely varies, and prorated mid-cycle additions can look like duplicates. The quarterly seat review is where this gets controlled.
Should an agency treat Figma as a project cost?
Possibly, where seats exist for a specific engagement or are rebilled. A cost that belongs to a job but sits in overhead makes that job look more profitable than it was, and the next proposal gets priced off the wrong margin. Where seats are permanent and shared across clients, overhead is the honest answer.
This page is about where the transaction belongs in your books. Whether a cost is deductible, and how it is treated on a return, is a question for your CPA — and consistent categorisation is what lets them answer it without guessing. Dedicated bookkeepers from $75/month, extra hours at $15/hour, wholesale $10/hour for CPA firms, with a 100% money-back guarantee on your 1st retainer, refundable on the unused balance.
Related Resources
Stop Deciding This Every Month
A dedicated bookkeeper who codes Figma the same way every time — from $75/month with a 100% money-back guarantee on your 1st retainer, refundable on the unused balance.