Bulk load forms from a spreadsheet
Pyrus can convert your Excel spreadsheets into tasks, which is handy if you manage your payroll in Excel or receive invoice lists from a contractor in xlsx format. Uploading your spreadsheets to Pyrus means you can automatically send pay stubs to your employees, submit invoices for approval, or handle any other spreadsheet workflow need you might have.
Pyrus Tip: An uploaded Excel file can have no more than 5000 filled-in rows. If this number is exceeded, the 5001st, and all consequent rows, will not be imported to the tasks.
How to fill out a form using an Excel spreadsheet
You’ll need two things:
- An Excel file. In this case, it’s a payroll spreadsheet that includes employee names, job titles, salaries, and other information.
- A Pyrus form. Note: the form’s field names must be the same as the names of the spreadsheet’s columns. In our case, the form should contain the fields “Employee name,” “Job title,” “Annual salary,” “State tax,” and others. Supported form field types include: Text, Date, Number, Money, Check Mark, Due Date, List, Phone and Contact.
Open the form and click on Import from Excel.
Click on Upload XLSX file and select the spreadsheet you need. Before you upload it, you can download a sample to see what the file should look like.
Before creating the tasks from this spreadsheet, Pyrus will suggest that you check the form fields. Make sure all data are in place and there aren’t any unsupported fields in the form. Click on Create forms.
Close the form creation window. You’ll find the filled-out forms in your Inbox and Tasks sections.
Pyrus will fill out as many forms as the number of rows in your spreadsheet, but not more than 5000 filled rows. All the data below, like the employee’s name and salary, came from the same row in the Excel spreadsheet.
You can use these tasks for accounting purposes or send them as pay stubs to your employees. In either case, don’t forget to to set up routing. This is what your payroll workflow might look like:
If routing is specified, each task will go to its respective employee as soon as it is created.