← ClaudeAtlas

fortax-reconciliationlisted

Reconcile two sets of records that should agree and explain every difference before any adjustment - books vs return (GSTR-1/3B/2B vs registers, 26AS/AIS vs books), control account vs subledger (debtors, creditors, fixed asset register, stock), bank vs books, related-party / group balances, a trial balance that does not tie. Narrows the gap to rows, tests one cause at a time, categorises reconciling items, ages them and states what stays open. Typical asks - "difference nikalo", "2B aur books me farak kyun hai", "26AS match nahi ho raha", "TB tally nahi ho raha", "debtors ledger aur control account alag hai".
amit-voais/fortax-skills · ★ 1 · DevOps & Infrastructure · score 77
Install: claude install-skill amit-voais/fortax-skills
# Reconciliation — find the difference, then explain it Needs Python 3 and internet: runs `scripts/fortax.py` (the Fortax engine on ai.fortax.in; your file is processed and not stored). Verdict first: two records agree, or they differ by an exact amount made of named items plus an unexplained balance. This skill helps prepare the working; the CA reviews and signs it off. ## The rule **No adjustment before the cause is known.** A difference that is plugged, rounded away, or "adjusted to match" is not reconciled — it is hidden, and it will surface in a notice. This applies hardest when the difference is small. A Rs 118 gap is a wrong tax rate somewhere; a Rs 1 gap is a rounding rule you have not identified yet. Size is not evidence of harmlessness. ## Use an engine where one exists | Pair | Do this | |---|---| | GSTR-2B vs purchase register | `fortax-gstr2b-reconciliation` (`fortax.py gstr2b`) — it matches; you judge its `_pairs_to_judge.json` | | GSTR-1 / 3B vs sales register | `fortax-gstr1-and-3b` (`fortax.py gstr1`) | | Bank statement vs books | `fortax-bank-statement-to-books` (`fortax.py bank`, then its BRS part) | | Everything else | this skill, with the matching done in a script or a workbook with formulas (`fortax-xlsx-manipulation`) | Numbers come from code: never add a column, compute a difference or count items by eye. ## When to use Any two records that should agree and do not: - GSTR-2B against the purchase register; GSTR-1 against the sales register; 3