Weave Code
Account Laravel Package
mybizna/account
Accounting module for MyBizna and Laravel apps, providing chart of accounts, journals, transactions, invoices, and financial reports. Ships with Eloquent models, migrations, controllers, and routes so you can add double-entry bookkeeping to your application quickly.
The Account module is an essential part of the MyBizna ERP system. It provides functionality related to managing and tracking financial accounts within your organization.
Frequently asked questions about Account
- How do I install mybizna/account in a Laravel application?
- Install the module with Composer using composer require mybizna/account. Laravel's package auto-discovery should register the service provider, after which you publish any config and migration files and run php artisan migrate. Check the repository README for the exact publish tags and any required setup steps for the MyBizna ERP context.
- Does mybizna/account support double-entry bookkeeping?
- Yes. The module is built around double-entry accounting concepts, providing a chart of accounts, journals, transactions, and invoices backed by Eloquent models and migrations. Financial reports are generated from the same ledger data, so debits and credits stay consistent across your records.
- Which Laravel versions are supported by mybizna/account?
- The supported Laravel and PHP versions are defined in the package's composer.json, not in the short description, so review those constraints before adding it to an existing project. Because the module is part of the MyBizna ERP ecosystem, it may also require related MyBizna core packages. Test installation on your target Laravel version in a branch before rolling it out.
- How do I publish the migrations and configuration for the account module?
- Use Laravel's vendor:publish command with the tag documented in the repository README, which copies the module's migrations and config into your application. After publishing, run php artisan migrate to create the accounting tables. Keeping published migrations in version control makes it easier to track schema changes across environments.
- Can I use mybizna/account outside of the MyBizna ERP system?
- The package is described as usable in MyBizna and other Laravel applications, since it ships standard Eloquent models, migrations, controllers, and routes. In practice, confirm whether it depends on shared MyBizna packages by checking its composer requirements and service providers. If those dependencies are light, it can serve as a standalone accounting layer in a custom Laravel app.
- What models and database tables does the package create for accounts and journals?
- The module provides Eloquent models and migrations for the chart of accounts, journals, transactions, and invoices, forming the core ledger structure. These tables store account definitions and the entries that post against them so balances can be derived. Review the published migration files to see exact column names before writing queries or integrations.
- How do I create invoices and generate financial reports with mybizna/account?
- Invoices and reports are handled by the controllers and routes the module ships, and you can also work directly with the underlying models and services from your own code. Typical flows include creating an invoice, posting the related journal entries, and then querying account balances for reports. Check the repository for the available endpoints and their expected request data.
- Can I customize or disable the routes and controllers included in the package?
- Because the module ships its own routes and controllers, you can override behavior by defining your own routes that point to custom controllers, or by registering the module's routes conditionally if configuration allows. Many Laravel modules let you disable package routes via a config flag, so verify what mybizna/account exposes. Extending the provided controllers is usually safer than editing vendor files.
- How should I test the accounting module in my Laravel application?
- Use the RefreshDatabase trait with the module's migrations so each test starts from a clean chart of accounts. Seed a few accounts, post journals and invoice transactions, then assert that debits equal credits and that balances match expectations. Running these tests against an in-memory SQLite or dedicated test database keeps them fast and isolated.
- Is mybizna/account actively maintained, and what are the alternatives?
- The module is maintained as part of the MyBizna ERP project, so activity generally follows that project's release cycle; check the GitHub repository for recent commits and issues. Alternatives include building a lightweight ledger on top of packages like brick/money, or evaluating other Laravel accounting packages with similar chart-of-accounts features. Compare migration structure, report coverage, and Laravel version support before deciding.
Weaver
How can I help you explore Laravel packages today?