The textile ERP that knows yarn and audits itself.

Yarn takes up water in humid air and gives it back in dry air. You keep a regain table per fibre and per SKU — dated defaults of 8.5% for cotton and 0.4% for polyester, to be checked against your mill contracts. Meter readings at receipt and at count are optional; nothing new is mandatory on the godown floor. Each count line shows book kg, expected moisture drift, unexplained kg and a classification, and the shrinkage report shows unexplained loss in kg and rupees by godown, fibre, month and by who counted. How a posted count adjusts stock is unchanged.

Where it stops: It shows unexplained loss for you to review; it does not say why it happened. A carton-only count cannot show drift, and a line with no meter reading assumes standard regain and says so. It is a model built on hand-held readings, not a lab conditioning test.

Short weight is argued on conditioned (commercial) weight: weighed weight × (1 + agreed regain) ÷ (1 + measured regain). A claim inside your tolerance is refused rather than raised, because a rejected claim costs credibility on the next one. It is valued at the purchase-order price where that is comparable, and the printed note shows every step for the mill to check.

Where it stops: The result is only as good as the meter reading and the regain you agreed with the mill. Formal disputes are settled by laboratory testing.

Every cheque received or issued moves in hand → deposited → cleared or bounced → re-presented, and each move is checked so an impossible one is refused. The deposit diary shows what to bank and when; staleness is checked against the three-month validity. Clearing a received cheque records the customer's payment exactly once — a double tap cannot create two. A bounce reverses that payment by marking it, keeps the history and records charges recoverable from the drawer, then computes the notice, payment and complaint dates. The bounce count shows on the customer's page and next to their name on the sell screen; if it cannot be read it says “unknown”, never “clean”.

The law it follows: Negotiable Instruments Act, 1881 — s.138 (notice within 30 days of the return memo; 15 days to pay) and s.142(1)(b) (complaint within one month after). Cheque validity: three months, RBI, from 1 April 2012.

Where it stops: It tracks the dates; it does not send notices or advise on a case. Not legal advice, and the screen says so.

Brokerage in all three conventions used in yarn markets — % of value, Rs per kg, Rs per bag — on a sale or a purchase order. It is computed per deal from the saved sale or PO rather than stored, and a deal whose brokerage cannot be computed says so instead of guessing. Payouts suggest TDS from dated rates you can edit. Each dalal's page shows deals, volume, customers introduced, how many cheques those customers bounced and what they still owe.

The law it follows: Income-tax Act, 1961, s.194H — 2% from 1 October 2024, above Rs 20,000 a year from 1 April 2025.

Where it stops: The TDS figure is a suggestion; the person recording the payout can change it, and whether you must deduct at all depends on your own turnover.

A cash receipt that would take one customer to Rs 2 lakh or more in a day, or against one bill, is blocked on the receipt form; an admin can override only with a written reason, kept on an append-only log. Cash paid to a mill or on an expense above the s.40A(3) limit is warned and the acknowledgement recorded. The MSME screen lists, bill by bill, which micro and small mills must be paid by when, and the 31 March exposure if they are not. Every threshold is dated and editable.

The law it follows: Income-tax Act, 1961 — s.269ST with s.271DA, s.40A(3), s.43B(h); MSMED Act, 2006 — s.15 (45 days at most, 15 without agreement) and s.16 (interest at three times the RBI bank rate, monthly rests).

Where it stops: The “one event or occasion” limb of s.269ST cannot be worked out from data, and the form says so. A supplier registered on Udyam as a trader is treated as not covered — confirm with your CA. Not legal or tax advice.

Every morning 18 checks run against your own books: gaps and out-of-order dates in the GST invoice series, cash receipts at the s.269ST limit, cash payments above s.40A(3), MSME bills heading past 43B(h), e-way bills split to stay under the threshold, duplicate bills, back-dated entries, sales below the damage-adjusted floor, credit-limit breaches, cancellations and stock adjustments, yarn shrinkage, repeat cheque bouncers, s.138 deadlines, related parties, dalal brokerage anomalies, round-sum cash expenses, and a Benford first-digit test. Each finding names the transactions behind it and the money at stake. It closes only with a written note from someone who did not make the entry — the database enforces that, not the screen.

The law it follows: CGST Rules, 2017 — rule 46(b) and rule 138; Income-tax Act, 1961 — s.269ST, s.40A(3), s.43B(h); Negotiable Instruments Act, 1881 — s.138. Every threshold is a dated default your admin can change.

Where it stops: It flags patterns for review; it is not an audit opinion and never says anything is fraud. Many findings will have innocent explanations — the point is that the explanation is written down before your CA asks. A check that could not run (a missing table, too little data for Benford) is shown as could-not-run, never as clean.