Talk About Expense Controls Without Sounding Accusatory

Expense control outreach becomes tense when an SDR opens with risk language or suggests weak governance. Finance leaders already manage policy decisions. They do not need an unfamiliar person to imply neglect. Lead with operating clarity. Ask how a policy question moves from an employee or manager to the person who answers. The answer shows daily work without an allegation about misuse or a control failure.

Start with a neutral reason for contact. An SDR might say, “I speak with finance teams about handoffs around expense questions. I wanted to learn how your team handles those questions today.” This opening leaves room for an honest reply. Avoid words such as leakage, abuse, weak controls, or prevention. Those labels push a prospect toward defense before the SDR knows anything about policy or process.

Consider fictional Harbor Works, a field services company. Crews receive cards for fuel, supplies, and occasional urgent purchases. Jobs close on Thursday. Receipts often arrive after crews return equipment on Friday. During an overnight repair, a supervisor asks finance whether a replacement hose fits policy. Finance receives the question in a shared inbox, searches for job details, and replies Friday morning. These details describe a process. No misconduct appears in the facts.

Ask where an employee starts when uncertainty arises. A finance leader might say employees read a policy guide, ask a manager, or send a message to a finance address. Follow with, “What information reaches finance with the question?” The answer might include a receipt photo, job number, manager note, or a short message with no attachment. Each version changes manual follow up. None signals poor governance.

Then ask about work outside the normal purchase path. Use plain language: “When a purchase needs an answer before normal review, who helps decide the next step?” A prospect might describe a supervisor call or a finance queue. Stay with the current sequence. Do not suggest a preferred approval route. Discovery involves learning where people pause, where information gets added, and who needs visibility.

Listen for ownership rather than pain words. One contact might own written policy. Another handles a daily inbox. Field operations often knows why a purchase occurred. An accounting colleague might collect receipts after work closes. If a finance leader says, “We already have controls,” reply, “I expected your team would. I am trying to understand where manual questions appear around those controls.” The reply respects existing work and returns to process detail.

Specific time questions help. Ask when a question arrives, when an answer usually reaches the employee, and whether another person adds context before finance responds. At Harbor Works, the supervisor sends an evening message with a job number. The finance coordinator sees the message Friday morning, then asks for a receipt. A field manager responds after lunch. The purchase question reaches a final record several days after the repair. This timeline gives the prospect a sequence worth examining.

Do not treat every late receipt as a policy issue. Late records often follow job timing, travel, manager availability, or a routine accounting schedule. Ask, “When a receipt arrives after a job closes, what does your team do with the receipt?” A finance leader might describe matching, filing, follow up, or manager review. Repeat their words. Then ask where a person must leave one system or message channel to finish the work.

A defensive response gives an SDR a chance to show discipline. In a fictional practice call, the CFO says, “Our team has strong controls. We do not need a lecture.” The SDR replies, “Understood. I am not making an assessment. I would value a picture of where your team spends time answering routine questions.” Then pause. Silence gives the prospect space. Do not fill the pause with a product statement.

If the CFO describes a busy inbox, ask one narrow follow up. “What sort of question appears there most often?” Managers might ask whether a purchase belongs to a job. Employees might ask what to attach after travel. Finance might ask for missing context. Each answer suggests an operating question for a later discussion. Avoid promises about shorter review time or fewer exceptions. Results depend on policy, staffing, and choices outside an initial call.

Good notes separate an observed workflow from an SDR interpretation. Write, “Supervisor sends job number by message at eight thirty.” Do not write, “Approval process causes delays.” The first note records a fact. The second assigns cause without evidence. Record the policy owner, the person who receives questions, the normal route, and one exception route. Leave space beside each item for prospect correction during a follow up.

Before inviting more people, ask the finance contact whether an operations partner adds useful context. An SDR might say, “You mentioned field managers supply job details after finance receives a question. Would a short conversation with one manager help us map the handoff accurately?” Finance retains control over the next step. Do not add participants merely to make a meeting larger. Invite the person who sees the process area under discussion.

Set an honest purpose for any follow up. At Harbor Works, the follow up might focus only on the route for an overnight repair question. Ask the finance contact which facts the field manager should bring, such as the job number, original message channel, receipt timing, and manager response. Ask who writes the final record and where the record sits. This preparation prevents a broad meeting about every expense policy. During the meeting, repeat the sequence back after each speaker adds a detail. Mark an unknown detail instead of filling the space with an SDR assumption. A focused map often earns more trust than a long product discussion.

Prepare a practice conversation around Harbor Works. One person plays the CFO. Another plays the SDR. The CFO says, “Our policy exists, and managers know their responsibilities.” The SDR acknowledges the statement, then asks how an overnight repair question reaches finance. The CFO describes the evening message, Friday review, and later receipt. The SDR writes each action in order and avoids labels such as failure, gap, or risk.

The role play continues with a useful next step. The SDR asks whether the CFO will share one redacted example from the prior Thursday and name the field manager who supplied job context. With finance approval, schedule a twenty minute discussion for the following Tuesday. Open by asking where the supervisor sent the original message and what information finance had at nine Friday morning. Write both answers beside the Harbor Works example before moving to any other topic.