Does depreciation post to the accounts?

Yes. The monthly run writes journal entries and will not post into a closed period.

What happens to items below the capitalisation threshold?

They are expensed automatically rather than capitalised, with the entry posted for you.

Do I have to capitalise assets manually?

No. Creating an asset with a purchase price posts the entry immediately - there is no queue to work through.

Can I find an asset physically?

Yes. Print QR labels and scan one to open the record, and run a physical audit that reassigns custody in bulk.

Does it handle impairment and revaluation?

Yes, each as its own posting rather than folded into depreciation or edited into the register.

Fixed Assets

Softbooq Plus

A register that agrees with the balance sheet, without anyone reconciling it.

Buy something and it capitalises itself. Depreciation runs monthly and posts. Dispose of it and the gain or loss is calculated for you. The asset register and the accounts are the same records seen two ways, rather than two lists somebody keeps in step.

Start Free Trial See pricing

Getting assets onto the books

The moment an asset is created is the moment the accounting should happen, not a queue somebody works through later.

Capitalisation posts itself

An asset with a purchase price posts the entry automatically - fixed asset debited by category, payable credited - with no operator accounting step and no pending-capitalisation queue to clear.

Low-value items expensed instead

Anything under your threshold is written to expense automatically rather than capitalised, so the register holds assets rather than a decade of keyboards.

Bought through procurement, cleared properly

A vendor bill for a capital item capitalises to the asset and clears the goods-received account, so the liability does not sit in two places.

Bring an existing register in

Import what you already hold by CSV, with cost and accumulated depreciation, so adopting the module does not mean re-entering years of history.

What happens to them over time

Every change in carrying value is a posting. All of them are here rather than in a spreadsheet beside the system.

Monthly depreciation, posted

A batch run that writes real journal entries and respects closed periods, so the register and the accounts cannot drift apart between month ends.

Disposal with the gain or loss calculated

Sell or retire an asset and the entry, including the result against net book value, is produced rather than worked out by hand.

Impairment as its own event

A write-down posts its own entry, so the reason carrying value fell is recorded rather than absorbed into the depreciation line.

Revaluation, where your standard allows it

Upward revaluation posted properly for the frameworks that permit it, instead of being edited into the register with no trail.

Status changes that need approving

Assets move between states through a workflow with gates, so writing something off is an approved action rather than a dropdown anyone can change.

Finding them in the real world

A register nobody can reconcile against the building is a list, not a register.

QR labels you print

Generate and print asset labels, so every item carries its own identity rather than a number written on tape.

Scan to open the record

Point a phone at the label and the asset opens - who holds it, what it cost, when it was serviced. Identifying a thing should not require the register.

Physical audit with bulk reassignment

Walk the site, record what is actually there, and reassign custody in bulk rather than one record at a time.

Where the value sits

Cost, accumulated depreciation and net book value by category and location, so the register answers the questions an auditor opens with.

The details that took the longest

Small decisions you only make after getting them wrong.

Every one of these is a specific behaviour, chosen for a specific reason. They are the difference between software that demos well and software that survives a year of month-ends.

There is no pending-capitalisation queue

Creating an asset with a price posts the entry there and then. Queues exist so accounting can be done later, and later is when the month closes with assets sitting outside the balance sheet because nobody worked the list.

Depreciation respects a closed period

The monthly run will not post into a period that has been closed. Software that quietly back-posts is software that changes a set of accounts somebody has already signed.

Impairment and depreciation are different entries

A write-down posts on its own rather than being folded into the depreciation charge. Combined, the accounts show an asset wearing out; separated, they show one that lost value for a reason worth knowing.

Nothing is an island

What reaches Assets without anyone typing it again.

Every one of these is a real data path, not a promise of "full integration".

Procurement

A vendor bill capitalises into an asset and clears goods-received

Finance

Depreciation, disposal and impairment all write journal entries

Assets are assigned to an employee as custodian

Maintenance

Work orders and service history are keyed to the asset

Reports

Cost and net book value feed the fixed asset register

IT devices live in the same register as everything else

Before you ask

Questions people ask about Assets.

Does depreciation post to the accounts?: Yes. The monthly run writes journal entries and will not post into a closed period.
What happens to items below the capitalisation threshold?: They are expensed automatically rather than capitalised, with the entry posted for you.
Do I have to capitalise assets manually?: No. Creating an asset with a purchase price posts the entry immediately - there is no queue to work through.
Can I find an asset physically?: Yes. Print QR labels and scan one to open the record, and run a physical audit that reassigns custody in bulk.
Does it handle impairment and revaluation?: Yes, each as its own posting rather than folded into depreciation or edited into the register.