TIME & WORK EVIDENCE
From recorded effort to a reviewed week of work.
Connect timers and manual entries with project context, weekly submissions, human approval and the billing work that follows.
Time records should explain the work, not create another island
An hours total is easier to use when the team can see the associated task, customer and description. Tsumira combines work timers and manual entry with a weekly review process. Recorded effort, billable classification, submitted time and approval remain distinct. The same record can then support the next commercial conversation without assuming that every recorded minute is already approved or invoiced.
Explore each function
See what each capability does, how it works and where it fits into your team’s workflow.
Work timer
Start your own timer with a description and optional authorized work reference. Stop it to create a time entry that can be reviewed in the weekly workflow.
Weekly timesheets
Bring your work entries into a weekly timesheet. Check project time, separate billable work and send the reviewed week to the right person.
Manual time entries
Enter the work date, duration and description, with optional authorized work context and a separate billing description.
Time approval
A designated human reviewer inspects the submitted timesheet and decides whether to approve it or return it for correction.
Time reports
Review recorded time by work and customer context, with separate total, billable and approved effort for the selected date range.
Time to billing
Pass eligible approved work into the connected billing process, while keeping pricing, invoice creation and document issue as separate reviewed decisions.
Record work in a form that can be reviewed
Start a timer while working, or add a manual entry after the activity. Both paths can carry an authorized work reference, a description, a separate billing description and a billable indicator. The person keeps a work date and duration rather than only a project-level estimate. One active timer per operator makes the running session clear, while eligible draft and rejected entries have correction paths before submission.
- Timer and manual recording
- Optional project/task reference
- Descriptions and billable context
Submit a specific week to a human reviewer
The weekly preview shows the entries, dates, durations and billing context that will be submitted. It identifies a defined set of work rather than asking the reviewer to approve an unexplained total. A designated human reviewer decides on approval or rejection under the applicable permission. A note can explain a correction request. The draft, submitted, approved and rejected states help both sides understand where the week stands.
- Reviewable weekly entry set
- Designated reviewer and decision note
- Explicit submission and approval states
Understand the effort before moving into finance
Reports separate total, billable and approved time within the returned records for a chosen interval. Eligible approved billable work can then connect to finance, where pricing and invoice issue are separate reviewed steps. The current report reads up to 2,000 matching entries. Work-date grouping follows Japan-based rules, and connected finance uses whole JPY and Japanese consumption tax. Evaluate those operating requirements explicitly when planning the team’s workflow.
- Separate effort measures
- Approved work connected to billing
- Explicit reporting and regional boundaries
A concrete workflow
Capture the work
Choose timer or manual entry and record enough task and activity context for another person to understand it.
Check the week
Correct eligible entries and inspect the current submission preview, including billable information.
Submit and review
Choose the reviewer, submit the defined week and follow the approval or correction decision.
Continue with evidence
Use the reviewed effort in reports or the connected finance workflow, inspecting pricing and documents separately.
An illustrative working example
Illustrative workflow: a service team’s working week
A service team mixes timed project tasks with manually entered workshops. At week end, each person checks descriptions and dates, then submits the current preview. The designated reviewer asks for clarification where necessary and approves the corrected week. The project lead can inspect the recorded effort, while the finance colleague separately reviews eligible billable work and its price before preparing a customer document.
Questions about this topic
Is this employee payroll or a legal attendance system?
This page describes recorded work, timesheets and their review. It does not establish payroll, country-specific attendance compliance or a replacement for legal employment records.
Can recorded and approved time differ?
Yes. An entry can be recorded before the week is submitted or approved. Those separate states are important for understanding the review process.
Does time approval also approve the final invoice?
No. Pricing and financial document issue are separate controlled actions, even when eligible approved work is connected to finance.
What current limits should an international team evaluate?
Work dates currently follow Japan-based rules. The time report reads up to 2,000 matching entries, and connected finance uses whole JPY with Japanese consumption tax.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Asana
Workflow concept: Plan task-context migration before starting a shared effort-recording workflow.
Microsoft Excel
Workflow concept: Prepare a reviewed effort report with explicit scope and approval states.
Xero
Workflow concept: Design a checked handover from approved effort to the accounting process.