A lot of Indian manufacturing groups are not one factory. Spinning sits in one state,
\n knitting in another, and the garmenting unit is somewhere else again. Auto components
\n look the same: machining in one place, assembly in another, a warehouse near the
\n customer.<\/p>\n
Nothing is sold when material moves between those units. It is your stock the whole way.
\n The tax system does not entirely agree.<\/p>\n
A transfer between two units of the same business, registered separately in different
\n states, is treated as a supply. Tax applies. Because the two ends are in different
\n states, it is integrated tax rather than the split central and state tax that applies
\n within one state.<\/p>\n
That has two practical consequences and both bite at month end.<\/p>\n
The first is that the tax charged depends on where each end of the document sits, not on
\n what is being moved. The same fabric, going to the same finishing unit, is taxed
\n differently depending on which of your plants it left from.<\/p>\n
The second is that this is a document, not a note. It needs to exist, be numbered, be
\n reconcilable, and match the goods that physically moved.<\/p>\n
The transfer is recorded as an issue.<\/strong> The material leaves stock at the The paperwork is produced somewhere else.<\/strong> The movement is in the system, Each unit keeps its own item master.<\/strong> The same yarn has three codes The unit is an organisation inside one system rather than a separate installation. Each Tax on a movement is worked out from the state at each end of the document. Within a The e-way bill is generated from that same movement rather than typed again on a portal, Stock is valued once. A transfer changes where the material is, not what it is worth. It is worth being exact, because compliance is where software gets oversold. Onfinity Take one inter-unit transfer from last month. Ask three questions.<\/p>\n What was the material worth at the sending unit, and what was it worth at the receiving If the last one takes more than a minute, that is not a reporting problem. It is four Manufacturing across units<\/a> Spinning in one state, garmenting in another. The greige never changes hands, but the movement between them is taxed, documented and reconciled like a sale.<\/p>\n","protected":false},"author":1,"featured_media":3218,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-3207","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business-hacks"],"_links":{"self":[{"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/posts\/3207"}],"collection":[{"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/comments?post=3207"}],"version-history":[{"count":1,"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/posts\/3207\/revisions"}],"predecessor-version":[{"id":3212,"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/posts\/3207\/revisions\/3212"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/media\/3218"}],"wp:attachment":[{"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/media?parent=3207"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/categories?post=3207"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/tags?post=3207"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n sending unit and gets received at the other end as though it appeared. Group stock is
\n understated in between, and the two ends carry different values for the same thing.<\/p>\n
\n the e-way bill is generated on a portal, and the two are connected by somebody
\n remembering. When a trip is cancelled, one of them gets updated.<\/p>\n
\n because three units set it up independently. Group-level stock is then an exercise in
\n matching names, done in a spreadsheet, once a month, by the person who is best at it.<\/p>\nWhat it should look like<\/h2>\n
\n has its own books and its own registration. They share one product master, so yarn is
\n one item wherever it sits.<\/p>\n
\n state it splits; across one it does not. Nobody decides that per transfer, because the
\n document already knows where it came from and where it is going.<\/p>\n
\n and cancelled from it when the trip is called off. There is one record of what moved and
\n the paperwork is a view of it.<\/p>\n
\n The group total is a total, not four spreadsheets added up with a note
\n about timing differences.<\/p>\nWhat this does not do<\/h2>\n
\n holds the data these filings are prepared from, and generates e-way bills and
\n e-invoices against documents that already exist in the system. It does not file
\n GST returns.<\/strong> The filing remains where it is today.<\/p>\nThe test<\/h2>\n
\n one? Were the e-way bill and the stock movement created from the same record, or typed
\n twice? And if somebody asks what the group holds of that item today, across every unit,
\n how long does the answer take?<\/p>\n
\n systems wearing one company’s name.<\/p>\n
\n ·
\n Stock and movements<\/a>
\n ·
\n Download the free edition<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"