|
|
|
|
|
|
by cd_mkdir
164 days ago
|
|
|
OP here. Just to share a bit of the engineering headache behind this: The hardest part wasn't the Django backend, it was getting the LIBR (Lowest Intermediate Balance Rule) logic to handle edge cases in the PDF parsing. Bank statements often group transactions by date, not time. If a user deposits $5k and withdraws $5k on the same day, the order matters for the 'dip' calculation. I ended up having to write a heuristic that forces 'Withdrawals First' (worst-case scenario for the claimant) to ensure the report stands up to conservative judicial scrutiny. If anyone here has worked with financial event sourcing for legal compliance, I'd love to know how you handle same-day timestamp ambiguity. |
|
|