# Data Ingestion Error - Resolving Common Data Ingestion Errors in Invoicing

In this tutorial, you'll learn how to identify and fix common errors that may occur while ingesting data. By the end of this guide, you'll be able to confidently review, identify, and correct errors in your data files to ensure a smooth ingestion process.

{% embed url="<https://youtu.be/Zrd6YPzfUvM?si=eLdM1jZHlb_NdL99>" %}
Fix common data ingestion errors with this quick troubleshooting guide
{% endembed %}

{% stepper %}
{% step %}
Start by ingesting a sample file for reference. This will help you understand the structure and identify potential issues.

![](/files/jHbOfgbK1avPGHM1z7ff)
{% endstep %}

{% step %}
Identify the **GSTN** for which you're ingesting the data. This step ensures that the data is being processed for the correct entity.

![](/files/Ee4btpJTQVHjigGZLUpB)

{% endstep %}

{% step %}
After selecting **GSTN**, choose the template as **India upload**. This template is specifically designed for data ingestion in the Indian context.

![](/files/qZlYYH5OSuX8LkuAOhSW)
{% endstep %}

{% step %}
Review the files and errors. For example, let's say there are five invoices: ING1, ING2, ING3, ING4, and NG5. Carefully examine each invoice for discrepancies.

![](/files/EPc32zqxRp4OBPV8tPH7)
{% endstep %}

{% step %}
Check the error for each invoice. For instance, the error for **ING1** indicates that the **HSN** or **SAC code** is incorrect. This step is crucial for pinpointing the exact issue.

![](/files/5mfigNHJ3NwnEyE7WtnV)

![](/files/PsbIsQFin0dGVfKiSOlT)
{% endstep %}

{% step %}
Correct the errors. For example, update the incorrect **HSN code** to the correct one. This ensures the data aligns with the required standards.

![](/files/Yw26NsFih1eKv9ch6vGd)

![](/files/1n7Kz5VyBEz6v3yUyrew)
{% endstep %}

{% step %}
If there's another error, identify and correct it. For example, the **SAC code** in the second line item might be invalid. Addressing such issues ensures data accuracy.

![](/files/QZX2utHqgYNbJCOJQHXh)
{% endstep %}

{% step %}
Update the **SAC code** with the correct **HSN code**. This resolves the errors for the affected files

![](/files/7W2Qfj5qi04AIRyIEsEd)

![](/files/0wDyLTDrEvHO1obgxnL3)
{% endstep %}

{% step %}
Review the next invoice, **ING2**. The errors here might include an invalid **GSTN** and a recipient state that doesn't match the buyer's **GSTN**. Identifying these issues is key to maintaining compliance.

![](/files/wo32qcSQfBquXLShEPw9)

![](/files/4QeLY16EP4jizxzYAqoY)
{% endstep %}

{% step %}
Correct these errors by updating the **GST number** and the recipient state code. This step ensures the invoice details are accurate and consistent.

![](/files/g95IPkSD0xopRBdWUw9B)

![](/files/pvZFmMJ83iDfD3mlmmmL)
{% endstep %}

{% step %}
Move on to the next invoice, **ING3**. The error here might be an invalid total taxable value for the invoice. Identifying such errors helps maintain financial accuracy.

![](/files/ywb3YrWl8tuSA6SGLBCn)

![](/files/4amR6mvKR2Bv4IQAkpBT)
{% endstep %}

{% step %}
Correct this error by adjusting the total taxable value. Ensure the value matches the expected calculations.

![](/files/NDniEsMqC7FeLhbX1MH9)
{% endstep %}

{% step %}
After correcting all errors, verify that all documents are accurate. Once you're confident everything is correct, proceed with the ingestion process.

![](/files/dIMqICBS0Si5L9Uy6PV0)

![](/files/5cWo7gYdLx5x9TMK0lgM)
{% endstep %}
{% endstepper %}

Thank you for following along with this tutorial. By carefully reviewing and correcting errors, you've ensured a seamless data ingestion process.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cleartax.in/product-help-and-support/for-large-businesses/e-invoicing/data-ingestion-error-resolving-common-data-ingestion-errors-in-invoicing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.