Inspiration
The project was born from a desire to master financial data integrity and spreadsheet automation. After encountering recurring #NAME? errors and formula propagation issues in our P&L and Balance Sheet models, we decided to build a robust diagnostic system to identify, document, and resolve these structural discrepancies.
What it does
Its just a financial model manually corrected by me
How we built it
We performed a cell-by-cell audit of our Excel financial model. We replaced hardcoded values with dynamic references, fixed broken SUM ranges that were missing line items, and implemented the fundamental accounting equation:
Challenges we ran into
The primary challenge was error propagation. A single typo in an intermediate cell (e.g., B1O instead of B10) caused a chain reaction of #NAME? errors across the P&L. Furthermore, reconciling the Cash Flow statement required ensuring that the "Opening Cash Balance" dynamically referenced the "Cash and Cash Equivalents" from the Balance Sheet, which was initially misaligned.
Accomplishments that we're proud of
Restored Balance: Successfully rectified the Balance Sheet for FY 2025-26, which was previously off by 14,038. Logical Consistency: Standardized the Income Statement to use a unified "Sum-of-negatives" approach for expenses. Dynamic Linking: Automated the transition between the Balance Sheet and Cash Flow statement.
What we learned
We learned that financial modeling is as much about structural logic as it is about accounting. A small syntax error is magnified by complex dependencies, making thorough audit trails essential. We also realized the importance of using referencing instead of hardcoding to ensure long-term model scalability.
What's next for FSF Error Logs & Correction
Its the end of project
Log in or sign up for Devpost to join the conversation.