Understanding ERP: how a business works as one connected system

A customer orders 100 office chairs. The salesperson agrees on the price, the warehouse prepares the stock, and finance arranges the invoice.

Each department has a different responsibility, but they are all handling the same sale. If they work from separate spreadsheets and messages, their information can disagree. Sales may promise chairs that are unavailable. The warehouse may deliver an outdated quantity. Finance may bill the customer for goods that have not yet been supplied.

An ERP connects these responsibilities through shared business records. Understanding those connections is the foundation for using DNA ERP effectively.

What is an ERP?

ERP stands for Enterprise Resource Planning. It is a system for managing a company's resources, commitments, operations, and financial records together.

Those resources include stock, money, materials, production capacity, and people's time. Commitments include customer orders, supplier purchases, project budgets, and promised delivery dates.

An ERP helps a business answer questions such as what it has promised customers, what remains to be delivered, what must be purchased or manufactured, how much has been billed or collected, and which activities are delayed or exceeding their budgets.

Its value comes from connecting the answers. A large sales order may look attractive, for example, but fulfilling it could require purchasing materials before the customer pays. Understanding the sale therefore also requires understanding stock availability and cash requirements.

How DNA ERP connects departments

DNA organises work into modules such as Sales, Purchasing, Inventory, Manufacturing, Projects, and Finance. Each module represents a business responsibility. Their records connect when work passes from one responsibility to another.

For a trading company, a customer order can lead to a warehouse delivery, an invoice, and a customer payment. If stock is insufficient, purchasing becomes part of the process. For a manufacturer, fulfilling an order may also involve material requirements and production. For a project business, the same commercial commitment may involve work packages, budgets, and milestone billing.

A delivery affects the warehouse's responsibilities. An invoice affects billing. A payment affects settlement. They describe related events, but each event has its own meaning.

The records that describe a sale

• Quotation: Business meaning: A proposed price and set of commercial terms; Question it answers: What are we offering?
• Sales order: Business meaning: The recorded customer commitment; Question it answers: What have we agreed to supply?
• Delivery note: Business meaning: The goods supplied in a particular delivery; Question it answers: What has left the warehouse for this customer?
• Sales invoice: Business meaning: The amount billed under the agreed arrangement; Question it answers: What are we charging the customer?
• Customer payment: Business meaning: Money received from the customer; Question it answers: What have we collected?
• Payment allocation: Business meaning: The connection between a receipt and the invoices it settles; Question it answers: Which outstanding amounts has that payment covered?

These events do not necessarily happen together. A customer may pay an advance before delivery. An order may be supplied in several deliveries. An invoice may be settled through several payments. A project may be billed according to completed milestones instead of quantities delivered.

DNA provides linked sales, delivery, invoice, and payment records for these arrangements. Its payment-term model distinguishes Days, Advance, Progress, and Mixed terms. The selected terms determine whether an order uses a billing plan; these arrangements should not be treated as interchangeable labels.

One order, several stages of completion

A fictional supplier agrees to sell 100 chairs at USD 200 each. The order value is USD 20,000, with taxes and additional charges excluded from this example. It delivers 60 chairs and invoices those chairs for USD 12,000. The customer pays USD 7,000, allocated to that invoice.

• Customer order: 100 chairs / USD 20,000
• Delivered: 60 chairs
• Still to deliver: 40 chairs
• Invoiced: USD 12,000
• Collected and allocated: USD 7,000
• Outstanding on the issued invoice: USD 5,000
• Order value not yet invoiced: USD 8,000

The USD 5,000 outstanding invoice balance and the USD 8,000 not yet invoiced represent different things. One is an unpaid billed amount; the other is a remaining billing commitment under this example.

DNA's delivery and billing progress information helps distinguish these positions. Sales can understand the remaining commitment, the warehouse the remaining quantity, and finance the unpaid invoice. Calling the entire order simply complete or incomplete would hide information those teams need.

Why shared business data matters

Transactions depend on reusable information called master data. This includes customers, suppliers, items, warehouses, units of measure, and payment terms.

Master data gives repeated business activity a consistent foundation. If departments use different records for the same customer, that customer's orders and payments can become fragmented. If an item's unit of measure is misunderstood, ten could mean ten individual pieces or ten boxes.

In DNA, customer settings and payment terms help establish the commercial context of a sale. Item and warehouse information establish what is being supplied and where it is held. Reliable reporting therefore begins with consistent records and accurate transactions.

How advanced DNA features address business needs

Partial delivery and billing help when a commitment is fulfilled over time. A supplier can track what has already been supplied and billed while retaining visibility of the remaining order.

Progress billing suits work billed at agreed stages. An installation contract might be billed after design approval, equipment delivery, and commissioning. DNA's billing plans connect these milestones to the commercial arrangement. This differs from ordinary quantity-based billing because the billing event is an agreed stage of work.

Advance payments and retention address different timing needs. An advance provides funding before later fulfilment. Retention is an agreed amount withheld until a later contractual condition is satisfied. DNA supports these arrangements within relevant billing workflows, including advance recovery and retention collection. Recovery applies money already paid toward a later invoice; it is not a second discount or a reduction in the agreed contract value. In the order-based recovery calculation, the amount applied is limited by both the remaining advance and the invoice subtotal used by that calculation, after line discounts and before tax.

Discounts, coupons, and promotions serve different commercial purposes. A negotiated discount may support a specific deal. A coupon identifies a controlled offer. A promotion applies an incentive under defined conditions, such as purchasing a qualifying quantity. DNA provides distinct features because their eligibility and business purpose differ.

Approvals and access rights distribute responsibility. Access rights govern what a person may do. Approval rules determine when a supported transaction needs additional authorisation. DNA can route certain approvals according to value, department, warehouse zone, or cost-centre responsibility.

Understanding what the system is telling you

An order is evidence of a commitment, not proof of collection. A delivery is evidence of goods supplied, not proof that every related invoice is settled. A high sales figure alone does not explain profitability or available cash.

The essential skill is to recognise what each record represents, how it relates to other records, and what remains unresolved. That understanding makes DNA's modules meaningful and provides the foundation for the specialist lessons that follow.