When the Acquirer Statement Is Wrong: The Notice Deadlines That Can End the Claim

A settlement lands short. A fee line appears that nobody recognises. An interchange category looks wrong across a whole month. Someone opens a ticket, and it gets scheduled behind the close — because a statement query feels like housekeeping, not a deadline.

It may be a deadline. In published merchant agreements from three different providers, the right to object to a statement, an invoice or a missing settlement is time-limited by contract, and the windows run from 5 business days to 60 days depending on what went wrong. In at least one, missing the window does not weaken the claim — it removes the provider's liability for it entirely. Nothing tells the merchant the clock is running. The statement arrives, and the clock starts.

This reference reads the actual clauses. There is no industry standard here to report — only individual contracts that differ in ways that matter. Decomposing the statement itself — which line is interchange, which is scheme fees, which is your acquirer's margin — is owned by reading your processing statement line by line and is not repeated here.

The Clause That Ends the Claim

The most explicit published example sits in U.S. Bank's Business Essentials payment processing terms, dated April 2026, under which Elavon is the processing party. Section 3.7, headed "Asserted Errors", does three separate things.

First, it puts the reconciliation duty on the merchant and requires written notice: "You must promptly examine all statements relating to the DDA and notify Elavon in writing of any errors in the statement you received from Elavon."

Second — the part to copy into your runbook — it prescribes exactly what the notice must contain:

• "Your business name and account number;"
• "The dollar amount of the asserted error;"
• "A description of the asserted error; and"
• "An explanation of why you believe an error exists and the cause of it, if known."

Third, it sets the consequence: "If you fail to provide written notice to Elavon of an asserted error within 45 days of the date of the Elavon statement or invoice containing the asserted error, Elavon will not be liable to you for any errors related to that statement."

Then comes the sentence almost nobody expects. Giving notice does not open a dispute you can escalate — it opens a standstill: "You may not make any claim against Elavon for any loss or expense relating to any asserted error for 45 days immediately following Elavon's receipt of your written notice." And in that window, "During that 45 day period, Elavon may investigate the asserted error (and you will not incur any cost or expense in connection with the asserted error without notifying Elavon), and notify you of its proposed resolution of the asserted error."

So the practical shape is a 45-day window to speak, then a 45-day window in which you may not act while the provider may investigate. Note the asymmetry: the bar on claiming is mandatory, the investigation is not.

The same clause appears in Elavon's own Operating Guide, published 30 April 2026, as section 7, in the third person: "If Company fails to provide written notice to Elavon of an asserted error within 45 days of the date of the Elavon statement or invoice containing the asserted error, Elavon will not be liable to Company for any errors related to that statement." Two first-party channels, one clause.

Set against it is the provider's own adjustment right, which has no matching clock: "All credits for funds provided to you are provisional and subject to reversal if Elavon does not receive payment of corresponding settlement amounts from the Payment Networks." The merchant's window to question a figure is finite; the provisional character of the credit is not.

Three Agreements, Three Different Clocks

The comparison is where the useful information is, because the three published clauses differ on every axis that matters.

Three axes differ, and each carries a distinct operational consequence.

Length. 30 business days, 45 days and 60 days are not close together once mapped onto a close calendar; a 45-day window from a statement date can expire before a quarter-end review begins.

What starts the clock. Fiserv's Malaysia terms are precise about a detail most merchants would get wrong: errors must be reported "within 60 days following the date (whichever is the earlier): (i) it first has access to the Statement, or portion of the Statement, containing the error; or (ii) the date of the Statement containing the error." The earlier-of construction means an operator who opens a portal report before the formal statement issues has already started the clock. Worldpay's Canadian agreement runs from "the date the report or invoice is made available to Merchant" — availability, not receipt, and not opening.

The mechanism. These are three different legal shapes, not three phrasings of one idea. A liability bar and a removed remedy are both defences the provider raises. Deemed acceptance is different in kind: Worldpay's clause provides that failing to reject in time "shall constitute Merchant's acceptance of the same", converting your inaction into an affirmative agreement that the figures are right. Fiserv does keep a cooperative obligation alive alongside its bar — the parties "will work together to resolve issues or disputes that arise in connection with the Statements, or the funds credited or debited to the Settlement Account" — but that sits beside the 60-day rule, not instead of it.

The two most dangerous shapes are the earlier-of trigger and deemed acceptance, for the same reason: neither requires the provider to do anything. No notice is sent, no acknowledgement issued, no state changed anywhere in your systems. The window opens and closes on the provider's calendar.

Missing money runs on its own clock again. Worldpay gives five business days to report settlement funds that did not arrive, failing which the same deemed-acceptance sentence applies; Fiserv imposes the duty without a number: "The Company must promptly notify Fiserv if it fails to receive any settlement funding or if there are any changes to the Settlement Account." Treat a missing payout and a wrong figure as two separate alerts.

What These Documents Do Not Establish

A handful of published agreements from three providers in three jurisdictions is evidence about those documents. It is not an industry norm, and it should not be read as one.

The instructive comparison sits inside a single brand, like document type against like. Elavon's UK Terms of Service is stamped 03/2026 against the US terms' April 2026 — within a month of each other — and it does impose a claim-notice duty. What it lacks is a statement-specific one: no asserted-error mechanic, no duty to review or reconcile statements, no deemed acceptance, no window running from a statement date. Its entire statements provision promises the merchant something rather than requiring anything of them: "We will provide you with monthly statements showing the value of all Sales Transactions acquired by Elavon as well as any: Merchant Service Charges; Refunds; Chargebacks; charges in the Schedule of Fees; Interchange Fees; as well as Fees and Adjustments." It is governed by the Laws of England and Wales.

What it has instead is a general claim clause. Section 22.6 requires the merchant to inform Elavon, with details of the claim and of the alleged loss, "immediately upon identifying such claim", and in any event within six months for general claims — or thirteen months for claims about rectifying unauthorised or incorrectly executed payment transactions, cut to six for a Large Corporate or Large Charity. Every limb runs from the same moment: "after you become aware (or should have reasonably become aware) of the act or omission which forms the basis of your claim". Ireland's Terms of Service carries the general six-month limb in the same words, without the thirteen-month one.

So the contrast is not presence against absence — it is the trigger, and that is the sharpest thing here. The US clause starts at the statement or invoice date: an objective clock that runs whether or not anyone opens the document. The UK and Irish clauses start at awareness, which does not begin until the merchant knows or reasonably should. Same brand, a month apart, two different theories of when a merchant's time ought to start; the clause travels with the governing law and the contracting entity, not with the logo. And where a UK merchant is a Large Corporate or Large Charity, or is "otherwise capable of doing so", it also agrees that the notification period for an unauthorised or incorrectly executed payment transaction is the contract's "rather than the period specified in regulation 74(1) of the Payment Services Regulations 2017" — a deliberate displacement of the statutory clock, not an absence of one.

Nor is one clause per agreement the norm. Fiserv's Malaysia schedule for Grab transactions sets its own window — settlement-funding errors reported within 30 days of receiving the funds or of access to the statement, whichever is earlier — half the 60 days the general terms give. Elavon's US operating agreement carries a second 45-day asserted-error clause for Electronic Gift Card direct settlement, with a harder consequence than §3.7: failure "will preclude further claims or assertion of the error". Read the schedules, not just the general terms.

The same discipline applies across providers: the 60-day rule is Fiserv's Malaysia entity, the 30-business-day rule Worldpay Canada Corporation under Ontario law. Neither transfers to the same brand elsewhere without checking. And where a provider publishes no merchant agreement at all, that is an absence of publication, not an absence of a term.

There is also no evidence here about outcomes. These sources establish what the contracts say, and nothing about what any acquirer concedes, refunds or waives in practice. Anyone quoting a typical success rate on statement disputes is not quoting these documents.

The instruction is to read your own agreement — general terms and schedules both. Search for statement, invoice, error, notice and claim, and record three things per clause: the number, the trigger, and the consequence. Searching for a phrase you expect is how a clause gets missed; search for the function. If your contract is genuinely silent, that is worth knowing too, and worth raising at renewal alongside the other terms covered in PSP contract red flags.

Building the Notice

Identify the disputed line precisely. A notice saying the fees look high is not a notice of an asserted error. You need the line, the amount, and the basis on which you think it is wrong.

Write to the contract's prescribed contents. Where the agreement lists them, as the Elavon clause does, use its list as your template: business name and account number, the dollar amount, a description, and an explanation of why an error exists and its cause if known. Where nothing is prescribed, use the same four anyway. Worldpay's Canadian agreement asks for written notice "specifically detailing any alleged failure, within thirty (30) days of the date on which the alleged failure first occurred" — a standard the four elements comfortably meet.

Send it in writing. Every clause examined here specifies writing. A support ticket, a phone call or a word to a relationship manager is not obviously the written notice the contract requires, and the burden of proving you gave notice sits with you.

Keep the standstill in view. Where a clause imposes one, you cannot claim while the provider may investigate — permissive on their side, binding on yours. The Elavon clause does not forbid you from spending on the matter; it requires you to notify Elavon before you do. Nothing about that period stops the next statement arriving with its own fresh clock.

Keep reconciling while it is open. A break left open across months becomes much harder to evidence, and your evidence pack is the same reconciliation output you should already be producing — see the PSP reconciliation failure runbook. If your pipeline normalises several providers, per the settlement-data ingestion reference, tag each provider's notice window onto the statement record so the deadline sits where the break is.

The Scheme-Rule Anchor, and Its Limits

Card scheme rules give you a framing device rather than a remedy. Visa's Core Rules require an acquirer to pay or credit its merchant's account promptly after Transaction Deposit, then constrain what may be netted off: "These payments must be the same as the Transaction totals, less any Credit Transactions or Original Credit Transactions, applicable discounts, Disputes, other agreed fees or Merchant reserve funds (if applicable) accumulated to guarantee the Merchant's, Sponsored Merchant's, Marketplace's, Payment Facilitator's, or Digital Wallet Operator's payment system obligations to the Acquirer."

The load-bearing word is agreed. When you cannot find the contractual basis for a deduction, the question is not whether it is fair but which agreed fee it is and where in your agreement it sits. In the Europe Region the rulebook adds a transparency duty: an acquirer "must provide an invoice to its Merchant for MIFs showing all of the following for the invoice period:", broken down by card type unless the merchant has chosen blended pricing.

Do not overstate this. These are obligations an acquirer owes under its Visa membership, enforced by Visa against the acquirer. The public rulebook creates no merchant dispute procedure, no notice deadline and no merchant right of action. Its value is that it tells you what a compliant statement should let you see — nothing more.

Operator Checklist

• Find the notice clauses in every acquiring and PSP agreement you hold — general terms and schedules — and record the number, the trigger and the consequence for each.
• Treat "made available" and "first has access" triggers as live from the moment a portal report appears, not from the formal statement date.
• Run a separate, shorter alert for settlement funds that did not arrive; it is a different clock in at least two of these agreements.
• Template the notice on the contract's own prescribed contents, and default to the Elavon four where nothing is prescribed.
• Send in writing, keep the timestamp, and diary any standstill the clause imposes.
• Never assume a deadline from another provider's contract, another market's version of the same brand's contract, or an article — this one included.

Related References

• The MDR Stack: Reading Your Processing Statement Line by Line — identifying the disputed line before you write the notice.
• PSP Reconciliation Failure Runbook — break handling and the evidence trail a notice depends on.
• 14 PSP Contract Red Flags That Cost Merchants Millions — the wider set of clauses worth redlining at renewal.
• Settlement Data Ingestion and Normalisation Across Multiple PSPs — where to store per-provider notice windows.