Rut Laravel Package

Product Decisions This Supports

• Chile market entry / localization. The package provides Chilean RUT validation, normalization, and generation. It is the kind of utility that unblocks a country launch: onboarding, KYC-lite checks, checkout, invoicing ("factura"), and any form where a Chilean tax ID is captured.
• Build vs. buy. The RUT checksum (módulo 11) is a known algorithm, but the long tail — dots, hyphens, the K check digit, leading zeros, lowercase input, format drift from users and spreadsheets — is where in-house implementations accumulate bug reports. For a small, well-scoped, maintained package, adopt rather than build; reserve engineering time for the parts of the Chilean flow that are actually differentiating.
• Data quality and deduplication. Canonicalization of user-entered RUTs lets you match and dedupe customer/supplier records reliably, which directly affects reporting, invoicing, and account merging decisions.
• Cost of validation coverage. The v5.3.0 addition of static RUT helpers lowers the friction of validating in places where dependency injection is awkward — seeders, factories, Artisan commands, one-off scripts, migration backfills. That makes "validate and normalize everywhere" a cheaper roadmap item than it was in 5.2.x, and it supports test-data generation for QA and demos of Chilean flows.
• Scope boundary to set expectations. This is format/checksum validation, not identity verification. Product decisions that require confirming a RUT actually exists at the Chilean SII are a separate integration; do not let "we validate RUTs" be read internally as "we verify businesses."

When to Consider This Package

Consider adopting when:

• You run a Laravel application (or a Laravel-adjacent service) serving Chilean users or Chilean B2B counterparties.
• You need validation in the framework's native idiom — form requests, validation rules, model casting/normalization — rather than a standalone validator you have to wire in yourself.
• You also need to generate valid RUTs for fixtures, factories, seeders, or QA environments, not just check them.
• You want the formatting/normalization edge cases handled by a maintainer instead of your team.

Look elsewhere when:

• The requirement is authoritative verification of a person or company (SII registry lookup, name matching, tax-status checks). This package will not satisfy that, and treating it as if it does creates compliance risk.
• You are outside Laravel/PHP — the ergonomics here are framework-shaped; a different stack should use a native library.
• You need multi-country document validation (CPF, CUIT, DNI, etc.) under one API. Evaluate a broader library rather than stitching several single-country packages.
• Your organization requires a dependency with a formal support contract or an SLA; this is a community package.

On v5.3.0 specifically: this is a minor release with one small functional addition (static RUT helpers) plus StyleCI and CI-configuration housekeeping. There are no indicated breaking changes, so teams already on 5.2.x can upgrade within the same major with low risk. The practical decision is simply whether to adopt the new static helpers in seeders and tests — a nice-to-have, not a reason to re-evaluate the dependency.

How to Pitch It (Stakeholders)

For executives: We need to accept Chilean tax IDs (RUTs) in our flows. Rather than build and maintain that validation ourselves, we can adopt a small, focused open-source Laravel package that handles validation, formatting, and test-data generation. It is a low-risk, narrow dependency: it does one thing, it is actively maintained, and the latest release (v5.3.0) is a routine minor update with no breaking changes. It supports the Chile-facing parts of the roadmap — onboarding, checkout, invoicing — and reduces the support burden of malformed-ID issues. Important caveat for planning: it confirms a RUT is well-formed, not that the business is real; any requirement for official verification is a separate scope with its own vendor and cost.

For engineering: Laragear/Rut gives us RUT validation and normalization in the Laravel idioms we already use — validation rules, form requests, casting — plus generation for factories and seeders. v5.3.0 adds static helpers so we can validate/generate without instantiating the service, which is handy in seeders, Artisan commands, and tests; the rest of the release is StyleCI and CI configuration churn. Upgrade from 5.2.x is a drop-in within the same major. Suggested guardrails: pin the version, wrap the package behind a thin internal adapter (a single validation rule plus a normalizer) so a future swap or a shift to a multi-country library doesn't ripple through the codebase, and keep the "format-valid vs. registry-verified" distinction explicit in code comments and product copy so no one ships a compliance claim the package can't back.