M1MaluOne ERP

MaluOne ERP overview

Follow the documents, stock and money through one connected business process. See what each team prepares, what the next team checks, and what managers review.

Discuss your ERP workflow

The full system at a glance

The full system at a glance: Sales & CRM, Purchasing, Inventory, Manufacturing, Finance, Management. Shared business records. Roles · Approvals · Branches · Audit history. Stock balances · Customer / supplier balances · Financial reports.
Illustrative business architecture, not a product screenshot. Confirm supported links, posting rules and controls in your demonstration.
Open full-size system image ↗

Business documents and working flows

Each document records a different event. An order is a commitment, a delivery records movement, an invoice records an amount billed, and a receipt records payment. Keep their references connected without treating them as the same event.

01 · Sales & CRM

Sales: quotation to collection

Sales advisor reviewing a customer order, warehouse staff preparing delivery, and finance matching invoice and receipt records.
Illustrated business example — not a product screenshot.

Who prepares it

Sales records customer requirements, products, prices and terms. The warehouse records actual dispatch; finance reviews billing and payment references.

What the next team checks

Check the approved order, actual quantity delivered and billing terms. Match each receipt to the correct customer invoice; keep undelivered and unpaid amounts separate.

  1. 01Quotation
  2. 02Sales order
  3. 03Delivery note
  4. 04Customer invoice
  5. 05Receipt
Illustrative document sequence. Actual document names and approval steps depend on the agreed scope.

Example

Order 100 units; deliver 60 and leave 40 pending. Invoice the delivered 60 for 12 million LAK under the agreed terms. Receiving 5 million leaves 7 million unpaid on that invoice.

Monetary examples exclude tax and other adjustments.
THE EXAMPLE AT A GLANCE

Customer order · 100 units

60Delivered
40Pending

60 + 40 = 100 units

Invoice · 12 million LAK

5mReceived
7mUnpaid

5m + 7m = 12m LAK

Illustrative figures; confirm the agreed business rules. Monetary examples exclude tax and other adjustments.

02 · Purchasing

Purchasing: request to payment

Buyer reviewing a supplier order while receiving staff count delivered cartons and inspect damaged goods.
Illustrated business example — not a product screenshot.

Who prepares it

The requesting team states the need. Purchasing agrees the supplier order. Receiving staff count and inspect goods; accounts payable reviews the invoice.

What the next team checks

Compare requested, ordered, received and invoiced quantities. Resolve shortages or damage and check supplier invoice references before approving payment.

  1. 01Purchase request
  2. 02Purchase order
  3. 03Goods receipt
  4. 04Supplier invoice
  5. 05Payment
Illustrative document sequence. Actual document names and approval steps depend on the agreed scope.

Example

Order 100 cartons at 300,000 LAK each; receive 80. The 20 outstanding cartons represent 6 million LAK at the order price. Review an invoice for all 100 against receipt evidence and agreed supplier terms.

Monetary examples exclude tax and other adjustments.
THE EXAMPLE AT A GLANCE

Purchase order · 100 cartons

80Received
20Outstanding

Record actual receipt: 80, not 100

Supplier invoice review

30mInvoice
24mReceived value
6mDifference

At 300,000 LAK per carton · review before payment

Illustrative figures; confirm the agreed business rules. Monetary examples exclude tax and other adjustments.

03 · Inventory

Inventory: movement to reconciliation

Warehouse staff scanning stock, transferring cartons between storage areas and checking a physical count.
Illustrated business example — not a product screenshot.

Who prepares it

Warehouse staff record the product, unit, location and actual quantity for each movement. A count team records physical quantities at an agreed cutoff.

What the next team checks

Trace each balance to receipts, transfers and issues. Investigate count differences before an authorized adjustment. Separate damaged or held items from saleable stock.

  1. 01Goods receipt
  2. 02Transfer record
  3. 03Issue / return
  4. 04Count sheet
  5. 05Approved adjustment
Illustrative document sequence. Actual document names and approval steps depend on the agreed scope.

Example

Receive 100 in A, transfer 30 to B and issue 20 from A. The balances are A=50 and B=30, total 80. The transfer changes location, not the total quantity.

Monetary examples exclude tax and other adjustments.
THE EXAMPLE AT A GLANCE

Stock after transfer and issue

50Warehouse A
30Warehouse B

100 received − 20 issued = 80 total

Warehouse B count review

30Recorded
28Counted
2Investigate

Retain count evidence before approving a correction

Illustrative figures; confirm the agreed business rules. Monetary examples exclude tax and other adjustments.

04 · Manufacturing

Manufacturing: plan to finished goods

Furniture workshop connecting material storage, table assembly, inspection and rework.
Illustrated business example — not a product screenshot.

Who prepares it

Planning confirms the current material list and required output. Production records actual consumption, returns, scrap, rework and finished quantities.

What the next team checks

Check material readiness, approved specifications and actual output. Confirm quality release, unfinished work and cost allocation requirements before agreeing scope.

  1. 01BOM / routing
  2. 02Production order
  3. 03Material issue
  4. 04Output record
  5. 05Cost review
Illustrative document sequence. Actual document names and approval steps depend on the agreed scope.

Example

Plan 50 tables but complete 48. Keep the remaining two visible as unfinished work. Reconcile materials consumed, returned or damaged before reviewing the cost of completed output.

Monetary examples exclude tax and other adjustments.
THE EXAMPLE AT A GLANCE

Production order · 50 tables

48Completed
2In progress

Planned quantity is not finished stock

Reconcile 204 issued legs

192In finished tables
8Unfinished work
4Damaged

192 + 8 + 4 = 204 legs

Illustrative figures; confirm the agreed business rules. Monetary examples exclude tax and other adjustments.

05 · Finance

Finance: source document to reports

Finance team comparing invoices, receipts and bank records during reconciliation.
Illustrated business example — not a product screenshot.

Who prepares it

Finance reviews source documents, account mapping, posting dates and approvals. Responsible reviewers reconcile bank, customer and supplier balances.

What the next team checks

Use consistent periods and filters. Trace report balances to source records. Confirm which entries are generated automatically and which require manual review or posting.

  1. 01Source document
  2. 02Entry / journal
  3. 03Reconciliation
  4. 04Financial reports
  5. 05Period close
Illustrative document sequence. Actual document names and approval steps depend on the agreed scope.

Example

A 10 million LAK invoice with a 4 million receipt leaves 6 million unpaid. An approved 1 million credit reduces that balance to 5 million. Invoice value and cash collected are different measures.

Monetary examples exclude tax and other adjustments.
THE EXAMPLE AT A GLANCE

Customer balance · million LAK

10mInvoice
4mReceipt
6mUnpaid

10m − 4m = 6m outstanding

After an approved credit

6mBefore credit
1mCredit
5mRemaining

6m − 1m = 5m outstanding

Illustrative figures; confirm the agreed business rules. Monetary examples exclude tax and other adjustments.

06 · Management

Management: responsibility to decision

Managers reviewing business documents, approval responsibilities and branch performance together.
Illustrated business example — not a product screenshot.

Who prepares it

Process owners define responsibilities and approval rules. Managers review supporting documents, decide within their authority and assign follow-up actions.

What the next team checks

Confirm access by role and branch, which changes require renewed approval, and what history is retained. Trace summary figures to the underlying documents.

  1. 01Role / policy
  2. 02Review request
  3. 03Approval decision
  4. 04Dashboard review
  5. 05Exception follow-up
Illustrative document sequence. Actual document names and approval steps depend on the agreed scope.

Example

With a sample review threshold of 5 million LAK, a 7 million purchase request requires manager review. Test the buyer and manager roles and a change made after approval.

Monetary examples exclude tax and other adjustments.
THE EXAMPLE AT A GLANCE

Sample approval rule

5mReview threshold
7mPurchase request

7m exceeds 5m LAK: manager review required

Decision and change review

01Buyer prepares
02Manager reviews
03Changes checked

Verify authority and retained history in the demo

Illustrative figures; confirm the agreed business rules. Monetary examples exclude tax and other adjustments.

What connects the teams?

One reference chain

Keep the customer or supplier, product, unit and original document reference consistent across handovers.

Actual events, separate statuses

Review ordered, delivered, invoiced and paid quantities or amounts independently. Partial transactions should remain explainable.

Controlled corrections

Use approved return, credit, cancellation or adjustment procedures. Retain the original evidence and review the stock and financial effects together.

Confirm the complete process in a demonstration

These diagrams explain the intended business workflow. Ask to see the normal transaction, a partial transaction and a correction with your own sample documents. Confirm supported modules, integrations, permissions, accounting rules and limitations in writing. The separate MaluOne CRM application manages MaluOne's own sales pipeline; automatic CRM-to-ERP exchange is not implied.

Bring one real order and its related documents. We can use them to discuss the workflow, responsibilities and implementation scope.

Discuss your ERP workflow