Landlords Accounting & Reports
Find missing bank-feed transactions and review possible duplicates
Check the account, filters and import result, then compare suspected duplicates with your bank statement.
On this page
Before you start
- Sign in to the correct landlord portfolio with accounting access. Follow any access or plan message shown on the page; demo and simulation accounts cannot save a duplicate-review decision.
- Have the bank statement or bank transaction history ready, including the account's last four digits, transaction date, amount and description.
- Use this guide for the accounting import feed. A linked feed reads bank transactions; it is separate from a renter's payment method and does not confirm that rent was paid or deposited.
Check the account and filters
Action: Open Accounting, then Transactions and Import feed. Choose All accounts, set Status to Everything, and clear the description, amount and date filters. Select Apply. Look for the statement entry, then narrow the account or description if needed.
The initial Status: Unbooked view hides booked, reconciled, transferred and ignored rows. An empty filtered list does not establish that a transaction was never imported. After changing the account, select Status: Everything again and Apply; switching accounts resets the status filter to Unbooked.
Check whether the account is linked or manual
Action: Open Accounts in the accounting navigation. Match the account name, bank and last four digits. Check Linked Accounts, Manual Accounts, and the archived, unlinked, or merged accounts section. Use View all to inspect an account, or View surviving account when a previous account was merged.
Manual accounts require a CSV or manual entry. Restore makes a retained account active again; it does not renew bank authorization. If authorization is needed, use Add account, then Link a bank when offered, and follow the connection prompts. If linking is unavailable or fails, keep the displayed message for support.
Refresh a linked feed and inspect the result
Action: Return to Import feed, open More beside Add transaction, and choose Refresh linked banks. Wait for the result, read the message, and search for the expected entry again with Status set to Everything.
An imported-row count is not proof that every linked account refreshed successfully. If the expected transaction is still missing or a connection message persists, contact support with the masked account details and the exact message instead of repeatedly unlinking or reconnecting the account.
Review the result of a manual CSV import
Action: For a manual account, open More, then Import a CSV. Use the bank's CSV with a date, description, and amount, or debit and credit columns. Choose the intended Account name and Import. Read the counts for imported rows, skipped duplicates, possible overlaps, rows before the bookkeeping start date, and unreadable rows.
Use the same account name for later imports into that manual account. Check the original file and import message before trying again; do not rename the account or alter transaction details just to get skipped rows accepted.
Compare a suspected duplicate before deciding
Action: When a row offers Compare imports, open it and compare This imported row with Possible matches already in the feed and your bank statement. Review the dates, amounts, descriptions, import identities and original accounts. Under Reviewed decision, choose Keep this row as a distinct bank event only for a separate real event, or Exclude this row; retain the existing event when it represents the same event. Select Save reviewed decision only when the comparison supports your choice.
Matching dates, amounts and descriptions suggest an overlap; they do not prove a duplicate. Close the comparison if you cannot tell. This comparison does not delete imports, reverse existing bookkeeping or fix two actual charges at the bank.
Check the saved decision or request help
Action: Read the saved result and choose Refresh account view. A row kept as distinct remains unbooked for normal review. An excluded row remains in history as ignored and offers Review exclusion. If a save times out or the result is unconfirmed, use Reload comparison to check its current state before choosing again.
If an expected entry still cannot be found, or the comparison says the row has protected history, contact support with the bank name, last four digits, transaction date, amount, description and exact message. Share a redacted screenshot if useful; do not send bank passwords or sign-in codes.
Check the result
- The account and status filters show whether an existing import was hidden from the initial Unbooked view.
- The import result identifies rows added or skipped, or gives you a specific unresolved issue to share with support.
- A confirmed duplicate-review decision leaves a distinct row unbooked or retains an excluded row as ignored; existing bookkeeping is not reversed by that decision.
Troubleshooting & questions
Does Imported 0 new transactions mean my bank feed is up to date?
No. It can mean there were no new rows to add, but the count alone does not confirm every account's connection or refresh result. Check the correct account and Everything status against your bank history. If an expected entry is still absent, retain the displayed message and contact support. The feed shows a limited set of recent imported rows, so an older entry may also remain outside the current view even after filtering.
Why were some rows in my CSV not imported?
Read the import result. Previously imported rows can be skipped, rows before your bookkeeping start date are left out, and unreadable rows are counted separately. The file must be no larger than 5 MB and include a readable date, description, and amount or debit and credit columns. Check Settings, then Accounting, to review the Bookkeeping start date. Changing that date does not by itself import earlier rows. Keep the original CSV and review the cause before importing again.
Can I exclude every pair with the same amount and date?
No. Two legitimate bank events can share the same details. Compare the statement and original imports first. Exclude is an explicit decision about the selected imported row; it retains that row as ignored and leaves the existing event and bookkeeping in place. If two account cards appear to represent the same bank account, Accounts offers Review duplicate account for a separate review; similar names or balances alone are not enough to merge them.
Why is Save reviewed decision unavailable, or why must I reload the comparison?
Wait for the comparison to load and choose a decision. Demo and simulation comparisons are read only. Imports with existing bookkeeping, protected reconciliation history, or other restrictions cannot be changed through this comparison. A changed comparison or an uncertain save result also requires Reload comparison before another decision. If it remains unavailable, keep the displayed reason and contact support rather than trying another way to ignore or book the row.
Why can I see an import but not an expense or a rent payment?
An unbooked import has not yet become a booked accounting entry. Check its status and category, and review any existing match before booking. Your saved transaction rules may already have booked it, so check Everything or Booked before adding another entry. For a rent charge or payment attempt, use Payments and the payment-activity guide; the accounting feed is not a renter payment method or a confirmation of settlement.