I need a seasoned AWS developer to architect and build an end-to-end, cloud-native accounting and tax application. The core of the system must cover invoicing, expense tracking, and a full tax-filing module, all delivered as a secure, multi-tenant SaaS running entirely on AWS. Key functionality • Real-time double-entry ledger supporting multi-currency books • Automated invoicing with payment gateway hooks (Stripe, PayPal, etc.) • Expense capture (manual and OCR upload) that flows straight into the ledger • Full tax engine able to calculate, file, and archive returns for multiple jurisdictions • On-demand reports: Profit & Loss, Balance Sheet, Cash Flow, plus fully customizable layouts • Direct bank feeds: pull transactions via secure bank APIs and reconcile automatically • Tight payroll integration so salary journals post without manual touch AWS architecture expectations A serverless first approach (Lambda, API Gateway, DynamoDB or Aurora Serverless, S3, Cognito, EventBridge) is preferred for scalability and cost control, but I’m open to your recommendation if you can justify an alternative. CI/CD through CodePipeline or GitHub Actions should deliver zero-downtime deployments, and infrastructure must be reproducible with CloudFormation or Terraform. Deliverables 1. Solution architecture diagram and tech stack decision document 2. Fully deployed MVP in my AWS account, reachable through a React or Angular SPA 3. Source code in a private Git repo with clear commit history and README setup instructions 4. API documentation (OpenAPI/Swagger) plus sample Postman collection 5. Unit and integration test suite hitting at least 80 % coverage 6. Knowledge-transfer walkthrough and handover of all credentials Acceptance criteria • Successful creation of invoices, expenses, and tax filings without errors • Accurate generation of P&L, Balance Sheet, and Cash Flow reports using live data • Bank feed connects to at least one sandbox institution and imports transactions • End-to-end test passes for a payroll run posting to the ledger • System withstands a load test of 1 000 concurrent users with response <300 ms p95 Timeline and milestone suggestions are welcome; I’m ready to start as soon as we agree on the architecture.