What You’re Actually Dealing With

⚠️ Important: Zoho Books' export format does not always match its import format. Re-importing an exported file without cleaning it first is one of the most reliable ways to reproduce this exact error.

Why This Error Happens: Root Cause Analysis

The "Please enter the right state code" error is almost always triggered by a field value mismatch — Zoho Books receives a value it doesn’t recognize in a state-related field. The most common triggers are:

• The Place of Supply field contains a full state name instead of a recognized code
• Billing State or Shipping State uses inconsistent formatting
• An exported file's "StateName-XX" format (e.g., Maharashtra-27) wasn’t cleaned before re-import
• State codes don’t match Zoho's internal accepted values list exactly
• For non-GST accounts: state abbreviations don’t match the selected country

The golden rule: Zoho Books requires field values it recognizes exactly. There’s no fuzzy matching.

Before You Start: Know Your Import Specs

Zoho Books has specific technical requirements for invoice imports that are worth confirming upfront:

• ✅ Supported formats: CSV, TSV, and XLS
• ✅ File size limit: 10 MB maximum
• ✅ Encoding: UTF-8 (Unicode) — save your CSV with this encoding
• ✅ XLSX files: Not officially supported for invoice import — convert to CSV or XLS first

Pro Tip: XLSX files can cause silent data corruption during import (especially with dates). Always save as CSV (UTF-8) or XLS before importing.

Solution 1: Fix the "Place of Supply" Field (Most Common Fix)

For Indian GST-enabled Zoho Books accounts, the Place of Supply column is the #1 trigger for this error. Zoho requires a specific two-digit numeric GST state code — not the state name.

The Correct Format

How to Fix It

Step 1: Locate these column headers in your CSV:

• Place of Supply
• place_of_supply
• State
• Billing State
• Shipping State

Step 2: Replace all state names with their 2-digit numeric codes using Find & Replace (Ctrl+H in Excel or Google Sheets).

Step 3: Test with 3–5 rows before running the full bulk import.

Solution 2: Stop Using Your Export as an Import Template

This is the trap most users fall into. When you export invoices from Zoho Books, the Place of Supply field often exports in a combined format like:

Maharashtra-27

But Zoho's import validator only accepts:

27

How to Clean It

In Excel:

=RIGHT(A2, 2)

(Extracts the last 2 characters — the numeric code)

In Google Sheets:

=REGEXEXTRACT(A2, "\d+$")

(Extracts the trailing digits)

Other Export-vs-Import Mismatches to Watch For

Also remove any export-only columns that don’t appear in Zoho's import template — extra columns can cause row-level validation failures across the entire file.

Solution 3: Use Zoho's Official Sample Template

Even with correct data, mismatched column headers cause Zoho to misread fields and throw validation errors. The safest approach is to always start from Zoho's own template.

Step 1: Navigate to Zoho Books → Invoices → Import

Step 2: Click "Download Sample File" — use this as your base. Do not rename columns.

Step 3: Map these critical fields correctly:

✅ Key Column Names (exact spelling matters):
- CustomerName       → Customer's full name
- InvoiceDate        → Match your org's date format (DD/MM/YYYY or MM/DD/YYYY)
- PlaceOfSupply      → 2-digit state code (e.g., 27)
- BillingState       → State name OR code (check org preference)
- ShippingState      → State name OR code
- ItemTaxName        → Must match existing tax name in Zoho exactly

Step 4: Verify your date format under:
Settings → Organization Profile → Date Format

⚠️ Date format mismatches can cascade into other field errors — including state validation failures — so always confirm this setting first.

Solution 4: Complete GST State Code Reference

Zoho Books maintains an internal list of valid state codes. Use this as your master reference:

01 - Jammu & Kashmir        19 - West Bengal
02 - Himachal Pradesh       20 - Jharkhand
03 - Punjab                 21 - Odisha
04 - Chandigarh             22 - Chhattisgarh
05 - Uttarakhand            23 - Madhya Pradesh
06 - Haryana                24 - Gujarat
07 - Delhi                  25 - Daman & Diu
08 - Rajasthan              26 - Dadra & Nagar Haveli
09 - Uttar Pradesh          27 - Maharashtra
10 - Bihar                  28 - Andhra Pradesh (Old)
11 - Sikkim                 29 - Karnataka
12 - Arunachal Pradesh      30 - Goa
13 - Nagaland               31 - Lakshadweep
14 - Manipur                32 - Kerala
15 - Mizoram                33 - Tamil Nadu
16 - Tripura                34 - Puducherry
17 - Meghalaya              35 - Andaman & Nicobar
18 - Assam                  36 - Telangana
                            37 - Andhra Pradesh (New)
                            38 - Ladakh
                            97 - Other Territory
                            99 - Centre Jurisdiction

⚠️ Watch for outdated codes: Ladakh (38) and the updated Andhra Pradesh split (28 vs. 37) are newer additions. Older templates may carry stale values that will fail validation.

Solution 5: Use Zoho's Field Mapping Tool During Import

Instead of fixing the CSV blindly, use Zoho's interactive field mapper to catch mismatches before they error out.

Step 1: Start the import:
Invoices → ⋮ (More) → Import Invoices → Upload CSV

Step 2: On the mapping screen, manually verify:

• Place of Supply maps to Zoho's Place of Supply field (not a generic "State" field)
• Billing and Shipping state columns map to their correct respective fields
• No critical fields are set to "Do Not Import"

Step 3: Use the preview rows — Zoho shows a sample of your first few rows before committing. Check that state values appear as clean 2-digit codes.

Step 4: Save your mapping profile once it’s working. Future imports won’t need reconfiguration.

Solution 6: Non-GST / International Accounts

If your Zoho Books account is not GST-enabled (US, UK, or other regions), the state code error has a different cause entirely.

For US accounts, use standard 2-letter USPS state abbreviations:

California → CA    |  New York → NY
Texas → TX         |  Florida → FL
Illinois → IL      |  Ohio → OH
Georgia → GA       |  Washington → WA

Common non-GST triggers:

• Country = United States but State = Ontario → country/state mismatch
• State field is blank when tax rules require a value → fill with N/A or a default
• State abbreviation uses 3 letters instead of the standard 2

Quick Diagnostic Checklist

Run through this before every import attempt:

□ Place of Supply uses 2-digit numeric codes (GST accounts)
□ Column headers match Zoho's official sample template exactly
□ Date format matches organization settings (Settings → Org Profile)
□ No merged cells or extra header rows in the CSV
□ Tax names match exactly what's configured in Zoho Books
□ No special characters or extra spaces in state fields
□ File saved as CSV (UTF-8) or XLS — not XLSX
□ Billing/Shipping country and state are consistent
□ Removed export-only columns not accepted on import
□ File size is under 10 MB
□ Tested with 3–5 rows before full bulk import

Recommended Fix Order

1️⃣  Download Zoho's official import sample template (don't reuse exports)
2️⃣  Fix Place of Supply → replace with 2-digit numeric state codes
3️⃣  Clean exported data: strip "StateName-XX" → keep only "XX"
4️⃣  Verify date format matches your org settings
5️⃣  Remove extra/export-only columns from the file
6️⃣  Test import with 5 rows using the field mapping tool
7️⃣  Save the mapping profile, then run the full bulk import

Streamline Your Entire Invoicing Workflow

Fixing the import error is step one — but if you’re regularly dealing with high-volume invoicing, it’s worth looking at the bigger picture. Zoho Books goes well beyond CSV imports: automated recurring invoices, GST return filing, payment reminders, and real-time financial dashboards all live in the same platform. If you’re not already using it end-to-end, you’re likely leaving time on the table.

For businesses managing inventory alongside invoicing, Zoho Inventory integrates directly with Zoho Books — keeping stock levels, purchase orders, and invoices in sync without manual reconciliation.

And if you find yourself needing to automate repetitive import workflows entirely — for example, pulling invoice data from a third-party system and pushing it into Zoho Books on a schedule — Zoho Flow can handle that without writing a single line of code.

Related Reading

If you’re working through other Zoho data and import challenges, these resources from the Creator Scripts blog may help:

• Zoho Inventory Management: Weighted Average Cost Method — Pair your invoice imports with smarter inventory costing
• Mastering Zoho Flow Custom Function Outputs — Automate data flows between Zoho apps
• Fix Invalid Request Issues in Zoho Mail — Troubleshoot other common Zoho error patterns
• Zoho Partners: Answering the Top 10 Questions — Understand how Zoho partners can accelerate your setup

Additional Resources

Still Stuck? Get Expert Help

If you've worked through every solution above and the error persists, it's likely an org-specific field configuration issue — something that isn't visible from the CSV alone. In that case:

1. Contact Zoho Books support with a 5-row sample CSV — they can identify configuration mismatches on their end
2. Work with a Zoho Partner who can audit your organization settings and import configuration directly

The team at Creator Scripts specializes in exactly this kind of Zoho Books troubleshooting and configuration work. Whether it’s a one-time import fix or a full accounting workflow buildout, reach out here and we’ll get your imports running cleanly.

Key Takeaways

• ✅ Never reuse an exported file as an import template — Zoho's export and import formats differ
• ✅ Place of Supply requires 2-digit numeric GST codes (e.g., 27 not Maharashtra)
• ✅ Supported import formats are CSV, TSV, and XLS — not XLSX — with a 10 MB file size limit
• ✅ Always test with 3–5 rows before committing a full bulk import
• ✅ Save your field mapping profile to avoid reconfiguring on every import
• ✅ Date format mismatches can cascade into state validation errors — always verify org settings first

✅ Optimization Summary

Fact-Checks & Corrections Applied