Results for “amount_in_dispute”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_DISPUTE_HISTORY is a Receivables (AR) module table in the AR schema that maintains an audit trail of invoice disputes recorded against individual payment schedules. Each row captures a discrete dispute event, including the disputed amount and the period during which the dispute was active, allowing organizations to reconstruct the full dispute lifecycle for any open or closed receivable. Because disputes frequently precede adjustments, credit memos, or write-offs, this table serves as a critical evidentiary record for collections and deduction management processes.

In Data Vault modeling terms, the mined foreign key structure suggests a satellite-leaning classification. The table's grain is tied to PAYMENT_SCHEDULE_ID, which references the parent hub-like AR_PAYMENT_SCHEDULES_ALL, while the descriptive attributes (amounts, dates, audit columns) behave as satellite content attached to that business entity. This classification is a heuristic suggestion rather than a documented design intent.

Key Information Stored

The table contains 13 documented columns. The surrogate primary key is DISPUTE_HISTORY_ID, enforced by AR_DISPUTE_HISTORY_PK and also backed by unique index AR_DISPUTE_HISTORY_U1. The most significant columns are:

• DISPUTE_HISTORY_ID — Surrogate primary key uniquely identifying each dispute history record.
• PAYMENT_SCHEDULE_ID — Foreign key to AR_PAYMENT_SCHEDULES_ALL, tying the dispute to a specific installment or payment schedule line.
• AMOUNT_DUE_REMAINING — The outstanding balance on the schedule at the time the dispute record was written.
• AMOUNT_IN_DISPUTE — The cumulative or referenced disputed balance associated with the schedule.
• DISPUTE_AMOUNT — The amount disputed for this specific history entry.
• START_DATE — The date the dispute became effective.
• END_DATE — The date the dispute was resolved or closed; a null value typically indicates an active dispute.
• CREATED_FROM — Indicates the source or channel through which the dispute record was created.
• CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the row was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns tracking the most recent modification.

Common Use Cases and Queries

Typical applications include collections aging analysis, deduction root-cause reporting, dispute resolution cycle-time measurement, and reconciliation of disputed balances against open receivables. A common query retrieves the current and historical disputes for a given customer's payment schedules:

• Reporting open disputes: filter on END_DATE IS NULL to isolate unresolved disputes and sum DISPUTE_AMOUNT.
• Linking to schedules: join AR_DISPUTE_HISTORY.PAYMENT_SCHEDULE_ID = AR_PAYMENT_SCHEDULES_ALL.PAYMENT_SCHEDULE_ID to retrieve customer, invoice, and due-date context.
• Cycle-time analysis: compute END_DATE - START_DATE per dispute to measure resolution duration by collector or customer.
• Trend reporting: group by CREATION_DATE or START_DATE to trend dispute volumes and amounts over time.
• Audit reconciliation: compare AMOUNT_DUE_REMAINING against AMOUNT_IN_DISPUTE to validate dispute balances.

Related Objects

• AR_PAYMENT_SCHEDULES_ALL — Parent table referenced by PAYMENT_SCHEDULE_ID; the primary join path for dispute context.
• AR_CASH_RECEIPTS_ALL and AR_CASH_RECEIPT_HISTORY_ALL — Cash application activity often linked to disputed schedules.
• AR_ADJUSTMENTS_ALL — Adjustments frequently written against disputes.
• RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL — Invoice headers and lines reached through the payment schedule.
• HZ_CUST_ACCOUNTS and HZ_CUST_ACCT_SITES_ALL — Customer identity referenced via the schedule's customer keys.

Because the documented metadata lists only one foreign key, joins beyond AR_PAYMENT_SCHEDULES_ALL are typically indirect and reached through the payment schedule's customer and transaction identifiers.