Every movement, however it is entered, builds the same document and goes through the same posting code. There is no second implementation to keep in step.
Bills of Materials
What each product is made of. Held as a recipe, exploded when you plan, and consumed at the cost Intacct holds when you produce.
Drives works order consumption
Works Orders
Production against a bill of materials. Components off, finished goods on, at the cost Intacct holds.
Backflush + run increase, one atomic post
Issue to WIP
Components out of stores into a work-in-progress warehouse, so consumption is visible before the job closes.
Inventory transfer
Item Transfer
Warehouse to warehouse, carrying bin, lot and serial detail where the client uses them.
Inventory transfer
Stock Control
Balance, ledger, projected quantity and stock on order, off the same numbers Intacct holds.
Read-only reporting
And a good deal more
Quality inspection and certificates of analysis, routings and job cards, projects and job costing, maintenance, lot and serial traceability, planning. Same platform, switched on when a client needs it rather than shipped by default.
What each one costs to turn on
Alongside these, a shop-floor screen carries the same movement flows in a form a supervisor can use on a tablet at the machine: a scan, a quantity, one button. It builds an ordinary stock document and submits it, so a rejection from Intacct rolls the movement back and the operator reads Intacct's own words on the screen in front of them.