When importing data to Silverbucket it is vital to keep the structure identical to the example datasheet to ensure a flawless import:

- First row contains the names of the headers - it is not necessary to edit the first row.
- Second row in your file is where your data starts to get imported
- Columns need to be in the same exact order as in the examples
- Rows after the default structure's last column are never read / handled when importing
- Never have hidden columns in your data sheets

- Importing actual hours for personnel between the given timespan.

1) 4,5 hours for project [RS]Bridge 2 with a note "Documentation" for user whose username is 'olivia.hall_91'
2) Row 2 will be skipped because no such project code is found in Silverbucket as "RS 23". Before re-integrating the file, a project with such Project Code should be created first.

- Silverbucket matches rows to Silverbucket's usernames case-sensitively ("SilverBucket_Support" is not considered the same as "silverbucket_support")

If the data structure was correct, you can see the outcome in Silverbucket right after the upload. You can check this by using the User Report that tracks actual hours, for example.