CheersagarGarment manufacturing and trade
Cheersagar keeps its books in Zoho and its customer relationships in an internal CRM. We built the layer between them on FastAPI and PostgreSQL: the integrations, the reporting the business runs on, and an AI layer that writes the read on a number without ever producing the number. Job work reconciliation software and fabric valuation reporting are the two halves that decide whether a margin figure survives scrutiny.
Build fingerprint
Where it runs, how we engaged, and what it was built on.
Technologies
What makes this problem genuinely hard - before any client name enters the page.
Under Section 143 of the CGST Act a principal sends inputs or capital goods to a job worker without paying tax. They travel on a delivery challan under Rule 45, not an invoice, so the system has to issue a document that carries quantity and value but posts no revenue. Returns are declared in ITC-04, half yearly above 5 crore aggregate turnover and annually at or below. Inputs have one year to come back and capital goods three, or the dispatch is deemed a supply.
Textile and apparel job work sits at a concessional 5 percent under SAC 9988, while residual job work went to 18 percent under the two slab change effective 22 September 2025. Garments are 5 percent up to 2,500 rupees per piece and 18 percent above. The threshold is per piece, so one invoice line can cross it while the line under it does not, and rate has to resolve from unit price at posting.
E-invoicing applies from 5 crore aggregate annual turnover, and since 1 April 2025 taxpayers at 10 crore and above have 30 days to report a document to the IRP, after which no IRN is issued. E-way bills are needed above 50,000 rupees, including challan based job work movement, which most generic ERPs never emit.
Closing stock has to cover work in progress mid line with partial labour absorbed, goods at a third party, and fabric in transit. Consumption posts at actual issue against a cut order. Backflushing on finished goods receipt back-calculates from standard, erasing every yield variance the season had to teach.
Cheersagar keeps its books in Zoho and its customer relationships in an internal CRM that predates the accounting move, and neither system knew the other existed. Any question crossing the two, which style is earning, which customer is slow, how this month reads against the last, meant exporting from both and joining by hand in a spreadsheet. The second problem was that nobody wanted a new place to look: the people who need these numbers are not the people who log into either system, and a garment business runs on a morning figure rather than an interactive one. So the brief was not a dashboard. It was to make the joined view exist, keep it current, and put a defensible read on top of it.
One service owns everything that talks to Zoho: invoices, sale orders, credit notes, customers. It holds the OAuth refresh, so no other part carries a credential and rotating access is one change.
The CRM holds what the accounting entries do not explain: who the customer is to the business, what was agreed, what is in flight. That is what turns a ledger row into something a person can act on.
Accounting and CRM extracts land in one schema and join there, so reports read from a shape designed for reporting rather than two systems designed for transactions.
The figures are computed first. The model then reads a completed row set and writes what moved, what it means and what to look at. It never produces the number it describes.
Tradeoffs
Every choice closed off something else. Those costs are stated, not hidden.
Instead of: A ledger inside the product, with Zoho as one more destination. Statutory accounting has to live where the returns are filed from, and a second ledger creates a reconciliation nobody asked for.
What we acceptedEvery figure the platform shows is a derived copy, only as fresh as its last sync, so a report compared against Zoho mid afternoon can differ without either being wrong.
Instead of: Letting the model query and calculate. A language model drafts good narrative over a number that is already correct. It is not an arithmetic engine, and a wrong figure in a finance report costs more than a missing paragraph.
What we acceptedEvery number the commentary might cite has to exist before the model runs, so a new angle of analysis means a new aggregate, not a new prompt.
Instead of: Each system reporting on itself, the join left to the reader. Every question worth asking crosses the two, and a join repeated per report is a join that disagrees with itself.
What we acceptedA Zoho customer to CRM account mapping somebody has to maintain. When it drifts, the failure is a quietly missing row rather than an error.
Reusable
Most accounting packages can only emit an invoice.
| Movement | Document | Rate | Also required |
|---|---|---|---|
| Inputs out to a job worker | Delivery challan, Rule 45 | No tax on the movement | E-way bill above 50,000; ITC-04 as sent |
| Processed goods returning | Challan against the original | No tax | ITC-04 as received; back in one year, three for capital goods |
| Job work billed back | Job worker's tax invoice | 5 percent textile and apparel, SAC 9988; 18 percent residual | Nothing further |
| Garment sold, 2,500 rupees or less per piece | Tax invoice | 5 percent | IRN from 5 crore AATO |
| Garment sold, above 2,500 rupees per piece | Tax invoice | 18 percent | IRN from 5 crore AATO |
Row one is where stock leaves the books entirely if the system can only emit invoices.
Delivery
Capabilities delivered and the scope of the build - not results attributed to it.
Capabilities
Scope
Scope of the build, not results attributed to it.
Bring us the part you think is hardest.
Zoho authentication and token refresh sit in one service, so rotating access is one change in one place.
Zoho stays the book of record and the reporting model is a derived copy, so a disputed figure is settled in Zoho, never in a report.
What transfers is the mapping and the definitions: how a Zoho customer resolves to a CRM account, and what each reported figure counts. The code is the smaller half.
Reflection
The customer mapping between Zoho and the CRM is maintained by hand, and it should have had an owner and an exception report on day one rather than after the first argument about a missing account. It is the quietest failure in the system, because a broken mapping produces a report that is complete looking and wrong. Second, the commentary is only as good as the figures beneath it: given a style with thin history the model still writes a confident paragraph. A minimum evidence gate is the next change.
Section 143 of the CGST Act lets a principal move inputs or capital goods without paying tax, and Rule 45 makes the delivery challan the document. An invoice would record a sale that never happened and take stock off the books while the principal still owns it. The movement goes into ITC-04 instead.
No. Every figure is computed before the model is called, and the model writes over a finished aggregate. Once a model computes a number in a finance report, nobody downstream can tell a rounding error from an invention.
The threshold is per piece: 5 percent at or below 2,500 rupees, 18 percent above. Rate resolves from unit price at posting, not from a customer or item setting.
Context
Tell us what your operation runs on today.
Real feedback from the people we've proudly partnered with.
Sales Director |Cintas
United States
Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.
Founder & CEO |Moneteo
We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.
CEO |E-Commerce Platform
Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.
