Salt Lake City Rental Bookkeeping: Review Bank Feeds Without Duplicating Payments

Homzora editorial team · Reviewed October 17, 2026

A connected bank feed can reduce data entry, but it does not explain every transaction automatically. A rental payment may already exist in a ledger before the related deposit appears in the feed. A transfer may appear as money leaving one account and entering another. Without a clear review process, importing more data can create duplicate or misleading records instead of better information.

This guide provides an administrative review method for a Salt Lake City rental owner. It does not prescribe accounting treatment or tax categories. Work with a qualified accountant on those decisions and use the software's documented process for matching, correcting, and reconciling transactions.

Identify the records that already exist

Before reviewing a feed, list the systems that record rental activity. You may have a tenant ledger, a payment processor, a bank connection, and manual entries. Identify which events each system records and how they connect.

Do not assume that the bank feed should create a new entry for every line without checking the existing workflow. A payment recorded through an integrated collection tool may already have a related record. Ask the vendor how its matching process works.

Keep a simple diagram or written explanation of the flow for authorized users. The purpose is to know where an event begins, where money is processed, and where the final account activity is reviewed.

Choose a review period and preserve the source

Identify the period being reviewed and obtain the relevant statements or exports. Record whether the feed is complete through the end of the period. A delayed connection should not be mistaken for proof that no transaction occurred.

Keep source records accessible while making corrections. Do not rely on a screen that may change after refreshing or reconnecting an account. Use the appropriate export or statement provided by the institution or platform.

Record the date of the review separately from the transaction dates. Later information may explain an earlier difference, and a clear chronology helps another reviewer understand why a correction was made.

Distinguish matching from adding

Ask the software provider to demonstrate the difference between matching a feed item to an existing record and adding a new record. Use fictional data if you are learning the process. Do not experiment on live records without understanding how to reverse an error appropriately.

Compare amount, date, reference, and context. Two transactions for the same amount may be separate events. Conversely, a difference in posting date may not mean the feed item is unrelated to the earlier payment record.

When uncertain, keep the item under review and gather more evidence. A visible unresolved transaction is preferable to a confident match that links money to the wrong tenant or property.

Review grouped deposits carefully

A bank deposit may represent more than one underlying payment or may reflect processing adjustments. Obtain the relevant processor detail and ask your accountant or software support how the arrangement should be represented.

Do not allocate the full deposit to a single tenant merely because its amount resembles that tenant's expected payment. Trace the components using the appropriate records. Keep the processor reference connected to the reviewed entry.

If a difference relates to a fee or another adjustment, document it explicitly rather than changing a tenant payment amount to make the bank total fit. The records should describe the actual events, not only produce equal totals.

Keep transfers from masquerading as new receipts

Identify movements between accounts and confirm their purpose. A transfer can appear as an inflow in one place without being a new payment from a tenant. Ask your accountant how to handle it in the chosen system.

Use the supported transfer workflow where appropriate rather than creating unrelated income and expense entries without guidance. Keep both sides connected so that a later reviewer can follow the movement.

This guide does not determine the treatment of owner contributions, distributions, deposits, or other funds. Those distinctions should be reviewed with the professional who understands your ownership structure and accounting setup.

Check property and entity assignments

Review the destination property or entity before accepting an automatic categorization. A familiar vendor name does not guarantee that every transaction belongs to the same building. Recurring rules can repeat an incorrect assumption efficiently.

For a document covering several properties, obtain guidance about allocation and preserve the basis used. Do not invent a split simply because the software allows percentages. The supporting record should explain why the allocation was made.

Keep mixed or unclear transactions on a question list. Provide the accountant with the source document and relevant facts rather than asking for a category without context.

Use a small exception register

Create a list for transactions that cannot yet be resolved. Include the date, amount, account, reason for uncertainty, person responsible, and next action. Avoid leaving unexplained notes scattered across several systems.

Examples might include an unknown deposit, a missing invoice, or a possible duplicate. Keep the description factual. Do not label an event as an error or misconduct before the evidence supports that conclusion.

Review the register regularly and close entries only when the supporting explanation is recorded. If the resolution changes a financial record, note how it was corrected through the approved process.

Evaluate bookkeeping tools against this workflow

Affiliate disclosure: Homzora may earn a commission if you sign up through these links. You can review Baselane or explore Rentec Direct when comparing rental bookkeeping tools. Check the current plan, terms, and available functions before selecting a product.

Baselane's bookkeeping page describes transaction organization and reporting. Its disclosure identifies it as a financial technology company, not an FDIC insured bank. Any banking service should be reviewed under the actual provider's terms; this guide makes no deposit insurance or yield promise.

Rentec Direct's accounting documentation is a starting point for assessing its tools. Ask the vendor to demonstrate the specific matching and review process you need instead of assuming a broad feature description answers every operational question.

Reconcile using an appropriate process

Follow the reconciliation method suitable for your accounting setup and software, with professional guidance where needed. Investigate differences rather than entering an unexplained adjustment to force agreement.

Document timing items and verify them against later evidence when appropriate. A transaction that has not appeared in one system may need follow up, but it should not be explained away indefinitely without checking.

Keep the reconciliation record and outstanding questions with the period's reports. Another authorized person should be able to understand what was checked and what remains unresolved.

Review reports after the underlying entries

Once records are reviewed, inspect the reports used for your operation. Trace a sample of totals back to their supporting entries. A report can look polished while reflecting a duplicate or incorrect property assignment.

Ask your accountant which report answers the question you have. Cash available, accounting income, and a tax result are not automatically the same measure. Avoid drawing conclusions from a number whose meaning is unclear.

Use the payment exception guide when a difference begins in the tenant payment record rather than the bank feed. Keep the investigation connected across systems without changing unrelated entries.

Improve rules only after understanding the exception

If a recurring classification is wrong, identify why before changing the rule. A vendor may work at several properties, or a description may be too broad. Test the revised rule on an appropriate sample and review the affected records.

Do not let a rule change silently rewrite historical information without understanding the consequences. Use the provider's documented controls and obtain help when the scope is unclear. Preserve the explanation for material corrections.

Train authorized users on the distinction between review, matching, and adding. A short example from your fictional test scenario can be more useful than a long list of interface instructions without context.

Finish with a record of what is known

At the end of the review, record the period, completed checks, unresolved items, and responsible follow up. Save the relevant reports and source references. A monthly review is useful when it leaves the next reviewer with fewer assumptions to reconstruct.

For a broader product evaluation, use the software workflow demonstration guide. It connects bookkeeping with the leasing and operational records that produce the transactions.

The goal is not to accept every feed item as quickly as possible. It is to maintain a clear explanation of the money movement without counting the same event twice or losing the evidence behind it.

Check the first import after a connection changes

When a bank connection is restored or replaced, review the date range of the first new import before approving matches in bulk. An overlapping period can contain transactions already represented in the books. A missing period can leave an apparent gap. Compare a small sample against the bank statement and existing entries, then document the boundaries you checked.

For example, if a manually entered vendor payment later appears in the imported feed, locate the existing payment record before deciding what action to take. Follow the provider's documented matching process rather than deleting either record simply because the amounts agree. Two different payments can share an amount. The payee, date, account, reference, and supporting invoice help establish whether the records describe the same event.