Document Transaction Setup

Document Transaction Setup defines the document types users can create in operations. A document type is the contract that tells users what the document represents and tells the system which lifecycle, approval, stock, pricing, numbering, or accounting behavior may apply.

This setup is shared. Agriculture, Production, Events, Inventory, Billing, and other services may launch document flows from their own context, but they should reuse these same document-type rules instead of creating service-owned document engines.

Workspace Reference

Workspace	How Users Reach It	What Users Usually Do There
Document Transaction Types	Document Transactions -> Setup -> Document Transaction Types	Create or maintain shared document types used across services.
Event Document Types	Events -> Setup -> Document Transaction Types	Reach the same shared document-type setup from the Events context when event users administer it.
Service Document Setup	Service-specific setup areas where available	Review package-managed document behavior that supports production, agriculture, inventory, billing, or inspections.

Type Details

Use the Type Details section to make the document easy to identify and select.

• Type Name is the user-facing name shown in lookups and tables.
• Domain groups the type under a business area such as General, Inventory, Sales, Production, Agriculture, Assets, HR, or Compliance.
• Family describes the document shape, such as Quote, Order, Requisition, Reservation, Issue, Receipt, Transfer, Inspection, Delivery, Return, Adjustment, Costing, or Other.
• Direction explains whether the document is inbound, outbound, internal, or not directional.
• Default Status controls the starting status for new documents. Most operational documents should start as Draft unless the business deliberately wants them released faster.
• Description should explain when the type is used and what users should not use it for.

Use specific names. For example, “Production Material Requisition” is clearer than “Request Form”.

Lifecycle And Numbering

Lifecycle settings control whether users can move the document directly through operations or whether a reviewer must approve it first.

• Document Number ID Template controls the numbering pattern users see on created documents. The backend resolves numbering from the saved document type and its mapped ID template, falling back only where no type-specific mapping exists.
• Requires Approval means users must route the document for approval before it is considered ready for downstream use.
• Default Workflow Template appears when approval is enabled and defines the approval path.
• Active controls whether users can select the type for new documents.

If a type is package-managed, treat it as a standard system-provided type. Update the rollout or package source instead of editing the live record directly.

Users should not rely on manually typed document numbers. Use External Reference for donor references, bank slips, field sheets, supplier notes, paper receipt numbers, or buyer references. The system-generated document number should come from the document type configuration.

Stock Dependency

Enable stock behavior only when the document should drive inventory movement or reservation behavior.

• Affects Stock marks the type as stock-aware.
• Stock Effect describes the intended stock behavior, such as reserve, receive, issue, transfer, or adjust.
• Stock Movement Type maps the document outcome to the stock movement users expect for inventory, valuation, and audit review.

If the document only records a commercial or approval decision and should not move inventory, leave stock behavior off.

Pricing Dependency

Enable pricing behavior when the document should calculate charges, accruals, collections, waivers, reversals, or other pricing effects.

• Affects Pricing turns on pricing integration for the document type.
• Pricing Profile selects the pricing setup used to calculate charges.
• Pricing Trigger Event lets administrators distinguish why the pricing rule should run.
• Pricing Effect Type explains the intended pricing outcome, such as assess, accrue, due, overdue, collect, waive, reverse, capitalize, or adjust.
• Post Pricing To GL means pricing results may be sent to accounting.
• Create Pricing Transaction means the pricing result should be recorded as a pricing transaction for follow-up.
• Fail Document On Pricing Error means the document should not proceed if pricing cannot be completed.

Use strict failures for documents where price accuracy is mandatory before approval or fulfillment.

GL Dependency

Enable direct GL behavior only when the document itself has accounting impact.

• Affects GL marks the type as directly accounting-relevant.
• Document GL Posting Rule selects the finance rule used for the document accounting.
• Document GL Amount Source controls which value is sent to accounting, such as total amount, subtotal, tax, discount, line total, or cost total.
• Document GL Posting Channel indicates whether posting is a back-office review action or a system-driven posting action.

Stock valuation accounting should normally be owned by the stock movement setup, not duplicated on the document type.

Setup Checklist

Before activating a document type, confirm:

• Users understand when to choose it.
• The family and direction match the business meaning.
• Approval is enabled only when a review is actually required.
• Stock behavior is enabled only for documents that should affect inventory.
• Pricing behavior is enabled only when the document should calculate or record charges.
• Direct GL behavior is enabled only when finance has mapped the posting rule.
• One sample document has been created and reviewed through its full lifecycle.

If the type is used by a service workspace, test it from that service context as well. For example, a production order type should be checked from the Production workspace, and an agriculture produce-delivery or settlement type should be checked from the Agriculture source workflow, not only from the generic document transaction list.