When a company funds software built for its own needs, an accounting question often arises during budgeting or year-end close: should the cost remain an expense, or can it be recognized as an asset and amortized? The answer depends not only on the contract or invoice, but on the work performed, its phase, and its use.

This guide presents the distinctions that help prepare a discussion with your accountant. It does not replace accounting or tax advice for your situation and does not promise a tax saving.

Preparation guidance, not accounting advice

French rules and their application depend on the facts, project documentation, and the company’s accounting policy. Have your accountant confirm the treatment, dates, and amortization period.

Should custom software be capitalized?

There is no automatic answer for all custom software. The French accounting framework sets conditions related to the project, the likelihood of success, the intention to use it durably, and the costs directly attributable to its creation or preparation.

The company should be able to reconstruct project phases, decisions, work performed, and the documents supporting the allocation of costs. A single invoice labeled “software development” may not be enough to explain the chosen treatment.

Conditions for recognizing development costs

For internally used software, documentation should show in particular that the project has a strong likelihood of technical success, that the company intends to produce it, and that it has assessed a minimum useful life and expected impact on its income statement.

The analysis must reflect the actual project. It is not a matter of renaming research, scoping, or maintenance after the fact to obtain a more favorable treatment. Costs expensed before the conditions were met are not automatically recoverable as an asset.

Which expenses may be capitalized?

Costs directly related to detailed design, programming, testing, and technical documentation may be assessed under the framework set by the French accounting plan when the conditions are met. The analysis should distinguish work needed to make the software operational from training, support, or ordinary use.

To support this distinction, request a sufficiently precise breakdown of work packages, days, or deliverables. The contract, reports, releases, and acceptance records can help connect the cost to the work actually performed.

Purchased software, SaaS, or custom-built software: key differences

Purchased software, a license, a SaaS subscription, and software built for the company’s own needs do not describe the same asset or service. Access duration, control over the code, acquisition date, go-live conditions, and included services should be assessed separately.

The commercial name of a contract is not enough to decide. A development contract may include configuration, support, training, subscriptions, or enhancements. Accounting treatment is prepared by matching invoiced lines to the work actually delivered.

How should maintenance and software enhancements be accounted for?

Corrective maintenance, support, and updates needed for ordinary operation follow a different logic from creating a new durable capability. Not every intervention should automatically be treated as a development cost.

A significant enhancement may require a specific analysis when it creates an identifiable component, adds new capability, and meets the applicable conditions. The invoice, functional scope, tests, and documentation should tell the same story.

When does amortization start and for how long?

For created software, the French accounting plan links the start of amortization to completion. The date should match when the software is complete for its intended use, not a date chosen solely to accelerate or delay the expense.

The useful life should reflect expected use, foreseeable technical obsolescence, business changes, and the company’s documented assessment. A standard duration cannot replace that analysis.

Worked example for accounting for a software project

Consider a project made up of initial scoping, development, testing, go-live, and an annual support contract. The analysis should not treat the total as one block by default. It should match each phase to its nature, date, and applicable accounting conditions.

The example mainly illustrates the method: keep contracts, quotes, deliverables, time records, and relevant evidence, then have the classification and amortization schedule confirmed. Actual amounts and entries must be prepared by the company’s advisor.

The right question is not only “can this software be capitalized?” It is “what work was performed, at which phase, for what use, and with what evidence?” This creates a factual basis for the discussion with the accountant.

Frequently asked questions

Is custom software always capitalized?

No. Treatment depends on the software, its use, the project phase, and the applicable accounting conditions. The fact that software is custom-built is not enough by itself.

Which development costs may be capitalized?

The French accounting framework distinguishes project conditions from costs directly attributable to creating and preparing the asset. The classification should be documented and confirmed by the accountant.

Is software maintenance an expense?

Maintenance, support, and fixes that preserve normal operation are generally assessed differently from an enhancement that creates an identifiable, durable component. The actual work delivered is decisive.

When does amortization start for created software?

The French accounting framework links the start date for created software to completion. The date and useful life must be consistent with the project and the company’s accounting policy.

Does this article provide personalized accounting or tax advice?

No. This is general preparation guidance. The company should have its treatment confirmed by its accountant or advisor, especially when several phases, contracts, or entities are involved.

Sources