A business that exists as its own legal entity needs its own PAN — the partnership firm, the LLP, the private limited company each holds a PAN separate from every partner’s and director’s personal PAN, because the entity earns, banks, pays tax, and deducts TDS in its own name. The sole proprietorship is the deliberate exception: it is not a separate entity, and the proprietor’s personal PAN serves the business. Getting this mapping right is the first fork in every business-PAN journey, and getting the entity PAN itself is a Form 49A application with entity documents in place of personal proofs.
This guide covers the business PAN completely: the entity-type mapping (who needs their own PAN and who uses personal), the fourth-character code system that reveals PAN types, documents by entity type, the application steps for firms and companies including the company-incorporation route where PAN arrives bundled, fees and timelines, the business uses that make the PAN urgent (bank account, GST, TDS), and the compliance notes that keep the entity PAN clean.
Overview
| Detail | Information |
|---|---|
| Who Needs Own PAN | Partnership firms, LLPs, companies, trusts, AOPs/BOIs |
| Who Uses Personal PAN | Sole proprietorships — proprietor’s PAN is the business PAN |
| Form | 49A with entity documents |
| 4th Character Codes | P-person, F-firm, C-company, T-trust, A-AOP, H-HUF |
| Fees | ~Rs 107 standard application |
| Company Shortcut | PAN allotted with incorporation via the MCA SPICe+ route |
| DOB Equivalent | Date of formation/incorporation (also the e-PAN password) |
The Entity Mapping — First Fork Decided
| Business Form | PAN Position |
|---|---|
| Sole proprietorship | Proprietor’s personal PAN serves — no separate PAN exists or is needed |
| Partnership firm | Own PAN (4th char F) — partners keep personal PANs separately |
| LLP | Own PAN (F) against the LLP incorporation |
| Private/Public company | Own PAN (C) — typically allotted at incorporation |
| HUF business | HUF PAN (H) with the karta applying |
| Trust/Society/AOP | Own PAN (T/A) with their formation documents |
The proprietorship row deserves its emphasis because agents mis-sell “business PANs” to proprietors constantly: the dukaan, the freelance practice, the single-owner trading business — all correctly run on the owner’s personal PAN, with GST, current accounts, and licences all accepting exactly that. A proprietor applying for a second “business” PAN is manufacturing the duplicate-PAN problem, not registering a business.
Documents by Entity Type
| Entity | Core Documents |
|---|---|
| Partnership firm | Partnership deed; registration certificate where registered; address proof of the firm |
| LLP | Certificate of incorporation; LLP agreement; registered office proof |
| Company | Certificate of incorporation; MOA/AOA context; registered office proof (mostly handled at SPICe+) |
| Trust | Trust deed; registration certificate |
| All entities | Authorised signatory’s details/PAN; the entity’s formation date; seal/stamp practices per form instructions |
How to Apply
Step 1 — Confirm the Entity Actually Needs Its Own PAN
Run the mapping table: proprietorships stop here and use the personal PAN; firms, LLPs, companies, trusts proceed. Companies mid-incorporation: check Step 4’s bundled route before applying separately.
Step 2 — Prepare the Entity Document Set
The formation document (deed/certificate) scanned cleanly, the firm/registered-office address proof, the authorised signatory identified with their PAN — assembled to the portal’s specs before the form opens.
Step 3 — File Form 49A as the Entity
Protean/UTIITSL → new PAN application → applicant category set to the entity type (Firm/Company/Trust as applicable) → the entity’s name EXACTLY as the formation document renders it → formation date → authorised signatory details → documents uploaded → fee paid → acknowledgment saved. The name-exactness matters doubly for entities: bank account opening will compare the PAN name against the deed/certificate verbatim.
Step 4 — The Company Shortcut — SPICe+ Bundling
Companies incorporating through the MCA’s SPICe+ process receive PAN (and TAN) as part of incorporation itself — the certificate arrives with PAN allotted, no separate application needed. Newly incorporating founders should let this bundled route serve and apply separately only for legacy/exception cases.
Step 5 — Deploy the Entity PAN
On allotment (e-PAN to the registered email; password = formation date DDMMYYYY): open the entity bank account, register GST where applicable (the GSTIN embeds this PAN), set up TDS compliance (the separate TAN application where the entity deducts), and quote the entity PAN on every business contract and filing — while keeping the strict separation: entity money and filings on the entity PAN, personal on personal.
Why the Entity PAN Is Urgent — The Dependency Chain
The business PAN sits at the head of a dependency chain that stalls without it: the current account (banks require the entity PAN), GST registration (the GSTIN’s characters 3–12 ARE the PAN), TDS compliance (TAN issuance and filings reference it), vendor onboarding at larger clients (PAN quoted on every invoice/agreement), and the entity’s own tax filings. New firms should file the PAN application the week the deed is signed — every downstream registration queues behind it, and the two-week allotment is the cheapest float in the whole setup timeline.
The Entity PAN’s First Month — Deployment Checklist
| Week | Action | Depends On |
|---|---|---|
| Week 1 | e-PAN into the entity document vault; details verified against the deed/certificate | Allotment |
| Week 1–2 | Current account application with PAN + formation documents | PAN in hand |
| Week 2–3 | GST registration where applicable (GSTIN embeds the PAN) | PAN operative, account helpful |
| Week 2–3 | TAN confirmed/applied where deduction duties loom | Deduction audit done |
| Week 3–4 | Invoice/agreement templates carrying PAN (and GSTIN); vendor-KYC packet assembled | Registrations issued |
| Ongoing | Entity-personal separation enforced from transaction one | Discipline, not paperwork |
The checklist’s logic is dependency-ordered: each row unlocks the next, which is why the PAN application belongs in formation week — every stall at the top cascades down the month.
Documents in Practice — The Scans That Clear Verification
- The deed/certificate scan — every page, legible, in order; verification reads names, dates, and signatures off it, and partial uploads are the entity route’s classic discrepancy
- Name-rendering vigilance — the application’s entity name typed character-for-character from the formation document, including punctuation and spacing (“&” versus “and” divergences haunt firms for years)
- Formation date accuracy — it becomes the record’s DOB-equivalent AND the e-PAN password; a typo here corrupts both
- Signatory coherence — the authorised signatory named in the application should match who the deed/board authorises; their personal PAN enters correctly rendered
- Address proofs current — the firm’s premises proof within recency windows, matching the address typed
A Worked Example — The Partnership’s First Fortnight
Two partners register a trading firm, and the sequence runs textbook: Day 0, the partnership deed executed and (state-process) registered; the same evening, scans made — deed complete, premises rent agreement, both partners’ PANs noted. Day 1: Form 49A filed as a Firm at the processor — name typed from the deed exactly, formation date per the deed, one partner as authorised signatory, documents uploaded, ~Rs 107 paid. Day 5: a discrepancy asks for a clearer deed page four; the rescan returns within the hour. Day 9: allotted — the firm’s e-PAN (fourth character F) downloads, password the formation date. Day 10: the current-account application goes to the bank with PAN + deed + premises proof. Day 13: account live; Day 14: GST registration begins on the firm PAN, trade name recorded. By week three, the firm invoices with PAN and GSTIN on the letterhead, and the partners’ personal PANs have touched nothing but the signatory fields — the separation clean from transaction one. The counterfactual timeline — PAN remembered only when the bank asked — adds two idle weeks to every row below it; the deed-week application is the whole difference.
Common Entity-PAN Mistakes — The Field List
- The proprietor applying as a “firm” — the category error that manufactures problems both directions; proprietorships are personal-PAN businesses
- Partner’s PAN used for firm banking “temporarily” — the mingling original sin; entity money waits for the entity PAN
- Shortened/stylised entity names — divergence from the deed that every downstream verification then queries
- Formation-date guesswork — the deed’s date is the date; approximations corrupt the record and the password
- Company founders applying separately post-SPICe+ — the bundled allotment already exists; a second application is the entity version of the duplicate trap
- The vault gap — entity e-PANs living in a founder’s personal inbox; custody belongs with the entity’s records and survives personnel changes
HUF, Trust, and AOP Notes — The Less-Travelled Entity Paths
- HUF PANs (H) — the karta applies with the HUF’s declaration/deed context and their own details as karta; the HUF then banks, invests, and files as its own taxpayer — a structure households use deliberately with professional advice
- Trust PANs (T) — the trust deed and registration anchor the application; trustees’ details enter as authorised persons, and the trust’s compliance calendar (its returns, its registrations where charitable frameworks apply) builds on the allotment
- AOP/BOI (A/B) — associations and bodies formalising joint activities apply with their formation resolutions/agreements; the category suits structures that are neither firms nor companies
- The shared spine — every category follows the same logic: formation document names the entity, the application copies it exactly, the fourth character announces the type, and the entity’s financial life runs strictly on its own number
Where the Entity PAN Meets Compliance Calendars
The allotment starts clocks worth diarising at formation: the entity’s income-tax return joins the annual calendar (due dates per entity type and audit applicability), GST returns run their cycles where registered, TDS quarters begin the moment deduction duties do, and the various registrar filings (firm/LLP/company annual requirements) proceed on their own schedules — all quoting the PAN that week one obtained. Small entities stumble not on any single filing but on never having built the calendar; the formation fortnight is the moment to write it, with the PAN’s arrival as the trigger. One page — entity PAN, TAN, GSTIN, bank, and the year’s due dates — pinned where the partners actually look, converts compliance from ambush to routine. The PAN is the first line on that page; the page is the real deliverable of a well-run formation.
The Founder’s One-Page Takeaway
Compress the guide for the formation week’s pinboard: proprietorship → personal PAN serves, no application; firm/LLP → Form 49A as the entity with the deed, filed the week it’s signed; company → PAN (and TAN) arrive bundled at SPICe+ incorporation, apply separately only for legacy cases; name typed from the formation document character-for-character; formation date exact (it’s also the e-PAN password); allotment deployed straight down the chain — bank, GST, TDS, templates; and entity-personal separation absolute from the first rupee. Everything else in the entity-PAN world — the fourth-character codes, the compliance calendars, the transition rules — builds on those seven lines, and the founder who runs them converts the registration season from a maze into a checklist.
The entity you formed deserves the clean start its paperwork can give it — file the PAN in deed week, deploy it in order, and let the business’s first month be about the business.
When Structures Evolve — PAN Events Across the Business Lifecycle
The entity PAN’s story continues past formation, and knowing the later chapters prevents their classic errors: growth events (new partners via amended deeds, registered-office moves, name changes) run as CORRECTIONS on the same firm PAN with the amended documents — never fresh applications; conversion events (proprietorship to firm, firm to company) create genuinely new legal persons whose new PANs coexist briefly with orderly wind-downs of the old structure’s registrations, per the transition frameworks; and closure events (dissolution, strike-off) close the entity’s tax life through final filings and the department’s processes, retiring the PAN with the entity rather than abandoning it live. The through-line across all three: the PAN tracks the legal person — corrections while it’s the same person, new allotments only when a new person exists, and formal closure when the person ends. Founders who map their business events to this line file the right paperwork at each turn; those who don’t accumulate the orphaned registrations and accidental duplicates that professional cleanups later bill handsomely to untangle.
From deed week to dissolution, the entity’s PAN is the thread its entire compliance life hangs on — spin it early, keep it exact, and every registration, account, and filing the business ever touches will find its anchor waiting.
The businesses that scale cleanly are, without exception, the ones whose paperwork foundations were poured level in week one — and the entity PAN is the first slab.
Conclusion
The business PAN question resolves into one mapping and one application: separate legal entity means separate PAN (firms, LLPs, companies, trusts — with companies getting theirs bundled at incorporation), proprietorships mean the personal PAN serves — and the application itself is Form 49A wearing entity documents, filed the week formation papers exist because everything else in the business setup waits behind it.
Map the entity honestly, name it exactly as the deed does, deploy the allotment down the dependency chain — and keep the entity-personal separation absolute from day one.
FAQs
1. I run a shop as a sole proprietor — do I need a business PAN for my dukaan?
No — the proprietorship is legally you, and your personal PAN is its business PAN: GST registration, the current account (banks open proprietorship accounts on the proprietor’s PAN plus business proofs), Udyam registration, and licences all run on it correctly. A separate “business PAN” for a proprietorship doesn’t exist as a category — and attempting one lands you in the duplicate-PAN penalty zone, not in better compliance. Where the question usually comes from is growth planning: if and when the business becomes a partnership or company, THAT new entity applies for its own PAN at formation — until then, your PAN, used consistently on every business document, is the complete answer.
2. Our partnership deed spells the firm name one way and we want the PAN in a shorter version — possible?
Resist it — the PAN should carry the firm’s name exactly as the deed renders it, because every downstream verification compares them: the bank opening the current account reads deed against PAN, GST registration reads PAN against application, and clients’ vendor-KYC reads all three. A shortened or stylised PAN name buys years of “name mismatch” queries for zero benefit. If the deed name is genuinely unwieldy, the fix is upstream — amend the deed to the intended name first, then PAN follows the amended deed. One principle covers all entity paperwork: a single canonical name, character for character, across deed, PAN, bank, and GST — divergence anywhere is future friction everywhere.
3. Does the firm’s PAN replace the partners’ personal PANs for anything?
Never — they operate in strict parallel: the firm’s PAN carries the firm’s income, its bank accounts, its GST, its TDS, and its return; each partner’s personal PAN carries their personal income including whatever they draw from the firm (remuneration, interest, profit share per the tax treatment), their personal accounts, and their personal return. No transaction should cross the line — firm revenue into personal accounts and vice versa is the classic small-firm hygiene failure that complicates taxes and audits. Two (or more) PANs, two clean streams, mapped to the deed’s terms: that separation, maintained from the first invoice, is most of what “business compliance” means at the small-firm scale.
