- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2 hours ago
Disputes Content Pack for US Regulations
Objective
The Disputes Content Pack for US Regulations [sn_disp_reg_cp_us] is mandatory for any US financial institution processing card or ACH disputes. It delivers the eight SLA definitions that enforce Reg E and Reg Z regulatory deadlines directly on dispute cases and tasks. Without it, the platform has no mechanism to track compliance timelines. This article explains what each SLA covers, how the platform applies them, and the key fields that drive SLA calculation. For the full list of content packs and the installation sequence, see FSO Disputes Content Pack for Card Network Rules.
Overview: Reg E and Reg Z
US financial institutions processing card and ACH disputes are subject to two primary consumer protection regulations:
- Regulation E (Reg E): governs electronic fund transfers (EFT), including debit card transactions, ATM withdrawals, ACH debits, and transactions from checking and savings accounts. It mandates specific timelines for provisional credit issuance, investigation completion, and written communication to cardholders.
- Regulation Z (Reg Z): governs credit card transactions under the Truth in Lending Act (TILA). It requires institutions to acknowledge billing error disputes and complete investigations within defined billing cycle windows.
What the Content Pack Installs
The Disputes Content Pack for US Regulations installs eight SLA definitions that automatically attach to dispute cases and tasks based on account type and the Dispute Reported Date. No new tables are added, as SLAs attach to the existing Card Disputes Service Case and Card Disputes Task tables.
| SLA Definition | Applied To | Description |
|---|---|---|
| Reg E 10-day provisional limit | Card Disputes Task [sn_bom_credit_card_disputes_task] | Provisional credit must be issued within 10 business days of the dispute reported date. |
| Reg E 20-day provisional limit | Card Disputes Task | Extended 20-day provisional credit window for new accounts (under 30 days old). |
| Reg E 45-day resolution limit | Card Disputes Service Case [sn_bom_credit_card_disputes_service] | Full investigation must be completed and communicated to cardholder within 45 days. |
| Reg E 90-day resolution limit | Card Disputes Service Case | Extended 90-day resolution window for new accounts or POS transactions. |
| Reg E acknowledgement limit | Card Disputes Service Case | Written acknowledgement must be issued to the cardholder. Cleared when Acknowledgement Sent flag is set to Yes. |
| Reg E PC reversal limit | Card Disputes Task | Provisional credit reversal deadline when a dispute is denied after provisional credit was issued. |
| Reg Z acknowledgement limit | Card Disputes Service Case | Acknowledgement deadline for credit card disputes under Reg Z. |
| Reg Z resolution limit | Card Disputes Service Case | Credit card dispute resolution deadline: two complete billing cycles, not to exceed 90 days. |
How SLAs Are Applied
- SLA start time is calculated from the Dispute Reported Date field on the transaction record, set automatically when a transaction is selected during intake.
- Reg E SLAs apply to debit, checking, and savings account disputes. Reg Z SLAs apply to credit card disputes. The platform evaluates account type at submission to apply the correct SLA set.
- The Is New Financial Account? option activates the extended SLA tiers for Reg E (20-day provisional and 90-day resolution windows).
- Agents must set the Acknowledgement Sent flag after issuing the dispute acknowledgement to mark acknowledgement SLAs as complete.
- SLA breach and at-risk cases surface on the Dispute Manager Workspace dashboard, enabling proactive management of regulatory deadlines across the team queue.
What's Next
Related resources:
- Full content pack reference: Exploring the Dispute Content Pack for US Regulations (ServiceNow Docs)
- For all Dispute Rules Content Packs and installation order, see FSO Disputes Content Pack for Card Network Rules.
- For the SLA fields on case and task tables (Dispute Reported Date, Acknowledgement Sent, Is New Financial Account?), see FSO Disputes Data Model and Core Data Objects.
- For the Dispute Manager role responsible for SLA monitoring, see FSO Disputes Roles and Personas.
- For Card Data Security tokenization alongside regulatory SLA compliance, see Card Data Security and PCI Compliance.
Have questions about Reg E or Reg Z SLA configuration? Post them in the FSO Community Forum.