J1INCHLN — Create TDS Remittance Challan (India)

Tax deducted at source from vendor payments sits on TDS payable accounts until it is paid to the government. J1INCHLN collects the open deductions for a period and section, posts the remittance and creates the internal challan document that links each deduction to the payment. That link is what later allows certificates and quarterly returns to state which challan paid which deduction.

It is run monthly after period-end, before the statutory due date for depositing TDS. Accounts payable or the tax team runs it per company code and section code, often in a monthly close calendar together with the TDS payment itself. It is also used when correcting a missed or partial remittance.

Select company code, fiscal year, posting date range, section code and the withholding tax types or codes to include. Run in test mode, review the items picked up against the TDS payable balance, then post. Record the challan document number, because the bank details of the payment are entered against it with J1INBANK once the tax has been paid.

Before the run, the TDS payable balance for the section in FBL3N should equal the open deductions of the period. After the run those items are cleared by the challan clearing document. The deductions in table WITH_ITEM should then carry the challan reference, which is what return and certificate programs read later.

The India withholding tax functions remain available in S/4HANA as part of the country version for India, using extended withholding tax. Program names and options can vary with support packages, so follow the current India localization documentation.

Challan problems usually surface months later in return defaults.

Owned by the tax or accounts payable team responsible for TDS compliance. Treasury handles the actual payment to the government, and the monthly close calendar should show both steps with named people and the statutory due date.