Question 1

Is my statement stored anywhere?

Accepted Answer

No. It is written to a RAM-backed workspace, read, and unlinked when the request ends. It never reaches a disk, is never logged, and there is no copy to delete later because none is made. A test in the build fails if any code path writes a request body outside that workspace.

Question 2

My statement has no lines or borders. Will it work?

Accepted Answer

That is the normal case for a statement and it is specifically handled. The columns are found by looking at where the gaps line up across consecutive rows, not by looking for rulings. A tool that only reads ruling lines reports no tables on most statements.

Question 3

Will debits come out negative?

Accepted Answer

If your statement writes them as (250.00), yes — that is read as −250 rather than as text. This matters because a value read as text silently drops out of every total you calculate afterwards.

Question 4

What if the statement is a scan?

Accepted Answer

Then it is a picture with no text to read, and the scanner will say no tables were found. The parse API with ocr=force reads it as text first, priced per page because OCR costs per page.

Bank statement to CSV

Related