What is on the screen today, and what can be switched on alongside it. Each option is scoped and quoted with you during implementation rather than assumed.
This is what your people land on. Twelve tiles, in work order, each one a switch — a site only shows the parts of the operation it actually runs.
However a movement is entered, at a desk or on a phone on the floor, it builds the same document and goes through the same posting code. There is no second implementation to keep in step.
Book a delivery in against a purchase order.
Updates stock and cost in Intacct
Work out what to make and what to buy. Explodes demand through the recipes and checks what is already on the floor.
Planning only, posts nothing
Current production orders. Components off, finished goods on, at the cost Intacct holds.
Backflush + run increase, one atomic post
Move components into a work-in-progress warehouse, so consumption is visible before the job closes.
Inventory transfer
Move stock between warehouses, carrying bin, lot and serial detail where you use them.
Inventory transfer
Check a batch against its specification, on receipt, in process, or before it ships.
Blocks release on failure
Send goods out against a customer order.
Relieves stock ahead of the Intacct invoice
Transfers, production and stock reports. Balance, ledger, projected quantity and stock on order.
Read-only reporting
Request material to buy, move or make, raised by the people who can see the shortage.
Feeds purchasing and production
What each product is made of, including intermediates that get made and then consumed in something else.
Drives planning and consumption
Specifications, instruments, procedures, certificates of analysis and non-conformances.
Evidence as a by-product of the work
Jobs, tasks and what they have cost. Site work and installations with time booked against them.
Job costing
Scan, count and confirm on a phone or tablet. The same movements as the desk screens, in a form built for a scan, a quantity and one button.
How to do each of these, step by step, inside the system rather than in a manual nobody opens.
Fuse is built using ERPNext, so a good deal more sits behind the working set. These are switched on when you need them rather than shipped by default, and each is scoped and quoted with you during implementation.
Every one of them answers to the same rule. Operations happen in Fuse; the accounting consequence goes to Intacct, live, and Intacct decides it. Adding maintenance scheduling or a CRM to your operation changes nothing about who owns the ledger.
However much of the operation Fuse takes on, the answer to "who does the accounting" never changes.
That is what makes the list above safe to hand to your finance director.