# Bookkeeping practices: client portal using Laravel ## Summary A client portal blueprint for bookkeeping practices built with Laravel on Ample. Domain schema: client_entities (legal_name, entity_type, accounting_software, period_cadence): clients and their bookkeeping cadence; engagements (client_entity_id, period_start, period_end, close_status): monthly or quarterly close engagements; document_requests (engagement_id, category, due_at, status, uploaded_object_key): receipts, statements and payroll summaries requested; close_checklists (engagement_id, item, done_at): close tasks per period; document_access (document_id, principal_reference, role, granted_at): who may read which document. Public information: service packages and cadence, onboarding checklist, contact details. Kept out of scope until handling is reviewed: bank statements and receipts, payroll data, login credentials for accounting software. Never store client accounting-software credentials in these flows; financial records are sensitive and no compliance is claimed. Technical basis verified on Laravel: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). ## Infrastructure requirements - Compute: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.) - Postgres: verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.) - S3-compatible object storage: verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.) ## Prerequisites - A Laravel project (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template) - A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted) - Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables - A review of which bookkeeping practices data classes may be handled at all; this blueprint models public information only ## Exact tested configuration - template: `php-8.5` - runtime: `php` - size: `s-1vcpu-1gb` - install: `composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader` - start: `frankenphp php-server --listen :$PORT --root public` ## Steps 1. **Model the bookkeeping practices domain.** Create the tables client_entities, engagements, document_requests, close_checklists, document_access. Clients and their bookkeeping cadence lives in client_entities; keep the sensitive classes (bank statements and receipts, payroll data, login credentials for accounting software) out of this schema. 2. **Workflow step 1.** Model client entities and engagement periods; every document belongs to one engagement. 3. **Workflow step 2.** Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client). 4. **Workflow step 3.** Store documents in the private bucket and stream them through the app. 5. **Workflow step 4.** Deploy and verify the negative authorization tests and an authorized download. 6. **Deploy.** Run the synchronous deploy once and read the result. Re-running with no change is a no-op. ``` ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... ``` 7. **Verify.** Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the bookkeeping practices workflow. ``` ample logs --kind build ``` ## Tested examples - **Laravel pattern fixture** (tests/deploy-canaries/laravel-patterns): Verified private document library basis for this blueprint. ## Success checks - app responds on its public URL (`/` on the live URL, expect ample canary laravel patterns) - private-document-library self-test from the example (`/p/private-document-library` on the live URL, expect see the pattern fixture checks) ## Limitations - The technical basis (private document library on Laravel) was verified with the pattern fixture; the bookkeeping practices 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. Never store client accounting-software credentials in these flows; financial records are sensitive and no compliance is claimed. - Public content and synthetic examples only until actual data-handling requirements have been reviewed. - Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified. - Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified. - PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not verified. ## Cost estimate Estimated 10.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371). - app server x1 `s-1vcpu-1gb`: 5.00 USD - managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included. ## Verification evidence - canary_run on 2026-09-20T20:36:21Z at revision `118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c)`: Laravel pattern fixture deployed on Ample (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template); the private document library checks passed: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). The blueprint's Bookkeeping practices schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-19T20:36:21Z) Last verified: 2026-09-20T20:36:21Z ## Execution binding MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-21T03:19:59.461917+00:00 at revision `49962bcade4f`, binding state `current`, required scopes: servers:write, databases:read, buckets:read.