Skip to article
ecomservices.io
Chargebacks · How to run this
MatchingNot on this page yetPricingCalculatorIntakeCalculatorReason codesCalculatorRepresentmentCalculatorThresholdsCalculatorAllocationCalculatorOptimisationCalculatorPrevention stackCalculatorProviders

Library · Chargebacks · How to run this

Forter case clock from submit to issuer close

How to run thisChargebacks3 steps
CalculatorForter representment lag days · Calculator lives in the articleOpen

Open one Forter contested-case ledger. Subtract submit day from issuer-close day. That integer is FT lag days. Outcome does not stretch or shrink the clock.

Tool: Representment lag days under Chargebacks. Neighbor on Ethoca: Ethoca lag. Dollar counterpart: alert-to-fight lag.

Ledger columns

Submit day — Day the Forter representment packet was filed on the contested-case ledger.

Issuer-close day — Day the issuer / network marked that Forter case closed.

FT lag days = issuer-close day − submit day. A fat FT lag days reading means chase packet prep or issuer queue on that Forter MID — blank chips stay blank.

Stops

Never invent FT lag days. Never drop alert-to-fight at-risk $ into submit/close columns. Never paste Ethoca filed/closed CSVs into Forter boxes. Never fuse MIDs when one Forter seat owns the open contested pile.

Related: Chargebacks, Ethoca lag, alert-to-fight lag, representment win.

Procedure

  1. Type filed day and closed day.
  2. Read FT lag days.
  3. Chase evidence / issuer queue when FT lag days are material.

Failure modes

  • Inventing FT lag days.
  • Loading alert-to-fight at-risk $ into filed/closed boxes.
  • Folding Ethoca lag into Forter boxes.

Worked example

None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.

Glossary

FT lag days
Closed day − filed day on one Forter representment cut.

Work with us — We run this job on your accounts. Services

FAQ

Is this Ethoca representment lag days?
Forter contested-case ledger vs Ethoca alert-desk fight export. [Representment lag days](/manuals/ethoca-representment-lag-days) stays on Ethoca. Submit / close days never leave Forter here.
Is this Forter alert-to-fight lag?
Case clock vs desk-wait dollars. [Alert-to-fight lag](/manuals/forter-alert-to-fight-lag) scores cases × AOV at-risk $. Here you only score issuer-close − submit days.
What FT lag days should I invent?
None. Read submit day and issuer-close day from the same Forter contested-case ledger.