- Is latysh/aba-bundle a Laravel package?
- No. It is a Symfony2 bundle registered through AppKernel, and it ships no Illuminate service provider, facade, or publishable config file, so Laravel's package discovery will not pick it up. The ABA generation logic is portable plain PHP, but the framework wiring is Symfony-specific.
- Can I install latysh/aba-bundle with Composer in a Laravel app?
- Practically no. The bundle's Symfony2-era constraints pull symfony/* components to the 2.3 to 2.8 line and likely require PHP 5.4 or 5.6, which conflicts with the symfony/http-foundation, console, and process versions modern Laravel needs. A composer require would trigger a downgrade cascade across the framework.
- What does latysh/aba-bundle actually generate?
- It writes Australian Banking Association (ABA/Cemtex) direct-entry files for bulk payments such as payroll or supplier runs. Records are fixed-width 120 characters: a type 0 header, type 1 detail records, and a type 7 trailer carrying record counts plus net, credit, and debit totals. Correct output also depends on BSB padding, transaction codes, ASCII encoding, and CRLF line endings.
- Which Laravel and PHP versions does latysh/aba-bundle support?
- None officially. It targets Symfony2, which reached end of life in November 2018, and its Composer constraints point at PHP 5.4 or 5.6. It is not PHP 8 compatible and has no Laravel version support at all.
- How is latysh/aba-bundle configured?
- Configuration is done the Symfony2 way, through bundle settings registered in AppKernel and Symfony config files, with the service fetched from the container. There is no Laravel config/aba.php to publish, and there is no ready-made place to bind your DE user ID, institution code, BSB, or account without rewriting the wiring.
- Is latysh/aba-bundle safe to use in production?
- The risk is high. The package has one star, zero dependents, and a score around 0.005, meaning no production validation, and the Symfony2 branch it targets receives no security patches. There is no meaningful test suite or golden-file fixture proving a bank ever accepted its output, and trailer totals, transaction codes, and filler records are exactly what banks reject.
- What are the alternatives to latysh/aba-bundle for ABA files in Laravel?
- The realistic options are forking the record-building logic into a standalone PHP library, vendoring the source into app/Support/Aba, or reimplementing from the public Cemtex specification. The spec is stable and the writer is roughly 200 lines of field padding and totals arithmetic, so an in-house implementation with golden-file tests is credible. Whichever path you choose, validate output with your bank before first live lodgement.
- How do I test ABA file output before lodging with a bank?
- Obtain one bank-accepted sample ABA file, store it as a fixture, and assert byte-for-byte equality from a fixed input set. Check 120-character record widths, CRLF line endings, ASCII encoding, BSB and account padding, transaction codes, and trailer counts and totals. A bank-provided sandbox or validation utility is worth more than any unit test here.
- Does latysh/aba-bundle parse ABA return files or dishonours?
- Almost certainly not. It is a writer only, generating header, detail, and trailer records, and there is no evidence of return-file or dishonour parsing. If you need reconciliation of inbound bank files, you will have to build or source that separately.
- How do I reuse latysh/aba-bundle's ABA logic in Laravel without the bundle?
- Treat the upstream source as a specification cross-check rather than a runtime dependency. Extract the record builders into framework-agnostic value objects such as HeaderRecord, DetailRecord, TrailerRecord, and AbaFile, then bind an AbaFileGenerator interface in an AppServiceProvider and expose DE user ID, institution code, bank name, BSB, and account via config/aba.php. No Symfony dependency needs to survive the port.