Extract Apparel Wholesale Invoices to Excel in India

To extract apparel wholesale invoices to Excel in India without losing the size matrix, keep the style or colour row as the parent record, expand each size column into a separate line-item row, and carry HSN, quantity, rate, taxable value, GST rate, place of supply, and CGST/SGST or IGST with every row. That gives you a spreadsheet where each style-size combination can be reviewed before GSTR-1 preparation, Tally import, or customer ledger update.

This matters because garment wholesale invoices are not simple item lists. A Surat or Tiruppur distributor may issue one tax invoice to a retailer where a single style has quantities under S, M, L, XL, and XXL, one rate, one HSN, one discount line, and a tax split based on the buyer's state. If an OCR tool reads those size columns as loose numbers, the Excel output may show quantities without style context. If it collapses the row into one item, the size-wise quantity disappears.

The useful output is not "invoice data" in the abstract. It is a normalised working file with one row for each invoice, customer, style or SKU, colour or shade, size, HSN, quantity, rate, taxable value, GST rate, tax split, and place of supply. When the invoice contains 12 pieces of a shirt in M, 8 in L, and 5 in XL, those become three rows, not one merged description and not three orphaned quantity cells.

That row shape is what makes the file usable under month-end pressure. On the 9th or 10th of the month, when a distributor's accountant has 80 PDF invoices and GSTR-1 is due soon after, the review job is not to admire an OCR table. It is to check whether customer GSTINs, state codes, HSNs, taxable values, and tax splits still tie back to the original invoices. A size-matrix invoice to Excel process that preserves those fields gives the accountant something they can filter, total, and correct before it enters the return or accounting system.

Why Generic OCR Breaks Garment Wholesale Invoices

Most generic invoice OCR expects a line table where each row already represents one item. Apparel wholesale invoices often do not work that way. A single line may read like a complete product row, then spread the actual quantities across size columns: S, M, L, XL, XXL, or a local size run used by the distributor. The HSN, rate, discount, and tax fields may sit at the end of the row, applying to every size cell in the matrix.

The other common layout looks easier but still needs care. Some invoices print one row per size variant, so the table has separate rows for the same style in M, L, and XL. Even there, the style, colour, HSN, and rate may be printed once and visually carried down by blank cells. A human accountant reads the blank as "same as above"; a weak extractor may read it as missing data.

That is why apparel size column invoice OCR fails in two predictable ways. It may flatten the matrix by treating each size quantity as a separate item without the style code, shade, HSN, or rate attached. Or it may collapse the row into a single item, preserving the total pieces but losing the size dimension that the retailer, warehouse, and accounts team need later.

The extraction also has to keep invoice-level details tied to every expanded row. Invoice number, date, supplier or distributor name, customer GSTIN, place of supply, and taxable value are not decoration. They are part of the tax invoice record, and they are the fields the accountant will use to trace the Excel row back to the PDF. For the broader field list that Indian GST invoices need to carry, use India GST invoice field requirements as the reference point, then add the apparel-specific size and style fields on top.

A good convert apparel SKU size matrix invoice Excel workflow therefore starts by deciding how the row should be understood. The parent row is the style or SKU with its colour or shade. The size cells are child quantities. The extracted spreadsheet should expand those child quantities into their own rows while repeating the parent context that was visually implied in the invoice.

Build The Target Excel Shape Before You Extract

Before you run conversion, define the row grain. For an apparel wholesale tax invoice, the safest grain is one row per invoice, customer, style, colour, size, HSN, quantity, rate, taxable value, GST rate, tax split, and place of supply. If that sentence feels too long, it is because the source invoice is doing several jobs at once: sales record, stock movement record, tax document, and customer balance evidence.

Keep header fields separate in your mind even though they will repeat in Excel. Invoice number, invoice date, distributor GSTIN, customer name, customer GSTIN, billing state, shipping state, place of supply, source PDF name, and page number are header or trace fields. They repeat across every expanded size row from the same invoice so a reviewer can filter the spreadsheet and still know where each line came from.

Line fields should describe the garment sale itself. A practical output table usually needs style or SKU, product description, colour or shade, size, HSN, quantity, unit rate, discount, taxable value, GST rate, CGST amount, SGST amount, IGST amount, and line total. If the invoice uses a matrix layout, the style and colour may appear once, while the size quantities appear across columns. The extractor should repeat the style and colour for each non-blank size cell and ignore blank or zero quantity cells unless the business wants them flagged as exceptions.

Combo packs and assortments need a deliberate choice. If the invoice sells a pack as one commercial unit but prints internal size quantities, the Excel file should make that visible instead of guessing. Use columns such as pack description, size, quantity in pieces, and billable unit if the distinction affects stock or GST review. If the invoice simply lists separate sizes under one style, one row per size is cleaner.

Colour and shade fields deserve the same treatment as size. Apparel invoices often tuck "navy", "rust", "shade 14", or fabric finish beside the product description rather than in a neat column. For textile wholesaler invoice to GSTR-1 Excel work, the GST return may not need shade, but the business review usually does. Keeping it as a structured column helps the accounts team tie the tax invoice back to dispatch records, retailer claims, and stock movement.

The source file reference is not optional in practice. When a taxable value total does not match, or a customer disputes a size breakup, the reviewer needs to jump back to the original PDF. A simple source_file and page_number column can save more time than another round of manual searching through renamed invoice scans.

Keep HSN, GST Rate, And Place Of Supply At Line Level

Apparel invoice extraction should not treat GST as one invoice-total field. The HSN and GST rate belong with the line item, especially when a distributor sells mixed garment categories or price bands on the same invoice. Woven men's garments may sit under HSN 6203, woven women's garments under 6204, while knitted equivalents may sit under 6103 or 6104. The Excel file should preserve the HSN printed on the invoice and make it reviewable beside the style, size, quantity, and rate.

The GST 2.0 rate change makes this more important for apparel. The 56th GST Council rate-rationalisation release lists apparel and clothing accessories under Chapters 61 and 62 with separate sale-value bands: not exceeding Rs. 2,500 per piece and exceeding Rs. 2,500 per piece, with the higher band moving from 12% to 18%. From 22 September 2025, the sub-Rs. 2,500 per-piece line remains at 5%, while the above-Rs. 2,500 per-piece line needs the higher 18% treatment. The relevant threshold is per piece, not the total value of the invoice. A single customer invoice can therefore contain lower-rate and higher-rate garment lines, and the spreadsheet must keep that rate attached to each extracted line.

Place of supply needs the same line-level discipline. If a Gujarat distributor with state code 24 sells to a Maharashtra retailer with state code 27, the tax split is IGST. If the same distributor sells within Gujarat, the tax split is CGST plus SGST. The extractor should capture the buyer GSTIN, billing or shipping state where relevant, place of supply, and the printed tax split so the accountant can catch cases where the invoice's tax treatment does not match the customer state.

This is not about asking an extraction tool to decide tax law. It is about preventing the spreadsheet from hiding the facts printed on the invoice. For extract HSN 6203 6204 GST invoice India work, the file should make HSN, rate, place of supply, and CGST/SGST or IGST visible enough that the accounts team can review exceptions before the data feeds GSTR-1 preparation.

Extract A Batch With Instructions For Size Expansion

Once the target Excel shape is clear, the extraction instruction should say exactly how the size matrix must be expanded. A generic prompt such as "extract invoice data" is too loose for apparel wholesale invoices. It may capture invoice totals and customer names but still miss the business-critical row structure.

For AI invoice data extraction for apparel invoice PDFs, write the prompt around the output row you want. Invoice Data Extraction lets users upload PDF, JPG, or PNG invoice files, describe the required data in a natural-language prompt, and download structured Excel, CSV, or JSON. For a Surat textile distributor invoice extraction task, the instruction can be direct: "Extract each apparel tax invoice into one row per style-size combination. For every row, include invoice number, invoice date, customer name, customer GSTIN, place of supply, style or SKU, product description, colour or shade, size, HSN, quantity, unit rate, discount, taxable value, GST rate, CGST, SGST, IGST, line total, source file name, and page number. If a product row has size columns such as S, M, L, XL, and XXL, create one output row for each non-zero size quantity and repeat the style, colour, HSN, rate, and tax fields."

That instruction tells the extractor not to treat the matrix as a visual table only. It explains the accounting grain. For a Tiruppur garment supplier invoice to spreadsheet workflow, you can adjust the size labels, product wording, and extra fields, but the core rule stays the same: one output row per size-bearing garment line, with the tax and source context repeated.

The review step still belongs to the accountant. The extracted Excel or CSV is the working file before GSTR-1 upload, Tally import, or customer-balance update. Review totals by invoice, check HSN and GST rate exceptions, and confirm that inter-state and intra-state tax splits survived the conversion. The extraction step should remove repetitive data entry, not remove professional review.

Handle Discounts, Freight, Samples, And Packing Lines Without Losing The Matrix

The difficult rows are usually not the main garment lines. They are the adjustments around them. A line-level discount should sit on the style-size row it affects. An invoice-level discount is different: it may need allocation across taxable lines, or it may need to be flagged separately so the accountant can decide how to treat it before trusting taxable value totals.

Freight and transport charges should not be silently merged into garment values. If the invoice prints freight as a separate taxable or non-taxable charge, extract it as its own row type with the printed HSN or SAC and tax treatment. The same applies to returnable packing, cartons, hangers, and other charges that appear below the garment matrix. These lines may not have sizes, but they still affect invoice totals and reconciliation.

Free-supply and sample lines need explicit flags. Apparel distributors may include sample pieces, replacement items, or promotional supply lines at nil or discounted value. If the spreadsheet only captures positive taxable rows, those lines can disappear even though they explain a quantity movement or a customer conversation later. A sample_flag or line_type column gives reviewers a way to separate commercial sales from exceptions.

Shade and colour variants are easy to lose because they are often printed as text near the style, not as a clean table column. A row might show one style code with multiple shade names stacked above the size matrix, or a colour may appear in the product description while sizes appear as columns. The extraction rule should preserve both colour and size, because stock teams and customer accounts usually care about both.

Recipient-side work is the mirror image. The retailer receiving the invoice may need the same structured rows to match purchase records and tax credits, so GSTR-2B ITC reconciliation for recipient retailers becomes easier when the distributor invoice was extracted with customer GSTIN, HSN, taxable value, and tax amount intact. For businesses where these same size-matrix invoices also feed stock valuation or landed-cost analysis, the related apparel size-matrix landed-cost workflows show why preserving style, size, and quantity at the earliest extraction stage matters beyond GST filing.

Review The Excel File Before GSTR-1 Or Tally Import

Start the review with control totals, not individual cells. Count the PDFs processed, count the invoice numbers extracted, and check whether any file produced no rows. Then total taxable value and tax amount by invoice and compare those totals with the original PDFs. If the invoice-level totals do not tie, fix that before spending time on size details.

Next, review customer GSTIN and place of supply. Sort or filter by state code and tax split so inter-state IGST invoices do not sit among within-state CGST and SGST invoices. For an India apparel wholesaler, this catches many return-preparation errors early because the same customer may have stores or billing addresses in different states.

Then test the size expansion. Pick several high-value invoices and compare the original matrix with the Excel rows. The total pieces for each style should equal the sum of the size rows. Blank size cells should not become phantom rows. Zero quantities should either be omitted or clearly flagged, depending on how the business wants to review exceptions.

After that, filter by HSN and GST rate. The review should make mixed-rate invoices visible, especially where per-piece value affects the rate band. Check whether freight, packing, sample, and discount rows have line types that keep them separate from normal garment sales. If the spreadsheet will become a textile wholesaler invoice to GSTR-1 Excel working file, these exception flags help the preparer decide what belongs in the return and what needs manual treatment.

For accounting import, keep the extracted file as a reviewed source sheet before reshaping it into the final import format. If the team is importing invoice data into TallyPrime, the garment extraction file may need column renaming, ledger mapping, voucher type decisions, and tax ledger alignment before import. The clean extraction file is still valuable because it gives the reviewer a structured, traceable base instead of forcing them back into each PDF.

For repeat distributor formats, save the prompt wording that worked well and reuse it with small edits for the next batch. The process becomes faster when the same row grain, field names, and exception columns are used every month, but the final review should stay in place: invoice count, customer details, size-wise quantities, taxable values, GST rate split, tax split, and exceptions.