Fixed Asset and Depreciation Extension

Fixed assets are the part of the general ledger that quietly stops matching. The register lives in a spreadsheet because the statutory books and the tax return need different useful lives. A revaluation was posted as a manual Journal Entry and never reflected in the asset's carrying value. A production line was sold in three pieces over two years and nobody split the original asset. Then the auditor asks for a movement schedule and finance rebuilds it by hand, again.

SAP Business One's own fixed assets functionality is competent at the ordinary case. It gives you asset classes, useful lives, straight-line and declining-balance depreciation, capitalisation from an A/P Invoice, planned depreciation runs and retirement. Where it runs out is parallel reality: the same asset carried at one value for the statutory books, another for the local tax authority and a third for group or IFRS reporting, together with the events that break a simple register - partial disposal, component splits, revaluation with catch-up, transfers between cost centres and locations, and insurance or replacement values that are not the accounting value.

Spreadsheets fill that gap and they fill it badly. Every period someone re-keys depreciation into a Journal Entry, the register drifts from the control accounts, and the audit trail is a filename with a date in it. This extension closes the gap inside SAP Business One so that the register is the source of truth and the ledger is posted from it.

What ECOSIRE builds

Nothing here is pre-built and there is no instant download. We scope the work against your chart of accounts, your asset classes and your tax rules, quote it at a fixed price, then build the extension for your company and install it into your test company database before it goes anywhere near production. A standard scope is one working week from signed quote to test install.

The deliverable is a SAP Business One add-on. Business logic and data access run through the Service Layer (REST/OData), with the DI API used where a client-side add-on component is required. Master data lives in User-Defined Objects and User-Defined Tables, extra fields on standard objects are User-Defined Fields, and nothing is written directly into SAP system tables. It targets SAP Business One 10.0 on Microsoft SQL Server and on SAP HANA, on-premise or cloud-hosted.

Parallel depreciation areas

A depreciation area master, held as a User-Defined Object, defines each parallel view of an asset: book, local tax, group or IFRS, and any management area you need. Each area carries its own method, useful life, period convention (full month, mid-month, or pro rata by day), start-date rule and G/L account determination. Depreciation is calculated per area per period; only the areas you flag as posting areas generate a Journal Entry, and the rest are kept as statistical schedules that feed the tax computation and the deferred tax working. A standard build covers straight line, declining balance with switch to straight line, sum-of-years-digits, units of production driven by a period usage entry, and immediate write-off below a capitalisation threshold.

Revaluation, impairment and catch-up

A revaluation document records the new gross or net value, the effective date, a reason code and the evidence reference, then recalculates the remaining schedule area by area - because a revaluation recognised in the books is frequently not recognised for tax. The build handles upward revaluation to a reserve, impairment through profit and loss, reversal within the limits you configure, and catch-up depreciation when an area is corrected retrospectively. Each recalculation is stored as a new schedule version rather than an overwrite, so a prior-period figure stays reproducible.

Part disposals, splits and transfers

Assets rarely leave in the shape they arrived. The build adds a split that carves a child asset out of a parent by quantity, percentage or explicit value, apportioning accumulated depreciation per area; a partial disposal that retires only the split portion and posts proceeds, disposal costs and gain or loss to configured accounts; and a transfer that moves an asset between cost centre, profit centre, Warehouse or location with an optional change of responsible employee. A disposal can be raised from the Sales Order or A/R Invoice that sold the asset, so the sale and the retirement are one linked chain instead of two unrelated postings.

The register and the reports finance actually asks for

The reporting layer ships as Crystal Reports layouts inside SAP Business One: asset register by class, location or cost centre; a movement schedule showing opening cost, additions, disposals, revaluation and closing cost, with the same treatment for accumulated depreciation; per-area depreciation forecast for budgeting; tax-versus-book reconciliation with the timing difference per asset; a disposal gain and loss listing; and a construction-in-progress listing of additions not yet capitalised. Query Manager queries are included for teams that prefer to build their own views, and every report exports to Excel and PDF.

Capitalisation from the documents you already post

Assets should originate from the transaction that created them. Lines on an A/P Invoice or Goods Receipt PO can be flagged for capitalisation and collected into a construction-in-progress asset that keeps the Business Partner, project and cost objects on each addition, then settled into one or more final assets on a settlement date. Where an addition carries non-capitalisable cost, the split is recorded on the line rather than argued about at year end.

Controls, approvals and audit trail

Capitalisation, revaluation, disposal and any retrospective change route through SAP Business One approval procedures using thresholds you set. Every document records who raised it, who approved it, the values before and after, and the Journal Entry it produced. A period lock per depreciation area blocks postings into a closed period, and a reconciliation report proves the register against the control accounts so the difference is either zero or explained by a named document.

Who this is for

Manufacturers, contractors, property owners and equipment-rental businesses; any group where the local tax code diverges from the statutory books; and any SAP Business One company running an asset register in Excel next to the ERP and wanting the two to be one thing. In practice the trigger is a second depreciation basis, a register large enough that manual maintenance is a monthly job, or an auditor who asks for a movement schedule.

How delivery works

1. Scoping call. We walk your asset classes, depreciation bases, tax conventions, approval rules, existing register and reporting requirements, and confirm your version, database platform and hosting arrangement. 2. Fixed quote against a written specification. Screens, fields, methods, reports and migration scope are listed. What is out of scope is listed too. 3. Build. Development against a copy of your company database, with a mid-build review so you see the screens before they are finished. 4. Install into your test company. Full deployment of objects, fields, account determination and reports, plus the opening register loaded and reconciled to your control accounts. 5. UAT and parallel run. You run one period alongside your existing method and compare it line by line. 6. Production install. Scheduled with you, out of hours if needed, with a documented rollback path. 7. Support window. Defect fixes and one round of configuration changes after your first close on the system.

After go-live

You get a named contact, the configuration workbook that records exactly how your build is set up, and retesting against your next SAP Business One patch or upgrade during the support window. Extensions after that - a new depreciation area, an additional statutory report, a different tax convention - are quoted as small changes against the same specification rather than as a rebuild.