Integrations

QuickBooks integration: post depreciation from Cohiva Control

In short

Cohiva Control posts monthly fixed-asset depreciation journals to QuickBooks from the same system that maintains the asset. The monthly run is idempotent, so re-running it does not double-post, posting state is tracked separately from the append-only depreciation ledger, and a failed post can be retried without corrupting the record.

QuickBooks integration: post depreciation from Cohiva Control

When your books are in QuickBooks and your assets are maintained somewhere else, depreciation becomes a monthly chore: export the asset data, work out the charge, key in a journal. Cohiva Control removes that step by posting fixed-asset depreciation directly into QuickBooks from the same system that maintains the asset. This page explains what posts, how it stays safe to run, and where QuickBooks fits.

What gets posted to QuickBooks

Each month, Cohiva Control computes depreciation for your assets across whichever methods they use, straight-line, diminishing value, double declining balance, units of production, sum of years digits or AASB 16 leases, and records the charge on an append-only depreciation ledger. From there it posts a journal into QuickBooks. The amount that posts is the amount the engine computed, carried as a fixed-precision decimal rounded half up, so QuickBooks and the maintenance system agree to the cent.

How to set it up

  1. Connect Cohiva Control to your QuickBooks company through the integration settings.
  2. Map your depreciation to the QuickBooks accounts you want the journal to hit.
  3. Confirm the assets you want depreciated, with their cost, residual value, method and useful life.
  4. Run the monthly depreciation, or let the scheduled run do it, and the journal posts to QuickBooks.

Posting safely: idempotent runs

Posting the same month twice is the usual hazard with automated journals. Cohiva Control’s monthly run is idempotent, so running it again for a month that has already posted does not create a second journal in QuickBooks. A retry after an interruption, or a scheduled run that overlaps a manual one, will not double-charge your accounts.

Keeping the ledger clean

The depreciation ledger in Cohiva Control is append-only and cannot be edited or deleted. To track whether a journal has posted, succeeded or failed without breaking that guarantee, posting state lives separately from the ledger row. The ledger records what depreciation occurred; the posting state records what happened when it was sent to QuickBooks. Because the two are separate, a failed post can be retried without ever touching the immutable record.

QuickBooks stays your ledger

Cohiva Control does not replace QuickBooks. QuickBooks remains your accounting system and the system of record for the financials. Cohiva Control computes depreciation on the asset your team maintains and posts the journal into QuickBooks, so the maintenance data and the books stay in step without anyone re-keying figures.

Beyond depreciation

The depreciation posting is part of a broader open platform. Work order completions can be posted out through signed webhooks and a typed SDK, so finished maintenance can trigger processes in other systems. The QuickBooks journal is the headline, but the same openness lets Cohiva Control fit the rest of your stack.

A note on advice

The depreciation features give general information about how Cohiva Control calculates depreciation. They are not accounting, tax or financial advice. Confirm treatment with your accountant or adviser.

Part of the Cohiva platform

Cohiva Control is part of the Cohiva platform. Leisure operators often run it with Cohiva Complex, and finance teams connect it to Cohiva Crunch for the general ledger. Explore the platform at www.cohiva.app.

This page provides general information about how Cohiva Control calculates depreciation. It is not accounting, tax or financial advice. Confirm treatment with your accountant or adviser.

Frequently asked questions

What does Cohiva Control post to QuickBooks?
Monthly fixed-asset depreciation, as a journal. The depreciation is computed in Cohiva Control on the same asset your team maintains, then posted into QuickBooks as your ledger.
Will it ever post the same month twice?
No. The monthly run is idempotent, so running it again for a month that has already posted does not create a second journal in QuickBooks.
What happens if a post to QuickBooks fails?
Posting state is tracked separately from the append-only depreciation ledger, so a failed post can be retried without altering the ledger row. The ledger stays immutable while the posting is corrected.
Does Cohiva Control replace QuickBooks?
No. QuickBooks remains your accounting system and ledger. Cohiva Control computes depreciation and posts the journal into QuickBooks, so the asset data and the books agree without re-keying.
Can work order data go out too?
Work order completions can be posted out through Cohiva Control's open platform using signed webhooks and a typed SDK, so finished maintenance can drive downstream processes.