Time Sheet Upload

This integration uploads time sheets. The Time Sheet Upload allows customers that are currently using a timekeeping system to maintain that system and utilize this upload to pass the pertinent data for supplier billing to SAP Fieldglass.

Connector Overview

Component

Detail

Company Type

Buyer

Supplier

MSP Partner

Version Type

API-V1.0

BULK-DELTA-V1.0

Format

CSV

Prerequisites

Company Details Setting must be turned on for Integration – Time Sheet Upload.

User role permission must be turned on for Upload Data and Download Data.

Predecessors

Workers

Related Connectors

Time Sheet Credit Debit Memo Upload

Full Time Sheet Credit Debit Memo Upload

TITO Time Sheet Detail Upload

File Formatting

Header

Component

Required?

Definition/Use

Notes

Value

Type

Yes

Timesheet

If you have a custom connector name for a standard connector, you may use the exact same custom name for the Type header; otherwise, you must use the standard name shown in the Value field.

Time Sheet Upload

Transaction

Yes, for API upload.  Bulk version does not require.

Only applicable for the API-V1.0 version.

Transaction Type

Determines how the data is validated:

Valid values are:

  • True. – In the event of any error(s), the entire file will be rejected.

  • False. – In the event of any error(s), only those records in error will be rejected and the remaining valid records will process. This is the default value for bulk upload.

Only applicable to the API version.

Approval Required

No

Determines if timesheets will be required to go through an approval process.

Valid values are:

  • True. – Time sheets will route through the appropriate approval process if one is assigned per the current configuration of SAP Fieldglass.

  • False. – Time sheets will bypass the approval process.

Bypassing approvals will also bypass, if enabled on the related job posting, the rule Disallow Approval Time/Expense Sheet/invoice when Committed Spend is Exceeded. This may result in the committed spend for the worker being exceeded.

If this field is not included in the header, the default value will be True.

Send Notification?

No

Determines if notifications related to the creation of time sheets will be sent to users.

Valid values are:

  • True. – Notifications will be sent to users per the SAP Fieldglass Messaging Configuration within the application. Note: Any notification configured to be sent during the normal time sheet creation, submission, and/or approval process will be sent.

  • False. – Notifications will not be sent.

If this field is not included in the header, the value will default to True.

Language

No

Determines the language to be used for values in the file, such as drop-down lists and radio buttons. Column headers will always default to the upload user's preferred language.

The valid language values are:

Arabic (Standard Arabic)
Chinese (Simplified)
Chinese (Traditional)
Dutch (Netherlands)
English (United Kingdom)
English (United States)
French (Canada)
French (France)
German (Germany)
Hebrew (Israel)
Hungarian (Hungary)
Italian (Italy)
Japanese (Japan)
Korean (Korea)
Mongolian (Mongolia)
Polish (Poland)
Portuguese (Brazil)
Portuguese (European)
Russian (Russia)
Spanish (Mexico)
Swedish (Sweden)

Number Format

No

Determines the number format to be used in the file.

The valid values are:

  • “#,##9.99" (Example: "1,234,567.99”)

  • “#.##9,99" (Example: "1.234.567,99”)

  • “#'##9.99" (Example: "1'234'567.99”)

  • “# ##9,99" (Example: "1 234 567,99”)

The quotes are required even if the value does not have a comma in it. If the header field is not present, the value will default to "#,##9.99" (Example: "1,234,567.99").

Date Format

No

Determines the data format used in the file.

The valid values are:

  • MM/DD/YYYY

  • DD/MM/YYYY

  • YYYY-MM-DD

If this header field is not present, the value will default to MM/DD/YYYY.

Submit

Yes

Determines the status in which the time sheets will be saved.

Valid values are:

  • True. – Timesheets will be considered completed and submitted to the next step in the time sheet workflow configured in SAP Fieldglass.

  • False. – The time sheets will be saved in draft status.

Buyer

Yes if supplier upload

Company Code of the buyer company to which the time sheets are to be saved.

If unknown, the code can be found under

Admin > Company Structure > Company Details on the buyer side of the application, or it is also the characters prefacing the letters “TS” in the timesheet IDs of the time sheets being uploaded.

Supplier Review

No

Routes the time sheet for supplier review.

Valid values are:

  • True– If ‘Supplier review on time sheets’ is On for the worker and the value passed is True in the header, the time sheet goes to the supplier for review.

  • False– Will not be sent to the supplier for review.

If the field is not included in the header, the default value will be False.

Associate Unassigned Cost Centers to Workers

or

Associate Unassigned Cost Centres to Workers

No

Determines if cost centers in the upload file that are not currently associated to worker should be associated to worker. (Also requires company config ‘Allow worker access to all Cost Centers and Task Codes, and submit Time Sheets through the UI (can be updated on worker only)’ to be enabled.

Valid values are:

  • True

  • False

If not included in header, the value will default to False.

Different spelling of header based on upload user’s language.

Comments

No

Upload comments.

Any text the user would like to enter may be entered here.

Values entered in this header field will appear in the Comments field at the bottom of all time sheets included in the upload file and will be visible to any application user that has access to view the time sheet. The comment entry date will be the time stamp of the upload and the author name will be the name of the user that uploaded the time sheet.

Immediately following the Header section of the upload is one blank line.

Detail

Field Header Name

Data Type

Length

Required?

Value(s)/Format

Description/Use/Field Rules

Job_Seeker_ID

or

Work_Order_ID

or

Worker_ID

or

Buyer_Ref

Text

16

Yes

Unique Identifier

Examples:

Job_Seeker_ID:XXXXJS00000001

Work_Order_ID:XXXXWO00000001

Worker_ID: XXXXWK00000001

Unique identifier for the worker. Can be any of the four listed to the left, but must be consistent throughout the file.

Last_Name

Text

200

No

Example:

Smith

Worker’s last name.

First_Name

Text

200

No

Example:

John

Worker’s first name.

Date

Date

Yes

Format should match that of the format configured for the company in the application.

Start date of the work week that time is being booked against. The day of the week on which the start date occurs will be dependent on the Timesheet Start Date configured in the Company Details section within the application.

Week_Start_Date

Date

Conditional

Format should match that of the format configured for the company in the application.

If using a bi-weekly start date, this is the start date of the single week for which time is being entered on the current record.

For bi-weekly time sheets, a minimum of two lines will be required for each time sheet (if time is being recorded for both weeks). For the initial week, the Date and the Week_Start Date fields will have the same value, and for the subsequent week, the Week_Start_Date will be seven days later than the Date field.

For 8 day time sheets, enter hours via the Date and Week Start Date columns similar to the existing bi-weekly/monthly requirements.

This field is not applicable for weekly time sheets.

Cost_Center_Code

Text

200

Yes

Valid SAP Fieldglass Cost Center Code.

Cost Center Code that the Worker’s hours are to be assigned. Value must be from the list of currently active Cost Centers in SAP Fieldglass at the time of the upload and must be associated with the Worker.

Cost_Center_Name

Text

200

No

Name related to the Cost Center Code listed above.

Task_Code

Text

100

Yes

Valid SAP Fieldglass Task Code.

Task Code that the worker’s hours are to be assigned. Value must be from the list of task codes. The Task Code must be active and assigned to the worker booking time against it.

Task_Name

Text

100

No

 

Name associated with the Task Code entered above.

GL_Account_Code

Text

100

Conditional

Valid Active GL Account code.

Must be from the list of current active GL account codes and must have an association to the worker for which time is being booked.

This column is applicable only if GLA allocation on job postings and statements of work is required plug-in is On.

This field is mutually exclusive with Segmented Object Detail field.

GL_Account_Name

Text

100

No

 

Name related to the GL Account entered above.

Segmented Object Detail

Text

2000

Conditional

Examples:

  • IS|Admin|12001

  • IS-Admin-12001

  • IS;Admin;12001

  • IS:Admin:12001

Segmented Object Detail string. Segments will be separated by delimiter on the Segmented Object.

Valid delimiters are colon (:), semi-colon (;), pipe (|) and dash (-).

Required if Segmented object detail configuration set.

This field is mutually exclusive with GL Account fields.

Location Code

Text

100

Conditional

Valid SAP Fieldglass location code

Location code for rate category.

Enable at least one sub-configuration for the company configuration Use multiple locations.

If left blank, system will assign hours for the Rate Category against the location that is flagged as ‘Primary’.

Location

Text

100

No

Location name for rate category.

Enable at least one sub-configuration for the company configuration Use multiple locations.

Rate_Category_Code

Text

100

Yes

Valid SAP Fieldglass Rate Category code.

Rate Category code that hours for current record should be recorded against. Rate paid for the hours entered will be those related to the Rate Category Code entered here. Value must be a current active Rate Category associated with the Worker.

Rate_Category_Name

Text

100

No

Name related to the Rate Category Code entered above.

UOM

Text

100

Yes

Valid values:

  • Hr (for hour)

  • Day

  • Mo (for month)

The unit of measure assigned to the Rate Code previously entered. 

Sun_Hrs

Decimal

No

Example:

08.00

Hours worked Sunday.

Range: 0.00 – 24.00*

Header is required even if no hours entered.

Sun_Comment

Text

100

No

Sunday Comments

Mon_Hrs

Decimal

No

Example:

08.00

Hours worked Monday.

Range: 0.00 – 24.00*

Header is required even if no hours entered.

Mon_Comment

Text

100

No

Monday Comments

Tue_Hrs

Decimal

No

Example:

08.00

Hours worked Tuesday.

Range: 0.00 – 24.00*

Header is required even if no hours entered.

Tue_Comment

Text

100

No

Tuesday Comments

Wed_Hrs

Decimal

No

Example:

08.00

Hours worked Wednesday.

Range: 0.00 – 24.00*

Header is required even if no hours entered.

Wed_Comment

Text

100

No

Wednesday Comments

Thu_Hrs

Decimal

No

Example:

08.00

Hours worked Thursday.

Range: 0.00 – 24.00*

Header is required even if no hours entered.

Thu_Comment

Text

100

No

Thursday Comments

Fri_Hrs

Decimal

No

Example:

08.00

Hours worked Friday.

Range: 0.00 – 24.00*

Header is required even if no hours entered.

Fri_Comment

Text

100

No

Friday Comments

Sat_Hrs

Decimal No

Example:

08.00

Hours worked Saturday.

Range: 0.00 – 24.00*

Header is required even if no hours entered.

Sat_Comment

Text

100

No

Saturday Comments

[c] Task Code Customer Field(s)

Dependent upon custom field type.

Dependent upon custom field type.

Dependent on custom field settings.

Dependent on custom field.

When Custom Field Type = Segmented Pick List and the Autopopulate Segment' rule on the Pick List = Yes, if a segment value is left blank on the upload, the value is auto populated on the document if there is only one possible value based on the previous segment values. If there is more than one possible value, an error message displays.

[c] Time Sheet Custom Field(s)

Dependent upon custom field type.

Dependent upon custom field type.

Dependent on custom field settings.

Dependent on custom field.

When Custom Field Type = Segmented Pick List and the Autopopulate Segment rule on the Pick List = Yes if a segment value is left blank on the upload, the value is auto populated on the document if there is only one possible value based on the previous segment values. If there is more than one possible value, an error message displays.

* Note: When the Buyer has the “enter 100th hour on TS” flag on, the hours can be entered in 100th hour increments, i.e., 8.01, 8.02…..8.99. However, if the flag is not turned on, then hours must be entered in quarter or 10th hour increments, i.e., 8.10, 8.20, 8.25, etc.

Unique Identifier

Each unique combination of the following fields will require another record.

  • Job Seeker ID/Worker ID/Work Order ID/Buyer Ref

  • Cost Center Code

  • Task Code

  • GL Account Code

  • Date

  • Week_Start_Date

  • Rate Category Code

The position of the primary key fields is important and cannot be moved.

Uniqueness Examples:

  • A worker with both Straight Time and Overtime hours will require at least two lines.

  • A worker booking time to three Cost Centers will require at least three lines.

  • A worker with two different Cost Centers and two different Task Code Customer Field values will require a minimum of four lines.

Configuration Considerations

#

Item

Notes

1

Associate Unassigned Cost Centers to Workers

or

Associate Unassigned Cost Centres to Workers

Prior to adding this header, company configuration ‘Allow worker access to all Cost Centers and Task Codes, and submit Time Sheets through the UI (can be updated on Worker only)’ must be enabled.

The first item is for upload users with language preference of English (United States). The second item is for those with preference of English (United Kingdom).

For Contingent Workers, the entered cost centers will be associated to the worker.

For SOW Workers, we will validate if the underlying SOW has the new SOW rule Give Workers Access to all Cost Centers belonging to the Legal Entity of the SOW enabled. If enabled, the entered Cost Centers will be associated to the SOW Worker, else the upload will fail for that worker.

2

Custom Fields

Prior to adding custom fields, determine if the value will be constant within a given time sheet or could have multiple values within a single time sheet. 

If only a single value per time sheet is required, then a time sheet custom field may be best. If it varies throughout the week, then a task code custom field is likely the best choice.

3

Data Feed Timing

If implementing an automated solution, it is important that the owners of both SAP Fieldglass and the time sheet system fully understand the data and processes of each system and ensure that the timing of data flowing between the two is set up to best ensure data integrity.

For example, if workers are only downloaded on Sundays and the time sheets are uploaded on Fridays, it is likely there will be issues with end dates and/or start dates as the updates to worker profiles do not arrive until after the worker’s time sheet data.

4

Associations

Cost Centers, Task Codes, Rate Categories, and GL Accounts can only be based on the list of those associated with the worker. If new items are required for booking of time, other than those currently associated with the worker, then those associations must be updated prior to uploading the hours.

5

Task Code Custom Field(s)

If a Task Code Custom Field is based on values within a pick list, then only those values will be valid in the Time Sheet Upload. If working with an external system, be sure that both application owners understand the full set of values that may be populated in this type of non-standard field.

6

Upload Timing

Ensure that time sheets are uploaded at the most opportune time to ensure that the most time sheets are approved and ready to be submitted for the time period, while at the same time being considerate of the supplier’s payroll cycle.

Monday evening is often the best practice for Time Sheet Upload submissions. This provides workers time to book time for the previous week and gives suppliers reasonable time to download and run their payroll.

7

Supplier Side Approvals

As mentioned above, it is possible to bypass Approvals by using this upload. If the Approval Required flag is set to False in the header, then all time sheet approvals will be bypassed.

If a buyer has suppliers that upload time sheets and they do not wish to allow them to bypass Approvals, then the Enforce Approvals on Supplier Side Uploads flag should be enabled in the Buyer’s Company Configuration. This will disallow suppliers from uploading time that bypasses the preconfigured approval workflow.

8

Time Sheet Revisions vs. Credit Debit Memos

It is important that thoughtful consideration be given to how time sheets and time sheet-based invoices will be corrected for a given company. The two options are exclusive of each, and each carries their own pros and cons.

Enabling time sheet revisions places the responsibility of correcting previously incorrect time sheets into the hands of the worker themselves. This can often be advantageous, since the worker would know better than anyone else the work they did and to which projects it should be billed.

In contrast, the Credit and Debit Memo functionality is handled by the worker’s supplier. Worker’s time sheets are locked once approved and cannot be altered in the future. Credit Debit Memos are adjustments to the time sheet-based invoices instead of the actual time sheets. This functionality has its own merits, since the final responsibility for correct billing often lies with the supplier.

9

Buyer Reference

It is important to remember that buyer_ref may not be unique in the system. For a given buyer ref and time sheet start date, there must be only one worker associated, otherwise an error will be generated.

10

Timesheet Revision

Internal Reference TIME_SHEET_REVISION_REASON must be assigned to a preconfigured Time Sheet Revised Reason.

Assumptions/Tips

  • The time sheet must be in Draft or Rejected status.

  • Total time sheet amount will be automatically rounded to a whole number, but displayed to two decimal points if the currency is Yen.

  • When uploading a Bi-weekly, Monthly, or Semi-monthly time sheets via the existing standard Time Sheet Upload users will continue to include multiple rows for each week of the Time Sheet Frequency period.

    Example: When uploading time for the second Semi-monthly period of August 2015, there would be three rows needed in the time sheet standard upload:

    • Row 1 – includes hours for 8/16 thru 8/22

    • Row 2 – includes hours for 8/23 thru 8/29

    • Row 3 – includes hours for 8/30 and 8/31

  • Bypassing approvals via header ‘Approval Required = False’ will also bypass, if enabled on the related job posting, the rule Disallow Approval Time/Expense Sheet/invoice when Committed Spend is Exceeded. This may result in committed spend for the worker being exceeded.

  • If Auto Invoice is enabled and if the new Job Posting Template/SOW Template flag Allow Additional Invoice Adjustment Currency is enabled, the system will look back to the latest confirmed Work Order/Work Order Revision/SOW/SOW Revision for the additional adjustments.

  • When a Time Sheet is submitted successfully via this upload, the system will update tenure information.​​​​​

  • Suppliers can upload buyer's time sheet custom fields.

  • Upload cannot affect time sheets in 'Revoked' status.

  • A read-only SOD value can be edited via this upload if the upload header 'Associate Unassigned Cost Centers to Workers' is set to true.

  • For Rates 2.0:

    • When Rates 2.0 is enabled and this upload is used to submit time sheets (not save time sheets as Draft), the system validates and processes rate rules when the rule Use Rule to Calculate Rate At is set to Time Sheet.

    • Rate values are calculated using the same logic as the UI, including how to determine the Calculate Rate's Rate Component Group, if used, and MSP Fee value.

    • For non-Rate Schedule time sheets, the rules process when the time sheet is submitted. If there is an issue with a Rate-based Rule, the time sheet goes into 'Pending Review' status instead of being sent for approval.

    • For Rate Schedule time sheets, once the rate schedule time sheet is submitted, the system runs any applicable rules logic (e.g. Time Sheet Rules to allocate time against rates) and then the rules process. This supports client use cases where the rates' values depend on the hours booked against certain rates. If there is an issue with a rate-based rule, the time sheet goes into 'Pending Review' status instead of being sent for approval.

Errors

The following errors can occur when processing this upload file:

Possible Errors and Resolutions

Error Message

Resolution

{0} column is missing.

None of the supported unique identifier columns are present in the upload file. The unique identifier for the worker can be any one of the following: Job_Seeker_Id, Work_Order_Id, Worker_Id, or Buyer_Ref. Choose one and use it consistently throughout the entire file.

{0} is invalid for {1}.

{0} is the project Cost Center code and its valid date range (for example, "CC001[01/01/2024 to 12/31/2024]"); {1} is the date for which hours were entered. The date falls outside the project Cost Center's valid date range. Remove hours for the date shown, or contact your administrator to extend the project Cost Center date range.

{0} must be between 0 and 24 Hours.

{0} is the day-of-week column name (for example, Monday). The hours entered for that day are less than 0 or greater than 24. Enter a value between 0 and 24 in the affected day column.

All records in file need {0} value. Record cannot be processed without this information.

{0} is the identifier column name (for example, Job_Seeker_Id). Every row in the upload file must include a value for the identifier column. Enter the required identifier value for every row.

Cannot enter time against two daily rates on same day.

The upload file contains two rows for the same worker and date that both use daily rate categories. Only one daily rate row is allowed per worker per day. Remove the duplicate daily rate row for the affected date.

Cannot submit a Time Sheet against a closed Work Order.

The Work Order associated with this time sheet has been closed. Contact your buyer administrator to confirm whether the Work Order should be reopened, or verify whether time should be submitted under a different Work Order.

External Ref is blank. Time Sheets cannot be uploaded.

The External Ref column is present in the file but no value was provided. Enter a valid External Ref value for each row, or replace External Ref with a supported identifier column (Job_Seeker_Id, Work_Order_Id, or Worker_Id).

Invalid General Ledger Account Code, or Cost Center/Task Code/General Ledger Account Code combination is invalid.

The General Ledger Account Code does not exist, or the combination of Cost Center Code, Task Code, and General Ledger Account Code is not valid for this worker. Verify the GL Account Code against the worker's cost allocation configuration and correct the value in the GL Account Code column.

Invalid Task Code or Cost Center/Task Code combination is invalid.

The Task Code does not exist or is not valid for the specified Cost Center and worker. Navigate to the Worker record and verify the Cost Allocation tab to confirm valid Cost Center and Task Code combinations. Correct the value in the Task Code column.

Invalid value entered for {0}. The value must be either 0 or 1.

{0} is the day-of-week column name. The rate category for this row uses checkbox (unit) entry and accepts only the values 0 or 1. Enter 0 or 1 in the affected day column.

Invalid values for Cost Center Code

The Cost Center Code in the upload file does not exist or is not assigned to this worker. Verify that the Cost Center is assigned to the worker on the Cost Allocation tab of the Worker record. Correct the value in the Cost Center Code column.

Invalid values for Date

The value in the Date column cannot be parsed using the company's configured date format. Verify that the date format in the file matches the format configured for your company and correct the value in the Date column.

Invalid values for Location Code

The Location Code value is not recognized, or the column header is incorrect. Verify that the location exists for your company and that the column header is spelled exactly as "Location Code". Correct the value in the Location Code column.

Job Seeker ID is key information to process the file, file can not be processed without this information, all record need to have value for it.

Every row in the upload file must include a Job Seeker ID value. Enter a valid Job Seeker ID for each row, or use an alternative identifier column (Work_Order_Id, Worker_Id, or Buyer_Ref) consistently throughout the file.

Missing data for Cost Center Code

The Cost Center Code column is present but no value was provided for this row. Enter a valid Cost Center Code for the worker.

Missing data for Date

The Date column is required but no value was provided for this row. Enter the time entry date in the Date column.

Missing data for Job Seeker ID

The Job Seeker ID column is present but no value was provided for this row. Enter a valid Job Seeker ID, or use an alternative identifier column (Work_Order_Id, Worker_Id, or Buyer_Ref) consistently throughout the file.

Missing data for Work Order ID

The Work Order ID column is present but no value was provided for this row. Enter a valid Work Order ID, or use an alternative identifier column (Job_Seeker_Id, Worker_Id, or Buyer_Ref) consistently throughout the file.

Missing data for Worker ID

The Worker ID column is present but no value was provided for this row. Enter a valid Worker ID, or use an alternative identifier column (Job_Seeker_Id, Work_Order_Id, or Buyer_Ref) consistently throughout the file.

No time entered. Time Sheet cannot be submitted.

The time sheet record group contains no hours entered for any day. Enter hours in at least one day column for the time sheet.

Please enter values from among {0} only, for the rate {1}.

{0} is the list of allowed fractional day values for the rate (for example, 0.25, 0.5, 0.75, 1.0); {1} is the rate category name. The hours entered for this row are not among the allowed fractional values for this daily prorated rate. Enter one of the values listed in {0} in the affected day column.

Rate Category is not associated to the specified Rate Unit.

The Rate Category Code and Rate Unit (UOM) values in the upload file are not a valid combination for this worker. Verify the rate category and unit combination against the worker's work order rates and correct the values in the Rate_Category_Code and Rate Unit columns.

Rate_Category_Code not valid for the specified Worker.

The Rate Category Code is not valid for this worker's work order. Verify the Rate Category Code against the worker's assigned rate categories and correct the value in the Rate_Category_Code column.

Segmented Object Detail value is invalid, or Cost Center/Task Code/Segmented Object Detail combination is invalid.

The Segmented Object Detail (SOD) value does not exist, or the combination of Cost Center Code, Task Code, and Segmented Object Detail is not valid for this worker. Verify the SOD value and its combination with the Cost Center Code and Task Code. Correct the values in the upload file.

Time Entry does not match against hours entered against Time In/Time Out for Date: {0}.

The hours in the time entry rows do not match the hours calculated from the Time In/Time Out records for the affected date. Review the time entry for that date and correct the hours in the daily hours columns (for example, Mon_Hrs, Tue_Hrs) so they match the totals derived from the Time In and Time Out values.

Time In/Time Out is not supported for daily rate with prorated values. Please contact your supervisor.

The time sheet uses TITO (Time In/Time Out) entry type, which is not compatible with a daily rate that has prorated fraction values. Contact your supervisor or program administrator to change the time sheet entry type or the rate configuration.

Time Sheet can only be uploaded for Buyer {0}, as specified on the header.

{0} is the buyer company code specified in the file header. At least one row references a time sheet that belongs to a different buyer. Verify that all rows in the upload file belong to the buyer company specified in the header.

Time Sheet can only be uploaded if they are in Sequence.

Time sheets for this worker must be uploaded in chronological order by start date. Reorder the records in the upload file so that time sheets are processed sequentially.

Time Sheet date does not match the date given in the file.

The date in the Date column does not fall within the time sheet's start and end date period. Verify the Date column value against the time sheet's start and end dates in the application and correct the value.

Time Sheet is associated to a Rate Schedule. To upload, please use Simplified Time Sheet or Valorized Time Sheet instead.

This time sheet is linked to a Rate Schedule and cannot be processed using the standard Time Sheet Upload connector. Use the Simplified Time Sheet Upload or Valorized Time Sheet Upload connector, which support rate-schedule-based time sheets. Contact your system administrator to confirm which connector is enabled for your company.

Time Sheet is in invalid status.

The time sheet is in a status that does not allow upload processing. Verify the time sheet status in the application and ensure it is in an eligible state before uploading.

Time Sheet not available for this date.

No draft time sheet exists for this worker on the specified date. Verify that the Date column value matches an existing time sheet start date. Open the Worker record and navigate to the Time & Expense tab to confirm available time sheet start dates.

Time Sheet or Credit/Debit Memo Upload of Monthly Time Sheets is not supported.

The worker's time sheet frequency is Monthly. Monthly time sheets cannot be submitted using the Time Sheet Upload connector. Submit the monthly time sheet manually through the application.

Time Sheet should be in DRAFT or Rejected Status.

The time sheet is not in Draft or Rejected status and cannot be submitted via upload. Verify the time sheet status in the application. Only time sheets in Draft or Rejected status can be submitted through this connector.

Time Sheet should be in Pending Validation Status.

The worker uses external validation and the time sheet must be in Pending Validation status for this upload operation. Verify the time sheet status and confirm that the external validation workflow is configured correctly for this worker.

Total hours entered across Time Sheets exceeds more than 24 for the following dates: {0}.

{0} is a comma-separated list of dates. The combined hours entered across multiple time sheets for this worker exceed 24 hours on the listed dates. Reduce hours for the affected dates so the daily total does not exceed 24 hours.

UOM is not correct, or rate category is not associated to Job Seeker: {0}, or the rate is not valid for the date(s) for which time has been entered. Please re-apply time to the appropriate rates.

One or more issues were found with the time entry. Verify the following: (1) the UOM column contains a valid value — Hr, Day, or Mo; (2) the Rate_Category_Code is an active rate category currently associated with the worker; and (3) the rate is valid for the time entry dates and has not expired. Correct the Rate_Category_Code and UOM columns and re-submit.

UOM not valid for the specified Worker.

The Rate Unit (UOM) value is not valid for this worker's work order. Verify the UOM against the worker's assigned rate categories and correct the value in the Rate Unit column.

Week Start Date is not valid for the Time Sheet.

For bi-weekly or semi-monthly time sheets, the Week_Start_Date value does not correspond to a valid week boundary on the time sheet. Open the Worker record in the application, navigate to the Time Sheet tab, and confirm the correct week start dates. Update the Week_Start_Date column in the upload file accordingly.