Bonus & Section 179 Depreciation
US tax law lets businesses expense much — sometimes all — of an asset's cost in year one: Section 179 elections and bonus depreciation. These are tax computations, jurisdiction-specific and election-driven, so REDA Financials doesn't guess them for you — but it gives you clean, auditable ways to record whatever your tax adviser elects. Here's how to handle first-year acceleration without bending your books.
Access you'll need. Any REDA Financials permission set can view an asset's ledger; recording Tax-book lines requires the Accounting Admin v2 or Accounting Controller v2 permission set.
First, a books-vs-tax truth
Under accounting standards, your financial books should depreciate assets over their real useful lives — Meridian's equipment takes its sixty months regardless of what the tax return does. Section 179 and bonus depreciation usually belong on the tax side of the ledger, not the financial side. That separation is exactly what the asset ledger's book lanes are for.
Three recipes
| Situation | Recipe |
|---|---|
| Standard case: books normal, tax accelerated | Let the Financial schedule run normally; record the accelerated tax figures as Tax-book ledger lines on the asset (see Multi-Ledger Depreciation). The per-asset book/tax difference becomes your deferred-tax working paper. |
| Policy expensing: small-value assets fully expensed in the books too | Use the Immediate / Full Expense method — one charge for the whole base at activation, on the register with a paper trail. Set it as the default on a "Small Equipment" asset type and the policy runs itself. |
| Partial first-year election reflected in books (where your policy allows) | A manual Asset Ledger line for the elected amount in year one, then adjust the remaining schedule prospectively — your controller's deliberate entry, documented on the asset. |
Immediate / Full Expense, up close
Since it's the closest built-in relative of first-year expensing, it's worth seeing exactly what the Immediate / Full Expense method does: at activation, instead of a monthly series, the schedule is one line for the whole remaining depreciable base. Had Meridian's $5,000 equipment used it, activation would have generated a single $5,000.00 charge in place of sixty lines of $83.33 — posted by the same nightly batch, through the same accounts (debit Depreciation Expense, credit Accumulated Depreciation), with the same audit trail. The asset then stands on the register at zero book value: still owned, still insurable, still disposable — just fully expensed.
That "still on the register" part is the method's whole advantage over simply not capitalizing small purchases: the register keeps custody of the thing, and the P&L takes the cost at once because your accounting policy says items of this class aren't material enough to spread.
Why the tax lane is safe by construction
Recipe one above leans on a mechanical fact worth stating plainly: the automation only operates on the Financial book. The schedule generator writes Financial-book lines; the nightly batch selects and posts only Scheduled Financial-book lines; and the asset's Accumulated Depreciation counts only Posted Financial-book lines. Tax-book entries you record are therefore inert by design — never auto-posted, never in NBV — which is exactly what a memo record of a tax election should be. The details live in Multi-Ledger Depreciation.
Common mistakes to avoid
| Mistake | Why it hurts | Do this instead |
|---|---|---|
| Setting the asset's method to Immediate / Full Expense to mirror a Section 179 election | The financial books expense the whole cost in month one — a real misstatement for a material asset, not a tax entry | Books keep the real life; the election goes in the Tax-book lane |
| Recording tax figures as Financial-book ledger lines | The nightly batch posts them to the GL when due | Set Book = Tax on every election entry |
| Hunting for a bonus/179 checkbox before year-end | There isn't one — time lost, and improvised workarounds tend to land in the wrong book | Use the three recipes above; they're the supported patterns |
| Leaving the book/tax difference undocumented per asset | The deferred-tax computation becomes an annual archaeology dig | Record elections asset-by-asset in the Tax book where practical — the working paper then writes itself |
Where to go next
- Multi-Ledger Depreciation — the tax-lane mechanics.
- Depreciation Rules & Methods — Immediate / Full Expense and friends.
- Depreciation Schedule Generation — prospective adjustments.
Frequently asked questions
Record it where it's useful to you: per asset if you want asset-level book/tax deltas (best for audits), or as a single year-end Tax-book entry on the dominant asset with a clear description. Either keeps the financial books untouched.
Mechanically similar (everything in period one), conceptually different: Immediate is an accounting policy choice for immaterial assets; Section 179 is a tax election that normally shouldn't rewrite your financial depreciation. Use Immediate only where your accounting policy genuinely expenses the class.
Every jurisdiction has its own acceleration schemes (India's additional depreciation, UK capital allowances…). The recipes are identical: books at real life, tax figures in the tax lane, differences documented per asset.
No — the batch only posts Financial-book lines, so Tax-book entries sit safely as records forever. That's the design that makes the tax lane trustworthy: nothing reaches your general ledger without a deliberate, hand-posted decision.
Not by itself, and it usually shouldn't: the Financial-book schedule keeps depreciating the real useful life while the election lives in the Tax book. Only if your accounting policy genuinely calls for accelerated book treatment would you change the asset's method — a controller's prospective adjustment, not a side effect of the tax return.
Was this article helpful?