AWS Builder Center
Weekend Showcase Challenge: Financial Flow Update

Weekend Showcase Challenge: Financial Flow Update

Financial Flow is a cloud-native personal finance PWA built on AWS Amplify Gen 2, Cognito, AppSync GraphQL, and DynamoDB. Designed for salary-to-salary budgeting across custom financial cycles, it features automated debt carry-forward for unsettled payables/receivables, in-line math expression logging, instant profile sync, and full offline support - giving users complete control over multi-cycle budgets.

AWS Student Builder Leader | Full-Stack Developer | Cloud Enthusiast


💡 Vision & What It Does

Earlier this summer during the build series, I published my initial build:  Financial Flow: Cloud-Native Personal Finance Management  a platform built with AWS Amplify Gen 2 that allows users to manage budgets across custom salary billing cycles instead of rigid calendar months.
While the initial version allowed users to log math-expression expenses and manage basic payables and receivables, users faced a major real-world challenge: What happens to unpaid debts when a financial cycle ends?
For this Weekend Showcase Challenge, I took Financial Flow further to solve this exact problem. The updated app introduces an Automated Debt Carry-Forward Engine, Real-Time Profile Display Name Synchronization, and enhanced AWS Amplify backend integrations.



🚀 What’s New: The Showcase Updates

Here are the major feature additions and refinements shipped for the Weekend Showcase:

1. Automated Debt Carry-Forward Across Cycles

Unpaid bills, group expenses, and personal loans often span across multiple billing periods. Manually re-entering unpaid debts when starting a new financial month is error-prone and time-consuming.
  • Automatic Cycle Rollover: When starting a new Financial Month, the engine automatically identifies all unsettled payables and receivables ( settled === false ) and carries them forward into the new cycle with updated date stamps.
  • Audit Trail Integrity: Predecessor debt records in past cycles are safely closed out and tagged ( Carried forward to [New Month] ), preserving historical ledger accuracy while preventing double-counting in active totals.
  • One-Click Import Banner: For active billing cycles, an intelligent banner in the Payables & Receivables dashboard detects past unsettled records and lets users migrate them into the current month with a single click.

2. User Display Name & Instant Profile Sync

  • Registration Display Name: Added custom display name input ( userAttributes.name ) during user registration powered by AWS Cognito User Pools.
  • Immediate Profile Sync: Updated the authentication callback so user display names update across the top header and sidebar profile badge immediately upon sign-in without requiring a page refresh.



🏗️ How I Built It & AWS Architecture Overview

Financial Flow is powered by AWS Amplify Gen 2, leveraging a 100% type-safe, code-first serverless architecture defined in TypeScript.


AWS Services Used:

  • AWS Amplify Gen 2: Manages code-first backend resource definitions ( amplify/auth/resource.ts ,  amplify/data/resource.ts ) and full-stack deployment via  amplify.yml .
  • AWS Cognito User Pools: Handles encrypted authentication, sign-up/sign-in flows, and custom user attributes ( name ,  email ).
  • AWS AppSync (GraphQL API): Executes fast GraphQL queries and mutations for transactions, debts, and financial cycle states.
  • Amazon DynamoDB: Serves as the NoSQL table storage backing  FinancialMonth ,  Expense , and  Debt  schema models.
  • AWS Amplify Hosting: Hosts the production web application with automated build pipelines.



🎓 What I Learned Across the Summer

Building and refining Financial Flow throughout the AWS Summer Build Series has been an incredible learning experience:
  1. Building Beyond MVPs: Taking an earlier summer build and refining it based on real-world edge cases (like debt carry-forward logic) demonstrated how serverless AWS architecture makes iterating on data models seamless.
  1. Type-Safe Backend Development: AWS Amplify Gen 2's TypeScript definitions allowed me to modify GraphQL schema models and backend triggers without leaving my IDE or writing manual CloudFormation templates.
  1. Data Integrity & State Handling: Managing multi-cycle rollover logic reinforced the importance of handling state transitions cleanly in DynamoDB to keep user ledgers accurate across past, present, and future billing periods.



🔗 Links to App & Previous Post

Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article