Fiscus

• 

  Dashboard

Inspiration

As a volunteer, Bryan was always knee deep in confusing financial forms, forced to manually process decades of red tape. Due to privacy concerns, he couldn't offload these tasks onto an agent. We decided to build a harness that indexes and stores financial documents with built in guards for privacy.

What it does

After uploading images of their financial information and forms, Fiscus stores form structure and data into its database. Users can then query Fiscus to answer their questions about their data.

How we built it

We used React and Node to build the web app, hosting our agent on AWS through Bedrock, and our database on CockroachDB.

Challenges we ran into

This was our first time using typescript, AWS, and CockroachDB. While setting up CockroachDB, we ran into an issue trying to complete one part of the project with a flask backend, while another with a node backend. This became an issue when trying to integrate both parts with our data redaction functions, forcing us to refactor the python portion.

Accomplishments that we're proud of

Successfully getting AWS and CockroachDB integrated with the frontend :) Also implementing multiple layers of redundancy to ensure financial data is scrubbed and consistent(memory layer, corrections loop, vector indexing, RBAC).

What we learned

Database utilization with CockroachDB, how to setup context persistence for agents, tried implementing Github CI tests to maintain functionality.

What's next for Fiscus

We want to continue refining Fiscus to be easy for organizations to use, and create more optionality for different service providers. Additionally, besides processing financial data for volunteer organizations, we'd like to expand to other types of documents. We'd also like to explore more tools, such as integrating Lambda for additional operations, or Stripe for payment processing.

Built With

• amazon-web-services
• cockroach
• node.js
• typescript