Four roads out of the same problem
Every manufacturer on Intacct eventually hits the gap between the ledger and the factory floor. There are four ways to close it, and three of them cost more than they look.
The floor is not in the system
Intacct holds the stock figure, the valuation and the general ledger, and holds them well. What it does not hold is the hour-by-hour reality of a factory: a batch part-consumed, a pallet moved to the wrong rack, a run confirmed at end of shift, a component swapped because the first choice ran out.
So that reality lives somewhere else. A whiteboard. A shared spreadsheet. A supervisor's notebook, keyed in on Friday by someone in finance who was not there.
Which means the stock figure is right at month end and approximately right the rest of the time — and nobody can say by how much.
The cost shows up as buying material the company already owns, as production stopped by a shortage nobody saw coming, as a valuation nobody quite trusts, and as skilled people spending their week rekeying what already happened.
Push the floor into Intacct
The obvious answer, and it fails on shape rather than on capability. Intacct is built for people who account for a business, not for people who run one. A storeman with a scanner needs three fields and a green button; giving them a transaction screen and a chart of accounts is slow on a good day and dangerous on a bad one.
It also puts operational users inside the accounting system, with the licence cost and the risk profile that implies. Most finance directors decline before the consultant finishes the sentence.
Replace Intacct with a manufacturing ERP
This solves the floor by demolishing everything that already works. The books move. Finance retrains. Reporting is rebuilt. Every integration around Intacct is re-done. Multi-entity consolidation, which was the reason for choosing Intacct in the first place, is now somebody else's problem.
For the consultant it is worse than a lost implementation — it is an Intacct estate leaving the platform because of a gap in the factory, not a gap in the accounting.
Build something bespoke
We know this road well, because we took it. Before Fuse existed on this platform we built a manufacturing application over Intacct from the ground up: works orders, bill-of-materials explosion, backflush, work in progress, all hand-written against the gateway.
It worked. We retired it anyway.
Everything it hand-built was standard behaviour in a platform we could have started from. We had written — and had to maintain, alone, forever — a worse version of software that already existed. Every client would have been a fork, and every fork a support liability.
Fuse is what we built once that lesson was paid for. The bespoke application became the requirements document, not the template.
The same maths applies to anyone considering it now. A bespoke build is a permanent development commitment carried by one client's budget, with no upgrade path and no second customer to spread it across.
Leave the books exactly where they are, and add the floor beside them
Fuse gives operational people screens shaped for their job, and posts every movement they make into Intacct as it happens. The ledger does not move. Finance does not retrain. Nothing about the Intacct estate changes except that its stock figure is now correct at four in the afternoon as well as at month end.
Intacct posts first
If Intacct rejects the post, the Fuse transaction does not stand. There is no half-committed state and no queue of failures to clear.
Fuse never invents a value
It records the cost Intacct accepted. Where Intacct holds no cost, it refuses and reports rather than substituting a plausible number.
Live, never batched
Movements post as they happen. Nothing waits for an overnight run and no journal is summarised on the way through.
Masters flow one way
Accounts, customers, suppliers, items, warehouses, bins, units, entities and tax schedules are mirrored from Intacct and read-only in Fuse.
There is never a second set of numbers to reconcile, because there is never a second set of numbers.
What this is worth to a Sage consultant
- It defends the estate
- The manufacturing gap is one of the more common reasons an Intacct client starts shopping. Closing it without moving the ledger turns a competitive threat into an upsell.
- It opens a market you currently pass on
- Manufacturers that were disqualified at the first meeting become viable, and viable with a differentiator nobody else in the room is offering.
- The work is implementation, not development
- Most of a Fuse project is configuration to how the client actually operates — which is the work a consultancy is already staffed and priced for.
- No per-client registration to wait on
- Because Fuse uses the XML gateway rather than the REST API, there is no app registration in the Sage developer portal standing between a signed deal and a working system.
- Nothing to defend at the audit
- Intacct remains the system of record, every write is logged in full, and the audit trail cannot be edited by anyone, including administrators.
The client keeps the accounting system they chose, and gains the factory system they were about to leave it for.
Everything else in this pack is detail underneath that sentence.