Billing Software for Adult Family Homes: What to Evaluate

Billing software for Adult Family Homes should connect the correct resident, facility, payer, agreement, charge period, payment, adjustment, and supporting record. It should not mix resident billing with the software vendor's own subscription page or pretend to replace accounting, tax, Medicaid, or legal review.

A clear billing module helps providers prepare invoices, track balances, record payments, reconcile activity, manage approved recurring charges, and produce readable statements. The complete workflow also needs access controls, audit history, correction handling, exports, and a safe process for admission, absence, rate change, transfer, and discharge.

This guide explains the features and tests to use when evaluating AFH billing software in the United States.

Separate three financial contexts

An AFH platform may contain several kinds of billing that must remain visibly separate.

Resident and payer billing

This covers charges for room, care, services, supplies, and other items authorized by the facility's agreements and applicable requirements. It can involve the resident, representative, private payer, or another approved party.

Facility accounting and expenses

This covers the provider's income, expenses, vendors, bank reconciliation, payroll, taxes, and financial statements. Resident invoices may feed accounting, but the ledgers and permissions serve a different purpose.

Platform subscription billing

This is what the facility pays the software company. The price should come from current platform billing configuration and remain synchronized with any public pricing notice. It does not belong on a resident invoice.

Use distinct navigation, terminology, permissions, reports, and exports so users never post a resident payment against a software subscription.

Build billing from the resident agreement

Recurring charges should originate from a reviewed billing setup tied to the resident and facility. Useful fields include:

• Resident and active facility
• Billing contact and payer relationship
• Agreement or authorization reference
• Effective period
• Base rate and billing frequency
• Included services
• Approved additional charge categories
• Deposit or credit information where applicable
• Proration rule
• Payment terms
• Statement delivery preference
• Notes and attachments

The software should not invent charges from care documentation. A Daily Note, task, or appointment may support an approved billable item, but a configured agreement and authorized review should control invoicing.

When the rate changes, create a new effective version. Do not overwrite the amount used for prior invoices.

The resident-management software guide explains how admission, absence, transfer, discharge, contacts, agreements, and resident status connect to operational modules.

Treat payer identity as structured data

Do not use a free-text “Bill to” line as the only payer record. Track payer name, relationship, address, email, phone, authorized delivery channel, effective dates, and related documentation.

A resident may have multiple financial contacts, but only approved people should receive statements or discuss the account. A family relationship alone does not create billing authority.

When the payer changes, preserve the former relationship and effective period. Future invoices use the new setup; historic invoices continue to show the payer and address used at issue time.

If one payer covers several residents, permissions and statements must still retain resident and facility boundaries. Do not expose another resident's balance through a payer search or combined email unless the exact consolidated arrangement is authorized.

Use an explicit invoice lifecycle

A practical status model includes:

• Draft
• Under review
• Approved
• Issued
• Partially paid
• Paid
• Past due
• Disputed
• Voided
• Written off

Draft and approval can be combined for a small provider, but the audit trail should still identify who created and issued the invoice.

Issued invoices should not be silently edited. Correct through a void, credit, debit adjustment, or replacement process that preserves the original amount, reason, user, and time.

Past due should be calculated from the due date and remaining balance. A notification should clear when the account is paid, adjusted, voided, or placed into an approved exception state.

Make line items understandable

Each invoice line should show:

• Service period or date
• Charge category
• Plain-language description
• Quantity and unit where used
• Rate
• Amount
• Adjustment or tax treatment when applicable
• Supporting reference

Avoid internal codes without descriptions. Group recurring room or care charges separately from one-time items, credits, refunds, and prior balances.

If a line comes from another workflow, link to the approved source without exposing unrelated resident information. The invoice remains a financial record; it should not contain detailed clinical notes.

Support zero-dollar informational lines only when they improve understanding. Do not crowd statements with every included service performed during the month.

Handle recurring charges safely

Recurring billing should create a distinct charge occurrence for each period. The generator needs an idempotency key so a retry cannot produce duplicate monthly charges.

Test:

• Mid-period admission
• Temporary absence
• Hospital leave
• Rate change during the month
• Transfer between facilities
• Discharge
• Month length and leap year
• Credit carried forward
• Delayed agreement entry

Do not hard-code one proration method. Display the configured rule and calculation, and require review when the source dates are incomplete or conflicting.

Stopping a recurring schedule should not delete prior charges. Future status, end date, user, and reason belong in history.

Distinguish private billing from program claims

Private-pay invoices, Medicaid-related records, long-term-care insurance documents, and other third-party payment workflows can have different fields and submission processes.

The software should state what it supports. Creating a resident invoice does not necessarily submit a government claim, satisfy a payer's authorization process, or verify coverage.

Use separate statuses for internal invoice issuance and external claim or reimbursement activity. “Submitted,” “accepted,” “denied,” and “paid” need an identified receiving organization and reference.

Avoid embedding changing reimbursement rates as permanent code. Use effective-dated configuration with source, approval, and history.

Record payments with traceable allocation

A payment record can include:

• Facility
• Resident account
• Payer
• Receipt date
• Payment method
• Amount
• Reference number
• Deposit batch
• Applied invoices and line amounts
• Unapplied balance
• Recorder and timestamp

Payment method details should be minimized. Do not store complete card or bank credentials in the application unless a compliant payment provider and appropriate architecture handle them.

Allow one payment to cover multiple authorized invoices while preserving exact allocation. Partial payments and overpayments should remain visible.

Reversing a payment creates a reversal event and restores the affected balances. It should not delete the original receipt.

Manage credits, refunds, disputes, and write-offs

These actions require distinct records because they have different financial meaning.

• Credit reduces an account or invoice balance
• Refund returns funds
• Dispute identifies a questioned charge
• Write-off changes collection treatment according to policy
• Void cancels an invoice or payment record through a controlled process

Require reason, amount, authorizing role, date, and related invoice. Large or unusual adjustments may need a second approval.

A dispute can pause reminders while preserving the due balance and communication history. Resolution should record the agreed outcome rather than simply dismiss the alert.

Keep resident funds separate

If the facility manages resident funds, do not combine them with the home's ordinary revenue or expense account. Use a separate workflow with the controls, records, statements, and permissions required by applicable policy and law.

WAC 388-76-10215 addresses protection, liquidation, or transfer of resident funds in specified circumstances. Providers should review the current Washington requirements and professional guidance for their exact practices.

The billing dashboard should clearly label resident-funds activity and prevent it from being treated as an ordinary payment to the business.

Reconcile the billing ledger

Reconciliation compares invoices, payments, deposits, adjustments, refunds, and external accounting or bank records.

Useful queues include:

• Unapplied payments
• Deposit difference
• Duplicate reference
• Reversed payment
• Invoice without billing setup
• Unexpected negative balance
• Export not accepted by accounting system
• Period not closed

Closing a billing period can restrict ordinary edits while allowing authorized adjustments in the next period. Reopening requires a reason and audit event.

Do not use a green “balanced” indicator without showing the included accounts, period, and difference calculation.

Integrate with accounting deliberately

An accounting export or integration should map facility, resident account, payer, income category, payment, refund, adjustment, and date consistently.

Define which system owns:

• Invoice number
• Customer record
• Chart-of-accounts mapping
• Payment status
• Tax treatment
• Closed periods
• Correction and deletion

Avoid two-way synchronization that silently overwrites records. Use explicit conflict handling and stable external identifiers.

The IRS explains in Publication 583 that businesses may choose a recordkeeping system suited to the business that clearly shows income and expenses, and discusses supporting records. Providers should work with qualified accounting and tax professionals to configure their actual books.

Produce professional invoices and statements

PDF and print should use a clean monochrome layout with:

• Facility legal and contact information
• Invoice number and issue date
• Resident and approved payer
• Service period
• Line items and adjustments
• Prior balance, payments, amount due, and due date
• Payment instructions
• Page numbers
• Contact for questions

Do not print the billing webpage, navigation, admin sidebar, or dashboard cards.

A statement can cover several invoices for one authorized account and period. Label opening balance, new charges, payments, credits, refunds, and closing balance.

Email should notify the recipient that a secure statement is available rather than attaching sensitive documents by default.

Provide useful billing reports

Essential reports include:

• Invoice register
• Accounts receivable aging
• Payments and deposit batches
• Adjustments, credits, and refunds
• Unapplied payments
• Charges by category
• Resident account statement
• Payer balances
• Voids and write-offs
• Billing audit history

Filters should include facility, resident, payer, invoice status, charge category, issue date, service period, payment date, and aging date.

State whether a report uses invoice date, service period, due date, or payment date. The AFH reporting-software guide explains consistent filters, PDF, print, export, permissions, and generation history.

Protect financial and resident information

Separate permissions for billing setup, invoice creation, approval, payment entry, refund, write-off, reports, export, and platform subscription administration.

Audit account changes, issued invoices, corrections, payments, allocations, reversals, downloads, and exports. Avoid placing balances or resident names in notification subject lines.

Use encryption, session controls, backups, recovery testing, vendor-access logging, and secure file delivery. If payment processing is integrated, understand which provider stores card or bank data and what compliance responsibilities apply.

Support staff should not see resident billing merely because they can manage the software subscription.

Test the complete billing cycle

Use demonstration accounts and ask the vendor to:

1. Create an effective-dated resident billing setup.
2. Generate a monthly invoice twice and prove no duplicate appears.
3. Prorate an admission and a discharge.
4. Change the rate mid-period without rewriting prior invoices.
5. Issue an invoice and correct it through an adjustment.
6. Record partial, full, and overpayment.
7. Reverse a payment and inspect allocation history.
8. Create a dispute, credit, refund, and write-off.
9. Switch facilities and test payer search and direct URLs.
10. Export the period to accounting and simulate a conflict.
11. Generate an invoice, statement, aging report, and audit report.
12. Revoke a billing user's access and retry a saved download.

Reconcile every report total to the source invoices, payments, and adjustments.

Frequently asked questions

Is AFH billing software the same as accounting software?

No. Resident billing can create invoices, statements, balances, and payment records. Accounting covers the broader books, financial statements, tax records, expenses, payroll, and reconciliation.

Should recurring invoices be editable after issue?

Issued invoices should be corrected through a controlled void or adjustment process that preserves the original record and history.

Can billing rates be hard-coded?

Use effective-dated configuration with approval, source, and history. Rates and agreements can change, and prior invoices must retain the amount used at the time.

Can family members view resident statements?

Only when the resident's authority, agreement, and facility permissions allow it. A family relationship alone should not grant billing access.

Does generating an invoice submit a Medicaid claim?

Not necessarily. The software should clearly identify which external claim or reimbursement functions it actually supports and preserve separate submission statuses.

Make every balance explainable

Strong AFH billing software connects the resident, payer, agreement, charge, invoice, payment, adjustment, and report without mixing unrelated financial contexts. Every balance should reconcile to traceable activity.

AFH Manager can connect facility-scoped resident billing with admissions, agreements, recurring charges, invoices, statements, payments, adjustments, permissions, audit history, formatted reports, and accounting exports. Providers can test the full billing cycle with demonstration accounts before entering live financial information.