Support
OneShift Billing guide
From a submitted week to an invoice: approving timesheets, the rates that price the time, and the statements that carry it to the customer. Approval needs timesheet-management rights or a team lead; rates and statements need billing rights.
Timesheet approval
Approvals lists every Submitted timesheet you may act on, one row per member. Open one and you get the week itself — still editable — with Approve and Reject at the bottom. Hover a pin or a note to connect them.
Website · Contoso
Are you sure you want to reject this timesheet? The employee will be able to edit and re-submit it.
Who can approve whom
| You are | You see | You can act on |
|---|---|---|
| Timesheet manager | Every Submitted timesheet in the workspace, your own included. | Any of them. Approving your own is allowed on purpose: rejecting it would be the weaker action, and either is visible in the audit trail. |
| Team lead | Submitted timesheets of the non-lead members in your teams. | Only those. The API refuses the rest: “You cannot approve your own timesheet.” and “You cannot approve another team lead’s timesheet.” |
| Workspace manager | Same as your timesheet rights give you. | Additionally “Delete” on a timesheet, after typing delete — never on an Approved one: “Approved timesheets cannot be deleted.” |
The AI review card
On a Submitted sheet you can act on, a Review card sits under the header. Its pill reads “Looks good” or “Needs review · N”, where N counts the findings; Approvals shows the same pill per timesheet. Out-of-office days are listed for information and never count.
- Approvals lists “Needs review” first, then “Looks good”, then timesheets that were not reviewed. The “Review” filter narrows the list to All, Needs review, Looks good or Not reviewed. Under each pill one line shows the most serious finding; hover it to read the whole text. A member with several submitted timesheets has one row with a pill per week, each named by its timesheet number; a week whose review has not run yet reads “Not reviewed”.
- When the calendar and activity could not be checked, the pill reads “Looks good · activity not checked” and the card adds “Calendar and activity could not be checked, so days with no time logged were not compared to activity.”
- Findings are plain checks: time logged against the expected time, calendar activity on a day with no time logged, a project or task budget this timesheet takes over (a project that was already over budget does not flag every later timesheet), time on a prepaid project, entries without a meaningful comment (blank, fewer than three letters such as “555”, or, when AI is available, text that describes no work such as “asdf”), and a week far from the member’s usual pattern. One meaningless comment is enough for “Needs review”. The finding lists each such entry (date, task and comment), and “Send back to describe” opens Reject with a reason that asks the member to describe those entries; edit it or confirm.
- An AI summary appears below, marked “🪄 AI-generated — review before approving”. When AI is unavailable or fails, the findings still show and the card says so.
- “Suggested changes” list moving time to another task or day, marking it non-billable, marking it as training, or rewording a billable entry’s comment that has real content but is unclear, misspelled or full of shorthand (shown as old → new), each with a reason and an “Apply” button. A comment that says nothing about the work is never reworded: only the member knows what was done. Nothing is applied on its own; Apply edits the entry (a partial move splits it) and removes that suggestion, and any other suggestion for the same entry, from the list. The rest stay available to apply one by one. The findings above are not recalculated until you press “Re-run review”.
- On a billable task’s entry that you made non-billable, you can click the dashed “Training” tag under Billable to turn it on. It records why the time is non-billable and shows a small “Training” tag on the entry; Training time is left out of the write-off and approver-edit signals. Making the entry billable again clears it. Applying “Mark as non-billable” never switches it on.
- “Mark as training” suggestions come from the member’s seniority (set on Member Settings) and how their training time has moved on each project: a member who is still within the ramp-up for a project is expected to spend some time learning, and the suggestion names how much. There is one suggestion per project; when the time comes from several entries it reads “N entries”. Applying it makes that time non-billable and also sets the Training tag. A member without a seniority gets none, and changing a member’s seniority marks their reviews as changed until you re-run them. If training on a project stops falling as expected, the card adds the finding “Training on X is not falling: N% in week W.” once, on the next review, not every week after. Under the findings, a muted line shows where training is improving (“Training on X fell from 40% to 15% (week 3 of 8).”) or finished (“No training on X in the last timesheets.”).
- “Apply N changes and approve” does both in one step. It lists every suggested change with a checkbox and the findings still to check; untick what you do not want and confirm. Either every selected change is applied and the timesheet approved, or nothing is saved — for example when the timesheet changed since the review (refresh it first). It is offered only while the review is current and has suggestions.
- “Refresh review” recomputes it. “Generate review” does the same when none exists yet (“Review not computed yet.”).
What the two buttons do
- 1Approve locks the week and releases its time The status turns Approved with your name and the date. Entries on non-billable tasks are forced non-billable. Every billable entry becomes a “free entry” in the customer’s pool, ready to be imported into a statement — only approved time is ever billed.
- 2Reject reopens it The member gets a Teams message from the agent — “❌ Your timesheet for {period} has been rejected by {your name}.” followed by “Reason: …” when you gave one — and a red banner on the sheet: “Previously rejected by”, the date and the reason. They edit and press “Submit for Approval” again; you can also “Re-submit for Approval” on their behalf, filling missing time onto the default task if one is set. When they re-submit, you get “🔄 {member}’s timesheet for {period} has been resubmitted and is ready for review.” Members without the Teams agent get no message, only the banner.
- 3Fix before you approve Cells, tasks, splits, comments and “Add Entry” all work on a Submitted sheet. Dates are limited to the timesheet period and the member’s working period: “Date is outside the member’s working period.”
Rates
A rate turns billable time into money on a statement. Rates are always per hour and in the workspace currency; a daily figure anywhere in the app is a display conversion. Four places can hold a rate, and the first one that is set wins.
- 1Project + positionthe member’s position on that projectBilling → Rates → Projects, per position rowSenior Developer on Website: €120/h
- 2Projectflat rate for everyone on the projectBilling → Rates → ProjectsWebsite: €95/hwins
- 3Positionthe member’s position, any projectBilling → Rates → PositionsSenior Developer: €110/h
- 4Workspacefallback for everything elseBilling → Rates → Workspace€80/h
Worked example
Maria is a Senior Developer logging on the Website project. Website has no position rate for her role but a flat project rate, so level 2 wins: €95/h. Her workspace-wide position rate (€110/h) only applies on projects without a project rate.
Checked top to bottom for each member and project when time is captured into a statement; the first rate that is set wins. A rate of 0 counts as set and makes the time non-billable.
The History button on the Billing rates page lists every rate and currency change across the workspace, positions and projects.
Where rates live
- Billing → Rates — one page, three sections. Workspace holds the currency and the fallback rate. Positions lists every position with an inline rate field and a “Clear rate” action. Projects lists every project with its flat rate, its budget and, per position, a position-on-this-project rate. Needs both billing and workspace management rights.
- Team → Positions — where positions are created and renamed. A position is a billing label (“Senior Developer”), not an access role.
- Team → member page — the Position dropdown assigns a member their position. “No position” means levels 1 and 3 never apply to them.
How a rate reaches a statement
- 1Resolved at import When approved time is imported into a statement, each entry gets the rate the ladder resolves for its member and project at that moment, together with the position name when a position level won. The amount is rate × hours, rounded once per rate slice.
- 2Frozen afterwards Imported rates are a snapshot. Renaming or deleting a position, or changing any rate, never rewrites an existing statement — approved statements stay billed as they were billed.
- 3Shown per slice The totals break each project down per rate: “4d × 960.00 = 3,840.00” with a pill naming the position, or “Standard rate” when no position was involved. Mixed rates on one project are normal when members hold different positions.
- 4Warned when stale If a rate changes after import, the statement shows “The project rate changed since this statement’s entries were captured.” on the list and on its page, even once approved. Remove and re-import the entries if the new rate should apply.
Statements
A statement is the billable story of one customer for one period: the approved entries, priced with frozen rates, netted against any prepaid allowance, and shown to the customer on the portal. Four statuses, one direction of travel.
Editable. Invisible on the customer portal.
Editable. Now visible to portal contacts with Statements access.
Locked: date, comment, entries and import are read-only. Can be sent to invoicing.
Locked for good. Only Revert brings it back, while the invoice is still a draft.
The statement page, annotated
Website
Warnings, in full
| Message | Tone | Means |
|---|---|---|
| There are open timesheets for this customer for {time} before the statement date. | red | Open or Submitted timesheets still hold time dated before this statement. Until Draft or In Review only. |
| There are {time} for this customer not yet imported into any statement. | amber | Approved time waiting in the free pool. Import it or make a new statement. |
| Some entries have dates after the statement date. | amber | Usually a wrong statement date. |
| Some entries are from an earlier month than the statement date. | amber | Late-approved time landing on the wrong month’s statement. |
| Project budget settings changed since this statement was created. | amber | The frozen budget snapshot no longer matches the project. Re-import if the new allowance should apply. |
| The project rate changed since this statement’s entries were captured. | amber | Captured rates are frozen; re-import the entries to re-price them. |
| Some entries for the same project have different billable rates or currencies. | red | Shown always, even once approved or invoiced. One member on two rates for one project is a mistake to look at. |
On the list the same messages sit behind a triangle icon per row, red when any red message applies. All but the last disappear once the statement is Approved or Invoiced.
Working with entries
- Import brings approved time in; “Create statement” on the list makes an empty statement dated today and opens the import picker at once. “Create all statements” makes one per customer, or one per project, for every customer with free time, dated as you choose, capturing only entries on or before that date.
- Move an entry to another task of the same customer: a different project re-prices it, a task within the project keeps the rate. Picking another customer’s project removes it from this statement instead.
- Split halves an entry (at least two minutes); the new half appears right below. Adjust applies a factor to a whole task, from 0.1× to 10×, skipping entries that would fall under one minute. Cut off billable time (also under Adjust) caps a task’s billable time at the figure you type, in days, hours or minutes: every billable entry keeps its proportional share, in whole minutes adding up to the cap exactly, and the excess splits off into a non-billable entry right below (an entry whose share rounds to nothing simply turns non-billable). Reset to baseline undoes all of it back to the submitted figures.
- Remove, per entry or per task, detaches. The entry returns to the free pool with your edits kept and its captured rate cleared, so the next import re-prices it. Deleting a whole statement does the same for all its entries. Timesheets are never changed by anything you do here.
- Layout stays put while you work: an entry you move to another task keeps its row until you reload, marked bold with a swap icon, so nothing jumps under your cursor.
AI assistance
- AI assist (sparkles button in the statement header) appears only while the statement is Draft or In Review, and only when AI is set up for your environment. It offers “Improve comments” and “Translate comments…”; the second asks for a target language. Both review every entry comment on the statement. Improve only suggests a change where it materially helps (unclear, jargon, errors, mixed languages); clean comments are left alone, so “No changes suggested.” is normal. Blank comments are skipped. Improve keeps the language and the facts; Translate converts the comments to the language you chose.
- Review before anything changes. A dialog shows each comment as a before/after diff, like the Description clarity panel, with a checkbox, Edit and Revert, plus “Select all / none”. Each Improve suggestion comes with the reason it was flagged and a one-line explanation. Suggestions that came back unchanged, empty or longer than 250 characters are skipped, and a note says how many. If the AI does not respond in time for some comments, a second note says “N comments could not be reviewed…”; apply what is there and run it again for the rest. The dialog is labelled “🪄 AI-generated suggestions — review before applying.” and the button reads “Apply N comments”. Nothing is saved until you press it; closing the dialog discards every suggestion.
- Comments stay at 250 characters. Applying overwrites the comment on the statement only; the original wording is still on the timesheet entry.
- Summary is a card on the statement page with free text the customer sees on the portal and in the Excel export. “Generate summary” (or “Regenerate” once one exists) takes an optional language, otherwise it writes in the language of the comments. The generated text describes what was worked on, synthesised from the entry comments; it leaves out hours, amounts and names because the customer already sees those on the statement. When a summary already exists you are asked “Replace the current summary?”. Generated text is captioned “🪄 AI-generated — review before sending”; you can edit it by hand, and it saves when you leave the field with the “Statement updated” toast. Like the rest of the statement it is locked once Approved or Invoiced.
The customer’s view
- 1Access is per contact and per project On the customer’s Contacts tab each contact has a Statements switch per project. A statement shows on the portal only when the contact may see every project on it.
- 2Sign-in is a link, not a password “Send portal login link” mails a link valid for 15 minutes; the contact can also ask for one from the portal sign-in page with their email.
- 3Drafts stay hidden, and nobody is emailed The portal lists In Review, Approved and Invoiced statements with their status, date and comment. Opening one shows the same totals, rate slices, prepaid note and task cards you see — read-only. There is no customer approval step and no automatic email: setting In Review only makes the statement visible. Tell the contact yourself, or send them a portal login link — the only email the portal ever sends.
- 4A summary and a place to ask questions When you wrote or generated a summary, the contact sees it under a “Summary” heading on the statement. Below the statement sits an “Ask about this statement” panel with starter questions such as “What was this time spent on?”, “Which project took the most time?” and “Is any of this non-billable?”. Answers are labelled “✨ AI generated” and come only from that statement’s contents; nothing is stored. Each contact can ask about 10 questions a minute, then sees “Too many questions. Please wait a minute and try again.”
- 5You see who looked Every open is recorded; the statement page lists “Customer views” with the contact and the last time they opened it.
Invoicing
- Send to invoicing needs an Approved statement, a billable total above zero in one currency, and a “Customer No.” in the customer’s settings matching Business Central. It creates a draft sales invoice with one line for the total, attaches the Excel export, stores the invoice number and sets Invoiced.
- Create invoices on the list does it for every eligible Approved statement at once, naming the ones it skips and why. It also skips statements with a zero total — “Nothing to invoice (zero billable total)” — such as a prepaid month with no overage.
- Mark as invoiced is the manual path for workspaces without a connector: same lock, no invoice number, no way back.
- Revert deletes the draft invoice in Business Central and returns the statement to Approved. Workspace managers only, and only while the invoice is still a draft there.
- Export writes one sheet: the header (customer, date, total charge and free time), every entry, then per project TOTAL, PREPAID and BILLED days — or hours in an Hours workspace — with rate and amount, one block per rate when positions differ.
The History button in a statement’s header opens a panel with everything that happened to it: status changes, invoice fields, entries added, removed or edited, and bulk actions such as applied factor, cut off billable time, reset to baseline and split. A capture of many entries shows as one event you can expand. Details are in the Audit log section of the Workspace guide.