Auto Log records recurring events into your banking ledger so your record can stay in step with activity outside Policy Stack. Premium recording comes directly from the policy's saved premium schedule. Loan repayment Auto Logs come from repayment scheduling surfaces. Income from an asset with an expected cash flow — a rental, a syndication, an equipment lease — is recorded the same way, from the asset's own cash-flow schedule.
Recorded Is Not Confirmed
Auto Log records what your schedule says should have happened. It never sees the money arrive. A row it wrote is an expectation until you confirm or correct it. In the banking ledger, asset income and scheduled premiums carry an Auto tag so you can tell them apart from entries you recorded yourself, and rows inferred from a carrier statement you uploaded carry the same tag for the same reason. Scheduled loan repayments are the exception: they say "· Auto-logged" at the end of their description but take no tag yet.
Correct a figure on the record's own page — the asset for cash flow, the policy for a premium — so the underlying record and your banking history stay in step. Policy Stack asks you to confirm scheduled premiums, note payments, and loan repayments. When asset-income confirmation is enabled, it also asks you to confirm asset income, and older unconfirmed rows remain available from the Assets page even when they did not create a notification.
What Auto Log Does
When a saved event becomes due, Policy Stack can create a pending ledger record and prompt you to confirm it. For premiums, you do not enter a second amount, cadence, or start date: the policy's premium schedule already contains those facts. A loan repayment uses its own repayment schedule.
Auto Log records what already happens on your schedule. It does not move money, change your autopay, submit a repayment, or contact your carrier — it keeps your Policy Stack records in sync with payments that happen outside the app.