Category: ERPNext

When a family-owned group grows from one company into four, the paperwork multiplies faster than the profit. I worked with a holding group that had a distribution arm, an installation service firm, a small manufacturing line, and a leasing entity that owned the vehicles and machines. Altogether about 150 employees, three sets of shareholders, and two currencies. Every month, the finance team spent six days consolidating numbers in spreadsheets, and every month, the family asked more questions than the numbers could answer.

The issues were not glamorous. Loans between the companies had no clear repayment schedule, one company charged rent to another but the invoice was never booked in the right month, and the leased equipment was carrying depreciation in the wrong entity. The owner, a sharp woman in her late fifties, summed it up in a single sentence: “I know total revenue, but I don’t know what each business actually earns.” That’s the sentence that brought ERPNext Consulting into the group.

Why consolidation fails when you run a multi-company group

Spreadsheets are fine for one company. The disaster begins the moment you need to eliminate balances between companies, revalue one currency inside another, and prepare a combined report where the numbers add up. The finance team tried to build reconciliation tables, but every month some invoice went missing or a sale between companies was recorded only on one side. The solution wasn’t to hire more people to feed the spreadsheet; it was to change the setup so that every entity logged its transactions into the same chart of accounts, with the same rules, against the same calendar.

• Set one fixed closing calendar: all four companies close their books on the same day every month, no exceptions, so the consolidation starts on a clean date.
• Create a single chart of accounts that everyone uses, and resist the urge to let each director customize their own account names, or the consolidation becomes a translation exercise instead of an arithmetic one.
• Book every transaction between companies immediately, with a document reference, so the balance between two companies can be verified in minutes instead of days.

The finance team’s consolidation time dropped from six days to half a day. More importantly, the quarterly family meeting changed its character: instead of debating whose numbers were right, they started debating which business deserved more capital, which is a much better problem to have. ERPNext Consulting‘s role was not to build an elaborate reporting palace, but to make the foundation clean enough that the family could finally see its own reality.

The one practice that made all the difference

Every invoice between companies, every loan repayment, every rental charge between entities, was given a document number and posted within 48 hours. That single rule eliminated more than half of the reconciliation problems in the first two months. The finance team was skeptical at first, because they were used to catching up at month end, and the thought of continuous posting required a discipline shift. But the shift paid off in a ratio they could immediately appreciate: one day of finance work per month, instead of nearly a week.

If your business has more than one legal entity, and you feel queasy when someone asks “what did each part of the group actually earn?”, then your first step is to run a single balance sheet between all entities involved. List every loan, rental, and service charge, and note which ones have a matching entry on the other side. The missing matches are your top two fixes for the next month. Once those are clean, your consolidation will start to feel like math instead of detective work, and that’s exactly the feeling a growing family business deserves.

A plant manager at a plastic injection molding facility once told me: “Every breakdown costs money twice.” The first cost is the obvious one — the repair bill and the downtime hours. The second cost is the one nobody writes down: the overtime shift needed to catch up on the missed production, the rush freight for the orders that fell behind, and the damaged trust of a customer who received a late shipment. On their floor, a single hour of unplanned downtime on the main line was worth 1,200 dollars in lost output, and that was before adding the repair cost.

In six months, that factory counted 27 unplanned breakdowns. The maintenance team was talented, but they spent their days fighting fires, and they never had time to plan proper maintenance work. This is a classic case where ERPNext Consulting doesn’t come in to teach complicated reliability theory, but to install a simple rhythm: see the machine history, generate the maintenance task before the failure, and make sure spare parts are already in the storeroom.

The rhythm of maintenance that actually works

• Every machine gets a run-time reading taken at the same time each day, and the system calculates when it crosses the service threshold. For example, a pump that needs service every 500 hours gets its maintenance task generated automatically at 490 hours.
• Spare parts are given a reorder point at 45 days of average consumption, so the storeroom doesn’t run out of the exact part you need during a Saturday night outage.
• Each completed maintenance ticket records the actual time and the parts used, building a history that shows which machines are costing you the most, so you can make better decisions about replacing them.

The rhythm took a little while to become natural. In the first month, the maintenance team still reacted to breakdowns because they didn’t trust the new schedule. But by the third month, the numbers started to shift. Over the next six months, breakdowns dropped from 27 to 11, and the plant manager estimated the company saved something in the neighborhood of 90 thousand dollars, mostly in avoided rush freight and overtime catch-up costs.

What to measure if you don’t know where to start

If you walk into your plant and your maintenance team knows exactly what’s going to break this week, you’re probably already ahead. If they don’t, pick the three machines that caused the most downtime last quarter and write down the top three part failures for each. That’s your starting list. Build a simple calendar task for each of those failure points, set a spare part minimum, and keep going from there.

The lesson from the injection molding plant is that ERPNext Consulting brings the structure, but the real change came from the maintenance planner who started trusting the calendar over the daily noise. When you stop paying for breakdowns twice, you’ll feel it in the budget, and you’ll also feel it in a quieter Monday morning, the mornings where you don’t start the week with a crisis.

A home goods retailer with three warehouses was bleeding 18% inventory accuracy. Every month, the stock counts in the system disagreed with what was physically on the shelves, and the team was spending 30 hours a week hunting for things that weren’t where they said they’d be. The owner’s favorite line was “the system is wrong” and, honestly, he was half right: the system repeated errors that the picking and receiving teams made every single day.

The turning point happened when a rush order for a wedding in two days couldn’t be fulfilled, because the system said a certain lamp shade was in stock, but the shelf location was empty. The customer left, the manager apologized, and the owner finally agreed that the problem was not the tools but the process. ERPNext Consulting started by counting the fastest-moving 100 items across the three sites, and just that exercise exposed a shocking rule: the most popular items also had the most inconsistent storage locations.

The three fixes that took the accuracy from 82% to 97%

1. First, every shelf gets a permanent address. The team stopped moving products to “temporary” spots after receiving, and any item found outside its shelf is treated as a mini-incident that gets logged with a reason.
2. Second, daily counts of the top 50 sellers per warehouse, done by the same person, at the same time, using a consistent counting method. Ten minutes a day, not a huge count at year end.
3. Third, transfer orders between warehouses must be posted the same day, not at the end of the month. This single rule eliminated most of the phantom inventory across all three sites.

By day 90, the accuracy had risen to 97%, and the emergency exception count dropped from dozens a week to three in the whole month. The picking team stopped losing time, the customer service team stopped promising items that did not exist, and the owner stopped confusing “the system is wrong” with “the workflow is wrong”. ERPNext Consulting came in as a guide, but the real ownership of the change landed with the warehouse supervisors who adopted the shelf addresses as their own idea.

What most warehouse managers still get wrong

They buy nicer equipment, more labels, more screens, and assume the accuracy improves automatically. It doesn’t. The accuracy improves when every move has a consequence: a shelf gets a location, a transfer gets posted the same day, a miscount gets explained. That’s a discipline problem, not a technology problem. Once the discipline is in place, the technology actually starts to work, because it’s fed with accurate information at every step.

For a business with multiple warehouses, don’t start with a full inventory count. Start by counting the 100 fastest-moving items, because those are the ones doing the most damage when they’re wrong. Track how long it takes you to reconcile those 100 items and why the errors occur. Fix the top three causes, then expand the routine. That’s how you get from “the system is wrong” to a number you can actually trust.

It started with a single jar. A customer in a northern suburb wrote in to say a batch of chili sauce smelled funny when she opened it, and her family felt queasy after dinner. That one message triggered a nightmare for a 60-product sauce manufacturer whose production records lived in a binder of handwritten forms and a single spreadsheet that nobody could sort reliably.

It took the quality manager two full days to identify which batches were affected. Two days of guessing, while a whole aisle of jars sat waiting for an answer.

Luckily, the test results came back clean, and the company avoided a formal recall. But the scare itself was enough to convince the owner that “lucky” is not a strategy. That’s when ERPNext Consulting came into the picture, not to install a big package of unnecessary features, but to build a simple traceability loop that a small production team could actually follow.

The traceability trail that fits in a single afternoon

The design principle was brutal simplicity. Every production batch gets a number printed on the label. The system records three facts for each batch: which raw material lots went in, which line and shift produced it, and which customer orders it shipped to. That’s it. No barcode scanners with exotic equipment, no industrial engineering degrees required. Just a rule that no batch gets released until those three facts are entered.

• Raw material lots are tagged at the receiving dock with the supplier’s own lot number and the delivery date, so a problem can be traced all the way back to the farm or the processor.
• Every production run starts a new batch record, and the line supervisor confirms it the same day, while the details are still fresh.
• Customer returns go into a dedicated screen, so any pattern like “three returns from one region” is visible within days instead of months.

Six months later, a supplier’s tomato paste shipment was found to have a sulfur smell. The manufacturer pulled the batch numbers that used that paste, identified the four customer orders that contained it, and had the retail stores informed within 15 minutes. The cost of that rapid response was a few phone calls and one email, versus the potential 80 thousand dollars in recalls, disposal fees, and damaged distributor trust that a slow response would have meant.

What traceability is really worth

Managers often think of traceability as a compliance burden, something to build for auditors. But the real value is defensive speed. A food business cannot control every ingredient that arrives at the dock, but it can control how fast the organization reacts when something goes wrong. That speed is precisely what ERPNext Consulting focuses on when it reviews a food manufacturer’s production records: if the answer to “where did this batch go?” takes more than a coffee break, the process needs to change.

If you run any business that buys ingredients or components and ships them onward, run this test this week: pick the most recent batch you produced, and find the answer to two questions in writing — which materials went in, and which orders went out. If you need more than one hour to answer, you have a process gap that will eventually cost you money. Close that gap now, before a bad batch finds you first.

The managing partner of a 40-person engineering consultancy looked at the spreadsheet for the fifth time, then said something I hear at nearly every services firm I visit. “We billed 70% of what we worked last month. I don’t know if that’s because we’re inefficient or because we just aren’t writing everything down.” That gap, the difference between hours worked and hours billed, is where consulting firms lose their profits without ever noticing.

The weird part is that the firm’s quality of work was excellent. Their clients loved them. But the people who designed the systems never designed one for capturing their own time properly, so a big chunk of effort just vanished.

ERPNext Consulting started this engagement by asking a very simple question: for any project, can you tell me the budgeted hours, the worked hours, and the remaining hours in under five minutes? The answer was no.

Where the hours were really going

We put time records in front of the engineers for three weeks, and the results were uncomfortable in the best way. Roughly a third of the “project work” time was actually spent on redoing calculations from earlier stages, because comments and review notes were living in emails nobody could search. Another chunk went to client requests that were never registered as contract changes, so the work was done but never billed.

1. Step one is to capture every hour, even the shameful ones, for three weeks before changing any process. You need a baseline, not a guess.
2. Step two is to name the project phase for every hour entered. A task called “general work” is a red flag that the naming doesn’t match the actual way the team operates.
3. Step three is to hold a weekly 30-minute review, not of each person’s efficiency, but of the top five unbilled activities that week, and decide who talks to the client about them.

Once the team could see the data, the fixes became obvious. Email-based review comments moved into the project log. Client change requests got logged the same day, with the billing consequence highlighted. The first month of the new routine lifted utilization from about 58% to 64%, and by the fourth month the firm was consistently billing above 75% of worked hours.

Why your spreadsheet is lying to you

Most services firms keep a separate spreadsheet for project revenue, and at the end of every quarter they stitch it together with payroll numbers. That’s painful, but the deeper issue is that a spreadsheet has no memory. It won’t tell you that a certain client type generates twice as many unbilled change requests, or that a certain project phase always swallows more hours than the estimate allowed. ERPNext Consulting pushed for a single project record, where budget hours, time capture, and billing status live together, and that’s what made the pattern visible.

If your firm operates on the 70% billing pattern, do one thing this week: print a list of the last ten projects and mark the ones that had scope changes during the work. Then check how many of those changes were actually billed. Most firms discover that the biggest names on their client list are also the most profitable to serve, not because they pay more, but because their change requests are formally tracked. That’s the shift worth making.

Seven years. That’s how long a box of oversized rubber gaskets had been sitting on the top shelf of a safety-equipment distributor I once worked with. The company was doing around 12 million in annual revenue, but its warehouse held an estimated 340 thousand dollars in inventory that had not moved in eighteen months.

The owner knew the stock was there. He’d walk past it every day on the way to his office. But nobody had ever taken the time to sort the slow movers from the dead inventory, and every season the purchasing team reordered the same fast-moving items while the warehouse filled up with the same slow-moving ones.

When the team partnered with ERPNext Consulting, the first task wasn’t installing anything. It was getting a customer sales history report that ranked every single product by the last time it was sold.

Why “just sell it cheaper” is the wrong first move

Most managers look at dead stock and immediately think of discounting. That’s backwards. Discounting the slowest items first just burns margin on products that nobody wants even at a lower price. The right order is to classify first, then decide.

• Items with no sales in 24 months: write them off, donate what you can, and list the salvageable material for scrap. The tax deduction comes from dealing with them, not from storing them.
• Items with a few sales but clear quarterly demand: move them to a smaller “slow lane” area, cut their order quantity by half, and reorder only after an actual order comes in.
• Items that sell steadily but always run short: set a simple reorder point equal to 45 days of average demand, so you stop running out of the products that actually pay the rent.

It sounds simple, but the discipline of actually applying it matters more than the classification itself. In one quarter, the distributor cut its dead inventory from 340 thousand to 95 thousand, and freed up enough warehouse space to rent out one bay to a neighboring company. ERPNext Consulting was the catalyst, but the owner’s willingness to accept that some purchases were a mistake, and to stop repeating them, was the real engine.

The habit that keeps the shelves honest

The real lesson was in the routine that came after the cleanup. A monthly report that lists every item with no movement in the past six months, reviewed for ten minutes by the owner and the purchasing manager, became the standard meeting. They agreed on a hard rule: no reorder on any item that has no recorded sale in the prior 90 days, no matter how cheap or how “obviously useful” the supplier claims it is.

If you have shelves full of quiet stock, set yourself a two-hour task: run a sales-by-item report covering the last 18 months, and ask every item that sold fewer than three times why it’s still there. You will find that most of those items are haunting the warehouse because somebody once ordered them “just in case”. Cut that habit first, and the space you’ll recover will pay for the whole exercise.

I remember the day clearly. A 55-person metal fabrication shop, run by two brothers who really knew how to weld, was staring at a job they thought was their best one. The CFO came to the weekly meeting with a printed job card, looked up, and said: “We billed 80 grand for this job, and I still can’t tell you if we made or lost money on it.” That’s the moment ERPNext Consulting gets invited into the room.

The problem wasn’t the workers, it was the data trail

The shop had a fine reputation in the town, but its costing was a disaster. Materials were pulled from the rack without any record, and the welders’ hours were marked down on paper at the end of the shift from memory. A job that looked profitable on the quote sheet was actually bleeding 11% of its value once every bolt, gas refill, and overtime hour was counted.

The fix started with three small habits, not a big dramatic rollout. Every material pull got logged against a job number. Every shift clocked labor hours into the same record. And scrap metal was weighed and tagged at the bin. That gave the brothers their first real picture of job-level profit in years. ERPNext Consulting has worked with plenty of shops like this, and the pattern is always the same: the data already exists inside the business, it’s just scattered across memory, notebooks, and spreadsheets.

What changed when the numbers finally lined up

• Quotes started from actual historical costs, not gut feel, which lifted the average profit margin on new work by 6.4 points within two quarters.
• The purchasing manager could see which steel grades were turning into scrap, so he stopped over-ordering the soft sheet stock that the painters kept rejecting.
• The owners finally had a weekly one-page report showing every open job, its costs to date, and its remaining budget. A meeting they used to avoid became the shortest one on the calendar.

Was it tedious in the first few weeks? Yes. The welders complained, the office manager complained, and one foreman swore he would quit rather than type a digital entry.

But the brothers held the line for a month, and the grumbling faded. The foreman who threatened to quit ended up being the one who showed new hires how to use the screens.

The real win appeared six months later

They took on a large, awkward architectural job that had gone through three quoting rounds already. The CFO opened the historical cost data on a similar job from the previous year, saw the hidden corners where that earlier job had lost money, and re-priced the new one accordingly. That single decision recovered more than the implementation fee.

If you run a shop that quotes jobs without knowing your true costs, do this tomorrow: pick the three biggest jobs from last year and reconstruct what they really cost you. If you can’t do it in an afternoon, that’s your first signal. The goal is not to get a nicer report, it’s to get a number you can trust before you promise a price to a customer.

There is a furniture maker I worked with whose sales team kept promising delivery dates that production had no idea about. Every Friday, the production manager would get a list of orders that were due soon, half of which required materials that were not even on site. The result was a permanent scramble: overtime, rushed purchases, and a 61% on-time delivery rate.

Sales had their own tracking spreadsheet, and purchasing had another one. Nobody was looking at the same number, so every department believed it was the only one doing its job properly. The owner summed it up better than any consultant could: we are all working hard — we are just not working together.

Making the production plan the single source of truth

ERPNext Consulting replaced the three spreadsheets with one production plan that everyone reads and writes to. When sales books a new order, it lands in the plan instantly. When purchasing sees raw material levels dip below the safety buffer, the system suggests a purchase order instead of waiting for someone to panic.

That sounds simple, and it is — but only if humans change their behavior too. The sales team had to stop promising custom lead times without checking the plan. The production manager had to enter completed work at the end of every shift, not on Monday morning. The discipline of daily updates was the hardest and most valuable part.

Three conversations that now happen daily

These are not meetings on a calendar. They are quick checks built into the daily routine:

• Sales reviews the production plan every morning and flags any promised date that conflicts with capacity.
• Purchasing checks the 14-day material shortage list, so long-lead items get ordered in time.
• Production updates actual completion numbers at day’s end, so everyone sees reality instead of hope.

Within five months, on-time delivery climbed from 61% to 89%, and overtime pay dropped by 30% because the scramble disappeared. The purchasing manager stopped making emergency calls to suppliers because the system flagged shortages two weeks earlier. The owner told me it was the first year they took a real family vacation in August, because for once, the factory did not require a hero to babysit it.

Take one look at your own sales-versus-production routine: if the agenda starts with what is the problem this week, you have a reactive culture. The fix is to make the plan the agenda. ERPNext Consulting can build the system that supports that conversation, but the conversation itself is on you to start tomorrow morning.

Picture this: five companies under one roof, five different ways of recording expenses, and a finance team that spent the first two weeks of every month glued to Excel. The group’s accountant called month-end the nightmare that never ends. Consolidated reports were delivered on the 22nd of the following month, which meant decisions were always made on stale data.

The mess came from small differences nobody thought mattered. One entity categorized freight as cost of goods, another as a selling expense. Intercompany loans were tracked differently in every ledger, and reconciling them took the finance team three full days each month. Twelve days of value were lost every single month, and the whole group just accepted it.

Standardize first, automate second

ERPNext Consulting started with the boring stuff, which is where all the money was hiding. They created one chart of accounts that all five entities had to follow, with mandatory fields for cost center and project code. Then they mapped intercompany transactions so that when entity A invoiced entity B, the system recorded both sides in one step.

The finance team resisted at first, especially the accountant who had her own clever spreadsheet. But once the first automated consolidation ran without a single manual adjustment, she became the biggest supporter. Her team now closes the books by the 4th business day, and the consolidated view of the group is available the next morning.

What a smooth close actually requires

Here is the minimum standard:

• One shared chart of accounts, enforced by the system so nobody can quietly invent a new category.
• A fixed close calendar with named owners for each task, from bank reconciliation to intercompany matching.
• A golden rule that any unapproved expense from the previous month gets rejected, not tucked into next month.

The group eliminated about 120 hours of manual consolidation work per month. More importantly, the CEO started getting real answers — which entity was profitable, which cost center was bleeding, and which client segment deserved more attention. The culture changed from we’ll fix it later to it must be right today.

If your month-end takes more than a week, run a simple audit: list every manual step between the last transaction and the final report. Each one is a candidate for elimination or automation. ERPNext Consulting specializes in exactly that kind of cleanup, but you can start by simply asking each finance person what they spent Wednesday on.

I will never forget the meeting where a custom fabrication shop owner showed me a proposal from a giant enterprise software vendor. The implementation was going to take 18 months, cost more than their entire annual profit, and require four new hires just to keep it running. He was excited because it did everything. I asked him how many of those features he would actually use in year one. He could not name ten.

That is the trap that catches mid-sized manufacturers constantly. They think bigger software equals a better business. In reality, a system that fits 80% of your needs and goes live in four months will beat a system that fits 95% in four years.

The fit-gap exercise that saved him $400,000

Our team at ERPNext Consulting ran a fit-gap analysis before anyone signed anything. We listed every process that mattered: quoting, purchasing, job costing, delivery scheduling, and warranty tracking. Then we checked which ones were standard and which were honestly different.

The findings stopped him cold. Only six things in his operation were genuinely unusual, and all six could be solved with custom reports and a small workflow adjustment. The giant system would have installed 400 features he never needed just to get the six he did.

What you should do before you even look at software

Run these three tests first:

• Write down the 15 processes that consume 90% of your team’s time, and mark each as standard or different.
• Insist that every vendor demo shows how they handle your truly different process — not the standard one.
• Estimate full cost of ownership per year, including people, updates, and hardware, not just the license fee.

That shop went live on its new system in 14 weeks with one internal champion working part-time. The total cost was less than a tenth of the giant quote, and the annual maintenance bill was barely noticeable. The owner later told me the best money he spent was the fit-gap analysis itself, because it made him see how much of an ERP is just decoration.

Before you take another vendor meeting, steal this move: get a consultant from ERPNext Consulting to spend two days in your office mapping your real bottlenecks first. The answer might be a new system, or it might be a better process. Either way, you will spend your money with your eyes open.