From Excel to transport software, without re-typing a single sheet
Your booking register, vehicle list, driver list and customer ledgers go in as they are. Columns are mapped, every row is checked, and nothing is saved until you confirm. This page is the switching guide.
*No credit card required
When Excel stops being enough
Excel is honest software. It does what you type. The trouble starts when the same trip has to be typed into the booking sheet, the invoice, the driver's sheet and the fuel sheet, by different people, on different days. Then:
- A customer asks for his statement and it takes an afternoon
- Two sheets disagree on what a driver was advanced
- The outstanding list is whatever was last pasted into it
- Nobody can say which truck made money last month without a weekend
The reason most transporters stay on Excel anyway is the switch itself: "enter all your data" means a week of typing. NShine ERP removes that week.
What goes in from your sheets
Your sheet | What NShine ERP imports it as | Note |
|---|---|---|
Booking register | Bookings | Customer, vehicle, driver, route, dates, amounts |
Vehicle list | Vehicles | Matched by registration number |
Driver and staff list | Drivers and employees | One sheet for both |
Customer list with balances | Customer ledgers | Opening balances carried in |
Supplier and truck-owner list | Supplier ledgers | Opening balances carried in |
Expense sheet | Expenses | One line per voucher |
Bank and cash transfers | Bank transactions | |
Bank statement export | Bank statement lines | For reconciliation |
Fuel register | Fuel entries | With paid, unpaid or paid-by-driver |
Purchase bills | Purchase invoices | One product line per invoice |
The order that works
Import the lists that other records point to first, so every booking finds its vehicle, driver and customer.
- Vehicles, by registration number.
- Drivers and employees.
- Customers and suppliers, with their opening balances.
- Bookings, as far back as you want history.
- Fuel, expenses and purchase bills for the same period.
- The bank statement, to reconcile what you have just brought in.
A fleet of 50 trucks and a year of bookings is an afternoon, most of it spent looking at the rows marked for review.
What happens to a bad row
Columns are mapped first
Upload the .xlsx or .xls. The importer reads your headings and matches them to its fields. You see the mapping before any row is touched.
Every row gets a verdict
Ready, needs review, or invalid. A missing vehicle number, a date in the wrong format, a customer that does not exist yet: each is called out on its row.
Nothing saves until Confirm
Fix the rows that need it, leave out the ones you do not want, then confirm. Until then nothing has been written to the system.
The first week
- Day 1: import vehicles, drivers, customers, suppliers. Take the next booking in NShine ERP instead of the sheet.
- Day 2: drivers start sending fuel slips and PODs on WhatsApp; the office approves them in AI Inbox.
- Day 3: the first invoice is raised from a booking, with tax and TDS, in a couple of minutes.
- Day 5: import last year's bookings and fuel so the reports have history.
- Day 7: open the vehicle profit report and the ageing report. The questions that took a weekend take a click.
What you keep
Excel itself: every list and report exports back to it
Your customer's consignment sheets: import them weekly the same way
Your bank statement routine: it imports for reconciliation
Your accountant's Tally: a one-way export is there
Watch the product in action
A walkthrough of the transport management software, in your preferred language.
Frequently asked questions
Excel import is included in every plan
Plans are priced by bookings per month and own vehicles, with a free trial and no setup fee. Pick the one that fits, or book a demo first.