Category: ERPNext

An engineering services firm with 40 people and $8 million in revenue had a cash flow problem that made no sense. They were winning projects, clients were happy, and yet the owner was borrowing to make payroll. The culprit was hiding in the gap between finishing work and actually sending an invoice.

I asked when their invoices were issued. The answer: about 30 days after a project milestone, sometimes 60. One project had $140,000 of finished work sitting unbilled because the project manager could not compile the hours. This is an absurdly common problem, and ERPNext Consulting sees it in almost every services business we walk into.

The fix was not a software change — it was a habit change

We mapped the whole flow: quote, contract, timesheet, milestone approval, invoice. The system was not the bottleneck. The breakdown was that engineers recorded their hours two or three times a week, and the billing person then had to chase project managers for approval.

ERPNext Consulting set up a simple rule: timesheets must be submitted daily, no exceptions. Not weekly, not when the project ends — daily. Project managers got a weekly report showing which engineers were missing entries, and within three weeks the data started arriving on time.

The exact steps we used

Here is the sequence that worked:

1. Freeze project scope and milestones in the system before any work begins, so billing has a clear trigger.
2. Make timesheet entry a hard daily habit, with the manager’s approval happening the next morning.
3. Generate the invoice within five working days of the milestone approval, and track days-unbilled as a real KPI.

The result: unbilled work dropped from $400,000 to $140,000 in four months, and days sales outstanding fell from 58 days to 34 days. For a typical project, the full quote-to-cash cycle now runs about 21 days from signed contract to money in the bank. The owner stopped borrowing for payroll and started funding growth from cash flow. ERPNext Consulting‘s involvement ended with a simple dashboard the office manager updates every Monday.

If you run a services business, do this one check today: list the last five completed milestones and write down today’s date versus the invoice date. If you spot a gap longer than a week, you have already found the money leaking out of your company.

A $25 million industrial parts distributor came to our team at ERPNext Consulting with a brand new problem: business was growing, but customers were complaining more than ever. They had three warehouses in three states, 11,000 SKUs, and every location ran its own spreadsheet. One branch would order 200 units from a supplier while another branch sat on 500 identical units that nobody could see.

The stockout rate had crept up to 15%, which means almost one in every six orders was missing something. The owner told me the most painful part was the phone calls from sales reps in the field asking warehouse staff to check inventory manually. Sales reps were becoming stock-checkers, and they hated it.

Visibility is not a screen — it is a discipline

ERPNext Consulting started by putting all three warehouses into one system with a shared product master. That sounds boring, but it was the turning point. Every bin got a code, every transfer between warehouses got a document, and every location became answerable for its own count.

Suddenly the branch that needed 100 units could see in real time that another branch had 380 and could transfer them overnight instead of ordering new stock. Inter-branch transfers increased by 40% in the first three months, and the company avoided about $60,000 in duplicate purchases.

What every distributor should measure weekly

Stop waiting for monthly reports. Track these three numbers every Monday morning:

• Stockout count in the last seven days, broken down by warehouse — not a monthly average.
• Transfer-on-time rate, because a transfer that takes four days defeats the purpose.
• Slow-moving inventory over 180 days, which is cash sleeping in a corner.

After six months the stockout rate dropped from 15% to 6%, and inventory turnover improved from 3.2 to 5.1 turns per year. The cash released was roughly $800,000, which the owner used to open a fourth branch. ERPNext Consulting also set up a simple alert so purchasing sees a supplier delay before it becomes a customer disappointment.

One honest warning: no system will fix a warehouse where staff do not update counts. If you walk the floor and see handwritten sticky notes on bins, fix that habit first, then bring in the software.

I sat down with a food manufacturer who proudly showed me a product margin report. It said her jam line was making 34%. Then I asked two questions: did that figure include the extra sugar wasted in changeovers, and did it cover the additional freight from split shipments? She went quiet. Her spreadsheet did neither.

That spreadsheet was actually a 40-column Excel monster, and the cost column was mostly a guess. Here is what ERPNext Consulting discovered during the first week: six of her 28 products were losing money while the report showed a profit. She had been subsidizing them for two years without knowing it.

Where the real cost hides

Here is where the true costs were hiding:

• Material waste on the production floor that never got recorded back into the product cost.
• Changeover time — switching from one flavor or size to another eats hours that nobody bills to a product.
• Freight and returns, which accountants often drop into a giant overhead bucket.

ERPNext Consulting rebuilt the costing model so every production order captured actual materials issued, actual hours worked, and actual waste. The team stopped relying on average costs and started comparing each batch against a standard. The numbers were uncomfortable at first, and that is exactly the point — an uncomfortable truth about cost is worth more than a comfortable guess.

What the fix was worth

Within two months the owner repriced six products, one of them by 19%. She also redesigned the changeover schedule, grouping similar products on the same production day to cut setup time by a third. The margin report now tells her team what is really happening.

Here is a useful test you can run tomorrow: pick your top five products and write down what you think each one actually costs. Then check whether waste, changeovers, and freight are part of that number. If they are not, your margin report is lying to you too — and ERPNext Consulting will tell you the hard truth instead of a pretty one.

It was a Thursday afternoon when the owner called. His inventory report said they had 3,400 units of a best-selling part, but the warehouse manager swore the shelf was nearly empty. That gap between screen and reality was costing them about $38,000 a month in rush orders and missed deliveries. If this sounds familiar, keep reading, because that business is not unique.

The ugly number: 18% of stock records were wrong

The first thing ERPNext Consulting did was not install software. They ran a full physical count in two of the three warehouses and compared everything to the spreadsheet records. The result: 18% of the items had incorrect quantities, and some had been wrong for over a year.

The owner told me he was shocked. I told him he should be — 18% error means nearly one in five decisions about buying or selling was based on fiction. We wrote off the ugly differences, set a fresh baseline, and only then started the implementation.

Three numbers that moved in the first 90 days

Here is what changed fastest:

• Stock accuracy climbed from 72% to 96% by making every pickup and put-away a required entry.
• Purchase orders started using real reorder points, and rush freight dropped by two-thirds.
• Sales staff finally saw live inventory at order time, so they stopped confirming dates they couldn’t meet.

The money showed up quickly. With fewer emergency orders and smarter planning, the business freed about $210,000 in cash that had been sitting in duplicated and slow-moving stock. That cash alone paid for the entire implementation effort in about five months.

The one thing that made it stick

No one likes entering data. Staff found excuses for the first three weeks, and the old spreadsheet habit was hard to break. ERPNext Consulting kept the go-live simple, with a rule that nobody touches the same transaction twice. Once people saw their own reports improve, the resistance melted.

If you take one action this week, do a cycle count of your top 50 items before you even talk to a consultant. The numbers you get will tell you how much chaos you are really dealing with — and that single count will make every future decision clearer.

The finance manager at a 22-person clothing exporter kept 14 spreadsheets for orders, fabric purchases, shipping, and invoices. Every month-end, she spent nine days reconciling them, and every month the numbers disagreed somewhere. When she asked the owner for help, the owner asked ERPNext Consulting to look at the mess. The first meeting lasted two hours, and the most useful thing said was: “Stop counting all the spreadsheets and start with the order file.”

Why spreadsheets fail exactly at the moment you grow

A spreadsheet is fine when you handle 30 orders a month. This exporter was handling 220, with fabric bought in bulk and split across multiple orders, and shipping costs that varied by port. The moment one order contains fabric from three purchases, a spreadsheet forces someone to become a human database. That someone was the finance manager, and she was exhausted.

The staged approach that made adoption painless

1. Week one to four: sales orders and a single customer list, replacing two spreadsheets.
2. Week five to eight: purchase orders linked to those sales orders, so fabric costs attached themselves automatically.
3. Week nine to twelve: invoices, payments, and the shipping log, with the finance team reviewing one live dashboard every morning.

Each stage let people keep their old habit until the new one proved itself. By the end of week twelve, the owner could see the profit on every order without asking anyone. Month-end closing dropped from nine days to three, and the finance manager stopped working the first weekend of every month.

What the first spreadsheet to kill is

It is not the biggest one. It is the one that everyone copies from and that nobody owns — for this exporter, it was the order log. The ERPNext Consulting team’s rule of thumb is simple: find the spreadsheet that gets emailed around most often, and that is your starting point. Replace that one file with a shared record and you immediately remove the worst bottleneck — the waiting for other people to send you the latest version.

If you are drowning in your own spreadsheets this month, pick the one file you resent most. That is the one to fix first, and it is the exact move that turned nine-day month-ends into a long weekend for this exporter’s finance team — with ERPNext Consulting guiding the sequence at every step.

They paid for the old system, hired consultants for six months, and still everyone used spreadsheets on the side. That is the story a 50-person machinery parts importer told when they came to ERPNext Consulting. They had run the old “go-live” but the data was full of mistakes, staff hated it, and the finance team reconciled everything in Excel anyway. They were 11 months in, and the system had become an expensive way to store bad information.

How to know your ERP is actually failing

Nobody will announce it. You know it when you see people exporting data from the system just to re-enter it into their own spreadsheets. This importer had exactly that: eleven departments, eleven private spreadsheets, and zero trust in the shared records.

The ERPNext Consulting team’s first move was not to promise a better system. It was to sit in the importing office and watch how orders actually moved from supplier to customer.

• Ask your warehouse team what number they trust more: the system’s stock figure or the notebook on the desk. That tells you everything.
• Check how long month-end closing takes. If it is more than a week, the system is not your source of truth.
• Look at the last 5 invoices: how many times did someone manually edit a price or a date because the system got in the way?

The restart that worked

ERPNext Consulting cut the scope down to three things: purchase orders, stock, and sales invoices — nothing else for the first two months. They made the warehouse staff responsible for the stock counts and gave them the authority to correct errors on the spot. Within four weeks, the private notebooks started disappearing. Six months later, month-end closing went from nine days to three, and the managing director could finally see the gross margin on every single order.

What saved this project was humility

The biggest mistake on the first attempt was trying to automate everything at once. This time, the team took eight weeks just to fix one process the way everyone actually worked, and only then added the next.

If your company is in a similar mess, do not pay for another big launch. Pick the single pain point that hurts the most, run it properly for a month, and make that your proof of concept. That is how a failed project became a working one.

A bakery with 25 employees supplies fresh loaves to three supermarket chains. One Tuesday morning, a supplier flagged that a single batch of flour might be contaminated. The supermarket buyer asked one question: “Can you tell me, within a day, exactly which of our shelves got products made with that flour?”

The bakery’s answer before the consulting work would have been a shrug. After working with ERPNext Consulting, the answer came back in 40 minutes.

What “traceability” really demands from a small food business

Traceability is not a fancy label on a bag. It means that for every finished product, you can list the batch of every raw material that went into it, where it was stored, and which customers received it. For this bakery, the ERPNext Consulting team set up batch numbers at the point of receiving flour, and those numbers followed the dough through mixing, baking, and packing.

1. Every raw material is received with a batch number, an expiry date, and the name of the supplier.
2. Production records capture which batches went into which mixing run, on which machine and shift.
3. Each finished pallet carries the batch links, so the delivery note for a supermarket shows the exact production history.

Why this was a business decision, not a compliance chore

When the audit came, the bakery produced a list of affected products in under an hour, and the supermarket’s buyer said it was the fastest response she had ever seen from a supplier that size. That moment protected the contract. Since then, the bakery has also reduced waste because expired ingredients surface on a weekly report instead of hiding at the back of a shelf. Knowing exactly what sits where saves money even when nothing goes wrong.

What you can test tomorrow

Pick one product you make, write down every ingredient and its supplier, and time yourself tracing it back. If it takes longer than half an hour, you have a gap. Small food businesses assume traceability is a big-company problem, but this case shows it is achievable with a small team when the batch number is captured at the first step. That single habit is what turned a scary Tuesday morning into a quiet 40-minute report for this bakery.

It was 9pm on a Saturday, and a customer in the shop wanted the last armchair in stock. The website had already sold it twenty minutes earlier. The shop manager called the owner, the owner called the delivery team, and the delivery team said the chair was still in the warehouse. Nobody knew the truth.

That is how a five-store furniture retailer with a web shop and two marketplaces ended up talking to ERPNext Consulting.

The real problem was not the double sale

The double sale was just the visible symptom. In a regular week this retailer was reconciling sales from four channels by hand every evening, and the numbers rarely matched. Stock-outs hit 18 percent of advertised items, and refunds for cancelled orders were eating up time and goodwill. The ERPNext Consulting team started with a simple rule: one central stock number, shared by every channel, updated at every sale.

How one count replaced four daily reconciliations

• Each channel gets the same stock level at the start of the day, and the system deducts a sale the moment it happens on any channel.
• Allocation rules reserve items for the in-store customer first when stock is below three units, because walk-in sales have no delivery cost.
• Staff receive a single consolidated pick list so the warehouse only touches each order once.

The numbers the owner now watches on Monday morning

After eight weeks, stock-out rates dropped from 18 percent to 4 percent, and the daily manual reconciliation simply disappeared. The owner told me the most valuable report is a simple one: items with fewer than three units across all channels, refreshed every morning. It tells him where to chase purchases before a problem starts.

The shift that made everything else possible was installing one shared stock record and insisting every channel connect to it. If you are an owner with two shops and a website, you can start this week: pick one spreadsheet, list your top 20 selling items, and update it from every channel every night for a fortnight. Then imagine what happens when the system does that for you automatically. That is exactly the leap ERPNext Consulting helped this five-store owner make.

A restaurant chain sent back an invoice and refused to pay it. The distributor checked and found the quoted price was 12 percent higher than the contract, because a sales rep had picked the wrong price list from an Excel dropdown. For a 30-person beverage wholesaler with 400 customers on different terms, this was not a one-off. It was a weekly event.

The managing director estimated those pricing mistakes cost around $90,000 a year in rebates, disputes, and awkward apologies.

Where the wrong prices were hiding

The ERPNext Consulting team spent a day listening to the sales team, then a day mapping every price rule the company had. There were customer-specific deals, volume discounts, promotional prices for certain products, and different tax rules by region. Each rule lived in someone’s head or in a messy spreadsheet. When a customer complained, the company just credited the difference instead of fixing the root cause.

What they put in place instead

• One price list per customer group, with a validity period, so old deals automatically expire.
• Volume discount rules that step down based on the last 90 days of purchases, not on a promised figure someone forgot.
• A simple approval step for any manual price override, so exceptions leave a trail and get reviewed monthly.

The quiet win nobody expected

Once the first version of the pricing rules went live, a second benefit appeared. Customers stopped calling to negotiate because the invoice matched the quote every time. Dispute emails dropped by more than half, and the finance team stopped spending two hours a week on credit notes. The managing director says the ERPNext Consulting setup paid for itself within the first quarter — not from new sales, but from money that used to leak out the back door.

If you are still approving manual price adjustments by email, start by listing your five biggest customer groups and writing down the exact rule that applies to each. That list is your starting point, and it is exactly how this wholesaler’s fix began. The invoices you send today are a test of how well you know your own pricing.

Marie is a partner at a 14-person structural engineering firm. She found out a project nicknamed “Green” was 18 percent over budget only when the client said no to an invoice. Her team had filled in timesheets every Friday, sometimes from memory, and the spreadsheet showed everything was fine. It was not fine.

Her first call was to ERPNext Consulting, and the conversation started with one simple question: what does each project actually cost, week by week?

The numbers that were hiding in plain sight

The ERPNext Consulting team set up project budgets with hourly rates for each engineer, then switched time logging from weekly memory to daily reality. Within six weeks, the data exposed three projects out of seven that were priced below what they actually cost to deliver. That gap added up to roughly $40,000 of profit leaking out per year — money the firm thought it was making.

• Planned hours versus booked hours, reviewed every Friday before payroll closed.
• Actual cost per hour compared to the billing rate for each project and each person.
• Remaining budget checked against the next milestone, so overruns surfaced two weeks early.

Why this hurts so many service firms

Most small consultancies treat a timesheet as an admin chore rather than a measurement tool. The result is that under-priced projects look profitable until the cash runs out. Marie’s firm now reviews project margins in a ten-minute Monday meeting, and they re-quote or re-scope any project that drops below a 35 percent margin target. The rule is simple: you cannot fix a margin problem you only discover at invoicing time.

What you can steal from this case tonight

Open your last three closed projects and compare the hours you billed with the hours your team actually worked. If any project is more than 15 percent off, you have found your error rate. That one calculation is the reason Marie called ERPNext Consulting — and the reason she now sleeps better at month-end.