Record time and bill reviewed work

Keep recorded work, review and customer billing separate#

Record actual time in the correct personal or corporate workspace. Choose an authorized project and, when relevant, its canonical task. Describe the work for the intended review audience. A time entry does not complete the task or establish delivery, customer acceptance, an issued invoice or payment.

Review the complete timesheet before disclosing it. A reviewer checks the submitted work within their current permissions. Approval retains the reviewed facts; it does not establish payroll entitlement, statutory working-time compliance or a customer’s agreement to pay.

Time billing is a separate deliberate financial workflow for a corporate workspace. Review the original time claim, the exact agreed rate, currency, tax interpretation and customer-facing description before creating and issuing its source invoice. Private work notes are not automatic customer invoice text.

Install the work context before recording time#

Install and configure Projects first. Its existing To Do prerequisite owns any optional task reference. Timesheets uses one app allowance; it does not create another copy of the task or charge a second fee for shared platform services. Dependencies are not silently installed.

New time needs current project contribution scope and Timesheets writing authority. To Do writing permission is not required merely to record time against an already authorized same-project task. Corporate time billing additionally needs configured/licensed Invoicing and the project’s explicit financial/billing grants.

Changing profile does not move records, licences, staff or a paid subscription. Retained approved billing sources keep their dependency. Re-enabling an app does not turn a protected source invoice into an ordinary editable or physical-stock record.

Official references: App prerequisites and installation ↗ · Plan work and deliver projects ↗

Set recording, review and billing policy deliberately#

The owner or administrator chooses the Timesheets write policy, default IANA timezone, manual/timer recording methods, reviewer mode and corporate approval policy. Confirm the private-draft and disclosure boundary and the actual business recordkeeping purpose. Ordinary setup does not require code edits.

Manual intervals and a server timer are alternative ways to create working facts. Neither proves attendance or customer acceptance. Existing sheets keep their confirmed timezone. Saved setup is versioned; a stale tab must reload instead of replacing a newer review policy.

Corporate billing is optional. It does not automatically authorize every project member to view rates or create invoices. Enabling it requires compatible Invoicing, and each financial action still checks current source grants. Personal records remain a tracking/review workflow without a corporate billing identity.

Distinguish the author, reviewer and financial actor#

The author sees their own working sheet and permitted retained history. Workspace administration, project membership or a workspace-readable project does not expose another person’s undisclosed working notes. New recording still needs current contribution and module writing authority.

Reviewers need Timesheets writing authority and actual project reading access. The policy either uses current project owners/managers or named eligible people. A named reviewer need not be allowed to change the project’s tasks, and naming them does not grant private-project access.

Financial viewing needs an explicit project financial-view grant, current Invoicing viewing and the Timesheets entitlement. Billing changes additionally require a project billing grant and current Timesheets/Invoicing writing. Restricting time recording does not silently revoke an existing financial-view grant: remove that grant or Invoicing viewing to hide the commercial source. A financial-only view discloses approved billable time and commercial facts, not hidden working/nonbillable totals, counts, notes or review lines. “Not disclosed” is different from zero. Read-only workspace users cannot become writers through a module selection.

Open one project week with a frozen timezone#

Choose a project you may currently contribute to, select its Monday-start calendar week and confirm the IANA timezone. One sheet belongs to that project, author and week. Its original timezone is retained even if project or setup defaults later change.

A valid interval may cross midnight but must fit the actual UTC boundaries of that calendar week in the retained zone. The work date equals the interval’s start calendar date in that zone. Overnight entries remain on that recorded work date; the app does not invent where an unpositioned break fell across days.

An empty draft that has never been submitted and has no active entry or timer may be cancelled with a reason. This lets you replace a mistaken week/zone without rewriting retained facts. Once work or submissions exist, use the controlled correction workflow rather than changing their meaning.

Record an actual interval without changing the task#

Open your project/week sheet and record the actual start and finish, declared break, internal work description and optional same-project task. The selected zone is visible beside the interval. Choose a repeated-clock offset deliberately; a nonexistent clock time cannot be saved.

Net duration is the real elapsed interval minus the break expressly declared. It must remain positive, fit the frozen week and be no longer than twenty-four hours. Record only actual work, not a future plan. Split a longer interval deliberately; the software never silently caps the actual capture.

Marking time billable is an input to review, not an agreed hourly rate or a charge. Work descriptions/notes stay internal to the author and submitted review audience. Recording time does not complete or edit the canonical task. Cancel a permitted working entry with a reason; submitted snapshots and original timer evidence remain retained.

1. Open the intended project week and confirm its zone.
2. Enter actual start/finish and the declared break.
3. Optionally choose a same-project task and describe the actual work.
4. Review the net duration and billable flag, then save the private working entry.

A declared break does not create a separate free interval#

No break is deducted automatically. Enter the duration you intend to declare, including zero when no break is declared. This is not a calculation of a statutory break entitlement or evidence that a break actually occurred.

A break duration has no recorded position inside the interval. The entire start-to-finish interval therefore occupies the author’s conflict window. To record different work during a break, enter deliberate separate nonoverlapping work intervals rather than assuming that subtracting minutes opens an unspecified gap.

Overlap checks include the author’s retained working intervals and active timer in this workspace, even when project access changes. A generic conflict can be returned without disclosing a hidden project. The app does not compare an organization’s work against the author’s unrelated personal or other-workspace time.

Preview the complete disclosure before submitting#

Stop or recover this sheet’s running timer, then choose Review the exact submission. Inspect the retained week/zone, complete entry count and actual/net/billable durations, and understand who can receive the disclosed work descriptions, notes, intervals, breaks and references.

Confirm the disclosure and submit the current source hash. The server seals the complete snapshot; it does not use only the visible pagination page. A changed sheet or review policy invalidates the old preview. A sheet supports up to five hundred active entries; oversized submissions are refused rather than truncated.

Current working entries and a submitted revision are separate records. A returned author may edit their draft privately. Reviewers continue to see the retained submitted facts until a fresh complete revision is deliberately disclosed.

Approve or return the exact retained revision#

Open the eligible review inbox and the exact submitted revision. Inspect all authorized source facts, then approve or return it with a meaningful reason and confirmation. The decision cites the sealed revision and source hash, not the author’s later private draft.

Both current authority and the submitted policy are required. Removing project membership or a reviewer selection takes effect server-side; an old tab or repeated request does not restore it. Changing named reviewers does not silently broaden the audience of an earlier named disclosure. Project-manager mode uses its declared current-role rule.

An approval establishes a reviewed time source. It does not complete tasks, prove customer acceptance, set a wage, establish an additional customer fee or create an invoice. A return retains the original submission and describes what the author should review before resubmitting.

Choose independent review or explicit owner self-review#

Corporate approval normally requires a different person. The author cannot approve their own submission merely by becoming a project manager or named reviewer. A workspace viewer remains read only.

An explicitly selected owner-self-review policy permits only the actual workspace owner to approve their own time, within current project/reviewer scope and the submitted policy, with a retained acknowledgement. It is not an automatic fallback when another reviewer is absent. A sole owner must choose and review this policy deliberately before submitting eligible work.

Personal sheets may be deliberately self-reviewed in their own profile. This does not create corporate financial authority or a payroll certificate. If a submission has no eligible reviewer, review current project access and policy; do not invent an approval or invite someone without a valid staff seat.

Choose the workspace and review audience before recording details#

Personal and corporate profiles have separate records, staff, licences and billing. An organization owner does not gain access to someone’s unrelated personal work. Project privacy and current project membership continue to apply when project work appears in a time workflow.

Working notes can contain information that is unsuitable for a broad team or customer audience. Keep them focused on the recorded work and use the intended review workflow to disclose the necessary facts. Do not paste unrelated employee medical, household, bank or confidential customer information into an entry.

Time review and financial authority are different permissions. A planning reviewer does not automatically receive hourly rates, customer amounts, financial agreements, invoice links or payment history. Read-only workspace roles remain read only, and an old browser tab cannot restore removed access.

Record a real date and an explicit timezone#

Use the declared IANA timezone shown beside the time form. A literal work date and an exact UTC start or finish instant serve different purposes. Your browser’s location or language does not change the recorded timezone or establish a business jurisdiction.

At a daylight-saving clock change, a local time may not exist or may occur twice. A nonexistent local time must be corrected. For a repeated local time, deliberately choose the intended UTC offset. Review the interval and actual duration before saving rather than assuming every displayed calendar day lasts twenty-four hours.

Saved work and submitted history retain the UTC start and finish plus each recorded timezone offset. The retained clock and UTC instant remain visible even if later timezone rules change. A new timezone default never rewrites an earlier sheet or time fact.

Use duration displays to understand the actual recorded seconds. Decimal hours, rounded display values, payroll hours and customer money are not interchangeable. Billing uses retained server-calculated source facts and the stated rounding policy, not a browser stopwatch or a guessed decimal-hour quantity.

A running display is not a saved time record#

Start and stop the timer deliberately for work you are currently allowed to record. The running display helps you follow the session; the server owns the saved start, stop and duration. Keep the project and task context visible so a browser tab does not silently switch your work to another profile.

A valid stop records the server finish and creates one private working entry. An invalid duration, declared break, overlap or crossed-week interval leaves the timer active and creates no entry. Choose Recover unmatched capture or cancel with a retained reason to record the finish and release the active slot, then enter justified actual intervals manually. Recovery never automatically allocates, approves or bills time.

Review the recorded result after stopping. A timer does not prove attendance, breaks, location, productivity, billable scope or legal working-time compliance. It does not automatically approve or invoice the work.

Review a separate commercial agreement for time#

Choose the actual customer and corporate seller identity. Review the currency, tax treatment, exact hourly rate and explicitly customer-facing description. Keep internal project names, task notes and review comments out of the public commercial text unless you deliberately author them there.

Approved time is not proof that the work falls outside an existing fixed-price or milestone agreement. Review the customer’s commercial scope before billing additional time. A project’s milestone invoice and a time invoice are distinct source claims; neither silently proves that charging for both is appropriate.

Normal Invoicing numbering, country, authority, payment and Accounting safeguards still apply. A source time invoice is a service record and cannot become a physical stock-dispatch source merely because it contains a quantity. A credit or recorded payment does not erase the original approved time or automatically authorize another full invoice.

Create and issue one retained time invoice#

After an exact time approval, deliberately save the commercial agreement, review the server-calculated source seconds/rate/charge/tax facts and approve its source hash. Enter the public invoice title and service description yourself. No private project, task or work note is filled into these customer fields.

The first workflow prices one whole approved sheet’s billable-seconds group at one agreed hourly rate. It rounds half-up once to the currency’s minor unit, then creates one quantity-one service line under normal exact Invoicing tax/discount rules. It does not approximate seconds with a three-decimal hour quantity or round every small entry independently. A group that rounds to zero stays recorded time rather than a fabricated positive invoice.

Create a source-owned draft, inspect it and issue separately. All revisions of the sheet share at most one current whole-sheet invoice claim. Generic invoice edits/conversion/issue/void cannot bypass that source. Source ownership and the non-stock service boundary persist even if Timesheets is disabled.

Only a never-issued draft without financial history or an unknown payment outcome may be safely discarded with a retained reason before replacement. Issued, paid, credited or authority-locked history does not release a second whole-sheet charge. Payments, credits and balances are read from Invoicing rather than copied into editable time flags.

Correct the time without rewriting issued money#

Withdraw a permitted current submission or open a retained correction with its reason. Edit the working facts privately, then submit and review a new exact revision. The previous effective approved source stays distinct until a replacement is approved; totals must not count both as current approved time.

If an unissued source invoice draft already exists, an authorized financial actor must resolve it safely before the time correction proceeds. The generic source blocker does not disclose private rate/customer details to an operational author.

An issued, paid or credited invoice keeps its original whole-sheet source even after a factual time correction. The new reviewed revision does not rewrite its amounts or authorize another full invoice. Review any credit or adjustment through normal Invoicing and the original commercial agreement. Do not erase a factual correction merely because financial history exists.

Recover a timer when the source or interval changed#

A timer that is too long, crosses its frozen week, conflicts with retained work or loses current source permission needs deliberate recovery or cancellation with a retained reason. That action records the server finish and releases the active slot. It does not silently shorten the original start/finish, create approved work or bill a customer.

When private project access is gone, the author’s recovery interface exposes an opaque own-timer reference and permitted recovery actions with a generic explanation. It does not fetch private project/task names, descriptions, notes or rates. Removed workspace staff do not regain workspace access through this recovery.

Review a permitted retained capture and allocate actual intervals manually only where current recording scope and overlap/week limits permit. Preserve the original capture and give any retained correction its reason. Do not add a second entry for time already converted successfully.

A stale version, changed workspace, revoked permission or expired demo is rechecked on direct/repeated requests. Keep entered data, reload the current source when instructed and review the new facts. The disposable demo is not a legal record archive.

Read, print and export the authorized source version#

Current private working facts, a submitted snapshot, an effective approved revision and an issued invoice’s original source can be different versions. Follow the labels and retained decisions. A historical view never overlays later private working edits.

Print identifies the source version and result pages shown. CSV applies current author/reviewer scope, neutralizes formula-leading free text and is limited to five thousand matching rows. Exports capture the authorized values before the request’s database context is cleared; they do not become empty or unscoped delayed queries.

Search, selectors, review history and source lists are paginated with stable secondary identifiers. A financial-only source is not an empty sheet: working counts, nonbillable totals and work notes are explicitly not disclosed. Retained actor names and source IDs survive eligible offboarding, while current access is revoked.

Review local recordkeeping without inventing payroll compliance#

This workflow records work and reviewed customer billing. It does not calculate statutory overtime, awards, minimum wages, paid leave, payroll, break entitlements or regulated attendance obligations. Those depend on the actual country, employment relationship and applicable rules.

Use the selected business jurisdiction and the existing country/recordkeeping guide for the appropriate local review. Language, geolocation, a currency choice, a successful local check or a demo action does not establish registration or authority approval. Existing ZATCA, FBR, ATO and other government-integration limitations remain in force.

Retain necessary originals, approval evidence and corrections for the applicable purpose and legal retention period. Do not delete a source record to hide financial history or assume that removing an employee should erase retained customer invoices.

Official references: Country, recordkeeping and tax review ↗