Inscricaoestadual Laravel Package

Product Decisions This Supports

• B2B onboarding & checkout gating: State registration (Inscrição Estadual, IE) is mandatory for Brazilian business customers in most fiscal flows. This package lets us validate the field at entry across all 27 states instead of shipping a generic "free text" field that fails downstream.
• Fiscal compliance for invoicing (NF-e/NFS-e): IE is a required attribute on fiscal documents. Validating it before invoice generation prevents SEFAZ rejections, rework, and support tickets — a direct revenue and operations concern, not just a data-quality nicety.
• Build vs. buy (strong "buy/adopt" case): Each state has its own IE format, prefix rules, and check-digit algorithm. Reimplementing and maintaining 27 rule sets plus future rule changes is pure undifferentiated toil. Adopting an MIT-licensed, single-purpose library eliminates that backlog item.
• ERP/back-office and partner integrations: Any customer-data sync, distributor onboarding, or marketplace seller verification that ingests IE values can reuse the same validation layer, keeping rules consistent across surfaces.
• Roadmap scoping: Enables features like "verified B2B account" badges, tax-ID–gated pricing tiers, and self-serve business registration — all of which depend on trustworthy IE data.

When to Consider This Package

Adopt when:

• The product serves the Brazilian market and captures business/corporate customers.
• You need syntactic validation (format + check digit) of IE at data entry, import, or pre-invoice time.
• You want a small, MIT-licensed, single-responsibility dependency rather than a heavyweight fiscal SDK.
• Your stack is PHP/Laravel and you want a light validation rule rather than a full tax-engine integration.

Look elsewhere (or proceed with caution) when:

• You need authoritative validation against SEFAZ state databases — this is an offline format/check-digit check, not a live tax-authority lookup.
• You need CNPJ/CPF validation, CEP/address normalization, or full NF-e emission — this solves IE only; plan for complementary libraries or a fiscal provider.
• Maintenance risk matters: with ~14 stars and an unknown/low-activity repo, treat it as a vendored or forked utility. Have engineering review the per-state rule coverage and check-digit logic before relying on it in revenue-critical paths, and pin the version.
• You are not operating in Brazil, or you are B2C-only with no tax-ID capture.

How to Pitch It (Stakeholders)

To executives: This is a small, free (MIT) component that lets us correctly validate Brazilian business tax registrations across all 27 states without building or maintaining that logic ourselves. It directly de-risks fiscal invoicing — bad tax IDs cause invoice rejections, manual rework, and customer friction — and unblocks B2B onboarding and tax-gated pricing. Cost is negligible; the win is avoided engineering effort and fewer compliance incidents.

To engineering: It's a focused, dependency-light PHP library covering per-state IE formats and check digits, drop-in for Laravel validation. Caveats: low community signal and unclear maintenance cadence — so we should pin/fork it, add unit tests around the states we actually serve, and keep our own thin validation wrapper so we can swap the implementation if needed. It does not replace live SEFAZ checks or handle CNPJ/CPF; scope those separately.

Bottom line: Low-cost, high-leverage adoption for Brazil-market B2B flows — approve for a time-boxed spike, with a vendoring and test-harness plan to manage the maintenance risk.