Import your data from Excel
Bulk-load counterparties and materials into ClaimDS from a spreadsheet — with the validation that flags duplicates, bad GSTINs and missing fields before anything is imported.
Setting up by hand is fine for a handful of records, but most teams have hundreds of partners and SKUs. Importing from Excel loads them in one pass — and because ClaimDS validates the file first, you get a clean catalogue rather than a fast mess.
Validation is the point
The reason to import through ClaimDS rather than dumping rows into a database is the validation. It checks every row for duplicates, GSTIN format and required fields, and refuses the bad ones — so the master data the rest of the product depends on starts clean.
Run the import
Follow the numbered steps below. If the import is flagged, the fixes are spelled out in fixing counterparty import errors.
Step-by-step
Open the area you're importing into
Go to Master Data → Counterparties or Master Data → Materials, depending on what you're loading. Import works the same way for both.
Prepare your spreadsheet
Put your records in the expected columns — for counterparties that includes the name, type and GST details; for materials the code, name, HSN and unit. One row per record.
Upload and let ClaimDS validate
Upload the file. ClaimDS validates every row before importing anything, so dirty data is caught rather than silently loaded. It tells you which rows have problems and why.
Fix the flagged rows
Resolve the duplicates, invalid GSTINs and missing fields it names, in your spreadsheet. The clean rows can import; you're only correcting the flagged ones.
Re-import until clean
Re-upload the corrected file. Repeat until it imports without flags — then your counterparties or materials are loaded and ready to use across ClaimDS.
Frequently asked
Will one bad row stop the whole import?
No. ClaimDS validates first and flags the problem rows, so you fix those rather than losing the good ones. Validation is there to keep bad data out, not to block you.
What gets flagged most often?
Duplicates, invalid GSTIN formats, and missing required fields. See fixing counterparty import errors for how to clear each.
Still stuck?
Book a demo and we'll walk through it on your own data — or just talk to us.