Time Track Central Documentation
website·Indexed 31 days ago
https://docs.timetrackcentral.comA web app extension for Microsoft Business Central that adds time and absence tracking, expense management, and work reports. Includes guides for the web app, Business Central configuration, and the BC Event Bridge for publishing real-time JSON events to external systems like Zapier, Make.com, and Power Automate.
What's inside Time Track Central
- Time Track Central is a web app extension for Microsoft Business Central designed for small and medium-sized organizations. It integrates time and absence tracking, expense claims, and work reports directly into Business Central, ensuring all resource data remains centralized without requiring a separate system. The application consists of several modules, the visibility of which depends on the company's enabled modules and the user's assigned role.
Overview of Time Track Central Standalone Tools
Time Track Central provides small, single-purpose Business Central extensions that are available as separate AppSource listings. These tools are independent of the main Time Track Central product, meaning they do not depend on Time Track Central Setup or other extensions, are not limited to Time Track Central data, and can be installed in any Business Central environment. Each has its own installation process, permissions, and licensing.Overview of Expense Management Workflow in Business Central
The Time Track Central expense management extension allows employees to log expenses and mileage in a unified web interface. The approval and financial processing occur within Business Central, where the finance department manages the workflow and posts approved claims into the Project G/L Journal.Overview of Time Track Central Web App modules
The Time Track Central web app is a single-page application organized into five top-level tabs. Visibility of these tabs depends on the company's enabled modules and the user's assigned role:
- Time Sheets: Used for recording and submitting work hours.
- Absences: Used for requesting and reviewing absences.
- Expenses: Used for managing expense claims and mileage.
- Work Reports: Used to bundle approved hours into reports for customers.
- Manager: Restricted to team or global admins; used for approvals, payroll export, and resource/capacity planning.
Overview of BC Event Bridge
BC Event Bridge publishes Business Central table changes as real-time JSON events. It hooks into global table triggers, allowing external systems to react to inserts, modifications, renames, or deletes without polling the Business Central API. It works with any table and does not require the full Time Track Central installation.Submit and approve expense claims and mileage
The Expenses module provides an interface for submitting expense claims and mileage. The approval process is handled entirely within Microsoft Business Central, providing the finance department with a complete overview of claims.Understand the Work Report approval flow
Work reports are used to request customer approval for worked hours. This flow is only active if the project is configured to use the 'Work Report' approval flow. In this mode, hours are not submitted for approval individually; instead, a work report admin bundles them into a report sent to the customer. Access to the Work Reports tab is restricted to work report admins and global admins.Interpret a Work Report Card
The Work Report Card provides a read-only overview of a specific report, including header details (project, external document number), key dates (sent, approved, expired), and approver contact information. It contains two primary embedded views:
- Time Sheet Details: Displays all underlying hours lines bundled into the report. Each row represents a resource per day and includes Resource, Time Sheet No., Date, Quantity, Customer Location, Description, Work Variant, From/Till, and Lunch. This view confirms when multiple employees are bundled into a single report.
- Log: A timestamped audit trail showing the event date/time, the user who performed the action, and associated comments.
Configure Azure Event Grid endpoint in Event Bridge
To use Azure Event Grid as an endpoint, provide the following configuration:
- Topic Endpoint: The Event Grid topic's endpoint URL (copied from the Overview tab in the Azure Portal). Example:
https://mytopic.westus2-1.eventgrid.azure.net/api/events. The URL must start withhttp://orhttps://; trailing slashes are automatically stripped.
Authentication: Supports API Key, OAuth 2.0, or an Event Grid SAS Token.
- If using API Key, the Key field must be set to
aeg-sas-key(the header name expected by Event Grid). - The topic must be configured for Event Grid Schema, not CloudEvents v1.0.
- Topic Endpoint: The Event Grid topic's endpoint URL (copied from the Overview tab in the Azure Portal). Example:
Understand how employee capacity is defined
Capacity represents the hours an employee is expected to work. These values are derived from work-hour templates assigned to the employee's resource, which are configured by an administrator within Business Central (BC).Understand the TimeTrack Central web layout
Every tab in the application follows a consistent four-part layout:
- Navigation: Used to move between weeks or jump to a specific year, month, or day. This is hidden by default and can be revealed by clicking the hamburger icon located below the profile icon.
- Smart editor: The input area used to enter a line by selecting the project, task, and hour type, and filling in the details.
- Details screen: Displays a list of entered lines. Clicking a line loads it back into the smart editor; the three-dot menu provides actions such as submit, approve, or reject.
- Summary/Totals: Displays totals for the period and provides the interface to submit hours or absences for approval.
Users can use the arrow buttons to toggle the visibility of the smart editor and the summary section.
Configure Work Variants for billable items
Work Variants allow employees to flag additional items (e.g., overnight stays, flights, materials) on a booked timesheet line that should be charged to the customer. When a work variant is selected on a timesheet line, the associated configured items are posted to the project. Whether a work variant is mandatory is controlled via the Project Type settings.