How to Record Third-Party Client Payments in a Law Firm Billing Workflow | RunSensible

When a client pays from a third-party account, the billing task is not just marking an invoice as paid. The firm also needs a clear operational record of how the payment was received, where the funds were deposited, which bill it applies to, and what supporting details explain the transaction. For firms that need to record third-party client payments, RunSensible supports a more organized billing workflow for documenting payments against bills and keeping payment status visible across the team.

The Problem With Third-Party Client Payments

Third-party payments are common in legal billing. A family member may pay for a client’s invoice. A company may cover a legal bill for an employee or representative. A client may use a business account, spouse’s account, or other external payer source.

The operational issue is that the payer name may not match the client name on the bill. If that payment is tracked only through an email, bank note, or side spreadsheet, staff may later struggle to answer basic questions:

1. Who paid this bill?
2. Which invoice was it applied to?
3. Was the bill fully paid or partially paid?
4. Which bank account received the funds?
5. Was proof of payment saved with the payment record?

Without a structured workflow, the firm may still receive the money, but the record behind the payment can become harder to verify internally.

A Realistic Use Case Scenario

A law firm sends an invoice to a client for completed work. The client replies that a parent, spouse, employer, or related business will pay the bill on their behalf. The funds arrive by check or wire transfer, but the payer’s name does not match the client record.

The billing team now needs to apply the payment to the correct bill while keeping enough context for future review. They do not want to rely on memory, email threads, or a separate spreadsheet. They need a payment record that shows the amount received, payment method, reference details, payment date, deposit account, and any relevant notes or proof of payment.

How RunSensible Supports Third-Party Payment Recording

RunSensible allows firms to record payments against bills by opening the bill and using the Record Payment workflow. The documented process supports payments received outside the online gateway, including payment types such as cash, check, wire transfer, or other externally processed payment methods.

That matters for third-party payments because these transactions often require additional context. In RunSensible, the firm can select the bank account where the funds were deposited, choose or add a payment method, enter the payment amount, set the payment date, add a reference ID, include notes in the description field, and attach supporting documentation where needed.

RunSensible also updates the bill status based on the amount received. If the full balance is paid, the bill can be updated to Paid. If only part of the balance is received, the bill can be updated to Partially Paid. This helps the team keep billing visibility tied to the bill itself rather than managing status separately.

Step-by-Step: How to Record Third-Party Client Payments

1. Open the correct bill record

Start by locating the bill that the third-party payment should be applied to. RunSensible’s Bills List includes key billing information such as bill number, status, total, balance, client, invoice date, and due date, which helps staff confirm they are working from the correct record.

This is especially important when the payer name does not match the client name. The bill record should be the anchor for the workflow.

2. Use the Record Payment workflow

From the bill page, use the Record Payment button to begin entering payment details. For payments received outside the online Pay Now gateway, RunSensible supports a manual payment workflow for direct payments such as cash, check, wire transfer, or another external payment type.

This gives the firm a structured way to record the transaction without treating it as a disconnected bank note or informal update.

3. Select the bank account where the funds were deposited

When recording the payment, select the relevant bank account from the dropdown. This helps the firm connect the payment record to the account where the funds were deposited.

RunSensible also supports setting up and managing bank accounts, which helps firms keep bank-related activity organized within the accounting workflow.

4. Choose or add the payment method

Next, select the payment method. If the specific method is not already listed, RunSensible allows users to add a new payment method from the payment method menu.

For a third-party payer scenario, this can help the firm distinguish between payment types such as wire transfer, check, cash, or another method the firm uses internally. The key is not to overcomplicate the workflow, but to make the payment record clear enough for staff to understand later.

5. Enter the payment amount and confirm bill status

Add the amount received. If the third party paid the full balance, RunSensible can update the bill status to Paid. If the payment only covers part of the balance, the system can adjust the bill status to Partially Paid.

This helps the team avoid a common billing problem: a payment is received, but the invoice status is not updated consistently.

6. Add reference details and a description

Use the reference ID, payment date, and description fields to add context. For a third-party account payment, the description can be used to note that the payment was received from a payer different from the client, along with any internal details the firm chooses to record.

This does not replace the firm’s own billing controls, verification process, or professional obligations. It simply gives the team a better operational place to keep the payment context attached to the bill.

7. Attach proof of payment when useful

RunSensible’s payment recording workflow also supports adding files to the payment record. Staff can attach supporting documentation such as proof of payment, a receipt, or another relevant file.

For third-party payments, this can be useful when the payment arrives with a wire confirmation, check image, client authorization note, receipt, or internal approval record.

8. Review payment activity when needed

After a payment is recorded, the firm can use RunSensible’s payment and transaction-related views to review payment details. The Help Center also describes how users can review account transactions for a specific account, helping teams monitor account activity over time.

This gives billing staff a clearer path for reviewing financial activity without relying only on separate notes.

Outcome

A structured third-party payment workflow helps law firms keep billing records more consistent. Instead of treating a third-party payment as an exception managed through scattered notes, the firm can record the payment against the bill, document the method and reference details, attach supporting files, and keep the bill status up to date.

The practical benefit is better visibility. Billing staff can see whether the bill is paid, partially paid, or still outstanding. Team members can understand how the payment was received. And the firm has a more organized record if the payment needs to be reviewed later.

This is especially helpful for firms that regularly receive payments from family members, companies, related businesses, or other payer sources that do not match the client name on the invoice.

If your firm needs a clearer way to record third-party client payments, RunSensible supports a more organized billing workflow for tracking payment details, keeping bill status updated, and storing relevant context with the payment record.

FAQs

Can RunSensible help record third-party client payments?

Yes. RunSensible supports recording payments against bills, including payments received outside online payment gateways, such as cash, check, wire transfer, or another external payment method.

Can I note that the payer is different from the client?

The payment recording workflow includes fields such as reference ID, payment date, description, and supporting file attachments. Firms can use those fields to keep relevant context with the payment record.

What happens if the third party only pays part of the bill?

When entering the payment amount, RunSensible can reflect whether the bill is fully paid or partially paid based on the amount received.

Can I attach proof of payment?

Yes. The documented payment recording workflow allows users to attach supporting documentation to the payment record.

Does RunSensible verify whether a third-party payment is legally acceptable?

RunSensible supports the operational billing workflow for recording payments. Firms should continue to follow their own professional, ethical, and accounting review processes when accepting payment from a third party.

Final Thought

Third-party client payments can create billing confusion when the payer name, client name, and invoice record are not clearly connected. RunSensible gives law firms a more structured way to record these payments against the correct bill, document key details, update payment status, and keep supporting information with the record. For firms that regularly receive payments from family members, businesses, or other outside payer sources, this creates a cleaner workflow and reduces avoidable administrative follow-up.

Help Center Links

• Record payments against bills – https://help.runsensible.com/billing/managing-recording-payment/
• Manage bills with action buttons – https://help.runsensible.com/billing/managing-bills-with-action-buttons/
• Search and customize bills – https://help.runsensible.com/billing/searching-and-customizing-bills/
• Manage online payments and bill reminders – https://help.runsensible.com/billing/online-payments-management/
• Set up and manage bank accounts – https://help.runsensible.com/accounting/setting-up-and-managing-bank-accounts/
• View account transactions – https://help.runsensible.com/accounting/viewing-account-transactions/