This article applies to Aiwyn Practice.
This article explains the path a time entry takes from the moment you save it to the moment a client is invoiced for it, and why the timing and wording of your entry decide what that client eventually reads.
Saving and submitting are different steps
An entry is saved the instant you select Create Time Entry, but it is not yet part of a submitted timesheet. Until you submit, it is flagged as draft. The summary row keeps draft hours visibly separate from the rest: the Total Hours metric reads as two numbers, for example 32.5 + 7.0 draft, so you can see how much of the period is still uncommitted. Nothing is lost if you close the page; drafts persist and stay fully editable.
Selecting Submit Timesheet moves the period's entries out of draft and into your firm's approval workflow. Your submission is also your confirmation that the hours are accurate. Saving protects your work; submitting hands it over.
Submission narrows what you can change
Once submitted, an entry cannot be moved back to draft. It can still be edited, but only by someone who holds the Edit Submitted Entry permission, which standard staff do not usually have. In practice this means a manager returns the timesheet for revision, or a staff member with the permission makes the change.
The approval workflow itself is configured per firm, not fixed by the product. Who reviews, and whether approval is automatic, depend on that configuration.
Approval is the gate into WIP
Once approved, entries leave the Timesheet's control and appear in WIP as unbilled value. This is the boundary that matters most: Timesheet is where work is captured, WIP is the inventory of billable value, and approval is the gate between them. An entry sitting in WIP has been accepted as an accurate record of work and is waiting for a billing decision.
Only billable time makes this journey. Non-billable and operational time stay on the timesheet and never enter WIP. See How work enters and leaves WIP and How Aiwyn classifies billable, non-billable and operational time.
Billing carries your note to the client
From WIP, entries are placed onto a draft invoice and, when that invoice is sent, onto an issued invoice. This is where the Notes (Client-Visible) text you wrote at capture time resurfaces as the default description on the invoice line. A note written carelessly on a Tuesday is a note the client may read on a bill weeks later.
Once an entry has been invoiced it is locked. A locked entry cannot be edited by anyone, whatever their permissions.
Each stage narrows what can change
Draft entries are fully editable. Submitted entries are editable only with elevated permission and cannot return to draft. Approved entries have become financial records in WIP. Locked entries have been billed and cannot be edited at all. That progression is why correcting a mistake gets harder the longer you leave it, and why logging as you go is worth more than reconstructing later. For the status names, see Time entry status reference.
The client-visible note is invoice copy
A time entry's Notes (Client-Visible) text is not internal documentation. It travels with the entry through approval into WIP and onto a draft invoice, where it becomes the line's default description. The person who eventually reads it is not your reviewer; it is the client comparing a bill against expectations.
This is why operational and time-off entries offer a separate field. Comments (internal use) stays inside the firm and is never displayed to clients. That is where reviewer context and internal reasoning belong. [SME to confirm: whether the Time tab also offers Comments (internal use); the product guide lists it only on the Operational and Time Off tabs.] Text written in the wrong field is either lost to the reviewer or exposed to the client.
Because the note is invoice copy, shorthand that makes sense in a timesheet grid reads badly on a bill. The practical test is whether the sentence would survive being read aloud to the client. The draft invoice reviewer can rewrite the description before the invoice goes out, but the window for wording it well cheaply is at capture. See How WIP becomes a draft invoice line item.
Logging daily produces a better record
Time logged the day it happened carries specifics: which client, which task, what was done. Time reconstructed on Friday from memory carries approximations: rounded durations, the wrong project, a generic description. Both produce a filled timesheet; only one produces an accurate one, and the reconstructed version is what reaches WIP and what a client is billed against.
The detail most easily lost is the Notes (Client-Visible) description, because it is the only field that cannot be inferred later. The product helps in three ways:
- Switching the timesheet to the Calendar layout plots entries against hourly slots, so an unlogged afternoon appears as empty space rather than as a missing row.
- Entries save as drafts immediately and stay editable until submission, so logging in small increments through the day costs nothing.
- Selecting a task in the My Work panel pre-fills the client, project and work code, so a daily entry takes seconds.
Related
- Time entry status reference
- Submit and correct a timesheet
- Log and manage time entries
- Work with the timesheet view
- How Aiwyn classifies billable, non-billable and operational time
- How timesheet rules shape what staff can log
- How work enters and leaves WIP
- How WIP becomes a draft invoice line item
- Timesheet screen and field reference