Rename and Map Indian PDF Fields to PAN, GSTIN, Branch, and Record Data

The biggest source of PDF automation errors is often naming, not drawing. Indian workflows use repeated identifiers and department-specific columns, so field names need to be specific before the template is trusted.

Use this workflow when the recurring PDF work includes PAN and GSTIN field cleanup, branch and vendor-code mapping, employee and student ID mapping, invoice and PO schema mapping, and packet-wide field naming. The page should stay tied to real Indian operating examples rather than cloning a global workflow and swapping in country terms.

• PAN and GSTIN field cleanup
• branch and vendor-code mapping
• employee and student ID mapping
• invoice and PO schema mapping
• packet-wide field naming

First clean geometry and field types, then rename. Renaming too early wastes time if a detected field later gets deleted or merged.

A practical setup pass is to upload one real PDF, review detected fields, correct names and types, map the field set to source data, and save the template before inviting respondents, running a batch, or publishing an API endpoint.

• Rename fields after geometry cleanup, not before.
• Use one naming convention for identifiers across the cluster.
• Resolve duplicate field names before saving the template.
• Keep internal-only review fields distinct from respondent fields.

Start from the source records the team already trusts: Excel headers, CSV headers, JSON keys, TXT schema files, and internal database field names. Keep the mapping explicit enough that a reviewer can tell where each value came from.

Use source-system names where possible. If the branch spreadsheet already uses gstin and vendor_code, the PDF should map directly to those headers unless there is a strong reason to rename them.

• pan_number, gstin, branch_code, vendor_code, employee_id
• invoice_number, po_number, challan_number, student_id, patient_id
• reviewer_id, approval_status, document_status, output_date

Rename-and-map work supports every runtime. Search & Fill, Fill By Link, API Fill, calculations, and grouped packets all depend on stable field names.

Search & Fill is the safest first runtime when a staff member still needs to inspect one record. Fill By Link is better when the source data should come from a respondent. API Fill is better after an internal system can send clean JSON to a saved template.

Create a naming convention for the India cluster before adding many pages: identifier fields, date fields, approval fields, and status fields should be easy to recognize across templates.

Start with one high-volume Indian workflow, validate a real record, then expand into adjacent PDFs only after the first template is dependable. That gives the India workflow cluster a real reason to exist.

• Find duplicate or vague names such as name, id, date, and address.
• Map one spreadsheet or JSON record into the renamed fields.
• Check checkbox option values against source tokens.
• Document naming choices that will be reused across templates.

Good field names make automation easier, but they do not decide whether a value is valid, approved, or complete. That review remains with the operating team.

DullyPDF handles field detection, cleanup, mapping, reusable templates, fill output, and reviewed PDF generation. It does not replace local policy, tax review, lending decisions, medical judgment, admissions decisions, procurement approval, or document-retention rules.

These workflow pages are meant to connect product mechanics to the India industry pages where the same mechanics show up in day-to-day paperwork.