Core Laravel Package

Product Decisions This Supports

• Regulatory Compliance for Latin American Markets: Accelerates development of tax-compliant invoicing (UBL 2.1) for Peru, Chile, or other regions requiring Sunat-compliant documents (e.g., Facturas, Boletas, Notas de Crédito/Débito, Recibos por Honorarios). Reduces risk of fines for non-compliance.
• Build vs. Buy: Justifies buying this package over custom development for teams lacking tax-domain expertise, especially if invoicing is a core feature (e.g., SaaS for SMEs, e-commerce platforms, or accounting tools).
• Roadmap Prioritization:
  • Phase 1: Integrate core invoicing/UBL 2.1 support to launch MVP for tax-compliant regions.
  • Phase 2: Extend to other document types (e.g., Guías de Remisión) or regions (e.g., Mexico’s CFDI) by leveraging the package’s modular design.
  • Phase 3: Customize error handling (via Error Code Provider) or notifications for internal workflows (e.g., Slack alerts for failed validations).
• Use Cases:
  • B2B SaaS: Automate tax-compliant invoicing for clients in regulated markets (e.g., Latin America).
  • Marketplaces: Generate compliant receipts/invoices for vendors (e.g., "Recibos por Honorarios" for freelancers).
  • ERP/Accounting Tools: Plug into existing systems to handle tax-specific logic (e.g., IGV inclusion in free transactions).

When to Consider This Package

• Adopt if:
  • Your product requires UBL 2.1 compliance (e.g., Peru/Chile invoicing) and you lack in-house tax-expertise.
  • You need pre-built document types (Facturas, Boletas, Notas de Crédito/Débito) with minimal customization.
  • Your team prioritizes speed over full control—this package handles ~80% of tax logic out-of-the-box.
  • You’re targeting SMEs or freelancers who need compliant receipts (e.g., "Recibos por Honorarios").
• Look elsewhere if:
  • You need active maintenance (last release: 2020; consider forking or supplementing with a newer package like Laravel-Invoices).
  • Your region uses non-UBL standards (e.g., CFDI for Mexico, VATMOSS for EU).
  • You require advanced customization (e.g., multi-country tax rules) without extending the package.
  • Your stack is non-PHP/Laravel (e.g., Node.js, Python).

How to Pitch It (Stakeholders)

For Executives: "Greenter Core lets us launch tax-compliant invoicing in Latin America 3–6 months faster by leveraging a battle-tested PHP package. For example, it handles Peru’s UBL 2.1 requirements (Facturas, Boletas) and auto-calculates taxes like IGV—reducing audit risks and dev overhead. The MIT license avoids vendor lock-in, and we can extend it for other regions later. Upfront cost: ~$X for customization; long-term savings: $Y in compliance fines and dev time."

For Engineering: *"This package gives us:

• UBL 2.1 support (Facturas, Boletas, Notas de Crédito/Débito) with Sunat-compliant fields (e.g., Sunat Codes, expiration dates).
• Modular design: We can swap out the Error Code Provider or Notificator for our alerting system (e.g., Laravel Echo).
• Laravel-native: Integrates cleanly with Eloquent models and validation. Trade-offs:
• Last release was 2020, but the core logic (UBL 2.1) is stable. We’ll need to:
  1. Test edge cases (e.g., free transactions with IGV).
  2. Fork if we need updates (low risk; MIT license).
  3. Build wrappers for non-UBL regions. Proposal: Use this for MVP, then evaluate forking or alternatives post-launch."*