Read a statement and put its movements on an account

Takes the statement as file in a multipart form, or a PDF one as page image parts in order. A PDF sent as file is filed with the account and read in the background, and the answer carries processing rather than lines: its import stays processing until the movements are on the account. CODA and CAMT are specified formats and are read exactly; a CSV or a spreadsheet whose header names its columns is read exactly too; anything else is read by a model, and read says which of the three happened. A movement already on the account, including one your bank reported before the file arrived, is returned marked duplicate and is never written twice. Send dryRun=true to see what would be imported without importing it, which is what the screen does before it asks.

Each line carries a hash. Send the hashes of the lines the owner picked as lines with the real import and only those are written, so a line unticked in the preview stays out. Leave lines out and every line not already held is written.

Once new movements are written, incoming money Dardaris is sure of is placed against what it pays, under the owner’s placement setting. History is never placed. placed and waiting say what happened; waiting is null when placing is left to the hourly pass.