A salesperson promises stock based on yesterday's sheet. Purchasing orders more, based on another sheet. Finance discovers both are wrong during month-end. Every one of them worked hard and did their job correctly by their own numbers. The process still produced an expensive surprise, because the same "order" existed as three different facts in three different places.
ETDA's Digital Maturity Index breaks Thai SMEs down by dimension, not just an overall score of 2.45: the personnel and culture dimension scores 2.54, and the process and management dimension — the part that governs exactly this kind of handoff between departments — scores 2.69. Both numbers sound close to acceptable in isolation. Neither one tells you whether a sale, a stock count, and an invoice actually describe the same event by the time they reach accounting. Most Thai SMEs have digital tools in every department. Very few have one sequence those tools actually agree on.
It sounds like a software integration problem — plug the systems together and the numbers will match. It's actually a sequencing problem: a sale, a stock movement, a purchase, a delivery, and a payment aren't five separate facts to be reconciled later. They're one business event, and the moment any step in that chain gets recorded independently, disagreement becomes a matter of when, not if.
One source of truth is not one giant screen. It is one agreed record for each business event.
This piece follows one order through the full chain from sale to management report, shows where most Thai SMEs break that chain without realizing it, and covers the controls and exceptions that keep it honest once it's connected.
Begin With Master Data
Agree on customers, suppliers, products, units, warehouses, prices, tax codes, and accounts before connecting anything else — this groundwork matters most once you've already recognized the operational signs that make disconnected data too costly to keep. Assign a named owner and an approval step for changes to each. A single duplicate item code can quietly defeat an otherwise well-designed ERP before its launch lunch is even finished.
The Event Chain: One Order, Eight Steps, One Truth
Think of a single sales order not as one document but as a chain of eight linked moments, each one feeding the next:
- Sales creates an approved quotation or order.
- The system checks available and already-committed stock.
- A shortage automatically creates a purchasing or replenishment signal.
- Purchase approval produces an order to the supplier.
- Receipt updates stock and records any discrepancy found.
- Delivery reduces stock and provides evidence of fulfilment.
- Invoice and payment status connect directly to finance.
- Management sees margin, backlog, stock, and cash impact from that same original event — not a separate report built later from a different export.
Call this the Event Chain: the discipline of treating one business event as one record that travels forward through every department, instead of eight departments each recording their own version of something that happened once.
Picture a hypothetical company called Sap Charoen Auto Parts, a fictional distributor supplying spare parts to garages across a province. Before connecting its systems, a single customer order at Sap Charoen existed as a WhatsApp message to the warehouse, a paper picking slip, a separate purchasing note when stock ran short, and a manually typed accounting entry once the invoice was paid — four independent records of one event, created by four different people at four different times, none of them automatically aware the others existed. The fix wasn't a bigger spreadsheet. It was making step two of the chain — checking real stock — impossible to skip before step one was confirmed, so every later step inherited a number that was already correct.
Design the Exceptions on Purpose
Real operations aren't eight clean steps every time. Define how the chain handles partial delivery, returns, damaged stock, a price override, a supplier delay, a cancelled order, and a manual adjustment — and give each exception a named owner and an explicit approval rule, rather than leaving staff to improvise a workaround that quietly becomes the new normal process.
Report From Operations, Not Monthly Archaeology
Useful dashboards show order backlog, stock availability, ageing, purchasing commitments, fulfilment time, and margin, each with a clear definition everyone actually agrees on. Reconcile these figures to accounting and investigate real differences, rather than exporting everything into yet another uncontrolled workbook that becomes its own disconnected source of truth. Across ASEAN, add entities, currencies, local taxes, warehouses, and access boundaries as needed — without losing the group-level definitions that let management compare across the whole business.
Put Controls Into the Flow, Not On Top of It
Set clear approval thresholds for price discounts, purchase value, stock adjustments, and supplier changes. Separate the request, approval, and payment roles where it genuinely matters. Keep audit history and reason codes attached to every exception, without turning ordinary daily work into a six-click ceremony nobody has patience for by month three.
Integrate Accounting Deliberately
Decide exactly when an operational event creates an accounting entry, and how a failed match gets reconciled rather than quietly ignored. Map tax codes, cost centers, payment terms, and document references, and have finance approve the mapping and test it against normal transactions, returns, partial deliveries, and corrections — not just the clean example in the vendor demo. If you're also planning to connect e-Tax Invoice and PromptBiz workflows, align these same document references before go-live so the two projects reinforce each other instead of duplicating work.
Plan Migration and Measure the Result
Clean product codes, units, opening stock, suppliers, customers, prices, and open transactions before migrating, and rehearse the migration itself, reconciling totals rather than assuming they'll match. Avoid importing years of low-quality history simply because storage space allows it — a clean shorter history beats a long messy one every time.
Track order-to-delivery time, stock accuracy, purchase approval time, emergency orders, manual adjustments, closing time, and report preparation time, with a named owner for each metric reviewed weekly during stabilization. Expect a genuine learning period, protect staff time for training, and keep a clear fallback for critical operations — running the old and new systems forever isn't a fallback, it's simply two jobs instead of one.
The Event Chain Playbook
- One Event, One Record — treat a sale, a stock movement, and a payment as stages of a single tracked event, never as separate facts to be reconciled after the fact.
- Exception Ownership — every deviation from the standard chain (a return, a price override, a delay) gets a named owner and an approval rule before it happens, not improvised after.
- Weekly Metric Review — during the first months live, review order-to-delivery time and stock accuracy weekly, because small chain breaks are far cheaper to fix in week three than in month six.
- Cross-Industry Check — a multi-branch clinic or hospital group runs the identical chain under different names: a booking becomes a service, which affects supply stock, which triggers billing, which closes into accounting — the discipline of one event, one record applies exactly the same way.
Continuity: What This Actually Comes Down To
If there's one word for what actually connects inventory, purchasing, sales, and accounting, it's Continuity — not a bigger dashboard, just making sure the same fact keeps its identity as it moves from department to department instead of being re-created from scratch at every handoff.
Here's a fair question to sit with: pick one order from last week and try to trace it — sale, stock, purchase, delivery, invoice, payment — using only the systems you have today. If that trail breaks anywhere, breaks quietly, or takes more than a few minutes to follow, that's exactly where your next expensive month-end surprise is already forming.
FAQ
Does connecting these processes mean replacing every existing system?
Not necessarily. It means agreeing on which system owns each part of the chain and making sure every step reliably passes the right information to the next one — sometimes through integration, not wholesale replacement.
What's the most common place the Event Chain actually breaks?
Between the sale and the stock check. Many Thai SMEs still let sales promise availability from a static export instead of checking committed and available stock in real time, which is exactly where the chain first splits into disagreeing versions.
How long does it typically take to see results after connecting the chain?
Expect a genuine stabilization period of a few months. The clearest early signal is usually fewer emergency calls to confirm stock and less time spent on manual reconciliation at month-end.
Do exceptions like returns and price overrides need to be automated too?
Not automated so much as defined — every exception needs a named owner and an approval rule, whether it's handled by a person or a system, so it doesn't quietly become an unrecorded workaround.
If your sales, stock, purchasing, and accounting numbers currently disagree by the time month-end arrives, request an operations mapping workshop from NAWA and we'll help you model one end-to-end flow and its exceptions before any configuration begins.