Upload data from Excel
Upload master data and transactions to ClaimDS from Excel — download the template, fill it, upload to preview and fix errors, then confirm the import.
Getting data into ClaimDS is a review-before-commit flow: you upload, ClaimDS shows you exactly what will happen, and only then does it write. That preview step is what keeps bad data out.
Two steps — preview, then commit
An upload never commits straight away. The first step validates your file and returns a preview — valid count, failed count, and the reason for each failure. The second step, once you're happy, imports the valid rows. You're never guessing what a file will do.
Do the upload
Follow the numbered steps below. Load things in dependency order — master data before transactions — so references resolve. For getting data out, see download and export to Excel.
Step-by-step
Download the template for what you're loading
Each thing you can import — counterparties, materials, business volume — has its own Excel template. Download it from the import screen. The template carries the column headers, an example row, and a notes sheet explaining each column.
Fill it from your ERP export
Map your ERP export into the template's columns. Keep dates in the expected format, put each tax component in its own column exactly as your ERP reported it, and use the short codes for classifications. For invoices, every line of one invoice shares the same document number.
Upload to preview
Upload the filled file. ClaimDS doesn't commit it yet — it parses and validates first, then shows you a preview — how many rows are valid, how many failed, and any warnings, with the reason against each failed row.
Review, then confirm
Check the preview. If it looks right, confirm the import and ClaimDS writes the valid rows. Valid rows go in even if some rows failed — one bad row, or one bad invoice, doesn't stop the rest.
Fix any failures and re-upload
If rows failed, download the issues report — it lists each failed row with the reason. Correct those in your file and upload again. The import is safe to retry; it won't double-load rows that are already in.
Frequently asked
Does a single bad row stop the whole upload?
No. Valid rows import and failed rows are reported separately, so a few errors don't block a good batch. For invoices, failures are per-document — one invoice failing doesn't stop the others.
Is there a size limit?
Yes — there's a file-size and row-count limit per upload (a malformed file, an oversized file, or too many rows is rejected as a whole). For large loads, split the file into batches.
What happens to tax columns on upload?
They're captured exactly as you enter them. ClaimDS does not recalculate or validate the GST rate on import — your ERP is the source of truth. See how tax is captured on your transactions.
Still stuck?
Book a demo and we'll walk through it on your own data — or just talk to us.