To categorize software subscriptions, code every recurring app or online service charge to a software subscriptions expense account, split further only if the client will read the detail. Treat a yearly plan paid upfront as a prepaid expense and release it monthly. Move personal apps on a business card to owner draws, not software expense.
One software subscriptions account or several?
One software subscriptions account is enough for most small clients. Split it into several only when the owner or a lender actually reads the split, or when the costs belong to different parts of the business. A chart of accounts with seven software accounts, each holding two charges, gives nobody better information and takes longer to code.
Reasons that justify a split:
- Cost of sales versus overhead. Software used to deliver the client's product, such as a hosting service for an online store, may belong in cost of sales so gross margin is accurate.
- Departments or locations. A client that reports by location may want each site's tools charged to it, though a class or location tag usually does this better than more accounts.
- Large single tools. One platform that costs as much as all the others combined can earn its own line.
If none of these apply, one account plus a clear vendor name on each line answers every question the client is likely to ask. A report filtered by vendor shows what each tool costs over the year.
A sample mapping table
The table below is an example of statement descriptions mapped to accounts for a fictional design studio. The descriptions are made up, but they follow the shape banks and card issuers print.
| Example statement description | Account | Note |
|---|---|---|
| DESIGNSUITE*MONTHLY 8005551234 | Software subscriptions | Monthly seat licences |
| CLOUDHOST.IO INV 20931 | Cost of sales, hosting | Hosts client websites |
| ACCTGAPP SUBSCRIPTION | Software subscriptions | The studio's own books |
| VIDEOFLIX MONTHLY | Owner draws | Personal streaming |
| DESIGNSUITE*ANNUAL 8005551234 | Prepaid expenses | Yearly plan, released monthly |
| LAPTOPSTORE ONLINE | Equipment, review | Hardware, not software |
Annual software plans paid upfront
An annual software plan paid upfront covers twelve months, so expensing it all in the month it was charged makes that month look expensive and the next eleven look cheap. Post the payment to a prepaid expenses asset, then move one twelfth to software subscriptions each month. Small annual charges can simply be expensed if the client agrees.
For an example plan of 1,200.00 charged on March 10:
- On the March statement, debit prepaid expenses 1,200.00 and credit the card or bank.
- At the end of each month from March to the following February, debit software subscriptions 100.00 and credit prepaid expenses 100.00.
- When the plan renews, the prepaid balance should be zero and the cycle starts again.
Whether to set a floor below which annual plans are expensed at once is a practice policy. Write it down for each client, so every bookkeeper on the file treats a 90.00 yearly plan the same way. The release schedule, and how to keep several prepaid items in step, is covered in recording prepaid expenses from a single statement line.
Which software charges are not subscriptions?
Software charges that are not subscriptions include one-off setup fees, payments to developers for custom work, licences bought outright and hardware sold with software included. These can belong in other accounts, and some may need to be capitalized rather than expensed. The vendor name alone does not settle it, so read the invoice when the amount is large.
Custom development and implementation
A payment to a developer for building a client portal or an internal tool is not a subscription. Whether it is an expense or an asset depends on what was built and the client's policy. The guide to whether to capitalize or expense a purchase gives a line-by-line way to decide, with a policy to apply each month.
Hardware from a software vendor
A charge from a company known for software may be for a device, such as a card reader or a tablet. Ask for the receipt. Hardware belongs in equipment or office supplies, depending on cost and the client's threshold, not in subscriptions.
Usage-based charges
Some cloud services bill by use rather than a flat fee, so the amount changes each month. They are still ordinary operating costs and go to the same account as the flat-fee tools. A sudden jump in a usage bill is worth a question to the client, because it can signal a forgotten test project or a compromised account.
Personal apps among business software subscriptions
Personal apps among business software subscriptions are charges for streaming, games, personal storage or fitness apps that the owner put on a business card. They are not business costs. Code them to owner draws, or to a shareholder account in a corporation, and agree with the client whether they will move those apps to a personal card.
App store charges are the hard case. A line from a phone platform's app store can be a business tool or a child's game, and the statement rarely says which. Ask the client to look up the receipts in their app store account once, then write a rule for the ones that repeat.
A short, friendly note gets this fixed faster than a list of charges. A message along the lines of "These four apps look personal; can they move to your own card from next month?" usually does it. Ready-to-adapt wording for this kind of request is in email templates for bookkeepers.
Software subscription rules for recurring vendor names
Software subscription rules are categorization rules keyed on the vendor name a charge carries every month. Subscriptions are the most predictable lines on a statement: same vendor, same day, often the same amount. One rule per vendor per client codes them for good, leaving only new vendors and changed amounts to look at.
Write rules on the stable part of the description. "DESIGNSUITE*" matches both monthly and annual charges from the same vendor, so if the client has both, write two rules, one matching "MONTHLY" and one matching "ANNUAL", and send the annual one to prepaid expenses.
In AutoBankConvert, a vendor rule you write once is applied to that client's statements every month, and a charge from a vendor the rules have not seen goes to the review queue with a suggested account. Approving it there teaches the rule. You can request a setup time to try it on your own clients' card statements.
Watch for price changes
A rule codes the charge, but it does not tell you the price went up. Glance at the software account total each month. A rise with no new vendor usually means a plan upgrade, an extra seat or a renewal at a higher rate, and the client may want to know.