Structured reports and exports
Filter and inspect supported attendance, payroll-preparation, distance, expense, workforce, and operations records before they leave Scootee.
Available records vary by enabled workflow
Office reports and handoffs
Scootee exports approved field records — conveyance in km and INR, attendance, payroll-preparation and expense data — as Excel workbooks and CSV reports for your payroll, accounting or HR system. A file export is not a native connector: named integrations, APIs and scheduled delivery are scoped separately.
What to confirm
Filter and inspect supported attendance, payroll-preparation, distance, expense, workforce, and operations records before they leave Scootee.
Available records vary by enabled workflow
Confirm required employee identifiers, categories, pay periods, review states, currencies, units, and columns against the receiving system before go-live.
Requires implementation confirmation
Agree how reviewed records will be delivered and checked. API, SFTP, scheduled delivery, and custom connectors are requirements to evaluate, not standard capabilities promised here.
Designed during the pilot
Office screens export the records they show, filtered by period and, where relevant, by selection:
Exports respect the same branch and department scope as the screen, so a reviewer only exports records they are allowed to see.
Accounts reviews completed sessions by employee and day, exports the selected period and pays through the usual payroll run, bank transfer or cheque. After payment, the entries are marked paid and cleared with a payment reference such as a bank UTR, cheque number or payroll reference, so they move out of the unpaid list before the next period is exported. Scootee itself does not move money. See conveyance reimbursement software for the full claim workflow.
A native connector to a named accounting or payroll product is not assumed. Most teams start by mapping the Excel export columns to the import format their accounting or payroll tool already accepts, then decide whether automation is worth building. Named connectors, APIs and scheduled delivery are evaluated and quoted individually as part of the Enterprise plan scope.
Employees can be imported in bulk from a spreadsheet, with a results file that shows which rows were created and which need correction. Attendance from a supported monthly workbook can also be imported; each import is hashed and audited so it is safe to retry. Other masters, such as branches, departments, customers and per-km rates, are set up during implementation — see the pilot planning guide.
Export one real period from the pilot and import it into a test company or a copy of your payroll sheet. Check employee identifiers, periods, categories, rejected and corrected rows, duplicates and totals at both ends, then keep a manual fallback until the process has run cleanly for a few cycles. The checklist below covers the same points.
US implementation requirements
The current conveyance export includes employee and session details, distance in kilometres, rates in INR per kilometre, INR amounts, and payment references. Confirm miles conversion, USD requirements, policy rates, and target fields. US payroll filing, ACH payments, and a universal accounting connector are not included by assumption.
Mileage evidence and US rollout questionsQuestions / answers
A native connector to your system is not assumed. Scootee provides supported reports and exports; named connectors, automatic sync, schedules, and support requirements must be confirmed for your implementation.
Scootee exports approved conveyance as an Excel workbook with kilometres, per-km rate in INR, amount and payment reference. Teams map those columns to their own Tally import or voucher process; a direct Tally connector is not part of the standard product.
Inspect the reports and exported fields needed for your process, then test a representative import with the receiving system. Current conveyance exports use kilometres and INR amounts; US miles, USD, policy rates, and field mapping must be confirmed before rollout.
Test employee identifiers, periods, categories, corrections, approval states, rejected records, duplicates, and totals. For an automated handoff, also agree retry behavior, monitoring, and an owner who checks both systems.
Bring a sample import format
Share the receiving system and sample column headers without employee or financial data. Confirm the available records, needed configuration, and any additional implementation work.