Clockify time,
posted to Business Central.
A Clockify integration for Microsoft Dynamics 365 Business Central. It turns approved time entries into posted project ledger entries, giving you per-project profit and loss without retyping a single timesheet.
CLOCKIFY 
BUSINESS CENTRAL An approved entry leaves Clockify and arrives as a posted project ledger entry.
From approval
to the ledger.
Time tracking stays in Clockify, accounting stays in Dynamics 365 Business Central, and the connector carries approved entries from one to the other. Nothing is approved twice and nothing is typed twice.
-
Approve in Clockify
Only approved entries sync. Your team tracks and approves time exactly where they do today; nothing changes on the Clockify side.
-
The middleware maps it
Our cloud service matches the user to a resource, the project to a project, the task to a task, and validates the posting date before anything is written.
-
A journal line is written
The entry lands in a dedicated project journal batch in Business Central, carrying its Clockify entry ID. It is visible, editable, and postable like any line typed by hand.
-
Posted to the ledger
The line posts to project ledger entries. Cost comes from Clockify, using the cost rate of each member, and version 1 sends no prices, so the ledger shows real cost and nothing invented.
Boring where
it matters.
-
One entry, once
Every line carries its Clockify entry ID, before and after posting. A replayed webhook or a double-fired approval can never reach the ledger twice, which means it can never double-bill a customer.
-
No credentials in your ERP
Business Central stores no Clockify key, password, or secret. The middleware signs in as a registered Microsoft Entra application that your administrator can disable at any time.
-
Dates checked before writing
Allowed posting ranges, per-user overrides, and accounting periods are validated up front. A bad date is a clean refusal with a reason, not a failure halfway through posting.
-
Your journals, your rules
Entries land in a dedicated project journal batch, so synced lines never mix with manual ones. Your dimensions and posting groups keep working unchanged.
-
Immutable once posted
Posted time is never changed by the connector. Corrections are made as reversing entries.
-
Built for the audit trail
The Clockify entry ID lives on both the journal line and the posted entry. Every ledger row traces back to who tracked the time, on what, and which approval released it.
We sit on both sides of this integration: a CAKE.com partner on the Clockify side, a Microsoft partner on the Business Central side.
What it deliberately does not do
- It stores no Clockify credentials in Business Central.
- It never modifies a posted entry; corrections are new entries.
- It does not invent master data. An unmapped project is skipped and reported, never a guess.
- It bypasses Business Central time sheets, so nothing is ever approved twice.
Coming to both marketplaces.
The connector already runs inside Clockify in our test workspace. Its Clockify add-on is on its way to the CAKE.com Marketplace, and its Business Central extension to Microsoft AppSource. New customers can start once both are listed.
Write to info@spainlink.es and we will tell you when. Let's build
something.
Tell us what you're working on. We reply to every message within one business day, usually faster.
or write to info@spainlink.es