# Accounting firms: form collection using Laravel

## Summary
A form collection blueprint for accounting firms built with Laravel on Ample. Domain schema:  
- **client_entities** (legal_name, entity_type, fiscal_year_end, jurisdiction): the businesses and individuals served;  
- **engagements** (client_entity_id, service_line, period_start, period_end, status): bookkeeping, tax and audit engagements by period;  
- **document_requests** (engagement_id, title, due_at, status, uploaded_object_key): requests for source documents;  
- **deliverables** (engagement_id, title, object_key, released_at): returns and statements released to the client;  
- **uploads** (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.  
Public information: service lines and typical engagement periods, filing calendars and deadlines, office locations.  
Kept out of scope until handling is reviewed: tax identifiers and financial statements, bank and payroll records, identity documents.  
Financial records and tax identifiers are regulated in most jurisdictions; the portal flows here model authorization only and claim no compliance.

## Representative Queries
- Accounting firms: form collection using Laravel  
- Where can I host Accounting firms: Form collection built with Laravel?  
- I need a genuinely specialized form collection workflow covering engagement periods, client entities and document authorization.

## Resource Requirements
- **primitive:compute**  
- **primitive:postgres**  
- **primitive:s3-compatible-object-storage**

## Infrastructure Requirements
1. **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.  
2. **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.  
3. **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## Workflow Steps
1. **Model the accounting firms domain**: Create the tables client_entities, engagements, document_requests, deliverables, uploads. The businesses and individuals served lives in client_entities; keep the sensitive classes (tax identifiers and financial statements, bank and payroll records, identity documents) out of this schema.
2. **Model document requests per engagement with due dates and status**.
3. **Validate uploaded files** (type, size) before storing them in the private bucket and linking them to the request.
4. **Authorize uploads by client entity**.
5. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
6. **Verify**: Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the accounting firms workflow.

## Limitations
- The technical basis (browser file uploads on Laravel) was verified with the pattern fixture; the accounting firms schema and workflow are an original design for this blueprint and were not executed as a separate application.
- No health, financial, privacy or other compliance claim is made. Financial records and tax identifiers are regulated in most jurisdictions; the portal flows here model authorization only and claim no compliance.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.

## Cost Estimate
**Currency**: USD  
**Monthly Amount**: 10.0  
**Basis**: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.

### Components
- **App server**: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
- **Managed PostgreSQL database**: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Success Checks
1. **App responds on its public URL**: Expect - ample canary laravel patterns
2. **Browser-file-uploads self-test**: Expect - see the pattern fixture checks

## Examples
**Title**: Laravel pattern fixture  
**Description**: Verified browser file uploads basis for this blueprint.

## Next Actions
- **Action**: Browse the catalog index  
- **Operation**: catalog_index  
- **Method**: GET  
- **Relative Path**: /v1/catalog

- **Action**: Prepare a side-effect-free deployment plan for an authorized project  
- **Operation**: plan_deployment  
- **Method**: POST  
- **Relative Path**: /v1/catalog/plan

--- 
**Note**: The content has been cleaned to contain only the main article content, preserving headings, structured data, and lists.
