A company pays monthly for a cloud system subscription, renews its HR system licence annually, and in July paid upfront for a full year of CRM access. Each of these payments lands on the desk of the accounting department and each can legitimately be classified in a different way. As a result, two similar expenses end up on different accounts, affect the financial result differently, and look different in the tax return.
How should this be done correctly? The answer depends on three things: the billing model with the supplier, the period covered by the payment, and what the company is actually acquiring, a property right or access to a service.
Three Cost Categories and Why the Distinction Matters
Before moving to examples, it is worth establishing what distinguishes the three possible classifications:
Intangible assets are acquired property rights used for a period of more than one year for the purposes of the entity. Classification as an intangible asset is determined by the nature of the item, not its value. The materiality principle may, however, influence how it is recognised in the accounting books. Intangible assets are capitalised on the balance sheet and amortised over time. Example: a one-off purchase of a perpetual software licence for PLN 30,000 net, with unrestricted right of use.
Period costs are expenses that relate to the current month or a short period not exceeding one year and do not generate future benefits beyond that period. They may be recorded directly as costs at the time of incurrence or in the month to which they relate. Example: a monthly SaaS system subscription, each invoice is the cost of that month.
Prepaid expenses (accruals) are costs already incurred but relating to future reporting periods. Pursuant to Article 39 of the Accounting Act, if an expense relates to more than one settlement period, it must be spread over time in proportion to the period it covers. Accounting entry: debit account 64-0, settled monthly on the credit side. Example: an annual licence fee paid upfront in January, covering the period January–December.
The 12-Month Rule, the Cornerstone of SaaS Classification
The key criterion distinguishing an intangible asset from a period cost is the period of economic usefulness of the right. At the same time, a period exceeding one year alone does not automatically qualify an item as an intangible asset, it must also involve the acquisition of a property right meeting the definition of an intangible asset. If the period of economic usefulness does not exceed one year, no intangible asset arises, even if the company has been using the same software for ten years by renewing the agreement annually.
This principle is confirmed by the draft new National Accounting Standard on intangible assets, currently under public consultation. The standard explicitly states: if the period of economic usefulness of a right does not exceed one year, the costs of acquiring it are recognised as period costs, even if there is a possibility of extending that period in the future.
What does this mean for SaaS subscriptions? In a typical SaaS model, the entity does not acquire a property right to the software but obtains the right to access a service provided by the supplier. In such cases, subscription expenditure does not, as a rule, meet the definition of an intangible asset and is recognised as a period cost or prepaid expense.
If the company does not pay for the next subscription period, access to the system expires. This means that in most cases, no asset meeting the definition of an intangible asset is acquired.
Can a Subscription Qualify as an Intangible Asset?
Situation 1: Monthly SaaS subscription
An invoice arrives each month, relates to the current month, and the amount is the same. This is the simplest case, a period cost, recognised directly as an operating expense in the month the invoice is received.
Accounting entry:
Debit account 40-2 “External services”
Credit account 30 “Purchase settlement” / 21 “Accounts payable”
No prepaid expense accrual required, no capitalisation on the balance sheet. Tax cost for CIT purposes: date of cost incurrence within the meaning of Article 15(4e) of the CIT Act.
Situation 2: Annual fee paid upfront (e.g. HR system subscription: invoice issued in January for the full year)
The company pays PLN 12,000 net in January for annual access to an HR platform, covering the period January–December. This is a cost relating to future periods, the matching principle requires it to be spread over time.
Accounting entry on receipt of the invoice in January (VAT omitted for simplicity):
Debit account 64-0 “Prepaid expenses” — PLN 12,000
Credit account 21 “Accounts payable” — PLN 12,000
Then, each month (over 12 months), a monthly write-off of PLN 1,000:
Debit account 40-2
Credit account 64-0
On the balance sheet at end of January: PLN 11,000 appears in assets as prepaid expenses (short-term). The financial result is charged PLN 1,000, not PLN 12,000.
Note on the materiality principle: if the amount is immaterial to the entity’s financial statements, the accounting policy may permit the full amount to be expensed at once, without creating a prepaid accrual. Any such simplification should be grounded in the adopted accounting policy and applied consistently to similar economic events.
Situation 3: Annual subscription invoice issued mid-year (e.g. CRM: invoice from July covering July–June of the following year)
This case spans two financial years. The PLN 6,000 fee paid in July covers: July–December of the current year (6 months × PLN 500 = PLN 3,000) and January–June of the following year (PLN 3,000).
Both time periods require separate recognition:
The July–December portion: current year cost, recognised monthly at PLN 500.
The January–June portion: prepaid expense: PLN 3,000 appears in assets as at 31 December and is written off in the following year.
Accounting entry in July: the full PLN 6,000 is posted to account 64-0, followed by monthly write-offs of PLN 500. As at 31 December, account 64-0 shows a balance of PLN 3,000, this amount will appear on the balance sheet as prepaid expenses (short-term, as it will be settled within 12 months).
Situation 4: One-off ERP system implementation fee (e.g. PLN 45,000 for configuration and implementation)
This is an entirely different case from a subscription. An implementation fee is not a subscription, it is a one-off cost incurred to bring the system into operation. The question is: does it qualify as an intangible asset or a period cost?
The answer depends on what the fee covers:
If the fee involves the acquisition of a property right (e.g. a perpetual licence, ownership of software or rights thereto) and the system will be used for more than one year, it may qualify as an intangible asset. A value above the entity’s adopted materiality threshold (for accounting purposes) and the relevant limits under tax regulations will require capitalisation and amortisation.
If the fee relates solely to implementation services (configuration, training, data migration) without the acquisition of property rights, i.e. it does not relate to an acquired intangible asset, it is the cost of an external service, recognised as a period cost or spread over time via prepaid accruals if it covers a longer period.
If the company uses the system under a SaaS model and the fee relates to activating cloud access, without acquiring a licence, it is a service cost. There are no grounds for capitalisation.
Conclusion: In practice, IT system implementations frequently comprise several distinct elements: licence, configuration, data migration, training, and post-implementation support. In such cases, the contract must be analysed and a determination made as to whether individual components should be recognised separately. The invoice description “implementation fee” alone is not conclusive, what matters is the nature of what is being acquired.
Tax Aspect: Accounting Accruals ≠ Tax Accruals
An important pitfall worth stating explicitly: the way costs are recognised in the accounting books does not automatically determine how they are treated for income tax purposes.
For CIT, costs that are not directly linked to revenues, which is typically the case for SaaS subscriptions, are, as a rule, deductible on the date of incurrence, i.e. the date on which the cost is recognised in the books on the basis of a received invoice or other accounting document, with the exception of costs recognised as provisions or accrued liabilities. However, if such a cost relates to a period exceeding the tax year, it should, pursuant to Article 15(4d) and (4e) of the CIT Act, be allocated proportionally to the length of the period it covers.
Example: a company pays PLN 24,000 in October for a two-year system subscription (October of the current year – September two years hence). For CIT purposes: 3/24 × PLN 24,000 = PLN 3,000 relates to the current tax year; 12/24 × PLN 24,000 = PLN 12,000 to the following year; and 9/24 × PLN 24,000 = PLN 9,000 to the year after. The same allocation applies in the accounts via account 64-0.
Summary: When to Apply Each Treatment
| Type of fee | Period | Classification | Account |
| Monthly SaaS subscription | ≤ 1 month | Period cost | Operating costs |
| Annual fee paid upfront | 12 months | Prepaid expense | 64-0, settled monthly |
| Annual fee spanning more than one financial year | >12 months | Prepaid expense (partly long-term) | 64-0, balance on balance sheet |
| One-off perpetual licence > 1 year | >12 months + property right | Intangible asset | Account 02, amortisation |
| Implementation fee (service, no property right acquired) | One-off | Period cost or prepaid expense | Operating costs / 64-0 |
What Does the Draft New National Accounting Standard on Intangibles Change?
The draft National Accounting Standard on intangible assets, currently under public consultation, consolidates the principles described above and elevates them to the status of a standard. It confirms the interpretive direction under which typical SaaS subscriptions are not recognised as intangible assets, since the entity does not acquire a property right to the software.
The standard will likely be applicable to financial statements for the year 2026. For companies that have approached this topic intuitively until now, this is a good moment to review the accounting policy and verify that the applicable classification rules for subscriptions are consistent with it.
Does Your Company Have an Up-to-Date Accounting Policy in This Area?
Correct classification of subscriptions affects not only compliance with accounting and tax regulations, but also the quality of financial data used for business management, the calculation of the financial result, and the conduct of the statutory audit. At BPiON, when managing clients’ accounting, we verify the classification of software costs as part of our ongoing service, we do not wait for an error to surface during an audit or tax inspection. If you would like to check whether your subscriptions are correctly recognised, we invite you to get in touch.
