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 Backfill loan activity, from a document rather than by hand.
On the Loans page, policy Loans tab, or a writable advisor policy workspace, choose Backfill loan activity → AI Extract → Upload a document. Upload a carrier statement or portal transaction history; Policy Stack identifies the format and opens its review. Importing requires Builder Pro for personal accounts.
Several files at once
You can choose up to 10 files for the same policy in one upload. Each is identified and read in turn. Loan accounting statements are reviewed one at a time — each one's running balance is checked on its own — with a Skip this file option and a button to move to the next statement after recording. Any portal transaction-history files in the same upload are reviewed together afterwards.
Every file has to be for the policy you opened the import from. When a file prints a different policy number, it is not included, and the review lists it with the reason. A file that prints no policy number is read, and the review notes that it could not be matched.
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.
The arithmetic check does not prove that extraction read every date or amount correctly. The review table remains available for comparison with the source document.