Sales and purchasing

Use /sales/workspace and /purchasing/workspace for document-based business activity. Menu access is associated with documents:read; creation, posting, approvals, and other actions have their own checks.

Start with the business event

A quotation communicates an offer. An order records an agreed demand or supply commitment. A delivery or goods receipt records physical movement. An invoice records billing. A credit document records a supported correction or return-related financial adjustment. Which types and transitions are available depends on configuration.

Do not use the names as proof of posting effects. Inspect the configured stage and resulting stock/accounting records for your business.

Create a document

1. Confirm the company, transaction direction, and document type.
2. Choose the customer or supplier, dates, reference, currency, and warehouse where relevant.
3. Add items with their quantity and unit. Review conversion factors when buying or selling in packs.
4. Check the price source, discount, tax, line amount, and totals.
5. Review payment terms, due date, and dimensions where used.
6. Save, inspect status, and follow the required approval or posting transition.

Never interpret a lookup displaying a record as proof that the record is eligible for every operation. An inactive item, missing setup, insufficient stock, closed period, or permission check can block a later action.

Follow the document flow

When copying or progressing from a source document, inspect the open quantity and references. A partial receipt or shipment should leave the remaining quantity identifiable. Do not create an unrelated full-quantity document as a shortcut around the remaining-quantity controls.

Record the source and target references so a colleague can follow the chain. When the same event appears in order, fulfilment, invoice, and payment views, those are related records rather than permission to enter the event again.

Purchasing example

The business orders ten cases, each containing twelve base units. A demonstration receipt of four cases should be checked against the configured conversion and expected 48 base units. Inspect the received warehouse, lot information where used, and cost values. The supplier invoice and its settlement may occur separately from the receipt.

The example establishes a verification method. Actual supported partial-flow behavior must be confirmed against your configured document types and release.

Sales example

Prepare a customer order for five units. Fulfil the quantity actually dispatched. Check the resulting delivery/invoice references and what remains open. Review revenue, tax, stock relief, and customer balance at the stages configured to produce those effects.

Returns and corrections

Start from the original document when the workflow supports it. Record the quantity and reason actually being returned or corrected. Separate physical receipt of returned goods, the credit document, and payment refund. These actions answer different business questions and may require different permissions.

Check the outcome

Inspect the original document status, related documents, Stock Movements, General Ledger, and partner statement. If a posting fails, preserve the reason and correct its cause before retrying the supported action. Do not assume every endpoint is safely repeatable after a timeout.