If your carrier issues a loan accounting statement — the page listing every loan, repayment, and interest charge with a running balance — Import statement reads it and records the history for you. It does the same job as Add past activity, from a document rather than by hand.
You'll find it on the Loans page: expand a policy's row, and Import statement sits next to Add past activity. Importing requires Builder Pro.
Every row is checked before anything is recorded
The statement is verified line by line: each row's balance must follow from the row before it, and the last row must agree with the total your carrier printed. A statement that does not add up is not imported. Instead the rows that did not follow are listed with what they read and what they follow to, so you can compare against your document and enter the history by hand if you prefer.
This check is why a carrier statement can be trusted as history rather than treated as an estimate.
Review before recording
Nothing is recorded until you choose to record it. The review table renders in the carrier's own column order, with the carrier's own transaction words, so you can hold it beside your document. Each row says what it becomes:
- Will be recorded — new to Policy Stack.
- Already recorded — matches something you already have.
- Partly recorded — one part of the row exists and the rest does not. A cash loan row is a draw and the advance interest charged with it, so half of it can already be present.
Below the table, a plain summary states how many events will be recorded, how many already match, whether the loan balance changes, and whether any estimate from a snapshot will be replaced by the carrier's detail.
What the import will not do
- It never deletes an existing loan event. An event you recorded that the statement does not show is reported and left alone — it may be activity that postdates the statement.
- It does not decide which draw a repayment paid down. Your carrier's statement does not say, and the import does not invent it.
- If the loan already has a starting balance, the statement's balance-forward row is not added again. The import says so, and the balance still reconciles to the carrier's total.
Undoing an import
Every import can be reversed from the same screen. Undo backs out the append-only loan events it recorded and removes the importer-created repayment entry that supports those events; it leaves the event history auditable. The statement itself stays in your documents — remove it there if you want it gone.
If a recording stops part way
Occasionally a statement passes its checks but cannot be recorded in full — most often when it carries more loan principal than the loan's recorded balance can account for. When that happens the import backs out everything it had already written, so the loan is left exactly as it was and you can address the reason and try again. Your balance is never left holding part of a statement. If the backout itself cannot finish, the screen says how many events are on the loan and offers Undo this import to remove them.
Related: Adding Past Loan Activity · How Policy Loans & Draws Work · Tracking Policy Loans