Reviewing Charleston Vacancy Water Charges and Owner Reimbursements
Homzora editorial team · Reviewed October 17, 2026
A utility charge during a vacancy can become confusing when the service account, paying person, and responsible period differ. A Charleston owner or manager should preserve those distinctions before assigning the charge to a property report. Start with the provider's bill and the actual service dates, then connect the payment to the instruction that explains who was expected to pay.
Charleston Water System service requests includes a temporary service process for property managers between tenants. Confirm the current terms directly for the property and period involved. The existence of that process does not prove it was used in a particular turnover. This guide concerns factual record organization and reconciliation. It does not prescribe tax treatment, security deposit handling, or the accounting rules for a particular management business.
Apply the local details to your decision
Open a vacancy service file when the outgoing tenancy ends. Include the requested stop or transfer date, any owner service confirmation, and the incoming account arrangement where applicable. Keep the original request and the provider's confirmed effective date distinct. If work continues during the gap, record which authorized activity required service. A cleaning appointment or repair invoice can help explain the timeline without determining who is legally liable for a disputed charge.
Imagine a fictional manager who pays a water bill from an authorized operating account and later seeks reimbursement from the owner. The file should retain the original bill, the payment evidence, the reimbursement request, and the owner's transfer. A reimbursement is a separate financial event from the provider payment. Combining them into a single unexplained number makes it harder to detect a duplicate or understand the period reviewed.
Check the bill's address and dates before attributing it. A first or final statement may include charges beyond the days you expected. Ask the provider about an unclear period rather than guessing from the payment date. The date money left an account is not necessarily the service date. If an adjustment later appears, link it to the original bill so the next reviewer does not treat it as an unrelated receipt.
If using Baselane accounting tools, test the import and categorization workflow with sample transactions. Baselane is a financial technology platform, not a bank. Review its current provider disclosures and any banking arrangements separately from the accounting interface. Do not assume that a suggested category is correct or that a connected feed eliminates the need to inspect the original utility document.
The final review should identify the covered vacancy period, the actual provider charge, the paying account, and any reimbursement still outstanding. Keep disputed or unexplained items in an exception list with a responsible person. Share only the details needed by the owner or bookkeeper, using an appropriate private channel. A concise, traceable record makes the next turnover easier and prevents a temporary utility arrangement from becoming a recurring mystery in the property accounts.
Build a complete working plan
Begin with the question the review must answer. You may be confirming that a payment reached the intended account, explaining an owner contribution, or checking whether a charge belongs to a particular property. State that question before opening a bank feed or report. A list of transactions is not yet an explanation. The review should connect the financial event to its supporting document and the operational reason it occurred, while leaving accounting or tax classifications to an appropriately qualified person where needed.
Give every reviewed item a stable reference. Use the property and unit identifier, transaction date, amount, payer or payee, and a document reference. A bank description can be abbreviated or unclear, so preserve the original statement alongside your notes. Do not overwrite the bank's wording with an interpretation that makes the evidence harder to trace. If a payment covers several items, create a separate allocation record showing how the total relates to each supporting document.
Separate the date an obligation arose from the date money moved. An invoice date, service period, payment initiation, and bank posting can all differ. Those differences do not automatically indicate an error, but they matter when comparing records. Keep the dates in distinct fields. A payment initiated near the end of a month may appear on a later statement. Resolve the timing before creating a second payment or marking the first one missing.
Check for duplicates before adding a manual entry. A connected feed, an imported file, and a manually entered record can refer to the same transaction. Search by amount, date range, and reference rather than relying on identical descriptions. If you find a possible duplicate, preserve the evidence and follow the system's correction process. Do not delete a record merely because it looks similar; two legitimate payments can have the same amount. Confirm the underlying event first.
Match a payment to the approved scope, not only to the invoice total. For a repair, locate the estimate, any approved change, evidence of completion, and the final bill. For an owner contribution or reimbursement, locate the instruction explaining its purpose. A bank transfer between accounts should not be mistaken for a new receipt simply because money appears in the receiving account. The correct accounting treatment depends on the circumstances, so keep the factual record clear for the person responsible for classification.
A hypothetical example helps isolate the issue. An owner sends $600 for a planned expense and later receives a $75 reimbursement after the final cost is confirmed. The reviewer should preserve the contribution, the actual expense, and the reimbursement as distinct events linked by an explanation. Combining them into one unexplained net figure can hide what happened. This example illustrates record organization only. It is not a recommendation about tax treatment, trust accounting, or how a particular business should recognize income.
Review exceptions in a separate queue. An unidentified payer, a reversed charge, a partial payment, or an unmatched invoice should remain visible until resolved. Give each exception an owner and a next action. Do not force it into a convenient category just to make a report look finished. A short list of clearly described open items is more useful than a supposedly complete report containing guesses. Carry unresolved items forward with their history so they are not investigated from scratch each month.
Use software as an aid to the review. A suggested category, imported description, or automated match still needs the level of oversight appropriate to the transaction. Test whether the system preserves attachments and correction history. If you use a financial technology platform, review the current provider disclosures and understand which institution supplies any banking services. A brand's convenient interface does not by itself establish deposit insurance, accounting accuracy, or suitability for every property related account.
Restrict access to financial records. Staff may need to confirm that a vendor was paid without seeing unrelated account activity. Use roles and exports that share only the necessary information. Avoid placing account numbers or resident payment details in a general maintenance chat. When sending records to a bookkeeper or accountant, use an agreed secure channel and include a clear explanation of unresolved items. A tidy file should improve the professional's review rather than conceal uncertainty.
Close the period with a reconciliation note. State which statements and records were reviewed, which items matched, what remains open, and who will handle the next action. Keep supporting evidence in a stable location. If an error is discovered later, document the correction and its reason instead of silently changing a prior report. This creates a dependable trail from the original transaction to the final explanation and makes the next review faster without sacrificing accuracy.
Close the reimbursement without losing the original bill
Create a direct link between the reimbursement request and the provider expense it concerns. The request should state the property, service period, amount sought, and paying account reference without exposing full account details unnecessarily. When the owner transfers funds, record the actual receipt date and match it to that request. If the amount differs, ask for the reason and preserve the explanation. Do not silently alter the original utility charge to make the two figures agree.
A fictional owner may reimburse several approved expenses in one transfer. In that case, retain an allocation showing which portion relates to water and which relates to other work. The bank description alone may not provide enough detail. The allocation should sum to the actual transfer and point to the individual documents. Any unresolved difference belongs in an exception queue with a named reviewer. This is factual reconciliation, not a recommendation about the tax or accounting category ultimately assigned by a professional.
At the end of the vacancy, check that the temporary service arrangement has reached its intended conclusion. Confirm the relevant dates and retain any final statement or adjustment. If the incoming resident's account information is involved, share only what is necessary and authorized. A bookkeeper reviewing the file should be able to understand the owner period without receiving the resident's entire private account history. The completed record should explain why the expense arose, who paid it, whether reimbursement occurred, and what remains unresolved. That clarity makes a later Charleston turnover easier because the prior example can guide the process without encouraging anyone to copy an old assumption about service dates or responsibility into a new tenancy.