The practical difficulty is often identification. The facility that transferred a person into care may not be the organization responsible for the invoice. A monthly statement may cover many cases, and a single case may include more than one service. A total balance alone cannot explain those relationships.
Why separate “received from” and “bill to”?
They answer different questions. The first describes an operational handoff. The second identifies the organization responsible under the billing arrangement. Treating them as the same field can put a correct service on the wrong partner's statement.
Halcyon's trade-customer documentation explicitly describes this distinction and explains that the two facilities can differ. That is first-party documentation of Halcyon's product and a useful illustration of the workflow. It is not evidence that another vendor offers the same consolidated-invoice feature.
In your own process, record the partner account reference and the operational facility reference separately. If a correction is needed, preserve the original record and the approved change so the office can explain why the billing destination changed.
What identifiers should appear on an invoice line?
Choose references both parties can recognize. A crematory's internal case number may not be enough for a funeral home using a different numbering system. Record the partner's reference where supplied and the crematory's reference on the working match register.
Agree on the minimum identifying detail required for routine billing communications. Avoid copying unnecessary private case information into an email merely because it is available in the operational record.
Our suggested matching fields are:
| Record | Purpose |
|---|---|
| Partner account and bill-to reference | Identify the responsible organization |
| Partner case reference | Let the partner locate its own record |
| Crematory case/service reference | Let the crematory locate the supporting work |
| Service date and description | Identify what is being charged |
| Agreed rate/source | Explain the amount without relying on memory |
| Adjustment reference | Trace an approved correction or extra charge |
| Invoice and line reference | Detect duplicates and support questions |
| Match status and owner | Turn a discrepancy into an assigned action |
This is a proposed reconciliation schema. Your accounting reviewer should adapt it to the firm's billing and retention requirements.
Which event makes a line ready to bill?
Define the trigger under the firm's agreements and accounting process. Do not assume that receiving a case, scheduling work and completing a service are the same event. The supporting record should show why the line is included in this billing period.
For a grouped statement, retain line-level references. A combined invoice is easier to process only if the receiving partner can still identify the individual services. A single unexplained monthly amount creates avoidable follow-up.
Keep financial readiness separate from operational authorization. A billing rule should not decide whether a cremation may proceed. The CANA process explanation describes identification and operational checkpoints; those records have a different purpose from an invoice.
How should the partner review a statement?
Start by matching the partner account and period. Then compare the statement's lines against the partner's case and service records. Mark matched lines, missing references, rate questions, duplicate candidates and services not found in the expected population.
Investigate before deleting a line that appears twice. Two similar descriptions can represent distinct approved services, while a genuine duplicate may have different invoice numbers. The supporting service reference and agreement determine the answer.
Use one discrepancy register for the statement review. Separate an unanswered question from an agreed credit. The partner should know whether to provide a case reference, confirm a rate or wait for the crematory's correction.
Do not state that the whole account is reconciled while material lines remain unexplained. Record the reviewed amount and unresolved items explicitly through the accounting process.
What should a discrepancy log look like?
Suggested columns are invoice, line reference, partner case reference, crematory reference, issue, amount questioned, evidence requested, responsible contact, next action and resolution reference.
Use a short set of issue types, such as missing case match, different service description, rate mismatch, duplicate candidate, credit not reflected and payment allocation question. These labels route the work; they should not automatically issue a financial correction.
Retain the communication that establishes an adjustment. A note saying “per call” is harder to review later than a dated reference identifying who agreed to what. Corrections should follow the firm's approved invoice or credit process rather than silently rewriting a previously issued statement.
A worked example with fictional charges
Suppose a monthly statement contains three lines: a $250 service for case T-101, a $250 service for T-102 and another $250 line described only as “cremation.” The total is $750, but the third line lacks the reference the partner needs to review it.
The reviewer marks the first two as matched and the third as missing a case reference. The crematory checks the supporting service record and supplies the correct reference, or identifies that it is a duplicate and processes the appropriate correction.
The reviewer does not assume the third charge is invalid simply because its description is weak. Nor does the reviewer mark it matched because the total looks plausible. The task is to connect the charge with evidence.
If a separate approved $40 service belongs to T-102, the invoice should make that relationship clear. The figures are illustrative, not market prices or accounting instructions.
How do payment and reconciliation connect?
Record which invoice or account activity a payment applies to according to the firm's process. A payment can be posted correctly while an individual charge remains under review. Conversely, a statement can be fully matched while payment is still outstanding.
Check for credits and adjustments before deciding that a remaining balance is unexplained. Keep the transaction references so the partner and crematory can compare the same activity.
The FuneralHQ reconciliation guide addresses payment matching more broadly. Trade statements add partner and service identity to that task; they should not be treated as ordinary family invoices with only a different contact name.
What should you ask a software vendor to demonstrate?
Bring two partner accounts, a case received from a different facility, an ordinary service and one disputed line. Ask the vendor to show the operational record, bill-to relationship, invoice and correction history. If grouped invoicing matters, confirm the exact feature rather than inferring it from a generic “trade services” label.
Review the accounting handoff with the bookkeeper. Confirm which records sync, how credits or refunds are handled and how the team detects a failed or repeated posting. A demonstration should include an exception, not only a clean invoice.
FuneralHQ supports crematory and trade-service workflows alongside cases, custody records, documents and accounting. Ask the team to demonstrate your partner-billing scenario and confirm any specialist invoicing scope in the proposal. The result you need is a statement another office can reconcile without reconstructing every case by telephone.
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.