Logging time and how it reaches your PSA's billing

Time you log in Current is the same time that shows up on your PSA's invoice — so the Log time dialog is built to match what your PSA actually requires, catch problems before you submit, and never silently lose an entry if the sync hiccups. The dialog speaks your provider's language: on Autotask the billing fields are billing code, work type, contract, and role; on ConnectWise they're work role, work type, and agreement. The flow is identical.

You can log time three ways: start a timer and stop it when you're done, quick-add time directly from a task card, or fill in a weekly timesheet grid. All three open the same Log time dialog and go through the same checks.

1. 1
   Pick what you worked on

   Choose the project, then the task or ticket. Anything not yet synced to your PSA is shown disabled, labeled "(not synced)."
2. 2
   Set date, hours, and start/end time

   Hours can be entered in quarter-hour increments; editing the end time recalculates hours automatically, and vice versa.
3. 3
   Fill in billing details

   The billing fields for your provider — billing code, work type, contract, and role on Autotask; work role, work type, and agreement on ConnectWise. Current pre-fills what it can from your PSA (see below), and warns you if the lists haven't synced yet.
4. 4
   Add a summary

   Required — your PSA needs a summary on every time entry. Internal notes are optional and never shown to partners.
5. 5
   Choose visibility

   Leave "Visible to co-managing users" off to keep the note internal, or turn it on to share it with a co-managing partner. It's never shown in the partner portal either way.
6. 6
   Log time

   Current saves the entry and, for a PSA-synced project, immediately tries to push it to your PSA.

Where your PSA already has an answer, Current uses it instead of guessing: the contract or agreement defaults to the exact one your PSA has on that project — matched by the contract's own id, not by picking a same-named contract that might belong to a different client — and the role defaults to your assigned role on that task if you're the assignee. Anything the PSA doesn't provide falls back to whatever you used last on that project — and if you've never logged time on that project, the billing code or work role defaults to the one you used most recently anywhere, so it's rarely blank. Every default stays editable.

How Current rounds logged hours is a workspace-wide setting a Tenant Admin controls in Settings — round up, round to the nearest, or don't round at all, in quarter-hour or tenth-hour steps. It applies to everyone's entries so the whole team bills the same way. It ships defaulted to exactly how Current has always rounded, so nobody's numbers change unless an admin deliberately changes the setting.

Current checks before you can log time against something that can't actually accept it, and shows you the specific reason rather than a generic error:

• ＋The project is Current-native — time here stays in Current and never tries to sync.
• ＋The task or ticket hasn't synced to your PSA yet.
• ＋The ticket's type doesn't accept time entries in your PSA.
• ＋Your Current account isn't linked to a PSA resource or member yet.

An entry moves through Draft, Submitted, Synced, and Approved (or Rejected). Approved and Rejected are read back from your PSA itself — Current doesn't guess at approval status. If a push fails, the entry stays as a local draft with the reason shown, so it's never silently lost; a manager can also retry other people's stuck drafts in bulk.

See "Project modes: PSA-synced or Current-native" for how project type determines whether time syncs at all, and "The partner financial firewall" for how time-entry data is kept away from partner viewers.