tds-booking-payment – Other skill for AI agents

TDS Booking & Payment

What it is: Tax deducted at source, deposited on time, filed and reconciled to the ledger.

Overview

Works out the smallest useful TDS Booking & Payment setup for the business in front of it, then

builds it only when asked. The default output is a short recommendation, not a

spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on

request, from one field list so they cannot drift apart.

Reconcile at least monthly. A deduction that is recorded at the time of payment and left

unreconciled until the return is due is how a liability drifts away from the challan.

This skill does not determine the rate that applies, does not file returns, and is not tax

advice. Rates and deadlines vary by country and change. The rate and the deadline come from

a qualified tax professional; this only holds the record.

Layer: Layer 6: Statutory. Fits: Starter stage. Table code: n/a.

When to Use This Skill

• tds register
• tds deposit tracker
• withholding tax log
• tds return working

Also use it when the user says "tax deducted at source, deposited on time, filed and reconciled to the ledger", or describes the same process happening in a

spreadsheet, a document or someone inboxes.

Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces

empty templates only - it never holds or processes real employee or customer data.

How It Works

No shared execution-contract file is bundled; follow this file’s empty-template scope and current host authorization rules. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

• "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
• "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
• "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
• "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

> Q: Which payments are you deducting TDS on today?

Step 2 - Ask only what is missing

Treat ambiguous replies as unanswered and ask which explicit option the user means. Record unknown values as Unknown; Unknown is not zero. A record must not be Done when a required check fails.

Skip anything the user already answered, in any earlier message. Ask the rest one at a

time, and stop as soon as the remaining answers would not change the output.

• Nature of payment - Which payment types are in scope? / How many vendors are affected? / Any thresholds?
• Rates - Where do the rates come from? / Are PANs collected? / Who confirms the rate?
• Deposits - How are you depositing? / Which account? / When is the next deadline?
• Returns - Who files? / Which periods? / Is it monthly or quarterly?
• Outcome - What do you need? / A deduction register, a deposit tracker or both?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless

they ask, and it never carries a value the user did not give.

module: tds-booking-payment
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Nature of payment": null
  "Rates": null
  "Deposits": null
  "Returns": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking

Step 4 - Recommend the smallest workflow

Build an already requested artifact without asking again. For advice-only requests, give a short recommendation and offer the relevant artifact.

Recommended approach: One record per deduction and payee, carrying the gross, the rate applied, the tax deducted, the deposit, the return and the reconciliation result for the period.

Why this one: TDS is four separate obligations - deduct, deposit, file, reconcile - and they fail in different places. One record per deduction keeps all four on the same row so a missed deposit shows up as a status, not as a surprise at filing time.

Workflow: Transaction identified → Rate applied → TDS deducted → Ledger updated → Deposited before the deadline → Return filed → Ledger reconciled at least monthly

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the

requested artifacts. For machine-readable text, keep prose outside the data; for files,

provide a usable link. Report material validation failures or limitations separately.

**A selected Notion output is rendered by notion-manual-import, so route the

Notion step there.** When the user selects Notion, hand that step to

@notion-manual-import: it holds the CSV, the property

mapping, the import steps and the verification checklist, and it renders the Field

Reference below instead of defining a table of its own. Do not restate the mapping

here and do not improvise the import steps. Manual CSV and mapping outputs need no

connection. For requested workspace changes, follow the shared contract: verify actual

tool access and the target before writing. A user saying "connected" is not tool evidence.

Never ask for a Notion password or token.

TDS Record Number,Tax Period,Nature of Payment,Payee Name,Payee PAN,Transaction Reference,Payment Date,Gross Payment/Base,TDS Rate %,TDS Deducted,Deducted On,TDS Payable Ledger,Deposit Date,Challan/Bank Reference,Amount Deposited,Return Filed Date,Return Reference,Ledger Reconciliation,Variance Amount,Reconciliation Frequency,Prepared By,Reviewed By,Status,Notes,TDS ID
TDS-2026-0194,2026-08,Professional Fees,Pixelworks Studio,PAN-MASKED-EXAMPLE,EXP-2026-0338,2026-08-18,32500.00,10,3250.00,2026-08-18,TDS Payable - Professional Fees,2026-09-15,CHL-2026-0912,2925.00,2026-10-15,TDS-Q2-2026-PF,Variance,325.00,Monthly,Sneha Iyer,Vikram Singh,In progress,Synthetic allocation: deducted 3250.00 minus deposited allocation 2925.00 leaves 325.00 pending; no legal timeliness or filing acceptance asserted.,TDS-001

CREATE TABLE tds_booking_payment (
  tds_record_number VARCHAR(255) NOT NULL UNIQUE,
  tax_period VARCHAR(255),
  nature_of_payment VARCHAR(100) NOT NULL,
  payee_name VARCHAR(255),
  payee_pan VARCHAR(255),
  transaction_reference VARCHAR(255),  -- relation -> target record
  payment_date DATE NOT NULL,
  gross_payment_base NUMERIC(14,2),
  tds_rate_pct NUMERIC,
  tds_deducted NUMERIC(14,2),
  deducted_on DATE,
  tds_payable_ledger VARCHAR(255),
  deposit_date DATE,
  challan_bank_reference VARCHAR(255),
  amount_deposited NUMERIC(14,2),
  return_filed_date DATE,
  return_reference VARCHAR(255),
  ledger_reconciliation VARCHAR(100) NOT NULL,
  variance_amount NUMERIC(14,2),
  reconciliation_frequency VARCHAR(100) NOT NULL,
  prepared_by VARCHAR(255),
  reviewed_by VARCHAR(255),
  status VARCHAR(100) NOT NULL,
  notes TEXT,
  tds_id VARCHAR(255) PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_tds_booking_payment_status ON tds_booking_payment (status);

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "TDS Booking & Payment",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "TDS Record Number": { "type": "string" },
      "Tax Period": { "type": "string" },
      "Nature of Payment": { "type": "string" },
      "Payee Name": { "type": "string" },
      "Payee PAN": { "type": "string" },
      "Transaction Reference": { "type": "string" },
      "Payment Date": { "type": "string", "format": "date" },
      "Gross Payment/Base": { "type": ["number", "null"] },
      "TDS Rate %": { "type": ["number", "null"] },
      "TDS Deducted": { "type": ["number", "null"] },
      "Deducted On": { "type": "string", "format": "date" },
      "TDS Payable Ledger": { "type": "string" },
      "Deposit Date": { "type": "string", "format": "date" },
      "Challan/Bank Reference": { "type": "string" },
      "Amount Deposited": { "type": ["number", "null"] },
      "Return Filed Date": { "type": "string", "format": "date" },
      "Return Reference": { "type": "string" },
      "Ledger Reconciliation": { "type": "string" },
      "Variance Amount": { "type": ["number", "null"] },
      "Reconciliation Frequency": { "type": "string" },
      "Prepared By": { "type": "string" },
      "Reviewed By": { "type": "string" },
      "Status": { "type": "string" },
      "Notes": { "type":

… (full content is in the download package)