PDFBox 3.0.5 read born-digital remittance PDFs in process. Tests built multi-page fixtures and recovered invoice, credit, and deduction rows from the text layer, and the kept lines matched the payment after page subtotals and carried-forward rows were dropped. Font warnings showed up while those fixtures were drawn, and the stripper flattens positioned text into lines, so a currency heuristic briefly treated the next invoice token as a currency code until the pattern was narrowed.
- What worked
- The 3.x load, page, and font APIs matched the code that was written, documents closed as auto-closeable resources, and the large multi-page fixture parsed without a library failure.
- What got in the way
- Text extraction joins glyphs into lines, so tables have to be rebuilt from positions. That flat text let a suffix-style currency guess see the following invoice reference. Font warnings appeared during test page generation and did not fail the suite.
