Results for “payment_reference_id”

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

Overview

JAI_AP_TDS_PAYMENTS is a transactional table in the JA (Asia/Pacific Localizations) product family of Oracle E-Business Suite. It stores the details of TDS (Tax Deducted at Source) challans generated when an organization remits withheld tax to the tax authority on behalf of a vendor. The table therefore acts as the payment-side counterpart to the withholding capture performed in Oracle Payables, linking each remittance to the vendor invoice, the tax regime, and the Form 16 header used for Indian statutory reporting. The object is owned by the JA schema and is marked VALID in the ETRM repository, with a documented physical schema of 30 columns in Release 12.2.2. It is present in both 12.1.1 and 12.2.2, since the JA localization schema is shared across these releases.

The heuristic Data Vault classification mined from the foreign-key structure is link. This reflects the table's nature as an associative entity that resolves the relationships between vendors, invoices, tax codes, operating units, and statutory Form 16 records, rather than functioning as a standalone hub or descriptive satellite.

Key Information Stored

The most significant columns fall into four functional groups:

• Payment identification: CHECK_ID, CHECK_NUMBER, CHECK_DATE, CHECK_DEPOSIT_DATE, BANK_NAME, PAYMENT_AMOUNT, CURRENCY_CODE, and PAYMENT_REFERENCE_ID capture the instrument used to remit TDS to the authority, along with its bank, amount, and deposit date.
• Challan and tax attributes: CHALLAN_NO, BSR_CODE, TDS_SECTION, TDS_TAX_ID, TDS_TAX_RATE, TAX_AMOUNT, and FIN_YEAR record the statutory challan reference, the tax section under which the deduction was made, the applicable tax code and rate, the tax amount remitted, and the financial year.
• Party relationships: VENDOR_ID and VENDOR_SITE_ID identify the deductee, while TAX_AUTHORITY_ID and TAX_AUTHORITY_SITE_ID identify the tax authority receiving the payment; ORG_TAN_NUM holds the deductor's TAN.
• Linkage and audit columns: PARENT_INVOICE_ID and INVOICE_DATE tie the remittance to the underlying AP invoice, FORM16_HDR_ID links to the Form 16 header, OPERATING_UNIT_ID identifies the responsible organization, and the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) with OBJECT_VERSION_NUMBER provide auditability and optimistic locking.

CHECK_ID is the surrogate primary key in the documented schema. Business-key candidates include CHALLAN_NO combined with FIN_YEAR and the TAN, though the metadata does not document a named unique index on these columns; any such constraint should be verified against the deployed dictionary.

Common Use Cases and Queries

Typical usage centres on challan reconciliation, TDS liability reporting, and Form 16 preparation. A common query joins the table to AP invoices to trace tax withheld on a specific vendor invoice:

• Reconciling challans against bank statements using CHALLAN_NO, CHECK_NUMBER, and PAYMENT_AMOUNT.
• Reporting TDS remittances by section and financial year, grouping on TDS_SECTION and FIN_YEAR filtered by OPERATING_UNIT_ID.
• Populating Form 16 and Form 26Q extracts by joining FORM16_HDR_ID to JAI_AP_TDS_F16_HDRS_ALL.
• Auditing deductor TAN compliance via ORG_TAN_NUM and TAX_AUTHORITY_ID.

A representative join is:

SELECT p.CHALLAN_NO, p.TDS_SECTION, p.TAX_AMOUNT, i.INVOICE_NUM
FROM   JAI_AP_TDS_PAYMENTS p, AP_INVOICES_ALL i
WHERE  p.PARENT_INVOICE_ID = i.INVOICE_ID;

Related Objects

The following objects are the most significant dependencies, based on the documented foreign keys:

• AP_INVOICES_ALL via PARENT_INVOICE_ID — the underlying payables invoice.
• HZ_PARTIES via VENDOR_ID and TAX_AUTHORITY_ID — the deductee and the tax authority.
• HZ_PARTY_SITES via VENDOR_SITE_ID and TAX_AUTHORITY_SITE_ID — the respective party sites.
• JAI_CMN_TAXES_ALL via TDS_TAX_ID — the withholding tax code definition.
• JAI_AP_TDS_F16_HDRS_ALL via FORM16_HDR_ID — the Form 16 header for statutory reporting.
• HR_ALL_ORGANIZATION_UNITS via OPERATING_UNIT_ID — the responsible operating unit.