Amir Programmer Guide
نسخه فارسی
Back to documentation index
This index is for developers and contributors. If you plan to change Laravel code, the database, tests, services, or accounting logic, start here.
Suggested Reading Path
- Project structure
- Database guide
- Testing guide
- Accounting basics
- Fiscal year
- Fiscal-year export/import
Technical Documentation
| File | Purpose |
|---|---|
| project-structure.md | Laravel architecture, folders, and code organization |
| database-guide.md | Tables, relationships, and database notes |
| testing-guide.md | Running tests and writing Feature and Unit tests |
| ../script/README.md | Data migration and utility scripts |
Accounting Domain Documentation for Development
| File | Purpose |
|---|---|
| accounting-basics.md | Debit/credit concepts, balanced documents, and transaction storage |
| user/inventory-costing.en.md | User-facing explanation of COGS and the moving weighted average method |
| return-sell-return-buy.md | Recording sales returns and purchase returns |
| fiscal-year.en.md | Fiscal-year concept and creation flow |
| FiscalYearExportImport.en.md | Fiscal-year export and import commands |
Important Rules for Code Changes
- Do not break accounting document balance.
- Company and fiscal-year data must remain separated.
- Financial changes must include Feature or Unit tests.
- Keep controllers thin and put business logic in services.
- Changes to transaction builders or cost-of-goods calculations need accounting-domain review.