Switched to ChatGPT Work and it’s a game-changer.
One prompt and it handles full workflows — competitor decks, proposals, analyses — using my files & style. Delivers polished, ready-to-ship work.
This is how AI should work. Loving GPT-5.6 agentic power. @OpenAI#ChatGPTWork
@thsottiaux@OpenAI I switched to GPT-5.6 Sol / Codex mainly because the Computer Use is a huge step up from Claude — it actually gets complex workflows, tool use, and long-running tasks right without constant hand-holding. Feels like real agentic coding finally works reliably. Loving it so far!
@DivaJain2 GST refund delay is effectively a working-capital cost—especially for small exporters already operating on thin cash buffers. Clean invoices, export evidence and reconciliation can reduce avoidable friction, but even perfect records cannot compensate for a slow refund process.
ICAI’s #AIS2026 asks: What should AI do in accounting?
At MoneyMistri, AI cuts busywork but never hides judgment. No blind autoposting.
Our GST invoice workflow: Extract ➔ Validate ➔ Highlight uncertainty ➔ Human approval ➔ Tally sync ➔ Verify.
Faster work, better proof.
Small GST update, real bookkeeping pain:
When bill-to and ship-to differ, those details cannot live in someone's memory.
Before the 1 Aug GSTN change, clean party masters: GSTIN/URP, state, PIN, delivery address.
Many portal errors start as messy invoice data.
GSTN's Ship-to GSTIN update is a good reminder that accounting AI gets judged on controls, not demo polish. In MoneyMistri, the concrete check is simple: if a purchase bill has a wrong GSTIN or tax split, it should be flagged before anything reaches TallyPrime. #buildinpublic
AIS2026 signals where accounting is heading: more AI, more automation, and more need for judgment. In GST workflows, automation should do the repetitive work, but it should still show uncertainty, preserve review, and prove what landed in TallyPrime.
@TaxationUpdates One-click import is useful for clean rows. The real test is what it does with mismatched GSTINs, invoice numbers, or totals. If those exceptions are not surfaced clearly, the speed is mostly cosmetic.
@tallysolutions That only works if the matching logic is explicit. Otherwise faster import just gets you to the wrong answer sooner. Validate GSTIN, invoice number, tax mode, and totals before posting.
Starting to build MoneyMistri more publicly.
Tiny lesson so far: invoice automation is not “OCR → done”.
For GST + Tally workflows, the real job is:
extract → validate GSTIN/tax/totals → human review → then post to Tally.
The review step is the product.
#buildinpublic
@MumbaiPolice my delivery due in 7 days in kota,Raj. My husband is stuck in Mum & been trying for a month to get permission but no success.I want my husband here at this crucial time and need your help in getting him here
@PMOIndia@uddhavthackeray@ashokgehlot51@PoliceRajasthan