Last week, our community focused on practical challenges and shared resources that can significantly streamline forensic accounting tasks. There was a lively exchange on dealing with complex bank PDFs and ensuring efficient production workflows. Members also shared various templates and strategies for creating effective summary schedules, an essential tool for presenting evidence clearly. Additionally, discussions around innovative approaches to cross-border tracing and the historical context of internal accounting controls drew considerable interest.
This Week’s Hot Topics
Taming messy bank PDFs before production
This thread delves into practical techniques for managing the chaos of bank PDFs, a common issue that can slow down the production process. Read more here
FRE 1006 summary schedules — best templates
Members are exchanging their preferred templates for FRE 1006 schedules, which are crucial for summarizing voluminous data in court. Read more here
Preparing flow-of-funds schedules for trial
This discussion covers how to effectively prepare flow-of-funds schedules, a key piece of evidence that can make or break a case. Read more here
Scalable flow-of-funds tracing workpapers
Explore how to develop workpapers that can scale, enabling seamless tracing of funds across complex networks. Read more here
Rapid cross-border tracing stack
Here, the conversation revolves around enhancing tracing speed and accuracy in a cross-border context, a growing necessity in global cases. Read more here
Who first mandated internal accounting controls
A fascinating look at the origins of internal accounting controls and their impact on modern practices. Read more here
Bank statement OCR that keeps rows intact
Dive into the technology that ensures OCR processes do not disrupt the integrity of bank statement data. Read more here
Shareable rules for detecting invoice splitting
This thread offers practical rules that can help in spotting and preventing invoice fraud, a persistent issue in accounting. Read more here
Looking forward to another week of insightful discussions. Your contributions make this community a valuable resource for us all.
I get fewer misreads by flattening and OCR‑ing in Acrobat, then extracting with Tabula (lattice); it keeps memo lines intact and makes the ‘summary schedule’ roll-up cleaner. If the columns drift I switch to stream or to pdfplumber — otherwise you’re reconciling spaghetti. Anyone mapping x‑coords for recurring layouts?
I keep a per‑bank “column map” and run Camelot (stream) with fixed column coords, then convert parentheses to negatives in Power Query — memo wraps stay intact; only caveat is pre‑rotating mixed‑orientation pages in Acrobat. @emiliaf_39 if you like Tabula, Camelot’s similar: https://camelot-py.readthedocs.io/.