Whether you can capitalise cloud costs depends not on the service named on the invoice but on whether the spending creates an intangible asset of your own, and on which reporting framework your accounts follow. The candidates are mainly costs incurred in the development phase of software you build yourself; running costs, research and access to someone else's SaaS application follow different rules. This guide sets out the questions for your tax adviser and auditor (in Germany, the Steuerberater and Wirtschaftsprüfer) and the evidence engineering has to produce. It is not accounting or tax advice; you make the decision with your adviser.
Which cloud costs could be in scope
A cloud invoice puts operations, development and experiments side by side. Separate them by activity first:
| Cost type | Example | First classification, to confirm with your adviser |
|---|---|---|
| Running costs | Compute, databases and data transfer of the live environment | Outside the statutory definition of development |
| Research and feasibility work | Experiments whose usability is still open, such as GPU runs to explore methods | Not capitalisable under HGB or IAS 38 |
| Development of your own software | Development, test and CI environments during the development phase | Possibly part of the asset's cost if directly attributable and the criteria are met |
| SaaS access | Subscription to an application the supplier runs | A service contract under IFRS |
| SaaS configuration or customisation | Set-up by the supplier or a third party | Usually an expense under IFRS, exceptionally your own code |
| Shared infrastructure | Networking, logging, shared clusters | Directly attributable only with a documented allocation key |
If development runs in the same Kubernetes cluster as production, you need at least a namespace view; understanding Kubernetes cluster cost explains what that view can show. Cloud spend is also only part of the question: developers' staff costs belong to the same assessment and need their own evidence.
Germany: the HGB option in § 248(2)
§ 248(2) of the German Commercial Code (HGB) allows internally generated intangible fixed assets to be recognised. It is an option, not an obligation. Internally generated brands, mastheads, publishing rights, customer lists and similar items are excluded.
§ 255(2a) HGB limits the cost to development expenditure and defines both phases:
- Development is the application of research findings or other knowledge to develop new goods or processes, or to improve existing ones through significant changes.
- Research is the independent, planned search for new knowledge where no statement can in principle be made about technical usability or commercial prospects.
- If research and development cannot be reliably distinguished, capitalisation is excluded. Research and selling costs may never be included (§ 255(2) sentence 4).
Using the option triggers follow-on duties whose reach depends on company size:
- Distribution block under § 268(8): profits may be distributed only if the remaining freely available reserves at least cover the capitalised amount less the related deferred tax liabilities.
- Notes disclosure under § 285 no. 22: total research and development costs and the capitalised share. Small corporations are exempt under § 288(1) no. 1.
- Deferred tax under § 274; small corporations are exempt under § 274a no. 4.
- Amortisation: where the useful life exceptionally cannot be estimated reliably, § 253(3) sentence 3 prescribes ten years.
For the tax balance sheet, § 5(2) of the Income Tax Act (EStG) applies: intangible fixed assets are recognised only if acquired for consideration. How your software is treated for tax is a question for your tax adviser; for the cost data it only means keeping the commercial and the tax view separately evidenced.
IFRS: IAS 38 and the IFRIC decisions on cloud software
IAS 38 also separates research from development, but without an option:
- Research expenditure is recognised as an expense when incurred (paragraph 54). If the phases of a project cannot be distinguished, everything is treated as research (paragraph 53).
- An asset arising from development shall be recognised if, and only if, the entity can demonstrate all six criteria in paragraph 57: technical feasibility, intention to complete, ability to use or sell, probable future economic benefits, adequate resources, and reliable measurement of the attributable expenditure.
- Cost includes only directly attributable costs of preparing the asset for its intended use (paragraph 66). General overheads, identified inefficiencies, initial operating losses and staff training are excluded (paragraph 67).
- Expenditure once recognised as an expense is not reinstated later (paragraph 71).
For SaaS, the IFRS Interpretations Committee has published two agenda decisions. March 2019: a contract that conveys only the right to receive future access to the supplier's software is a service contract, neither a lease nor an intangible asset. March 2021, on configuration and customisation: the customer often recognises no asset because it does not control the software. An exception is, for example, additional code from which the customer can obtain the benefits. Otherwise the cost is expensed when the service is performed: on configuration if that service is distinct, otherwise over the contract term. A prepayment is shown as an asset until then.
UK note: FRS 102 Section 18
FRS 102 makes capitalising development costs an accounting policy an entity may choose (paragraph 18.8H), with the same six criteria as IAS 38. Research is expensed (18.8E), and a chosen policy applies to all expenditure that meets the criteria (18.8K). The 2024 Periodic Review amendments leave these paragraphs unchanged and add no specific rule on cloud configuration costs.
The evidence engineering needs to produce
What matters is whether you can show that a cost was assigned to a project in its development phase at the time it was incurred. Four requirements follow:
- Separate environments. Separate AWS accounts or Azure subscriptions for development and production are the strongest evidence, because the split does not depend on tags.
- Tag project and environment before cost arises. AWS can backfill cost allocation tag activation for up to twelve months, but only where the tag was on the resource at the time. Azure carries resource tags into usage data only while the tag is applied. Azure tag inheritance, by contrast, applies changed tags to the whole current month.
- Record phases as dated decisions, not tags. The start and end of the development phase belong in the project record with the reasoning. A phase tag that someone later renames proves little.
- Show shared costs with their key. Unallocated cost stays visible instead of being quietly added to a project.
A tag policy in AWS Organizations can set the required tags. report_required_tag_for reports missing tags when your infrastructure-as-code tool has tag policy validation turned on:
{
"tags": {
"Project": {
"tag_key": { "@@assign": "Project" },
"report_required_tag_for": {
"@@assign": ["ec2:ALL_SUPPORTED", "rds:ALL_SUPPORTED", "s3:ALL_SUPPORTED"]
}
},
"Environment": {
"tag_key": { "@@assign": "Environment" },
"tag_value": { "@@assign": ["Production", "Staging", "Development"] },
"report_required_tag_for": {
"@@assign": ["ec2:ALL_SUPPORTED", "rds:ALL_SUPPORTED", "s3:ALL_SUPPORTED"]
}
}
}
}
Each month, add an export of cost by project, environment and cost centre with its data version, reconciled to the invoice as described in cloud costs at month-end.
Adviser questionnaire
Framework and policy
- Which framework applies to the entity accounts and, where relevant, the group: HGB, IFRS or FRS 102?
- Do we use the § 248(2) HGB option, or choose the FRS 102 paragraph 18.8H policy, and for which projects?
- What do the distribution block, notes disclosures and deferred tax mean at our size?
Project boundaries
- From which documented date does the development phase begin, and what evidence do you need for it?
- When does it end, and what counts as operation or maintenance afterwards?
- How do we treat periods in which research and development cannot be separated?
Scope of costs
- Which cloud costs count as directly attributable: development, test and CI environments, test data?
- Is an allocation key for shared infrastructure acceptable, and which one?
- How do we treat Savings Plans or reservations whose discount covers development and production together?
SaaS and tax
- Is a SaaS contract pure access, and are configuration services distinct from it?
- Do our own extensions create code that we control?
- What difference arises between the commercial and the tax balance sheet, and who documents it?
- What useful life do we use, and which records do we keep, for how long?
Have the answers recorded with a date and version. When the project or the framework changes, answer the questionnaire again.
Common mistakes
- Adding tags later and using them as evidence. A tag set afterwards does not show what a resource was used for at the time. On AWS it does not reach past usage; on Azure, tag inheritance reaches at most the current month, and then with today's value.
- Development in the production account. Without account separation or complete tags, the development share cannot be evidenced.
- Capitalising whole monthly invoices. An invoice mixes operations, experiments and development; only the evidenced development share is even up for assessment.
- Carrying IFRS logic into HGB or the other way round. HGB and FRS 102 offer a choice, IAS 38 does not, and the German tax balance sheet follows its own rule under § 5(2) EStG.
What Costfluent covers
Costfluent assigns cloud cost through ordered allocation rules to segments, each naming an owning team, product and cost centre, and shows unallocated cost separately; saved cost reports filtered by project and environment tags can be emailed on a schedule. That is showback that supports your evidence, not a capitalisation decision and not a journal entry. See Costfluent for finance and cost allocation in the glossary. The monthly cloud cost review shows where these figures fit in the monthly cycle.
Sources and method
Checked on 2026-10-10. HGB § 248, § 253, § 255, § 268, § 274, § 274a, § 285 and § 288; § 5 EStG; IAS 38 in the consolidated text of Regulation (EU) 2023/1803; IFRS Interpretations Committee agenda decisions of March 2019 and March 2021; FRC FRS 102, September 2024 and Amendments from the Periodic Review 2024; AWS Tag policy syntax and Backfill cost allocation tags; Microsoft Understand Cost Management data and Tag inheritance. The table, evidence list and questionnaire are Costfluent recommendations, not accounting, tax or legal advice.



