CommunityCoding & Developmentgithub.com

parinshahAIbuilder/india-finance-agent-skills

Test an Indian company's trade payables and vendor payments against the MSMED Act 2006 payment deadlines (15 days, or up to 45 days by written agreement) and Section 43B(h) of the Income-tax Act. Returns overdue micro and small enterprise dues, the 43B(h) disallowance at year end, Section 16 compound interest (three times the RBI bank rate), the Schedule III / Section 22 MSME disclosure note, payables ageing in the Schedule III format, MSME Form 1 data, and a payment-priority list. Ends with a SAFE / PAY-BEFORE-31-MARCH / DISALLOWANCE verdict. Use whenever the user mentions MSME payables, 43B(h), Udyam vendors, 45-day rule, MSME interest, MSME Form 1, MSME disclosure in financial statements, or trade payables ageing, even if no section is named.

What is india-finance-agent-skills?

india-finance-agent-skills is a Claude Code agent skill that test an Indian company's trade payables and vendor payments against the MSMED Act 2006 payment deadlines (15 days, or up to 45 days by written agreement) and Section 43B(h) of the Income-tax Act. Returns overdue micro and small enterprise dues, the 43B(h) disallowance at year end, Section 16 compound interest (three times the RBI bank rate), the Schedule III / Section 22 MSME disclosure note, payables ageing in the Schedule III format, MSME Form 1 data, and a payment-priority list. Ends with a SAFE / PAY-BEFORE-31-MARCH / DISALLOWANCE verdict. Use whenever the user mentions MSME payables, 43B(h), Udyam vendors, 45-day rule, MSME interest, MSME Form 1, MSME disclosure in financial statements, or trade payables ageing, even if no section is named.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/parinshahAIbuilder/india-finance-agent-skills/tree/HEAD/msme-43bh-payables-gate

Installed? Explore more Coding & Development skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

MSME 43B(h) Payables Gate

You are a payables compliance reviewer for an Indian company. Your job: find every rupee owed to a micro or small enterprise that is past its legal due date, quantify the tax and interest cost, and produce the disclosures the auditor will ask for.

Status line (always first)

VERDICT: <SAFE | PAY-BEFORE-31-MARCH | DISALLOWANCE> | Overdue MSE dues ₹<x> | 43B(h) at risk ₹<y> | MSMED interest ₹<z> | As at <date>

  • SAFE: no micro/small dues past the due date.
  • PAY-BEFORE-31-MARCH: overdue dues exist, but paying them within the previous year still saves the deduction (the run date is before 31 March).
  • DISALLOWANCE: the year has closed with overdue MSE dues unpaid. They are added back this year and allowed in the year of payment.

Rules the skill applies

  • Who is covered: suppliers with a Udyam registration classified as micro or small. Medium enterprises are outside 43B(h) (MSMED interest still applies to them under the Act, but they are reported separately). Traders (wholesale/retail) registered through Udyam are treated as outside the delayed-payment chapter. Flag them, and let the user confirm.
  • Due date (MSMED Act s.15): payment by the agreed date, never later than 45 days from the day of acceptance or deemed acceptance. With no written agreement: 15 days. If acceptance dates are not given, use the invoice date or GRN date, whichever is later, and say so.
  • Section 43B(h): an amount payable to a micro/small enterprise that is unpaid past the s.15 deadline at year end is deductible only in the year it is actually paid.
  • Interest (s.16): compound interest with monthly rests at three times the bank rate notified by RBI, from the day after the due date. Ask for the bank rate to use, or state the one you used and its date. Interest is not tax-deductible (s.23).
  • Supplier status date: the classification counts as on the date of the transaction. A vendor that registered on Udyam after the invoice is out of scope for that invoice. Flag this when the registration dates are given.

Inputs

Required: open-item payables or the purchase register with vendor, invoice no, invoice date, amount, and the payments with their dates and the invoices they settle. Vendor master with Udyam number and category (micro/small/medium/none). Optional: GRN / acceptance dates, agreed credit terms per vendor (with whether they are in writing), RBI bank rate, the prior-year 43B(h) disallowance schedule (for payments made this year, which are now allowable).

If the Udyam category is missing for a vendor with a large balance, list them under "Need data". Do not assume their status.

Steps

  1. Tag each vendor: Micro / Small / Medium / Not MSME / Trader / Unknown.
  2. Compute the due date per invoice (agreed written terms capped at 45 days; otherwise 15 days).
  3. Apply payments FIFO unless the payment data names the invoice. Record partial payments.
  4. For each invoice: days to pay (or days outstanding as at the run date), days overdue, the overdue amount, and the s.16 interest.
  5. 43B(h) test at the year end (31 March): unpaid MSE amounts past their due date → disallowance. Amounts not yet due at 31 March are not disallowed. Watch for invoices whose 45 days run past 31 March.
  6. Reversal schedule: prior-year disallowed amounts paid this year → deductible this year.
  7. Payables ageing (Schedule III): outstanding for < 1 yr, 1–2 yrs, 2–3 yrs, > 3 yrs, from the due date of payment (or the transaction date if there is no due date), in the rows MSME / Others / Disputed dues – MSME / Disputed dues – Others.
  8. MSMED s.22 disclosure: (i) principal and interest due and unpaid at year end; (ii) interest paid under s.16 with the payments made beyond the due date; (iii) interest due and payable for delays where the principal was paid late but the interest was not; (iv) interest accrued and unpaid at year end; (v) further interest due in succeeding years until it is actually paid.
  9. MSME Form 1 (half-yearly, MCA): vendor-wise amounts outstanding for over 45 days, with the reasons. Applies to companies whose MSE dues exceed 45 days.

Output

  1. Excel workbook MSME_43Bh_<Entity>_<date>.xlsx, formulas live:
    • Summary: the verdict figures, the disallowance, the interest, and payments due in the next 15 days.
    • Invoice_Test: every invoice with category, terms basis, due date, paid date, days overdue, interest, 43B(h) flag, and source row.
    • Ageing_ScheduleIII, Sec22_Disclosure, MSME_Form1, Reversal_PriorYear.
    • Pay_Priority: unpaid MSE invoices sorted by due date, then amount, with the cumulative cash needed.
  2. Draft disclosure note in Ind AS / Schedule III language, ready for the notes to accounts.
  3. Chat summary: status line, top 10 vendors by overdue amount, and the cash needed before 31 March to avoid disallowance.

Final pass

  • Overdue + not-yet-due + paid = total MSE purchases in the period.
  • Check 3 interest calculations by hand.
  • Confirm that the ageing total equals the payables ledger balance.
  • Check that no medium enterprise or trader is in the 43B(h) figure.

Cannot verify

  • Need data: Udyam category or registration date for the listed vendors, written agreements for credit terms over 15 days, acceptance dates.
  • Need decision: disputed invoices (excluded from overdue only if a genuine dispute is documented), trader status.

Limits

This is a review aid, not legal or tax advice. Classification and acceptance dates drive the answer, so confirm them. Bank rate and Udyam status come from the user. The skill makes no external calls.

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

parinshahAIbuilder/india-finance-agent-skills

Reconcile a bank book (Tally, SAP, Zoho, Busy or any ERP ledger export) against the bank statement (PDF, Excel or CSV from any Indian or international bank) and produce a classic Bank Reconciliation Statement, matched and unmatched items, cheques issued not presented, deposits not credited, bank charges, interest, NACH/ECS/UPI/NEFT items not in the books, duplicate entries, stale cheques over three months, and suggested journal entries. Ends with a RECONCILED / RECONCILED-WITH-ITEMS / DOES-NOT-CLOSE verdict. Use whenever the user mentions BRS, bank reconciliation, bank book vs statement, unreconciled entries, month-end bank tie-out, or "why doesn't my bank balance match", even if the bank is not named.

parinshahAIbuilder/india-finance-agent-skills

Turn a budget file and an actuals file (GL, trial balance or MIS, single entity or branch-wise / cost-centre-wise / region-wise) into a Budget vs Actual pack, with month and year-to-date variances, favourable/adverse flags that respect the sign of revenue vs cost, price/volume/mix splits where units are given, a full-year re-forecast, and management commentary that explains each material variance in one or two plain-English sentences backed by the numbers. Ends with an ON-TRACK / WATCH / ACTION-NEEDED verdict per branch and overall. Use whenever the user mentions budget vs actual, BvA, variance analysis, MIS commentary, branch-wise performance, cost-centre review, re-forecast, or "why are we over budget", even if no template is given.

parinshahAIbuilder/india-finance-agent-skills

Reconcile an Indian purchase register (Tally, SAP, Zoho, Busy or any ERP export) against GSTR-2B / IMS downloads and return matched, mismatched, missing-in-2B and missing-in-books invoices, the ITC at risk in rupees, Rule 37 / 37A / Section 16(4) / Section 17(5) exposure, and vendor follow-up emails. Ends with a CLAIM / CLAIM-WITH-HOLD / DO-NOT-FILE verdict for the GSTR-3B. Use whenever the user mentions GSTR-2B, 2A, IMS, ITC reconciliation, input tax credit mismatch, purchase register vs GST portal, vendor not filed GSTR-1, or "how much ITC can I claim this month", even if no rule is named.

parinshahAIbuilder/india-finance-agent-skills

Scan a full general ledger or day book export (Tally, SAP, Oracle, Zoho, Busy, or any ERP) for the journal-entry red flags that auditors test under SA 240 / ISA 240 and SA 330, and that Section 143(3)(i) internal financial control reviews look for. Flags entries posted on weekends, holidays or after hours; round amounts; just-below-approval-limit amounts; manual entries to revenue, cash or suspense; unusual account pairings; entries by unexpected or senior users; back-dated or post-close entries; reversals right after period end; duplicate entries; Benford's-law anomalies; and entries with missing or one-word narrations. Scores every entry, ranks the riskiest, and returns a sample with selection rationale. Ends with a LOW / ELEVATED / HIGH risk verdict. Use whenever the user mentions JE testing, journal entry testing, management override, fraud risk, ledger scrutiny, day book review, CARO / IFC testing, or "check the ledger for anything unusual", even if no standard is named.

Related Skills