A tip adjustment is the restaurant industry's daily special in payments: the card is authorized for the food bill, the customer writes in a tip, and the final captured amount differs from the authorized amount. The card networks built tolerance for this — but tolerance has limits, some processors charge extra for the privilege, and batching at the wrong moment turns a routine close-out into a reconciliation mess.
What a tip adjustment actually is
Step one: the server runs the card for the $50 food bill — that's the authorization, a hold on the customer's funds. Step two: the customer adds a $10 tip on the slip or the terminal. Step three: the POS adjusts the transaction to $60 and, at batch time, captures the final amount. Authorization, adjustment, capture — three events for one dinner.
On flat-rate pricing (say 2.6% + $0.10), the math is counterintuitive: the $0.10 fixed fee spreads over a bigger ticket, so the tip slightly dilutes the effective rate — $1.66 on $60 is 2.77%, versus $1.40 on $50 which is 2.80%. Tips don't raise your percentage rate; they raise your volume, and the dollars scale with it. The real tip costs are elsewhere: extra tip-adjustment fees some processors charge per adjusted transaction, and the decline risk below.
The 20% trap (auth tolerance)
Card networks cap how far a capture can exceed the original authorization without a fresh approval. For restaurant transactions, Visa's tolerance is about 20% over the authorized amount — a figure documented by payments engineers, not by any processor's marketing.
Go past it and one of two things happens: the issuer can decline the capture outright, or the gateway silently splits it into a new incremental authorization that's evaluated independently — with its own risk scoring and its own chance of a soft decline that has nothing to do with the original approval. One operator measured the damage: roughly 1 in 30 tabs over $100 declined on heavy-tipping nights, all clustered where tip percentages ran above average.
Their fix is worth stealing: cap tip-adjusted captures at 18% over the auth and force a fresh authorization for anything beyond. In POS terms: if a customer tips 30% on a $200 tab ($60 on $200 = 30% over auth), don't let the system blindly adjust — re-run the card for the full amount. One awkward ten-second re-tap beats a declined $260 capture and an unpaid tab.
The batching mistake
The batching mistake is settling the day's card transactions before tips are finalized. Some POS systems hold credit-card payments for later tip finalization; others batch everything immediately. Shift4's Dine POS even has a dedicated setting for it — Business Settings → Advanced → "Include All Credit Card Payments in the Daily Batch" — which controls whether payments are held for tip finalization or finalized immediately.
Batch before the tips are in and you get the worst of both worlds: the batch total doesn't match the POS sales-plus-tips report, reconciliation becomes detective work, and any tip entered after the batch needs separate handling. There's also a fee angle: some processors charge extra fees for tip adjustments, and at least one US program (Shift4's Advantage) explicitly states that processing fees on adjusted tip amounts are the merchant's responsibility — the surcharge can't be applied to the adjusted tip.
The rule is simple: tips first, batch second. Always. The batch is the last thing that happens at night, not the first.
The correct nightly tip procedure
- Collect every signed slip (or verify every tableside tip entry) before touching the batch. No slip left in an apron pocket.
- Enter/verify all tips in the POS against their authorizations. The POS should show each transaction as food amount + tip = total.
- Flag the outliers. Any tip pushing the total more than ~18–20% over the authorized amount gets a fresh authorization (re-run the card) instead of a blind adjustment.
- Check the POS setting. Confirm your system is set to hold payments for tip finalization rather than auto-batching early — in Shift4 Dine that's Business Settings → Advanced → "Include All Credit Card Payments in the Daily Batch"; your POS has an equivalent.
- Run the batch. Only now — after every tip is finalized — close out and settle.
- Reconcile immediately. Batch total must equal (food sales + tips) to the cent. Any variance gets investigated tonight, not at month-end.
What success looks like: the batch report matches the POS sales-plus-tips report exactly, zero authorizations are left open overnight, and no capture ever exceeds ~118% of its authorization. Do this nightly and the two tip costs — the decline risk and the reconciliation mess — both go to zero.
FAQ
How do tip adjustments work on credit cards?
The card is authorized for the pre-tip amount, the tip is added in the POS, and the adjusted total is captured at batch time. The capture can exceed the authorization by about 20% (Visa's restaurant tolerance) before the issuer may require a fresh authorization.
Can a tip be declined on a credit card?
The tip itself isn't declined separately, but the whole capture can be declined if it exceeds the authorization tolerance — roughly 1 in 30 large tabs on heavy-tipping nights in one operator's measurement. Re-running the card for big tips prevents it.
When should a restaurant batch credit cards?
After all tips are entered and finalized — tips first, batch second, always. Batching early creates reconciliation variances and complicates any tip entered after the batch.