Integration setup best practices
Best practices for your ClaimDS Excel integration — load master data before transactions, keep tax verbatim from your ERP, and correct by re-uploading.
A little discipline at setup makes the Excel integration smooth for the long run. None of this is hard — it's mostly about loading things in the right order and letting your ERP stay the source of truth. Here's what works.
Load in dependency order
Load master data first, transactions second, agreements last. Transactions reference counterparties and materials, so those have to exist before an invoice that mentions them will import cleanly. A good first-time order:
- Counterparties and materials (and HSN codes)
- Sales and purchase business volume
- Agreements
Let your ERP own the numbers
Map each tax component into its own column and enter it exactly as your ERP reported it — ClaimDS captures tax verbatim and won't recalculate it. The same goes for prices and invoice values. Your ERP did the determination; the upload just carries it across.
Get the formats right once
Keep dates in the format the template expects, use the short codes for classifications, and remember ClaimDS derives the financial year from the document date (April–March). Set your export mapping up correctly once and every load afterwards is routine.
Plan corrections, not just loads
A failed row never blocks a good batch — fix the flagged rows and re-upload. But remember that for transactions, a document and line number is consumed permanently: to correct a loaded invoice, edit or cancel it in ClaimDS rather than re-uploading the same number. Decide your correction routine up front.
Settle into a cadence
Pick a rhythm that matches your close — many teams upload business volume daily or weekly and keep master data in step as it changes. Reconcile at period end. A steady cadence beats a big, occasional catch-up load.
Related
Still stuck?
Book a demo and we'll walk through it on your own data — or just talk to us.