Run a Lockbox Workflow Discovery Conversation

Lockbox interest often begins when a finance team is tired of opening mail and coding payments. A treasury specialist should ask about the full receipt path before discussing a service. Ask which payments arrive by mail, who opens them, how remittance data reaches the receivables system, and where errors surface. Explain early: processing speed and implementation outcomes depend on approved review and the customer’s own workflow. Curiosity produces a more useful conversation than a fast product description.

Begin with a request for a recent payment story. “Please walk me through one mailed payment from arrival through posting.” A story exposes steps which a volume figure hides. Ask who receives the envelope, where checks stay before deposit, who reads remittance notes, and what happens when the amount or reference does not match. Let the customer describe the current work in sequence. Do not fill a pause with assumptions about pain, staffing, or a future process.

Volume still matters, though volume alone rarely explains effort. Ask how many mailed payments arrive in a typical period, whether arrivals cluster around particular dates, and whether staff work through a backlog after a peak. Ask which payment types create the longest handling time. A small number of complex payments often takes more attention than a large set of clean payments. The goal is not to force a problem statement. The goal is to understand where people spend time and where the customer sees risk or delay.

In a fictional example, Willow Supply receives mailed payments from a mixed group of customers. Rosa, the receivables manager, says two staff members open envelopes each morning and enter references into the receivables system. Her first estimate is 180 envelopes during a busy week. When the treasury specialist asks about exceptions, Rosa explains handwritten references lead to extra research. A check amount sometimes matches an invoice total, yet the remittance note points toward another customer account. This detail carries more meaning than the headline envelope count.

Ask how exception work moves. Who first notices an unclear reference? Does one person contact a customer, or does the item move to an account manager? Where does the team record an unresolved item? How does someone learn an item has received an answer? These questions reveal the coordination behind a simple payment. They also show which people should join a later review. Do not assume the person who opens mail owns every decision. Finance, customer service, billing, and sales operations sometimes hold different parts of the path.

Data capture deserves equal attention. Ask Rosa whether staff enter details from paper, scan information into another system, or receive files from a separate source. Ask which fields matter for posting and who needs access to those fields. A service conversation needs the customer’s actual remittance needs, not a generic statement about visibility. If the team relies on a customer account number and invoice reference, note both. If staff often work from handwritten notes, ask for examples of the ambiguity without requesting sensitive payment details during an early conversation.

A good specialist uses neutral language when a customer describes a burden. Rosa says, “We lose time searching old emails when a note is unclear.” A useful reflection is, “The delay appears after receipt, during research on unclear remittance.” The reflection gives Rosa a chance to correct the picture. Avoid turning her words into a claim about faster posting or fewer errors. Her team might care most about a cleaner research path, more consistent records, or access for a second team. Let the customer choose the objective.

Ask about controls in operational terms without presenting requirements. Who opens mail, who prepares the information for posting, and who reviews exceptions? Where do responsibilities change hands? What record helps a manager see items awaiting resolution? The customer might have a process already, or the team might be revising one. Your questions should map reality rather than grade their approach. A later review benefits from knowing where a workflow depends on a single person, where a team lacks shared status, or where handoffs create delays.

Preparation for a next meeting should be specific. Ask Rosa which recent records would help the team explain the process, such as a sample of redacted remittance formats, a count of unresolved items by week, or a simple map of receipt through posting. Do not ask customers to send sensitive material by an unsuitable route. Instead, identify the kind of record and agree on the appropriate channel with the relevant people. Explain why each item helps. A sample format helps clarify data capture. An exception count helps estimate where research begins.

Ask one question about variation across customers. Rosa might receive clean remittance from several large customers and unclear notes from occasional purchasers. Find out whether staff use different research paths for each group or whether every exception enters one folder. This distinction affects who should describe the present workflow during review. A conversation based on actual variation keeps the discussion focused on work, records, and people rather than a generic service claim.

Avoid a premature option discussion. A customer who says, “We spend hours opening envelopes,” often seeks relief, but an answer needs more detail. Ask whether the team wants to change mail handling, remittance research, posting visibility, or some combination. Ask what a better working day would look like in concrete terms. Rosa might say her team wants every unresolved payment visible before noon so account managers know which customers need follow up. Such a statement gives a future review a target without promising an outcome.

In a fictional role practice, one colleague plays Rosa and supplies partial answers. The specialist begins with the path of one payment. Rosa says payments arrive by 10:00, staff open envelopes by noon, and unclear notes move into an email folder. The specialist asks who checks the folder and what counts as resolved. When Rosa says an account manager often replies the next afternoon, the specialist records a handoff rather than labeling the process inefficient. The observer listens for product claims and replaces them with questions about workflow.

Close the fictional discovery with a visible next action. Rosa agrees to bring a one page process sketch and five redacted examples of unclear remittance formats to a Tuesday review at 2:00. The specialist sends a note describing those items, asks Rosa to include the colleague who owns posting decisions, and records Rosa’s goal of seeing unresolved payments before noon. On Tuesday, begin by placing Rosa’s sketch on the screen and ask her to point to the moment an unclear reference first enters the process.