Category: ERP

Here’s the most uncomfortable moment I see in small manufacturing companies: the P&L says you made $120,000 last month, and the bank balance says you have $14,000. Everyone stares at the screen. Nobody knows what to say. In one 40-person machining shop, that exact gap is what triggered their ERP Consulting engagement.

Months of Profit, Days of Cash

We found their story in three numbers. They were shipping products 11 days after production, but customers were paying at 47 days. Meanwhile, their own suppliers got paid at 31 days. That’s a 16-day hole they were financing out of their own pocket, every single month.

1. Pull last quarter’s invoices and sort them by days-to-pay. Circle anything over 45 days.
2. Compare that with your own supplier terms — is your money coming in slower than it leaves?
3. Pick one sluggish customer each month and renegotiate payment terms in exchange for a small early-payment discount.

The biggest lever is rarely price. It’s the timeline between shipping and payment.

The 15-Minute Weekly Cash Ritual

They set up one calendar meeting. Same time, every Tuesday. Just the owner, the controller, and a single-page cash forecast for the next 12 weeks. No spreadsheets projected on screen, no 30-line grids, just three boxes: expected in, expected out, and what’s due in 7 days.

Within 12 weeks, their cash buffer grew from $14,000 to over $190,000, and not because sales jumped. Because they could see the next wall in advance and chose not to hit it.

What ERP Consulting Actually Does Here

The software doesn’t write better invoices for you. What an ERP Consulting setup gives you is a single timeline pulled from real invoices, not from someone’s memory. When the controller trusted the numbers, the Tuesday meeting stopped being detective work.

If you don’t know your own days-to-pay this afternoon, that’s your starting line. Ask your office manager for this quarter’s top 5 invoices and the dates they were paid.

I walked into a client’s warehouse in the middle of a July heatwave. The racks were full, the bins looked organized, and the warehouse manager was proud of his “6-week supply” rule. Then we pulled up the last-movement dates. That walk changed how we ran the entire ERP Consulting review.

The 18-Month Shelf Test

We made a game of it. Every bin that hadn’t been touched in 18 months got a red dot. By day two, the warehouse looked like it had measles: 23% of their 5,000 SKUs hadn’t moved in over a year. That’s roughly $800,000 of cash sitting as dead weight.

Nobody was stealing. Nobody was careless. The problem was that the reorder points were set back when the company had one product line and three loyal customers. Demand had changed, but the minimums hadn’t.

Until You Set a Review Schedule, the Data Won’t Save You

Here’s what we did: we ran a slow-mover report every Friday instead of once a quarter. Every item with zero movement for 120 days got flagged to a human, not an algorithm.

• Set reorder points from the last 12 months of actual demand, then review them every quarter
• For any SKU with zero sales in 4 months, cut the reorder quantity by half automatically
• Do a physical “dust walk” twice a year — walk every aisle and touch anything that looks forgotten

The result? Within five months they freed up $340,000 in working capital and cut their stock write-off line by over 60%.

Why This Task Belongs to a Business Manager, Not an IT Guy

The ERP Consulting team built the reports, sure. But the decision to kill a slow-mover is yours, not your software’s. A system will show you the numbers; you have to make the uncomfortable call.

Start tomorrow with the simplest possible question: walk your floor, find one thing that hasn’t moved in a year, and ask the people who use it every day whether they’d cry if it disappeared.

The purchasing manager at a mid-sized cabinet manufacturer found it by accident. She was reviewing a year of invoices from the firm’s biggest hardwood supplier and noticed that two invoices, from three months apart, had exactly the same invoice number — but different amounts. That single discovery led to a full audit that found $186,000 in duplicate payments, wrong prices, and early-payment discounts never taken. On a company making $2 million a year, that was 9 percent of profit, paid away to nobody’s benefit.

How a supplier can overcharge you without breaking any obvious rule

When ERP Consulting pulled the full payment history, the overcharges broke down into four repeating patterns. Hardly any of them were fraud. Most were simply errors and mismatched information that the old system had no way to catch.

• Two invoices carrying the same number were each paid in full because the payment approval process only checked the dollar amount, not the invoice number against history.
• The supplier sent revised pricing in September, but the system still paid the July rates because the price list was updated in a separate spreadsheet that nobody synced.
• Invoices with small but real math errors — a tax miscalculation, a rounding mistake, a shipping line added twice — flowed through because nobody re-calculated the total by hand.
• The company paid every invoice on the 30th day, even the ones that carried a 2 percent discount for paying within ten days. The discounts it missed across a year added up to over $27,000.

The fix: three rules that caught errors in the first week

The ERP Consulting engagement set up a simple approval flow that every invoice must pass through before payment. The system checks the invoice number against every invoice already paid — any repeat gets flagged immediately. It compares the unit price on the invoice to the agreed price loaded in the system, and it holds any invoice that differs by more than half a percent. It also calculates the early-payment discount and pays every qualifying invoice on day nine instead of day thirty.

The results came fast. In the first week alone, the system flagged three duplicate invoices worth $14,000. In the first quarter, recovered overcharges and captured discounts totaled more than the cost of the entire ERP Consulting project. But the bigger win was quieter: the purchasing manager stopped spending three hours a week checking invoices by hand, because the check now ran automatically.

The check you can run this week, no software needed

Sort your last twelve months of supplier invoices by invoice number and look for any number that appears twice. Then pick your five biggest suppliers, find the “agreed price” on your purchase orders, and compare it to what you paid on the last ten invoices. You will almost certainly find at least one overcharge — that’s the norm, not the exception.

The cost of late payments and missed discounts is easier to see: add up every early-payment discount on your pending invoices and calculate what 2 percent of them is worth. If that number surprises you, you have your business case. ERP Consulting can show you exactly where the payment controls should go, but the first sort by invoice number is a ten-minute job you can do today.

The controller spent the first week of every month rebuilding the same five reports. Sales came from one spreadsheet, purchases from another, and inventory from a third that the warehouse manager updated “whenever he remembered.” At month-end, the sales manager’s numbers and the controller’s numbers differed by about 11 percent, and the owner made decisions based on whichever document was newest. That was the real operating system of a company doing $22 million a year.

When good growth meets bad data, someone always pays

The tipping point came when the company landed its biggest customer ever — a national retailer that ordered $1.4 million in the first six months. The order was great news right up until the fulfillment chaos started. The company oversold two items it didn’t have, underordered one it had plenty of, and shipped three customer orders to wrong warehouses because the address list lived in an email thread.

The customer’s logistics manager called the owner and asked a simple question: “Do you actually know what you have?” He could not honestly say yes. That’s when he called in ERP Consulting.

The review took three weeks and produced a strange document: a map of every spreadsheet, every “final version” file, and every manual transfer between the two. There were 14 active trackers, at least five of which disagreed with each other on basic facts like current stock and open purchase orders.

What the first 90 days looked like

The ERP Consulting team did not replace everything at once. They started with one core: a single shared system for purchase orders, inventory, and sales orders, so that all three functions read from the same set of numbers. The old spreadsheets were frozen on a shared drive for reference but banned from daily decisions.

Conversion of the messy files took six weekends, mostly because the data in the trackers didn’t match and every conflict had to be resolved with a phone call. The team worked through the cleanup in three stages:

1. Freeze every spreadsheet and assign one person as the single keeper of each type of data — one for stock, one for orders, one for prices.
2. Enter all open purchase orders and open sales orders into the new system before touching historical numbers, so the live picture is complete and current.
3. Run a weekly “one version of the truth” check where the warehouse count, the system count, and the spreadsheet count are compared side by side until they agree.

The first clean month-end came 60 days after go-live. The controller closed the books in four days instead of nine, and the sales and finance numbers matched to the dollar for the first time in the company’s history.

The results that show up in the bank account

Three months in, the company stopped paying for 17 percent more inventory than it sold, because purchasing finally saw real stock levels before ordering. The national retailer’s fulfillment complaints dropped from four per week to zero in the second quarter, and the account grew. The owner said the system paid for itself in the first inventory cycle just through fewer rush orders and fewer emergency freight bills.

Your test could not be simpler. Print the current stock list, the open purchase orders, and the open sales orders from your three most important “systems.” If the quantities don’t tell one consistent story, you are running on opinions, not data.

ERP Consulting can help you build the single version of the truth. But before you call anyone, count how many spreadsheets your team updates manually every week — that number is your starting point.

The write-off report arrived in March, covering the previous quarter, and the warehouse manager nearly choked on his coffee: $43,000 of frozen food had gone past its best-before date while sitting in the back of the cold room. The year-end number was worse — $87,000 in expired stock, all thrown out. For a food distributor with $8 million in annual revenue, that was a full 1 percent of sales, evaporated.

Why stock was dying in a cold room that had plenty of space

The warehouse had empty racks, so this wasn’t a space problem. The issue was that nobody knew what was actually in the back rows. New deliveries were stacked in front, and the older pallets stayed buried until someone got curious.

By then, the dates had passed. An ERP Consulting review traced the trail of every expired pallet in that quarter and found four identical patterns in every single case.

• Incoming pallets were logged by product name and supplier, but the best-before date was written on the box — never into the system, so no report could ever warn anyone.
• Pick lists were filled from the nearest stack, not the oldest stock, because there was no rule for which pallet to pick first.
• The cold room had daily temperature logs, but nobody connected a slow cooling fault in the back corner to the shorter shelf life of the product stored there.
• No one had ever run a “pallets shipping in the next 14 days” report, because the data didn’t exist.

The fix: dates in the system, and a 14-day warning

ERP Consulting set up three changes. First, every inbound pallet gets a shelf-life date typed into the system at receiving — it takes ten seconds per pallet. Second, the system flags any pallet with fewer than 14 days of shelf life left, and the fastest-moving product line gets picked from that flagged stock first. Third, the warehouse added a “last in, first moved” rule for short-life items, meaning the newest delivery goes into the back rows so the older stock comes out first.

The first quarter under the new rules produced a write-off of $18,000. The second quarter came in at $12,000. Most of that remaining amount was a single refrigeration failure that the temperature alarm did catch — but slowly. The team saved roughly $70,000 in a year with changes that cost nothing but discipline.

What to check this afternoon

Walk to your own warehouse or back room and look at the ten pallets with the oldest dates. Then check the system: does it even know those dates exist? If the answer is no, you’re holding a lottery ticket to the write-off report.

Start by making the date part of the receiving record on Monday morning, and run a report every Friday afternoon listing anything expiring in the next two weeks. That one habit will cut your spoilage faster than any renegotiated supplier contract. If the reporting structure isn’t obvious, an ERP Consulting workshop can map it in half a day.

“We don’t lose money on projects,” the CFO said at our first meeting. “We just lose time.” The senior architect sitting next to her laughed — he had just spent a full week on a facade the client approved in an email, even though the contract clearly stated no work begins before a purchase order arrives.

That week’s time, about 40 hours in total, sat in a timesheet for three weeks. Then it got quietly deleted because nobody knew how to bill it.

Where the hours were hiding

This was a 40-person architecture and engineering firm, and the ERP Consulting review started with one month of timesheets. It took two days to reconcile them. The consultants found 620 hours of logged work that had no project attached, no billing code, and no owner. At the firm’s average billing rate of $145 an hour, that was almost $90,000 in work the firm performed and never invoiced.

The root cause was not lazy staff. It was a broken handoff. The project manager tracked change requests in a spreadsheet, the accounting team used a completely separate system, and sales kept its own list of promised discounts.

The three lists never talked to each other. Work got done, hours got logged, and the invoice left out anything that didn’t match the original contract.

The fix: no hour exists without a billing destination

The ERP Consulting team introduced one rule and enforced it for 45 days, and it applied to every single hour worked.

1. Every hour entered in the timesheet must carry a project number, a phase code, and a billing status — “billable,” “not billable,” or “needs approval” — before it can be saved.
2. Every change request from a client gets a code in the system within 24 hours, so the work and the billing path exist before the employee starts.
3. Every Monday, the project manager reviews the previous week’s “needs approval” hours and either chases the change order or reclassifies them as not billable. No hour stays unassigned for more than seven days.

The first week was painful; experienced architects hated typing an extra code. By week four, it was automatic. By the end of the fourth month, unbilled and unassigned hours had dropped to 28 hours for the entire month — down from 620.

What that meant for the owner

With the hours finally visible, the firm discovered it had been underbidding its own services for years. Two standard project types were consistently running 14 percent over estimate, and the firm had never adjusted its prices because the data was scattered. The owner raised rates on those two project types, and the backlog stayed full. That single pricing correction added more profit than winning one new client.

Your move this week: pull your firm’s last thirty days of timesheets and count the hours that have no project or no billing code. If that number is more than 50, you are leaving at least one employee’s worth of revenue on the table. You don’t need a new department — you need a rule that no hour exists without a billing destination. ERP Consulting can design that rule for your workflow, but the count first is all yours.

Ray ran a clothing retailer with three stores in neighboring towns. Every month he did the same ritual: he added each store’s sales, subtracted its rent and staff, and declared Store A the winner. It made $38,000 a month, while Store C limped along at $9,000.

The problem was that his simple math missed nearly everything that actually costs money. When ERP Consulting mapped the real expenses, the results turned his ranking upside down — Store A was losing $4,000 a month once the true costs landed on it, and Store C quietly made $11,000.

Why the simplest numbers lied so badly

Ray’s stores were far from independent. Staff from Store B regularly covered shifts at Store A, and their time was never recharged. Inventory flowed between all three stores almost weekly, but the transfers weren’t recorded — so Store A kept credit for goods it had sold months ago. Then there were the shared costs: the district manager’s salary, the delivery van, the marketing spend, and the software fees were all sitting in the “general” pile, never allocated to anyone.

The ERP Consulting review found that 38 percent of Store A’s apparent profit came from those unallocated costs and unreported transfers. Accounting for them changed every store’s story.

What a true per-store profit statement looks like

• Every hour a Store B employee works in Store A gets charged to Store A’s labor line that same week.
• Every unit moved between stores is logged as an inter-store transfer with the original cost attached, so profit follows the product to the store that actually sells it.
• Shared costs — manager salary, van, advertising, software — are split by each store’s share of revenue, calculated once a month and reviewed by the owner in ten minutes.

With those three rules in place, the first true statement took about six hours to build. The second month took ninety minutes because the data collection was already happening.

The move that changed everything

Once Ray could see the real numbers, he made two decisions in a single week. He moved his best-selling product line from Store B to Store C and cut Store A’s hours, which saved $3,200 in labor without hurting sales. By the end of the quarter, Store C was the profitable anchor, and the combined profit of all three stores was up 22 percent — with zero new inventory bought.

Here’s your ten-minute test: take a store that looks strong and ask what costs are allocated to it. If the answer is “just rent and staff,” you’re seeing the same illusion Ray saw. Run a rough allocation of every shared dollar and see if your best store is still your best store. ERP Consulting can walk you through building a per-store statement, but the first step is deciding you want to see the truth.

An aluminum fabrication shop with 34 employees won seven big custom jobs last year. The owner was happy because his spreadsheet said those jobs carried a 38 percent profit margin. When year-end came, the bank statement told a different story — actual profit was closer to 12 percent.

He had no idea where the 26 points went. That is exactly the problem ERP Consulting gets called in to solve.

Three customers left, and the fourth cut their order in half

The investigation started with the seven job folders. The ERP Consulting team sat with the production supervisor and rebuilt the cost of each job from the shop floor up. What they found was not one big mistake — it was twenty small ones that nobody had a way to see.

The biggest surprise was material. The estimator priced aluminum at the market rate from six months earlier, but the shop bought a lot of it on short notice from a local supplier at a 14 percent premium. Rework was the second surprise: 740 hours of rework were charged to “general overhead” instead of to the jobs that caused them. When 740 hours disappear into overhead, every job looks more profitable than it really is.

The fix: charge every hour to a job, and review costs before the job closes

The changes were surprisingly simple. The ERP Consulting team installed three rules that took effect on a Monday morning.

1. Every employee writes a job number on their timecard at the start of each day — including the owner and the office manager, so no hour hides in overhead.
2. Every material purchase gets linked to a job number the moment the purchase order goes out, so pricing gaps surface while you can still react.
3. Every Thursday, the estimator, the supervisor, and the owner compare actual costs to the estimate on every open job and decide on the spot what to do.

In nine weeks, the system produced something the owner had never seen: a true profit number per job, while the job was still running, not three months after it shipped. The last two jobs of the year came in at 31 percent and 29 percent margin. Not as good as the fake 38 percent, but real.

Run this test on your own numbers

Pull your last three completed jobs and ask three questions. Did every pound of material get traced to a job? Did every hour of labor get charged somewhere specific? Did anyone compare actual costs to the estimate at the moment the job closed? If the answer to any of these is “no,” your profit number is fiction.

ERP Consulting can show you what the real number is. Start with one job folder this afternoon — pick the smallest one you have and rebuild its cost line by line. The gap between what you think you made and what you actually made is the size of your problem, and your first fix is free.

It was a Friday at 4:15 pm. The warehouse manager at a $12 million industrial parts distributor opened bin R-34, expecting to find 380 stainless steel widgets. The bin was empty, but the computer said the inventory was exactly where it should be.

That single mismatch turned into a three-week investigation. It ended with 41,000 units unaccounted for — roughly $230,000 in missing or misstated stock.

Where the widgets actually went

The team running the ERP Consulting engagement started by pulling the transaction history for those 41,000 units. What they found was not theft. It was something more common and more fixable: inventory was moving in four places nobody had bothered to record.

• Receiving clerks signed for deliveries and put stock straight to the shelves without scanning — the system never knew the goods arrived.
• Sales reps handed out free samples to win orders, and nobody wrote those units off.
• Customers returned damaged parts that the front desk accepted without a return slip, so the units vanished from the records.
• The owner “borrowed” parts for a personal project in year one, and the staff quietly followed that example ever since.

What changed when the counts became real

The ERP Consulting team didn’t install a fancy tracking system. They made three simple rules and enforced them for 30 days.

Every inbound pallet gets scanned within two hours of arrival. Every sample, return, and damage gets a stock movement code before the item leaves the dock. Every bin gets a blind count every month — the counter doesn’t see the system number until after they write theirs down.

The messiest part was the first count. It took 18 people and a Saturday to count the whole warehouse. The second month took four hours.

The number that matters

Inventory accuracy climbed from 72 percent to 98.5 percent in eleven weeks. The purchasing manager stopped ordering parts that were already sitting in the back corner, which cut the next month’s purchase total by 19 percent.

Here is your action for this week: pick fifty random bins and count them blind. If more than ten don’t match the system, you have the same problem this distributor had. The exact fix will depend on where your stock is leaking, but the first step is always the same — stop trusting the screen until the shelf agrees with it.

Run this test before you spend a dollar on more software. ERP Consulting can help you map the leaks, but the count is yours to do.

A family-owned building materials group ran five separate companies: the wholesale business, the transport arm, the installation crew, a small manufacturing line, and a property holding entity. Same family, same building, same office — but three different accounting systems, a set of intercompany loans that “everyone kind of knew about,” and a month-end closing process that lasted 18 working days.

Here’s what the finance director said when we asked how the group was performing, and it should make any multi-entity owner wince: “We don’t really know what the group made last month.” Not “we’re still reconciling.” Not “we have a slightly different view.” The most senior finance person in the building had no solid answer for the group’s actual profit.

Intercompany transactions are the silent killer

The transport company invoiced the wholesaler for deliveries. The wholesaler paid late. The manufacturing line bought raw materials from the wholesaler at one price and sold finished goods back at another. Each entity’s books were accurate on their own; the moment you consolidated, the intercompany balances fought each other, and two accountants spent four days chasing one difference.

The ERP Consulting work introduced one rule that erased an entire category of pain: every intercompany transaction gets a documented invoice with a matching number on both sides. If the transport arm raises an invoice for a delivery, the wholesaler’s system must show that exact document the same day. No exceptions, no “we’ll book it next month.”

How the closing went from 18 days to 4

• All five companies post to a shared ledger structure with the same chart of accounts and the same month-end cutoff date.
• Intercompany balances are checked weekly, not at month-end; any unmatched pair over $5,000 gets escalated the same Friday.
• Consolidation reports run automatically from the shared data, eliminating the spreadsheet that “usually needs a manual adjustment.”

The first month after the change, the close took 9 days. The second month, 6. By the fifth month it was steady at 4. And for the first time, the owners got a single page showing every entity’s revenue, cost, and profit — with numbers the CFO could defend in front of the bank.

The ERP Consulting follow-up at month three included a simple test: the CFO produced the group’s consolidated profit in under an hour, from memory of where the report lives, not from a week of chasing. That single capability — one version of the truth for the whole family — changed how those owners made decisions. When you can see the whole picture on a Tuesday morning, you stop managing by guesswork.