From a PDF to a number you can defend

The path, end to end

The whole path, before the detail. Squares transform, triangles decide.

1. 01

   It arrives without anyone doing data entry

   Forward a statement to your private drop-address, or connect the mailbox it already lands in. The address is provider-agnostic on our side, so it works from a personal inbox, an assistant's, or a shared one like reports@firm.com.

   Every delivery is recorded: what came in, whether it was ingested, rejected or failed, and why.

2. 02

   A classifier throws out what is not a report

   A mailbox is noisy. Before anything is read, each attachment is classified as a fund report or not. Payslips, invoices and the rest are rejected with a reason, and anything that is not a PDF stops right there.

   This gate matters more the wider you open the funnel.

3. 03

   Two checks stop the same statement counting twice

   The first compares files byte for byte, so a report that arrives both by forwarding and through a connected mailbox resolves to a single record. The second is a logical key of owner, fund, period and report type, which catches the harder case: two different scans of the same quarterly report, one original and one re-rendered, that are not byte-identical but describe the same quarter.

   Double-counted capital calls are the most expensive kind of quiet error. Both gates run before anything commits.

4. 04

   The document is converted and read in the EU

   The PDF is converted to text in an EU region, then read by a model in an EU region. Both hops fail closed: if a non-EU region is configured, the call raises an error rather than quietly sending your documents somewhere else. Before the text leaves, names of people and entities from your own directory are replaced with opaque placeholders, and the table mapping them back never goes with it.

   Amounts and dates are not masked, because reading them is the entire point. We would rather write that down than let you assume otherwise.

5. 05

   The extraction is scored against itself

   Rather than ask a second model whether the first was right, the extracted record is scored on its own completeness and internal consistency. A statement that filled every field lands at the top of the range; a missing fund name or period end drops it below the bar.

   No extra model call, no network, so the score cannot itself fail or drift.

6. 06

   Below the bar, the numbers go nowhere

   A report under the threshold is flagged, and both the cashflow path and the valuation path skip flagged reports entirely. Its figures cannot reach your portfolio at all until a person opens the review queue, which shows exactly which checks it failed. You approve it, re-run the extraction against a better scan, or archive it.

   Uncertain data is not entered as provisional and cleaned up later. It is inert until someone signs off.

7. 07

   The number keeps its route home

   Once committed, every figure references the document it was read from and what kind of source that was. When your administrator's IRR disagrees with ours, the question stops being whose spreadsheet is right and becomes which cashflows each of us counted, as of when, and from which page.

   This is the only reason the metrics are worth computing at all.