Bookkeeping practices: client portal using Laravel · Ample Computer

Bookkeeping practices: client portal using Laravel

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. 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).

What it runs on

You need

Exact tested configuration

installcomposer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader

runtimephp

sizes-1vcpu-1gb

startfrankenphp php-server --listen :$PORT --root public

templatephp-8.5

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 <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
  1. 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 <deployment_id> --kind build

How it was checked

✓app responds on its public URL· http get/ → “ample canary laravel patterns”
✓private-document-library self-test from the example· http get/p/private-document-library → “see the pattern fixture checks”

Evidence

  1. November 6, 2026 · canary run
    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.

Tested examples

What it doesn’t cover