📥 Data Import
Import existing data into LKG for Billing using a guided 5-step wizard. Supports CSV, Excel, XML, and JSON source files. Map your source columns to system fields, preview the data, and commit.
Navigate to Integrations → Data Import.
Import List
The Data Import page lists all previous import jobs with their status and results.
| Column | Description |
|---|---|
| Import # | Auto-generated import job ID |
| Entity Type | Type of data imported (Parties, Items, Invoices, etc.) |
| Source | File format used |
| Status | Queued, Running, Completed, Partially Completed, Failed, Cancelled |
| Records | Total, successful, and failed record counts |
| Date | When the import was started |
| Actions | View details, re-run |
Starting a New Import
Click + New Import to open the 5-step wizard.
Step 1 — Source Selection
| Field | Description |
|---|---|
| Source Format | CSV, Excel (.xlsx), XML, or JSON |
| Entity Type | What data you're importing — see supported types below |
| Mapping Template | Optionally reuse a saved field mapping from a previous import |
Supported Entity Types
| Entity | Description |
|---|---|
| Parties | Customers and suppliers |
| Items | Products and services |
| Invoices | Sales invoices |
| Purchases | Purchase bills |
| Payments | Payment records |
| Ledgers | Accounting ledger entries |
| Bundle | Multiple entity types in one import |
Step 2 — File Upload & Deduplication
Upload your source file and configure how duplicates are handled.
Deduplication Keys
Choose which field(s) identify duplicate records:
| Key | Used For |
|---|---|
| GSTIN | Parties with GST numbers |
| Phone | Parties with phone numbers |
| Parties with email addresses | |
| Product Code | Items with product codes |
| Name | Match by name (case-insensitive) |
Dry Run
Enable Dry Run to validate and preview the import without committing any data to the database. Recommended before the first real import.
Step 3 — Field Mapping
The system analyses your source file headers and automatically suggests mappings to system fields.
| Indicator | Meaning |
|---|---|
| 🟢 Green (≥90%) | High-confidence auto-mapping |
| 🟡 Amber (≥70%) | Moderate confidence — review suggested mapping |
| 🔴 Red (<70%) | Low confidence — manual mapping required |
- Override any auto-detected mapping by selecting the correct target field from the dropdown
- Columns that should not be imported can be set to Ignore
- Required fields missing from the source are highlighted as errors
Saving a Mapping Template
Click Save as Template to store the current mapping for future imports of the same file format.
Step 4 — Data Preview
Review a row-by-row preview of how the data will be imported:
| Indicator | Meaning |
|---|---|
| 🟢 Green | Row will import successfully |
| 🟡 Yellow | Row has warnings (will import with caveats) |
| 🔴 Red | Row has errors and will be skipped |
Expand any row to see the detailed field values and the specific error or warning message.
If there are many errors, click Back to return to Field Mapping and correct the configuration before proceeding.
Step 5 — Run & Monitor
Click Commit to start the import. The wizard shows real-time progress:
- Progress bar with percentage complete
- Running count of processed, successful, and failed records
Import Statuses
| Status | Description |
|---|---|
| Queued | Import is scheduled, not yet started |
| Running | Import actively processing records |
| Completed | All records processed successfully |
| Partially Completed | Some records succeeded, some failed |
| Failed | Import failed — check error details |
| Cancelled | Import was cancelled mid-run |
Click Cancel to stop a running import. Records already processed are kept.
Viewing Import Details
Click any import from the list to view:
- Full record-by-record results
- Error messages for failed rows
- Summary statistics