Keep a disputed company-card purchase moving from evidence collection to a verified issuer outcome. Separate a submitted claim, a temporary credit and a financially closed case.
A cardholder reports a duplicate charge. Finance collects a receipt, marks the expense as disputed and waits for a refund. Weeks later, nobody can find an issuer case number. The internal task was completed, but the external dispute was never confirmed.
A corporate card dispute workflow controls that gap. It connects the original purchase, the disputed amount, the merchant conversation, the issuer case and the accounting outcome. It is for finance teams managing company-paid purchase cards, not merchants defending customer chargebacks.
The controls below are recommended operating practices. Your current business-card agreement, programme instructions and issuer case notices determine submission requirements, deadlines and payment treatment. Do not import consumer-card protections or another issuer’s timetable into your programme.
Classify the problem before choosing the route
Start with the original posted transaction and the cardholder’s account of what happened. A missing receipt, an unauthorized internal purchase and a transaction made by an unknown person are different problems. A policy violation does not by itself establish a valid issuer dispute.
Chase’s dispute guidance distinguishes recognized charge errors from activity not authorized by an account user. It also advises retaining merchant-contact details and contacting the issuer immediately for suspected unauthorized use. Use that distinction to triage the case, while following your own programme’s reporting route.
- Evidence problem: the purchase may be valid, but documentation is missing. Follow the receipt-recovery and expense-review process.
- Recognized charge error: identify the exact issue, such as duplicate billing, a different amount or an unreceived credit. Preserve merchant correspondence.
- Suspected unauthorized use: escalate promptly to the card administrator and issuer through the verified channel. Do not wait for the ordinary merchant-response queue.
- Commercial disagreement: retain the agreement and delivery evidence. The issuer determines whether its dispute process applies; an internal complaint is not a guaranteed recovery.
Keep authorizations distinct from posted charges. Ask the issuer how to handle a pending transaction rather than representing a pending amount as an accepted dispute. The company’s credit card policy should identify the authorized reporter and backup owner.
Create one case for the disputed amount
Assign an internal case ID linked to the issuer transaction reference. Record the full charge and the disputed portion separately. A £300 disagreement on a £1,200 purchase is not automatically a dispute over the entire £1,200.
The minimum case register should include:
- Company entity, programme, masked card identifier, merchant and transaction reference.
- Purchase date, posting date, statement reference, original amount/currency and disputed amount/currency.
- Reason, factual chronology, requested remedy and evidence links.
- Cardholder, case owner, authorized issuer submitter, finance reviewer and backup.
- Issuer deadline, its source, relevant time zone, internal preparation deadline and next action date.
- Merchant contact and promised credit; issuer case number, submission acknowledgement and later evidence requests.
- Every credit or reversal, whether temporary or final, its reference and accounting review.
Keep full card details and sensitive documents in the approved secure channel, not a widely shared tracker. Store only what each role needs. Preserve original documents and add dated corrections instead of rewriting the chronology.
Use evidence gates, not a single “disputed” status
| State and owner | Evidence needed to advance | Exception and recovery |
|---|---|---|
| Reported — cardholder and administrator | Original transaction, amount in question and factual reason; urgent unauthorized-use route assessed. | Unknown descriptor: investigate with authorized users; suspected compromise goes promptly to issuer/security handling. |
| Preparing — case owner | Reason-specific packet, merchant history, current issuer requirements and sourced deadline. | Missing evidence: assign a supplier, delivery or cardholder follow-up. Escalate deadline risk without inventing proof. |
| Reviewed — finance reviewer | Amount and narrative agree with documents; authorized submitter and submission channel confirmed. | Changed claim or partial amount: return for review with the revised basis visible. |
| Submitted — authorized submitter | Issuer acknowledgement, submission time, case reference and copy of what was actually sent. | No acknowledgement: verify receipt through the issuer. Do not assume an internal approval or uploaded file opened the case. |
| Under review — case owner | Current issuer status, evidence requests, response deadlines and confirmed supplementary submissions. | Request unanswered or case rejected: escalate to the authorized owner; use only permitted further review routes. |
| Outcome received — finance and accounting | Issuer decision, all merchant/issuer credits and reversals, remaining amount and approved accounting treatment. | Temporary credit or conflicting credits: retain an open financial exception until disposition is established. |
| Closed — independent reviewer | Final case outcome, transaction/credit linkage, ledger references and documented residual treatment. | Later reversal or new evidence: reopen the linked case and require renewed review, not a silent balance edit. |
Closing the evidence task is not the same as closing the issuer case. Likewise, a final issuer decision is not proof that the resulting credit was posted correctly in the ledger.
Prepare the packet for the actual dispute reason
Match the documents to what you are asserting
A duplicate-charge case needs the transaction references and evidence explaining why both charges relate to one purchase. An incorrect-amount case needs the agreed amount and the charged amount. For a cancellation or unreceived credit, retain the relevant terms, cancellation/return record, merchant response and any promised credit details.
Citi’s commercial-card dispute form illustrates reason-specific questions and separate transaction and dispute amounts. It is an older published form, not authority to use its historical submission details for your current programme. Obtain the current required form or online instructions from your issuer.
Write a short factual chronology that the documents support. Distinguish what the cardholder observed from what the merchant promised and what the issuer confirmed. Do not label a recognized purchase as unauthorized simply because the merchant has not resolved a complaint.
Protect the issuer deadline during merchant follow-up
Merchant resolution and issuer preparation can run in parallel. Record the merchant’s response date, but do not assume it extends the issuer’s filing window. Ask the authorized issuer contact what must be submitted and when, and retain that answer.
Citi’s corporate quick-reference guide shows that selecting a reason may trigger additional document instructions. A submitted online screen therefore should not be treated as proof that every required supporting step is complete. Follow the current case-specific instructions.
Track the external case and every financial movement
Keep a dated log of issuer acknowledgements, requests, responses and decisions. Verify that a supplementary file was sent to the correct case and retain receipt evidence. For example, Chase’s submission and tracking instructions describe separate actions for opening a dispute and viewing its status. Your workflow should preserve the same operational distinction, whatever interface your issuer uses.
Accounting should keep the original charge visible and determine its treatment while the dispute is unresolved. Treasury follows the applicable statement-payment instructions; an employee’s dispute report is not an authorization to reduce the issuer payment. Obtain programme-specific guidance rather than assuming every business card receives the same payment relief.
For each adjustment, record source, amount, date, reference and finality. A merchant’s promise, a posted merchant refund and a temporary issuer credit are three different pieces of evidence. If two credits concern the same disputed amount, notify the issuer through the approved channel and obtain instructions before treating both as final recovery.
Worked example: two credits do not prove double recovery
Illustrative example, USD; no fees or currency effects. A company has a $1,200 posted purchase. It accepts $900 of the charge but disputes a $300 overcharge. The case packet supports only that $300 difference.
- The authorized submitter obtains an issuer case reference for $300 and saves the submission acknowledgement.
- The issuer posts a $300 credit identified in the case notice as temporary. Finance records that status; the case is not financially closed.
- The merchant later posts a separate $300 refund for the same overcharge. The account now shows $600 of credits against a $300 issue.
- The case owner sends both credit references to the issuer and requests the correct disposition. Accounting retains the extra $300 as an unresolved reconciliation item under its approved treatment, not assumed savings.
- If the issuer subsequently reverses its temporary $300 credit, the adjustments net to the intended $300 recovery: $300 + $300 − $300. The resulting net purchase is $900.
The reversal in step five is a hypothetical outcome, not a promise about issuer behaviour. If the actual decision differs, record that decision and resolve the remaining balance accordingly. Close only after the issuer outcome, posted transactions and approved ledger treatment agree.
Where Workhint fits
The coordination work sits between cardholders, reviewers, the authorized issuer submitter and accounting. Workhint’s Workflow Engine describes approval routing, roles and required information or files before a step advances. Those capabilities are relevant to organizing a dispute-evidence packet and its internal review.
The Workflow Automation Software solution describes forms, review stages, owners and next actions across teams. The matrix above is a proposed workflow design to validate in your implementation, not a claim that a prebuilt card-dispute module exists.
These pages do not establish native issuer-case submission, card feeds, deadline interpretation, credit finality decisions or automatic ledger postings for this process. Keep issuer actions and accounting records in their authorized systems and bring back their evidence before advancing the coordination task.
Frequently asked questions
Who should submit a corporate-card dispute?
The person authorized under the actual card programme. Finance can prepare and review the packet without assuming it has permission to act as the cardholder or programme administrator.
Does a merchant refund close the issuer case?
Not automatically. Give the issuer the refund reference and follow its instructions for the existing case. Verify any temporary credit or later reversal before financial closure.
Can a dispute cover only part of a purchase?
Record the exact disputed portion and ask the issuer how to submit it. Keep the original charge intact and do not enlarge the claim to match a convenient statement amount.
What if the issuer rejects the claim?
Retain the decision and route any permitted review or new evidence to the authorized owner. Accounting determines the remaining balance and posting treatment. Do not mark the amount recovered merely because the internal investigation is complete.

Leave a Reply