This article proposes an internal monthly review workflow. It does not set a legal deposit percentage, release rule, revenue-recognition policy or reporting deadline. Those depend on the arrangement, jurisdiction and applicable accounting requirements. Insurance-funded arrangements also need their own records and should not be forced into a trust-account reconciliation merely because both are called preneed.
Which records are you reconciling?
Define the account and period before calculating anything. Identify the trustee, the statement dates and the contract population covered. A reconciliation becomes confusing when one list contains several locations or funding types while another covers only one account.
As a state-specific example, Kentucky's preneed reporting regulation enumerates beginning balance, deposits, withdrawals, earnings, market changes and ending balance in its reconciliation requirements. That source illustrates why transaction categories and contract records matter. It does not establish the required process for every other state.
Our suggested working packet contains the prior approved reconciliation, the current trustee statement, the contract register, the firm's relevant receipts/disbursements and supporting documents for changes. Keep the versions and dates clear so a reviewer can reproduce the comparison.
What belongs in the contract register?
Use a stable contract reference that can be matched across records. Keep the contracting location, funding type, relevant account reference and current administrative status. Retain the supporting agreement and authorized changes in approved storage.
Do not treat a family's payment, a trustee receipt and a serviced-contract event as interchangeable. They can relate to the same contract while occurring on different dates and requiring different evidence. A reconciliation should explain those relationships rather than compressing them into a single amount.
The register should also distinguish active records from contracts with a refund, transfer, servicing event or unresolved review. Use the firm's approved definitions and retain the history behind a status change.
This is a proposed data structure. The firm's accounting and compliance reviewers should determine the precise records and treatment required for its arrangements.
How should the monthly comparison work?
First, confirm the beginning balance agrees with the preceding approved period. Investigate a mismatch before using the current period to conceal it. Next, compare the statement's activity with the relevant contract and transaction records, using stable references where available.
Group differences by the question they create:
| Exception | Review question | Evidence to obtain |
|---|---|---|
| Receipt not matched to trustee activity | Is this timing, a missing reference or another issue? | Receipt, remittance and trustee confirmation |
| Trustee activity without a contract match | Which contract does this belong to? | Trustee detail and source agreement |
| Serviced contract still shown in the wrong population | Has the authorized change been recorded in both places? | Service record and relevant trustee documentation |
| Refund or transfer mismatch | Are the amount, date and destination correctly represented? | Approved documents and transaction evidence |
| Earnings/fees/valuation difference | Is the statement being compared on a consistent basis? | Statement detail and accountant's treatment |
| Prior-period unresolved item | What remains open, and who owns it? | Prior exception and current follow-up |
The table describes investigation questions, not permission to move funds. A reconciliation exception should lead to review through the firm's approved controls.
Why does the cutoff date matter?
Two accurate records can disagree temporarily because they describe different stages or dates. A payment recorded by the firm near period-end may appear on a later trustee statement. That possibility needs evidence; it should not become a catch-all explanation for an unexplained difference.
Record the dates involved and the document supporting the timing explanation. Carry a documented timing item into the next review and verify whether it cleared as expected. An item that remains open requires another action, not indefinite copying into later months.
Keep corrections to prior periods identifiable. If a transaction was misclassified, record the approved correction and its effect rather than silently editing the old reconciliation until the numbers appear to match.
A worked example with fictional amounts
Suppose a simplified statement begins at $100,000. It shows $5,000 of additions, $2,000 of withdrawals and a net $300 increase from the statement's other activity. Its ending balance is $103,300: $100,000 + $5,000 − $2,000 + $300.
The arithmetic agrees, but the firm's register shows $5,500 associated with new receipts for the period. The $500 difference is an exception to investigate. Staff should identify the relevant receipt, contract and remittance evidence rather than inserting a balancing amount.
If the reviewer establishes that the $500 appears on the next statement, record the supporting dates and the subsequent clearance. If the evidence does not establish that explanation, leave the item unresolved with an owner. The example is illustrative and does not prescribe how a real transaction should be booked or trusted.
This is why a correct statement roll-forward is necessary but insufficient. It checks the statement's movement, while contract matching checks the relationship between that statement and the firm's records.
What should an exception log contain?
Use one row per distinct issue with a stable exception ID. Include the period, account reference, contract reference where known, amount or affected record, issue category, supporting evidence, owner and next action.
Record the resolution and approving reviewer when it is completed. Do not delete the original exception merely because it was resolved. A later reviewer needs to understand what happened and whether the same issue has recurred.
For sensitive financial and contract information, use the firm's approved access and storage arrangements. A blank worksheet can be shared for training; completed registers belong in the controlled record system, not a public marketing analytics tool.
How does QuickBooks fit?
QuickBooks can be part of the firm's accounting process, but an accounting entry alone does not establish the complete contract or trustee history. Define which system holds the contract, which records the relevant financial activity and how the reviewer matches them.
Ask the bookkeeper to demonstrate a new contract, a later payment and a serviced or refunded arrangement using the approved accounting treatment. Do not assume a generic invoice/payment sync performs the entire preneed compliance process.
The FuneralHQ QuickBooks guide covers the wider connection. The separate preneed-to-at-need guide addresses the case handoff. Reconciliation needs to check the records affected by that handoff rather than merely copying the contract's face amount into a new case.
What should the reviewer approve?
The review should identify the population and period, confirm the comparisons performed, list unresolved exceptions and record the next actions. Where an item remains open, approval should not be worded as though every difference has been resolved.
Choose a review cadence that supports the firm's obligations and workload. The monthly cadence proposed here is an internal management recommendation; required submissions may follow different schedules and formats.
FuneralHQ offers preneed management, accounting and case workflows. Bring a redacted reconciliation example to the demonstration with your qualified reviewer. Confirm what the software records, which comparisons staff perform and what remains with the trustee or adviser. A useful demonstration makes those responsibilities clear before the system becomes part of the monthly close.
Blank working template
Open the accompanying blank CSV worksheet. This editorial template contains headings only. Adapt it to the firm’s reviewed process before use and keep completed records in approved storage.
The FuneralHQ advantage
The family balance and the books should agree
FuneralHQ keeps card and ACH activity, payment plans, case balances, and QuickBooks Online connected so staff can answer the family and accounting can reconcile the same record.
We will work through a real example with you, from the first details to the finished record.
See it on one of your casesAbout the FuneralHQ Editorial Team
This guide was written by the FuneralHQ Editorial Team, the in-house team behind funeral home software used by independent firms to run cases, documents, payments, and QuickBooks sync in one record. Our editorial standards explain how we review product claims, outside sources, automation, updates, and corrections.