By Eric Kuvykin. Reviewed October 17, 2026. This practical guide replaces an earlier general commentary article at the same address.
A reviewed surcharge policy can drift after launch. A new ordering channel, receipt template or menu update can create an inconsistency that was absent from the original test. Schedule a configuration audit that compares the approved policy with what the customer actually encounters. The audit does not establish legal compliance; it identifies questions for the provider and qualified adviser before a discrepancy becomes routine.
Start from the approved record
Find the latest policy decision, provider instructions, legal review and test results. Record the accounts, locations and channels covered. If that file is missing, treat the gap as an unresolved review item rather than assuming an old terminal setting is authorized. Identify the person responsible for maintaining the policy and the person allowed to edit the system.
For New York operations, recheck the Department of State surcharge guidance; for New Jersey, consult the Division of Consumer Affairs FAQs. Note the source-review date and any question that requires professional interpretation. A multi-state business should not apply one location’s documented decision to every store without examining the other locations’ requirements.
Compare the live customer journey
Capture prices at the first point of presentation, the checkout, the confirmation and the receipt. Include printed materials, telephone scripts, web pages and third-party ordering tools. Compare those artifacts with the approved review file. Record the exact discrepancy and the system owner who can correct it. Avoid fixing one screen while leaving the underlying pricing rule or another channel unexplained.
Use the vendor’s authorized test method to review a supported eligible transaction and a payment method that should be handled differently under the approved configuration. Then check cancellation, full refund and partial refund behavior. Reconcile the displayed amount with the recorded transaction. If a result differs from the approved expectation, pause the affected change and obtain a supported resolution.
Control changes after the audit
Keep a dated log of corrections, configuration versions, staff training and replacement signs. A new location, software release, service package or pricing display should trigger a scoped retest. Customer complaints should enter the same log with facts and a response owner, so repeated confusion is visible to the person responsible for the policy rather than remaining in individual employees’ memories.
Use the pricing decision review when the underlying policy needs reconsideration, and the statement checklist when checking the recorded amounts. The New Jersey business guide connects the audit with broader operating records. Close each discrepancy only when the relevant reviewer has accepted the correction and the live result matches the approved expectation. An auditable configuration is easier to maintain than a collection of settings whose original purpose has been lost.
