Client Dinner Etiquette: Who Pays and How

Three companies at one table. Your client, their partner, and your team. The check arrives. Whose expense account owns this meal? The answer isn't about who ordered what—it's about who benefits from the relationship.

The client dinner isn’t a meal. It’s an investment.

At a personal dinner, splitting the bill is about fairness: who ate what, who drank more, who should pay their share. At a client dinner, the calculus is entirely different. The person who pays is making a strategic investment in a business relationship. The cost of the meal is secondary to the value of the relationship being cultivated.

This distinction matters because it changes who reaches for the check. In personal dining, the modest orderer might resist subsidizing the heavy spender. In client dining, the host company wants to absorb the cost—because the alternative (making the client pay or splitting) signals that the relationship isn’t worth the investment.

The anthropologist Marcel Mauss identified this dynamic in 1925. His landmark work The Gift argued that gift-giving in traditional societies was never purely generous—it was a mechanism for creating obligation and cementing relationships. The gift binds the recipient to the giver. A business dinner works the same way. When you pay for a client’s meal, you’re not being generous. You’re creating a subtle social debt that tilts the relationship in your favor.

78%

of executives say business meals are essential to relationship-building, according to a 2023 survey of Fortune 500 companies. The meal itself is the medium. Payment is the message.

Robert Cialdini’s research on persuasion reinforces this. His 1984 book Influence documented the power of reciprocity: when someone does something for us, we feel obligated to return the favor. Free samples at supermarkets work on this principle. So do client dinners. The $400 steak dinner creates an asymmetry that makes saying “no” to your proposal slightly harder.

Sources: Mauss, The Gift: The Form and Reason for Exchange in Archaic Societies (1925); Cialdini, Influence: The Psychology of Persuasion (1984).

When to expense vs. when to split

The decision to expense a meal (company pays) versus split (individuals pay) depends on the nature of the relationship and the purpose of the meal. Here’s the framework:

EXPENSEYou’re the seller

If you’re pitching, selling, or seeking to deepen a business relationship, you pay. The client should never reach for their wallet. This is non-negotiable across cultures.

EXPENSEYou initiated the meeting

Whoever proposed the meal covers it. “Let me take you to dinner” is a commitment, not a suggestion. If you invited, you host.

EXPENSEThe client is visiting your city

When someone travels to meet you, hospitality norms activate. The host city’s representative covers the meal as a gesture of welcome.

SPLITPeer-to-peer relationship

When there’s no power asymmetry—two founders grabbing coffee, industry peers at a conference—splitting is natural and expected.

SPLITOngoing partnership

Long-term partners often rotate who pays. Today you host, next quarter they host. The relationship is established; the obligation is balanced.

SPLITMixed personal/business

If the meal is more social than strategic—old colleagues catching up, friends who happen to work together—splitting is appropriate.

The golden rule: If you’re asking “should I expense this?” you probably should. Companies allocate entertainment budgets precisely for relationship-building meals. Not using it signals either ignorance of your expense policy or lack of strategic thinking about the relationship.

When multiple companies are at the table

The most complex client dinners involve three or more companies. A typical scenario: you’re the vendor, your client brought their implementation partner, and everyone is at a steakhouse discussing the project. The check is $1,200. Whose expense account absorbs it?

SAP Concur’s 2023 analysis of 192 million expense reports found that the average business meal expense reached $55 per person—but client-facing dinners with multiple stakeholders routinely exceed $100 per head. At a table of 8, that’s an $800+ decision that needs to be resolved before the server returns.

SituationWho pays

Vendor + Client + Client’s partnerVendor pays. You invited the client; you own the meal.

Two vendors + ClientVendors split, client pays nothing. Negotiate quickly before check arrives.

Vendor + Client + Vendor’s subcontractorVendor pays for all. Your sub is your responsibility.

Multiple peers, no clear buyer/sellerSplit evenly by company, or the meeting initiator covers.

The critical principle: the client should never witness the negotiation about who pays. If there’s ambiguity about which vendor covers the bill, resolve it in advance or with a discreet conversation away from the table. The worst outcome is two vendors awkwardly reaching for the check while the client watches.

Carlos Cabral-Cardoso and Miguel Pina e Cunha’s 2003 research on business meals as organizational rituals specifically noted that the “who pays” moment is the climax of the dinner performance. Getting it wrong doesn’t just cost money—it signals disorganization, lack of authority, or worse, that you’re not serious about the relationship.

Sources: SAP Concur, “Business Meals and Entertainment Expenses” (2023); Cabral-Cardoso & Cunha, “The business lunch: toward a research agenda,” Leadership & Organization Development Journal (2003).

The expense policy reality

Understanding your company’s expense policy before the dinner is non-negotiable. Nothing is more embarrassing than offering to host a client dinner, then realizing your expense limit is $50/person when the restaurant averages $150.

50%Tax deduction for business meals (US, post-2022)

$75Typical per-person cap for client entertainment

100%Reimbursement rate at most large companies for approved entertainment

Key policy questions to know before booking:

Per-person limits: Many companies cap entertainment at $75-150 per head
Alcohol policies: Some companies reimburse only food, not drinks
Approval requirements: Large dinners may need pre-approval from a manager
Documentation: Most require attendee names and business purpose on the receipt
Client gifts vs. meals: Gifts over certain thresholds may trigger compliance issues

Andrew Stark’s research on the ethics of business gifts and entertainment noted that the line between “relationship-building” and “bribery” is often a matter of degree, disclosure, and organizational policy. A $400 dinner is normal client entertainment. A $4,000 dinner without documentation starts raising questions. Know where your company draws the line.

Source: Stark, “Gifts, Bribes, and the Law: A Framework for Distinguishing Between Legal and Illegal Payments,” Journal of Business Ethics (2000).

International client etiquette: what your global clients expect

Payment norms vary dramatically across cultures. What signals respect in New York may cause offense in Tokyo. Geert Hofstede’s cultural dimensions research and the GLOBE study of 62 societies provide the framework for understanding these differences.

The key dimension is power distance—how much a culture accepts and expects unequal power distribution. High power-distance cultures (China, Japan, Middle East) expect the senior or wealthier party to pay. Low power-distance cultures (Scandinavia, Netherlands) are comfortable with splitting.

JapanHost pays, always

Never split with a Japanese client. The most senior person or host organization pays. Settle the bill discreetly—excuse yourself and pay at the register. Showing the receipt at the table is gauche.

ChinaFace and generosity

Paying for guests is a matter of “mianzi” (face). The host demonstrates status and respect by covering the bill. Expect a performative “fight” over who pays—insist firmly but graciously. Let the client pay only if they escalate strongly.

Middle EastHospitality as honor

Paying for guests is deeply connected to honor and hospitality. Refusing to let the host pay can be insulting. If hosting a Middle Eastern client in your city, you pay. If visiting their city, expect them to insist.

GermanyPrecise and pragmatic

Germans are comfortable with itemized splitting even in business contexts. However, if you invited, you pay. Efficiency is valued—don’t make a production of the payment process.

United StatesThe seller pays

American business culture defaults to: whoever is selling pays. The client’s money is sacred. Making a client reach for their wallet during a sales process is considered gauche.

ScandinaviaSplitting is default

Nordic cultures are comfortable splitting even with clients. High individualism and low power distance make Dutch treat acceptable. However, the “seller pays” norm still applies to active sales situations.

Hsien Chin Hu’s foundational 1944 research on Chinese “face” concepts explains why payment norms matter so much in high-context cultures. “Lian” (moral character) and “mianzi” (social standing) are at stake in every business interaction. A misstep in who pays can damage the relationship more than any pricing negotiation.

“In China, a man’s ‘face’ is the respect of his fellow men that he can claim for himself from his social position. The loss of face is the loss of the respect of others and society.”
Hsien Chin Hu, American Anthropologist (1944)

Sources: Hofstede, Culture’s Consequences (2001); House et al., Culture, Leadership, and Organizations: The GLOBE Study (2004); Hu, “The Chinese Concepts of ‘Face,’” American Anthropologist (1944).

When splitting between companies makes sense

Not every multi-company dinner needs a single payer. In peer relationships—two startups collaborating, industry partners at a conference, board members meeting informally—splitting by company is appropriate and efficient.

The mechanics matter. When 3 companies with 8 people total split a $1,400 dinner, the question is: split per person, or split by company?

CompanyAttendeesPer-person splitEqual company split

Your company4 people$700$467

Partner A3 people$525$467

Partner B1 person$175$467

The per-person split penalizes smaller delegations. If Partner B sent one senior executive while you sent four junior associates, per-person feels unfair. Equal company splits can work for true peer relationships, but require agreement before the meal.

Best practice: Before a multi-company dinner with unclear payment norms, the meeting organizer should send a brief message: “Happy to host this one” or “Let’s plan to split by company.” Clarity prevents the awkward check moment.

Recovery: when the check moment goes wrong

Sometimes the check arrives and everything goes sideways. Two vendors reach simultaneously. A client offers to pay when they shouldn’t. Someone mentions splitting when the cultural norm forbids it. Here’s how to recover:

Two vendors both reach

Whoever has the primary relationship wins. If unclear, the one who initiated the meeting pays. Say: “I’ve got this one—you can get the next.” Then actually let them get the next one.

Client insists on paying

Push back once firmly: “Please, you’re our guest.” If they persist strongly, let them. Some executives feel uncomfortable being hosted. Graciously accept, but make clear you’ll reciprocate.

Someone suggests splitting with a client

Intercept immediately: “No, we’ve got this.” Never let the client perceive hesitation about covering them. Apologize privately to whoever suggested splitting—they may not have understood the relationship dynamics.

Expense policy prevents full coverage

Pay what you can expense, cover the difference personally, then sort out reimbursement later. Never make a client witness expense policy constraints. The relationship is worth the temporary out-of-pocket.

Fiddick and Cummins’s cross-cultural research on noblesse oblige found that higher-status individuals are expected to be generous—and that this expectation is strongest in business contexts. When you’re the seller, you have the higher-status position at the meal (you want something). The obligation to pay is part of that role.

Source: Fiddick & Cummins, “A Cross-Cultural Study of Noblesse Oblige in Economic Decision-Making,” Human Nature (2013).

After the meal: documentation and follow-through

The check moment is just the beginning. Proper documentation and follow-up separate amateur entertaining from professional relationship-building.

Document the business purpose

Write the attendee names and business purpose on the receipt before leaving. "Client dinner - Acme Corp Q2 implementation planning" is sufficient. Your finance team will thank you.

Submit the expense promptly

Don't let receipts pile up. Submit within 48 hours while the context is fresh. Delayed expense reports invite questions and delays.

Send a follow-up note

A brief email the next morning: "Great dinner last night. Let's keep the momentum going on [topic]." The meal is an investment; the follow-up is the return.

Track the relationship

Note in your CRM or calendar when you last hosted this client. Rotate hosting duties with partners. Remember who paid last time.

How research shaped the design

When client dinners involve splitting—peer relationships, rotating hosts, or multi-company peer dinners—the research points to specific requirements:

Multi-company dinners create complex splits→

splitty can assign people to groups, calculating per-company totals for separate expense reports

Speed matters at high-stakes meals→

30-second receipt scanning means the split is done before the client notices any calculation happening

Documentation is required for expenses→

Itemized breakdowns with exact per-person totals satisfy even the strictest corporate expense policies

Discretion is valued in business contexts→

The app handles math privately—no passing phones around the table or asking “what did you order?”

Three companies. One check. Zero awkwardness.

Scan the receipt. Assign by company. Get the exact breakdown your expense report needs.