CRM configuration guide
This reference web app mirrors the full refund workflow. The steps below reproduce each piece in the Closepoint USA LLC sub-account. Verify the sub-account name before making changes. Production outreach stays disabled until you approve the pilot; you handle payment release in Deluxe.
1Create the custom objects
Create three custom objects in the sub-account:
- Municipal Tax Refund — one record per original check. Unique import key:
Check Number.Title= closing file number (the contact reference number). Fields: original check date, municipality, original amount (separate from approved refund amount), source comment, source row, status, approved refund amount, approver 1, approver 2, Deluxe check number, export batch id, hold reason, flag, internal notes, recipient-facing message. - Refund Claim Submission — one per claimant per check. Fields: claimant contact id, role, locked name, mailing address 1/2, city, state, zip, email, cell phone, paid-directly flag, payer description, documents, comments, staged changes, status.
- Closing File Notice Log — one per closing file. Fields: title, covered check ids, sent-at, recipients, message id, attempts, next resend date. Prevents duplicate notices.
2Import the 196 checks & reconcile
Import the Municipal Tax Payments tab. Use Check Number as the unique key and Title as the closing file number. Six closing files have two checks — preserve both. Store original check date, municipality, amount, source comment, and source row. Keep the original amount separate from the approved refund amount.
Start each case at Needs contact verification. Match buyer and seller to each closing file using verified closing records keyed by file number (the contact reference number). Link each party by contact ID + role. Flag uncertain matches for staff review.
3Send one BCC notice per closing file
- To: claira.sm@closepointusa.com · BCC: verified buyer + seller · CC: empty · Reply-to: claira.sm@closepointusa.com
- Log the send against the closing file and all covered checks so a second check does not trigger a duplicate notice.
- Hold cases with missing, shared, or suspect emails for staff review.
- If no reply in 3 days, resend and check GHL contact records using the file number. Also send a text from Closepoint USA LLC to the buyer and seller of record.
- Test actual delivery and inspect headers in the two BCC test inboxes: claira.sm@closepointusa.com, marketing@closepointusa.com. The CRM's standard test email alone does not verify BCC delivery.
- Use a shared portal entry link requiring each party to sign in independently. Keep personal details, claim documents, and payment amounts out of the shared message.
4Build the claimant portal
After sign-in, show each party only the case info they are authorized to see and their own submissions. Verify access on the server — a shared email link or a file number alone must never grant access.
- Display first and last name from the verified closing record as read-only. Require the claimant to affirm the name or flag it for staff review. A comment never auto-changes the payee.
- Require mailing address, email, and cell phone (required even if none on file). Address line 2 optional.
- Require an upload to submit (PDFs + common images). Ask whether the claimant paid directly or through a current/former mortgage servicer. Ask for documentation identifying the actual payer and connecting the payment to the property and tax period. Include a comments box.
- Save each submission and its documents to the correct case and claimant. Keep uploads private to authorized staff and the submitting claimant. Preserve buyer and seller submissions separately.
- Stage contact changes for review. Staff apply verified address/email/cell to the existing GHL contact by contact ID, with a record of changes. Verify a newly supplied email before using it for a Deluxe payment.
5Staff review & dual approval
Statuses: Needs contact verification, Awaiting response, Under review, On hold, Approved, Exported, Issued. Alert staff when proof arrives.
- Before approval: match proof to property, tax period, payer, and amount; review the closing ledger for entitlement; reconcile the outstanding municipal check with accounting.
- Route competing claims, split payments, name changes, mixed fees, and unclear funding to staff.
- Dual approval: approver 1 confirms payee + verified delivery email; approver 2 (different person) confirms payee + email + amount. Approvers: Lisa Ely (lisa@closepointusa.com) and Christopher Brown (claira.sm@closepointusa.com).
- Keep claimant comments, internal review notes, and the recipient-facing payment message in separate fields.
6Generate the Deluxe batch CSV
Export only approved, unexported payments. Write the exact 16 headers in order (preserve the trailing space in Invoice ):
Check Number,payee,Payee email,Attention,Company,Address 1,Address 2,City,State,Zip,delivery method override,Personal message,Amount,memo,Invoice ,Invoice Date
- Leave
Check Numberblank so Deluxe assigns it. Store the original municipal check number internally for reconciliation. - Fill payee, Payee email, and address from approved, verified info. Use the approved refund amount in
Amount. No cell phone column. - Put Closepoint's approved recipient-facing comments in
Personal message. UseTitleforInvoiceand the original checkDateforInvoice Date. - Verify the accepted date format, blank check number behavior, and email-only delivery settings with the Deluxe import mapping before a live batch.
- Use an export batch ID so the same payments can be re-downloaded without becoming eligible for a new batch. After issuance, record the Deluxe-assigned check number against the original case.
7Verify & report back
Test: missing cell phone, changed email, payee-name correction, two claims on the same check, two checks on the same closing file, a user opening another party's case, and a double export attempt. Generate a dummy Deluxe CSV and inspect header order, blank check number, invoice fields, and recipient message. Leave production outreach disabled until pilot approval.
Open decisions before launch
- Approve the BCC integration approach (native action cannot BCC both parties in one message).
- Approve the claimant-portal approach if the native portal cannot enforce required fields, locked name, and per-case access.
- Decide how to handle cases where only one party has a verified email (hold the notice until you decide).
- Confirm the closing-record source (contact reference number = file number) and the two staff approvers.
- Approve the pilot before production outreach is enabled.