Download the PHP package azaharizaman/nexus-payable without Composer
On this page you can find all versions of the php package azaharizaman/nexus-payable. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download azaharizaman/nexus-payable
More information about azaharizaman/nexus-payable
Files in azaharizaman/nexus-payable
Package nexus-payable
Short Description Nexus Payable Package - Framework-agnostic accounts payable management
License MIT
Informations about the package nexus-payable
Nexus\Payable
Framework-agnostic accounts payable, vendor bill management, 3-way matching, and payment processing for the Nexus ERP system.
Overview
The Nexus\Payable package provides comprehensive accounts payable (AP) functionality including:
- Vendor Management: Complete vendor lifecycle with configurable payment terms and matching tolerances
- Bill Processing: Vendor bill submission via manual entry or CSV import (OCR planned for Phase 2)
- 3-Way Matching: Automated matching of Purchase Orders, Goods Received Notes, and Vendor Invoices
- Payment Scheduling: Automated due date calculation with early payment discount tracking
- GL Integration: Seamless posting to
Nexus\Financegeneral ledger - Multi-Currency Support: Full currency conversion via
Nexus\Currency - Audit Trail: Comprehensive change tracking via
Nexus\AuditLogger
Key Features
Enterprise-Grade AP Management
- Per-Vendor Tolerance Configuration: Configure quantity and price variance thresholds per vendor
- Flexible Payment Terms: Net 30, 2/10 Net 30, COD, and custom terms
- Multi-Currency Bills: Store bills in original currency with base currency equivalent
- Payment Reconciliation: Automatic matching of payments to GL postings
- Aging Reports: 30/60/90-day vendor aging analysis
3-Way Matching Engine
The matching engine validates vendor bills against:
- Purchase Order (PO) from
Nexus\Procurement- Expected quantity and agreed price - Goods Received Note (GRN) from
Nexus\Inventory- Actual received quantity - Vendor Invoice - Billed quantity and price
Configurable per-vendor tolerance rules prevent GL posting when variances exceed thresholds.
Payment Processing
- Automated payment scheduling with due date calculation
- Early payment discount tracking and alerts
- GL journal entry generation via
Nexus\Finance - Payment approval workflows (optional via
Nexus\Workflow) - Bank transfer file generation (Phase 2)
Architecture
This package follows the Nexus Architecture Principle: "Logic in Packages, Implementation in Applications."
Package Layer (Pure PHP)
- Framework-agnostic: No Laravel dependencies
- Business Logic: All AP rules, matching algorithms, payment calculations
- Interfaces: Defines data structures and persistence contracts
- Value Objects: Immutable domain objects (PaymentTerm, MatchingTolerance, etc.)
- Services: PayableManager, MatchingEngine, PaymentScheduler for orchestration
Application Layer (Laravel/Atomy)
- Eloquent Models: Vendor, VendorBill, VendorBillLine, BillMatching, PaymentSchedule
- Repository Implementations: Concrete persistence implementations
- Database Migrations: Schema definitions
- Service Provider: IoC container bindings
- API Controllers: RESTful endpoints for AP operations
Installation
Requirements
- PHP: ^8.3
- Dependencies:
azaharizaman/nexus-finance- General ledger integrationazaharizaman/nexus-period- Fiscal period validationazaharizaman/nexus-uom- Unit of measurement (currency)azaharizaman/nexus-currency- Multi-currency supportazaharizaman/nexus-audit-logger- Change trackingpsr/log- Logging interface
Core Concepts
Vendor Management
Bill Submission
3-Way Matching
Payment Processing
Directory Structure
Integration with Nexus Packages
Required Dependencies
- Nexus\Finance: GL journal entry posting for AP liability and expense accounts
- Nexus\Period: Fiscal period validation for bill dating
- Nexus\Uom: Currency management and conversion
- Nexus\Currency: Exchange rate resolution for multi-currency bills
- Nexus\AuditLogger: Audit trail for all AP state changes
Optional Dependencies
- Nexus\Procurement: Purchase Order data for 3-way matching
- Nexus\Inventory: Goods Received Note data for 3-way matching
- Nexus\Workflow: Multi-level payment approval workflows
- Nexus\DataProcessor: OCR for automated bill data extraction (Phase 2)
- Nexus\EventStream: Event sourcing for payment lifecycle (large enterprises)
Consumed By
- Nexus\Accounting: Financial statement generation (AP aging reports)
- Nexus\Export: Payment advice document generation
Performance Requirements
- Bill submission and validation: < 200ms per bill
- 3-way matching: < 500ms for 100-line bill
- Payment scheduling: < 100ms per payment
- GL posting: < 300ms (via Finance package)
- Vendor aging report: < 3s for 10,000 bills
Security & Compliance
- Immutable Bills: Once matched and posted, bills cannot be modified (reversal only)
- Tenant Isolation: All data scoped to tenant ID
- Audit Trail: All state changes logged to
Nexus\AuditLogger - Field-Level Encryption: Bank details encrypted at rest
- RBAC Integration: Authorization via
Nexus\Identity(application layer)
Roadmap
Phase 1 (Current - V1.0)
- ✅ Vendor management with configurable tolerances
- ✅ Manual bill submission and CSV import
- ✅ 3-way matching engine
- ✅ Payment scheduling and GL integration
- ✅ Multi-currency support
Phase 2 (Future)
- ⏳ OCR integration via
Nexus\DataProcessor - ⏳ Payment approval workflows via
Nexus\Workflow - ⏳ Bank transfer file generation
- ⏳ Automatic payment reminders
- ⏳ Vendor portal for self-service bill submission
Phase 3 (Enterprise)
- ⏳ Event sourcing via
Nexus\EventStream - ⏳ Advanced analytics and forecasting
- ⏳ Batch payment processing
- ⏳ ACH/wire transfer integration
Testing
📖 Documentation
Package Documentation
- Getting Started Guide - Quick start guide with prerequisites, core concepts (3-way matching, payment terms), and first integration
- API Reference - Complete documentation of all 21 interfaces, 5 enums, 2 value objects, and 8 exceptions
- Integration Guide - Laravel and Symfony integration examples with complete code
- Basic Usage Example - Simple vendor bill creation and payment processing
- Advanced Usage Example - 3-way matching, payment scheduling, variance handling
Additional Resources
IMPLEMENTATION_SUMMARY.md- Implementation progress, architecture, and metricsREQUIREMENTS.md- Detailed requirements (128 requirements documented)TEST_SUITE_SUMMARY.md- Test coverage strategy and planned tests (83 tests)VALUATION_MATRIX.md- Package valuation metrics ($190,710 estimated value)- See root
ARCHITECTURE.mdfor overall system architecture - See
docs/NEXUS_PACKAGES_REFERENCE.mdfor integration with other Nexus packages
License
MIT License - see LICENSE file for details.
Support
Part of the Nexus ERP Monorepo.
- Main Documentation: See package
docs/folder - Architecture: See root
/ARCHITECTURE.md - Package Reference: See
docs/NEXUS_PACKAGES_REFERENCE.md