Field descriptions: Sales transactions
The fields that appear in your
The following tables describe the buttons and More actions menu options that might appear on a Order Entry transaction. The options you'll see depend on the following factors:
-
Whether the transaction is in Add, Edit, or View mode
-
The transaction state
-
The transaction definition configuration
-
The application configuration
Buttons
| Field | Description |
|---|---|
| Post |
Saves the transaction and, if applicable, posts the transaction to the GL or Accounts Receivable (as configured in the Transaction posting option in the transaction definition). This button appears when the transaction is in Add or Edit mode if the transaction state is not Converted. |
| Draft |
Saves the transaction with a Draft state. |
| Cancel |
Cancels any changes and exits the transaction. This button appears when the transaction is in Add or Edit mode. |
| Edit |
Places the transaction in Edit mode. This button appears when the transaction is in View mode and the following conditions are true:
|
| Done |
Exits the transaction. This button appears when the transaction is in View mode. |
|
Post & Pay |
Displays the Select Invoice Payment page. This page allows you to apply a full or partial payment to the invoice. Post & Pay appears when the invoice is in Edit mode if the invoice state is not Converted or Partially Converted. When selected, it will post any invoice changes before displaying the Select Invoice Payment page. Pay appears when the invoice is in View mode if the invoice state is not Draft, Converted, or Partially Converted. These buttons only appear if payment processing is set up in Order Entry. Learn more about applying payments to an invoice in Order Entry. |
| Print or email |
Displays the Print or email dialog box from which you can choose to print and/or email a PDF of the transaction. Printing a PDF from this dialog box will set the transaction's Printed flag to Y. Learn more about how to print or email an individual document. This button appears when the transaction is in Edit or View mode. |
More Actions menu
| Option | Description |
|---|---|
| Post & new |
Saves the transaction and, if applicable, posts the transaction to the GL or Accounts Receivable (as configured in the Transaction posting option in the transaction definition), and displays and new transaction page. This option appears when the transaction is in Add mode. |
| Post & print |
This option appears when a transaction is in Add mode or when a Draft transaction is in Edit mode. |
| Draft & continue |
Saves the transaction with a Draft state and stays on the current transaction to allow further changes. This option appears when a transaction is in Add mode or when a Draft transaction is in Edit mode. |
| Copy from |
Copies the information in another sales transaction into the current transaction. When you select this menu option, a Select Order Entry transaction list appears. Find the transaction from which you want to copy and select the Select link next to it. The system populates the current transaction with the information from the selected transaction. This option appears when the transaction is in Add mode. |
|
View as XML |
Displays the XML code for the transaction. You can use a field's XML code to help identify it in CSV import templates, printed document templates, and in some error messages. To help identify a blank field's code, enter the UI field label in the field before choosing the View as XML option. Then scan the XML for the desired label text.
This option appears when the transaction is in Edit or View mode. |
|
View as PDF |
Displays the transaction as a PDF in your browser's default PDF viewer. This lets you review the document without setting the Printed flag to Yes. Learn more about printing an individual document. This option appears when the transaction is in Edit or View mode. |
| Post & continue |
Saves the transaction and, if applicable, posts the transaction to the GL or Accounts Receivable (as configured in the Transaction posting option in the transaction definition), and stays on the current transaction to allow further changes. This option appears when the transaction is in Edit mode if the transaction state is not Converted or Partially Converted. |
| View audit trail |
Displays the Audit Trail page for the transaction, which shows who changed the transaction and when the changes happened. Learn more about the audit trail. This option appears when the transaction is in Edit or View mode. |
| Repeat |
Starts the process to copy the current transaction into a recurring template, which the system uses to create recurring transactions. This option appears when the transaction is in Edit or View mode. |
| Convert to |
Lets you convert the entire transaction into the next transaction in the workflow. Go to Convert to and select the transaction to which you want to covert. The new transaction appears and displays all the information from the source transaction. This option appears in Edit or View mode and the following conditions are true:
|
| Copy to |
For example, you can create a new sales order from an existing sales order or OE sales invoiceinvoice. This option appears when the transaction is in Edit or View mode. |
| Edit Entries layout |
Sage Intacct administrators can change the column layout in the Entries section of a transaction. You can customize the grid to show only the columns that are meaningful to your company. The columns that do not display in the grid are still accessible by selecting Show details for each transaction line item. You can also rearrange the columns in any desired order. Learn how to customize a transaction's Entries grid layout. |
Transaction tab
The following tables describe each field on a transaction page.
Transaction tab: Header section
| Field | Description |
|---|---|
|
Date |
If you are creating a transaction, this field defaults to today's date. If you are converting a transaction, this field defaults either to today's date or the source transaction's date, depending on your defined user preference. Use the calendar tool to change the date. This field is required. |
|
Customer |
Use the Customer selection list to select the desired customer. This field is required. You can change the Customer in a Draft or Pending transaction if the Edit policy and Allow edit of customer fields on the transaction definition are set appropriately. Learn more about the Allow edit of customer option. |
| Supplier |
Use the Supplier selection list to select the desired supplier. Selecting a supplier is not required unless the following conditions exist:
You can change the supplier in a Draft of Pending transaction if the Edit policy and Allow edit of supplier fields on the transaction definition are set appropriately. Learn more about the Allow edit of supplier option. |
|
Project |
Use the Project selection list to select the desired project If the Projects dimension is enabled in Order Entry or Purchasing, this field is available to any company with an Order Entry or Purchasing subscription. No Projects subscription is necessary. |
|
Document number |
Enter a number to identify the transaction. This field appears in add or edit mode if the transaction definition does not have a Numbering sequence selected. A document number is not required in draft transactions. |
|
GL posting date |
Use the calendar tool to select the date the invoice will post to the GL. |
|
|
Defaults to the contact identified as the This field is required. To edit the contact address or e-mail address from this page:
|
|
|
Defaults to the contact that's identified as the Ship-to contact on the selected If Enable ship-to contact at the line level is set to true in the Configure Order Entry page, expect the following behavior: If you change this Ship to contact, the system updates all line item Ship to contacts that previously matched this header value to the new value. It will not affect line level ship to contacts that were specified as different ship to contacts. This field is required. |
| Deliver to |
This field only appears if Enable deliver-to contact at the header level is selected in the Configure Purchasing page. Defaults as follows:
Depending on whether the transaction definition allows editing on this field, you may be able to select a different contact record. |
|
Converted from |
This field appears only if the transaction was converted from another transaction. When the transaction is in edit or view mode, the field displays a link to the transaction it was converted from. If the transaction was converted from multiple source transactions (several transactions were merged in the Process Transactions page), the link reads as "Multiple source transactions". |
| Convert from an existing transaction | Select the link to review a list of transactions available to convert. |
|
VAT Reg No |
This field only applies to companies subscribed to the Taxes application. A read-only field that displays the VAT registration number for the Ship to contact. If the Ship to contact doesn't have a tax number specified, the field is blank. Learn more about entering taxable transactions. |
|
This field only appears if your companies subscribed to the Taxes application and the following conditions are true:
Select the tax solution that you want to use for determining and capturing tax for the transaction. All the tax solutions that are set up for your company appear in the dropdown list. If you select No Tax, taxes aren't added to the transaction. If you converted to this transaction from another transaction in which a tax solution couldn't be selected, it's possible that the locations in the transaction you converted from do not map to the selected tax solution.
If that happens, you'll receive an error message when you post the transaction. Change the locations so that they belong to an entity that uses the selected tax solution. The location dropdown list in the converted to transaction is filtered to display only those locations that belong to an entity. Example Assume you to convert Sales orders to OE sales invoices in your sales workflow. The transaction definition for Sales orders doesn't include a tax subtotal line, but the transaction definition for OE sales invoices includes a tax subtotal line. When you enter a sales order, you can select a location from any entity for each line item. When you convert the sales order to an OE sales invoice, you select a tax solution for the invoice. If any of the locations do not belong to an entity that's associated with the tax solution, you cannot save the invoice until you change those locations. |
|
|
Payment terms |
Use the |
|
Expiration date |
If the Payment term field contains a value, the Expiration date field defaults to the transaction date + the number of days in the term. Use the calendar tool to select the date when the quote will no longer be valid. This field is required. This field is only applicable to quotes and supplies requests. |
|
Ship date |
If the Payment term field contains a value, the Ship date field defaults to the transaction date + the number of days in the term. Use the calendar tool to select the date the items in the sales order are expected to ship. This field is only applicable to orders. |
|
Date due |
If the Payment term field contains a value, the Date due field defaults to the applicable date based on the term. Use the calendar tool to select the date payment is due. |
|
Reference |
Enter a reference to another document or any text as needed. For OE sales invoices that are generated from Projects, Intacct populates this field with the value from the Purchase order number field from the project, if applicable. |
|
Customer PO number |
Enter the purchase order number the customer provided to make it easier to associate the sales transaction with the customer's PO number. For invoices generated from Projects: Intacct does not populate this field with a value during invoice generation. Instead, it populates the invoice Reference field with the Purchase order number from the project. |
|
Message |
Enter any text that you want to appear on the printed document. This message prints in addition to any Optional default text defined in the transaction definition or text defined in the document template. |
|
Shipping method |
Use the Shipping method selection list to select the shipping method.
|
|
Attachment |
Add any supporting documents as an attachment. Learn more about adding attachments. |
|
Sales contract ID Sales contract description |
The contract reference number and any text description of the contract. These fields are only applicable if the invoice was created from a recurring template. |
|
Base currency |
Use the selection list to select the functional currency to use for the transaction. This field is only applicable to multi-entity, multi-currency companies that have multiple base currencies enabled and is only displayed when the transaction is created at the top level company. |
|
Txn currency |
Defaults to the transaction currency associated with the selected customer. If you want to change the default, use the Transaction currency dropdown list to select the currency in which the transaction is to be expressed. This field is only applicable to multi-currency companies. |
|
Exchange rate date |
The date the exchange rate used by the transaction was valid. Defaults to today's date. Use the calendar tool to select a different date. This field is only applicable to multi-currency companies. |
|
Exchange rate type |
Defaults to the exchange rate type defined in the transaction definition. If the transaction definition is set to allow user override of the exchange rate type, you can use the selection list to select a different exchange rate type. If you edit an existing rate or import a rate that doesn't include an exchange rate type, the system automatically sets the Exchange rate type to Custom. This field is only applicable to multi-currency companies. Learn more about Exchange rate types. |
|
Exchange rate |
Defaults to the exchange rate for the selected Txn currency (if that currency is different from the base currency) based on the date entered in the Date field. If the transaction definition is set to allow user override of the exchange rate, you can edit this field. This field is only applicable to multi-currency companies. |
|
State |
After posting a transaction, this field displays the workflow status. Learn more about transaction states. |
|
Fair value price list |
Displays the default Fair value price list. This field only appears if Revenue Management is configured to Enable MEA allocations. If Revenue Management is configured to also Enable override of fair value price lists, you can use the selection list to select a different fair value price list. |
|
MEA allocation |
Displays a link to the MEA (Multiple Element Arrangement). Allocation Details page for the transaction if applicable. Learn about MEA allocations in Order Entry. |
| Contract | Displays a link to the contract. This field is only applicable if the invoice was generated from the Contracts application. |
Transaction tab: Shipping dates subsection
This subsection appears if Enable shipping dates in Purchasing and Order Entry is selected in the Configure Inventory Control page.
This subsection appears if Enable shipping dates in Purchasing and Order Entry is selected in the Configure Inventory Control page.
The fields in this section provide additional date tracking capabilities that are typically used by integration systems but can also be used in custom reporting to improve order management.
| Field | Description |
|---|---|
|
Need by date |
The date |
|
Ship by date |
The date the goods should be shipped so they arrive when the customer needs them. This field is automatically calculated based on the Need by date minus the Estimated days in transit from the shipping method. The default shipping method for the transaction (the Shipping method field) is determined in this order:
If the value of Estimated days in transit is blank or a shipping method is not specified, the Ship by date is the same as the Need by date. If the Need by date or shipping method is changed, the Ship by date is recalculated. So, if you manually override the value in Ship by date, you need to override it again.
|
|
Cancel after date |
The date after which the transaction should be canceled. |
|
Do not ship before date |
The date before which the goods cannot be shipped. |
|
Do not ship after date |
The date after which the goods cannot be shipped. |
|
Service delivery date |
If services are related to the order of the goods, such as installation or customization, the date those services are scheduled. |
|
Tracking number |
A text field for shipper tracking numbers. If goods are shipped in multiple shipments, you can enter multiple numbers. Separate multiple numbers by a comma with no spaces.
|
|
Shipped date |
The date the goods were shipped. |
Transaction tab: Additional information section
The following optional sections appear on order and quote documents if you enable them in the corresponding transaction definition. These sections allow you to capture new and changing information throughout the life cycle of orders or quotes, regardless of their document state.
This section is applicable only if your company is subscribed to Construction.
| Field | Description |
|---|---|
| Scope | Identify what work is included and excluded, as well as the reason why and terms. |
| Schedule | Identify dates for work milestones. |
|
Internal Reference and External Reference |
Identify who authorized the work internally and externally and when they authorized the work. |
| Bond | Identify information about performance and payment bonds, as well as information about the surety companies that hold the bonds. |
Transaction tab: Entries section
Sage Intacct administrators can change the column layout for the Entries grid to display the most meaningful columns for each transaction definition. Learn more about customizing the Entries layout.
| Field | Description |
|---|---|
| Item ID |
Select an item from the dropdown list. The transaction needs to have at least one item to be posted or saved as a draft. |
| Warehouse |
This field might default to the warehouse that's associated with the selected item or a warehouse that you've defined in your user preferences in the general preferences section. Use the Warehouse selection list to select the applicable warehouse as needed. |
| Conversion type | If price conversion is enabled, you can specify the price for a non-inventory item measured only by a single amount. Or, calculate the transaction amount based on the line-item quantity. |
| Quantity |
Indicates the quantity of the corresponding item. |
|
Unit |
The unit of measure of the corresponding item. If you have customized your column order, make sure to update the Quantity after any change to Unit is made. Learn more about units of measure. |
| Price |
Defaults to the number of base units in the selected unit of measure multiplied by the base price per unit identified for the item after all price lists have been evaluated. For multi-currency companies, the Price is expressed in the transaction currency. If the transaction definition has Line-item price enabled (in the User overrides section), you can edit this field. You cannot enter a negative value for inventory, kit, or stockable kit items. If the application is configured to allow override of the line item conversion type, you can enter or change the value. The price column is hidden if Hide price is configured in the associated transaction definition.
|
| Extended price |
Displays the Price multiplied by the Quantity. If Line-item price is enabled in the transaction definition (in the User overrides section), you can edit this field. The General Ledger requires journal entry amounts to have only two decimal places. So, Intacct rounds the Extended price to two decimal places. |
| Cost | Displays the number of base units in the selected unit of measure multiplied by cost per unit for the item, as determined by the item's selected Cost method. The system truncates the Cost to two decimal places even if the full precision is greater. Depending on the transaction type and item's cost method, this field might be editable. For items with a standard cost method, it's always read-only. |
| Extended cost | Displays the Cost multiplied by the Quantity. The system truncates the Extended Cost to two decimal places even if the full precision is greater. This field is read-only. |
| Source document ID |
Displays the ID of the previous transaction document in the workflow. If Purchasing is configured to Enable conversions for multiple source documents, you can select a document. Learn more about converting multiple documents or lines into a single transaction. |
| Source document line ID |
Displays the line number and item ID of the previous transaction document in the workflow. For example, if the source transaction includes the third line item for a hammer, it might display as 3-H001. If Purchasing is configured to Enable conversions for multiple source documents, you can select a document line. Learn more about converting multiple documents or lines into a single transaction. |
|
Item description |
Defaults to the Extended description for the item. You can change this field. This field might appear in the printed document, depending on your document template definition. Learn more about document templates. |
|
Memo |
Enter any text regarding the item. You can enter up to 400 alpha-numeric characters. This field might appear in the printed document, depending on your document template definition. You cannot edit this field if the invoice was generated from Projects or Contracts. For OE sales invoices generated from Projects: Intacct might populate this field with the following values:
For OE sales invoices generated from Contracts: Intacct might populate this field with the following value: Contract line <line no>, billing schedule date <date>. |
| Ship to/Deliver to | Select a contact as the item receiver. |
| Originating document ID | The original workflow transaction ID. |
| Originating document line ID | The original workflow transaction document line ID reference. Displays the line number and the Item ID, for example, 1-# |
| Delivery method | Indicate how the item will be delivered to the receiver, after it has been shipped from a vendor or transferred from a warehouse. The dropdown list includes all shipping methods. |
| Need by date | The date you need the goods to arrive on your premises. The default is the due date. |
| Do not ship before/after date | The date before or after which the goods cannot be shipped. |
| Promised by date | The date the supplier promised to deliver the goods. |
| Cancel after date | The date after which the transaction is to be canceled. Unless a line-level default is applied, the default is the date in the header. |
|
Location |
Use the Location selection list to select a Location dimension for the line item. |
|
Department |
Use the Department selection list to select a department dimension for the line item. |
|
Customer |
Use the Customer selection list to select a customer dimension for the line item. This field appears only if Purchasing is configured to use the Customer dimension. |
|
Class |
Use the Class selection list to select a class dimension for this line item. This field appears only if Purchasing is configured to use the Class dimension. |
|
Project |
Use the Project selection list to select a project dimension for the line item. This field appears only if Purchasing is configured to use the Project dimension. Don't see your project in the dropdown list?
Your project might have a project status that prevents the entry of certain transactions. For more information, contact your system administrator. |
|
Supplier |
Use the Supplier selection list to select a supplier dimension for the line item. The supplier that's selected in this field must either match the supplier in the header or be identified as a child of the parent supplier identified in the header. This field appears only if Order Entry is configured to use the Vendor dimension. |
|
Employee |
Use the Employee selection list to select an employee dimension for the line item. This field appears only if Purchasing is configured to use the Employee dimension. |
Transaction tab: Subtotals section
This section only appears if the transaction definition includes subtotals.
| Field | Description |
|---|---|
|
Description |
The description of the subtotal. |
|
Percent |
This field is editable only if defined for a specific subtotal in the transaction definition. Allows you to enter a percentage that will be applied to the transaction total. For example, say you have a restocking fee that's 3 percent of the total transaction. Enter 3 in this field. |
|
Transaction value |
This field is only editable if defined for a specific subtotal in the transaction definition. Allows you to enter a value expressed in the transaction currency that will be added to or subtracted from the transaction total (depending on how the subtotal was defined in the transaction definition). For example, you have a shipping fee of R10.00. Type 10 in this field. |
|
Base value |
The Transaction value expressed in the base currency. |
|
Transaction total |
The total value of the transaction expressed in the transaction currency. |
|
Base total |
The Transaction total expressed in the base currency. |
|
Department
|
This field only appears if the transaction definition allows the user to override the department. Defaults to the department defined in the transaction definition. Use the Department selection list to select the desired department. |
|
Location |
This field only appears If the transaction definition allows the user to override the location. Defaults to the location defined in the transaction definition. Use the Location selection list to select the desired location. |
Posting details tab
This tab appears if the transaction definition for the transaction is set to post to AR or the General Ledger.
Posting details tab: Posted AR Invoices
| Field | Description |
|---|---|
|
Invoice number |
The record number assigned to the invoice. |
|
Reference number |
The customer's purchase order number or another reference number. This text appears in the GL Detail report under the Document column. |
|
Invoice date |
The transaction date. |
|
Invoice gross total |
The total amount of the invoice. |
|
Amount paid |
The amount that has been paid on the invoice. |
|
Amount due |
The remaining amount that needs to be paid on the invoice. |
Posting details tab: General ledger journals posted
| Field | Description |
|---|---|
|
Book ID |
Indicates the reporting book the journal posts into. This can be either Accrual or Cash, depending on the reporting method set up in the General Ledger. |
|
Journal |
The journal into which the transaction posted. |
|
Journal no |
Select to drill down to the Journal Entries page. |
|
Date |
The GL posting date. |
|
Type |
The type of posting. |
|
Line no. |
The line number represents the line in the journal entry that corresponds to the posting entry of the transaction. |
|
Account number |
The account number of the account to which the transaction posted. |
|
Account name |
The GL account to which the transaction posted. |
|
Location |
The location assigned to the transaction. |
|
Debit amount |
The amount debited from the account. |
|
Credit amount |
The amount credited to the account. |
|
Txn currency, Debit txn amount, and Credit txn amount |
If the company is enabled for multi-currency, these fields show the currency for the transaction and the debit and credit amounts in the transaction currency. |
|
Memo |
The memo for the transaction. This could be something that clarifies the reason for the transaction. |
Posting details tab: General ledger journals posted for inter-entity cost of goods sold (COGS)
Appears if inventory has been sold from a warehouse that's in a different entity and you've configured Order Entry for automatic inter-entity journal entries. The table displays the inter-entity COGS journal entries that are created to balance the inter-entity receivable and payable accounts for the cost of goods sold.
| Field | Description |
|---|---|
|
Book ID |
Indicates the reporting book the journal posts into. This can be either Accrual or Cash, depending on the reporting method set up in the General Ledger. |
|
Journal |
The journal into which the transaction posted. |
|
Journal no |
Select to drill down to the Journal Entries page. |
|
Date |
The GL posting date. |
|
Line no. |
The line number represents the line in the journal entry that corresponds to the posting entry of the transaction. |
|
Account number |
The account number of the account to which the transaction posted. |
|
Account name |
The inter-entity GL account to which the transaction posted. |
|
Location |
The location assigned to the transaction. |
|
Debit amount |
The amount debited from the account. |
|
Credit amount |
The amount credited to the account. |
|
Txn currency, Debit txn amount, and Credit txn amount |
If the company is enabled for multi-currency, these fields show the currency for the transaction and the debit and credit amounts in the transaction currency. |
|
Memo |
The memo for the transaction. This could be something that clarifies the reason for the transaction. |
Change documents tab
This tab only appears for Construction subscriptions when you open a source transaction definition (enabled for Change Management) in View mode. Sections on this tab include:
-
Original source document: lists original source document amounts.
-
Draft changes: lists all draft change documents for this source document.
-
Posted changes: lists all posted change documents for this source document.
| Field | Description |
|---|---|
| Document no. | The Document number entered at document creation. Select the link to view the document. |
| Type | The type of source document. This is the name of the source document. |
| State | After posting a transaction, this field displays the workflow status. |
| Change log number | How many change requests are logged in Sage Intacct against this document. |
| Date | The date the document was created. |
| Posting date | The GL posting date of the document. |
| Original amount | Sum of the original Extended price for the document, calculated using the Quantity field. |
| Original base amount | For multi-currency companies. Sum of the original Extended price for the document, calculated using the Quantity field, in the company's base currency. |
| Draft change amount |
The total amount of existing draft change requests for this source document. |
| Draft change base amount | For multi-currency companies. The total amount of existing draft change requests for this source document in the company's base currency. |
| Posted change amount |
The total posted amount of change requests for this document. Calculated net of Revised extended price - Extended price. |
| Posted change base amount | For multi-currency companies. The total posted amount of change requests for this document. |
| Revised amount | Sum of Revised extended price for all document lines, based on the revised quantity field. |
| Revised base amount | For multi-currency companies. Sum of Revised extended price for all document lines, based on the revised quantity field in the company's base currency. |
| Original amount | Sum of the original calculated amounts for all document lines. |
| Revised amount | Sum of the revised amounts for all document lines. |
History tab
This tab shows a header and additional sections applicable to the transaction type.
History tab: Header section
| Field | Description |
|---|---|
| Created by |
The user ID of the user who created the transaction. |
| Created date |
The date the transaction was created. |
| Modified by |
The user ID of the user who last changed the transaction. |
| Modified date |
The date and time the transaction was last changed. |
| Customer | The customer associated with the transaction |
| Document number |
The transaction identifier. |
| Printed |
Indicates whether the transaction has ever been printed. If the transaction definition has its Edit policy or Delete policy set to Before printing, you won't be able to edit or delete the transaction after the Printed flag is set to Yes. |
| Last delivered date |
The date the transaction was last printed |
| Last delivered by |
The user ID of the user who last printed or emailed the transaction. If Printed is No, this field is blank. |
| Document template | Transaction document type |
| Email history/New email history | This link opens the Email delivery log to view transaction delivery history via email. If no entries appear, the transaction has not been emailed. Learn about the email delivery log. |
| Record number |
The record number is an automatically applied transaction tracking number. You can use this as a reference for a draft transaction without a document number. To identify draft transactions saved without a Document number, include a Record number column on a list.
|
History tab: History table
The History table displays one entry for each existing transaction in the workflow associated with the selected transaction.
| Field | Description |
|---|---|
| Date |
The date the corresponding transaction was created. |
| Created by |
The user ID of the user who created the corresponding transaction. |
| Date modified |
The date and time the corresponding transaction was last changed. |
| Modified by |
The user ID of the user who last changed the corresponding transaction. |
| Transaction |
The transaction type and document number for a transaction in a workflow. Select a link in this column to open the transaction in a separate browser window. |
| Converted from |
The transaction from which the corresponding transaction was converted. This field is blank if the corresponding transaction is transaction is the first transaction in a workflow. |
| Transaction definition |
Links to the transaction definition for the corresponding transaction. |
| State |
The workflow state of the corresponding transaction. Learn more about Order Entry transaction states. |
History tab: Drop-ship details
This table displays the sales transaction and purchasing transaction relationship for drop-ship line items. This table only displays if drop ship has been set up for your company and the sales transaction includes a drop-ship line item.
| Field | Description |
|---|---|
| When created | The date the corresponding drop-ship transactions were created. |
| Created by login ID | The user ID of the user who created the corresponding drop-ship transactions. |
| Sales document ID | The transaction type and document number for the drop-ship sales transaction. Select the link in this column to open the sales transaction in a separate browser window. |
| Sales line no. | The line number associated with the drop-ship item in the sales transaction. |
| Item name | The description of the drop-ship item. |
| Purchasing document ID | The transaction type and document number for the drop-ship purchasing transaction. Select the link in this column to open the purchasing transaction in a separate browser window |
| Purchasing line no. | The line number associated with the drop-ship item in the purchasing transaction. |
Buy-to-order details
This table displays the sales transaction and purchasing transaction relationship for buy-to-order line items. This table only displays if buy to order has been set up for your company and the sales transaction includes a buy-to-order line item.
| Field | Description |
|---|---|
| When created | The date the corresponding buy-to-order transactions were created. |
| Created by login ID | The user ID of the user who created the corresponding buy-to-order transactions. |
| Sales document ID | The transaction type and document number for the buy-to-order sales transaction. Select the link in this column to open the sales transaction in a separate browser window. |
| Sales line no. | The line number associated with the buy-to-order item in the sales transaction. |
| Item name | The description of the buy-to-order item. |
| Purchasing document ID | The transaction type and document number for the buy-to-order purchasing transaction. Select the link in this column to open the purchasing transaction in a separate browser window |
| Purchasing line no. | The line number associated with the buy-to-order item in the purchasing transaction. |
History tab: Line-item conversion templates
This table appears in the History tab if you converted one or more line items into recurring templates.
| Field | Description |
|---|---|
| Document type | The type of transaction that will be created by the recurring template. For example, a OE sales invoice. |
| Template | Select the link to open the recurring template in a separate browser window. |
| Transactions | Select this link to view any transactions that were created from the recurring template. |
| Line no. | The sales transaction line number of the item that was converted by line. |
| Item ID | The Item ID of the item that was converted by line. |
| Memo | Any text entered in the Memo field for the item that was converted by line. |
| Amount | The Extended price of the item that was converted by line. |
Source and attachments tab
This tab only appears for Project invoices with source documents and their corresponding attachments.
Link source document attachments to project invoices
| Field | Description |
|---|---|
| View source link | Links to source transactions for the billable lines included in this invoice with attachments.
Only links to source documents with attachments appear. No links appear for billable lines without attachments. |
| Source document | Identifies the name of the source document for the billable line, if available. |
| Source document type | Indicates the type of billable source document, such as timesheet entry, expense report, Order Entry transaction, General Ledger transaction, or Purchasing transaction. |
| Attachment | Links to the attachment included in the source document for the billable line. Each billable line can only have one attachment assigned to it but each attachment can contain one or more files. Select the link to view the files in the attachment. |
| Attachment size | Indicates the file size of the attachment.
Large files can impact your ability to email invoices with corresponding source document attachments included. Learn more about including source documents and their attachments in email. |
Payment tab
View any payment information for the transaction on this tab. The information in this tab is read-only. This tab appears after you save the sales transaction if Display payment status is selected in the Configure Order Entry page.
| Field | Description |
|---|---|
| View | Links to the Posted Payment page for the corresponding payment. |
| Payment status |
Displays one of the following:
|
| Invoice amount | The Total for the Extended Price column in the Transaction tab. |
| Total paid | The total of the payments that have been applied to the transaction. |
| Amount due | The Invoice amount less the Total paid. |
| Base invoice amount | The Invoice amount expressed in your company's base currency. This field is only applicable to multi-currency companies. |
| Base total paid | The Total paid expressed in your company's base currency. This field is only applicable to multi-currency companies. |
| Base amount due | The Amount due expressed in your company's base currency. This field is only applicable to multi-currency companies. |
| Payment type |
Displays one of the following:
|
| Payment method |
The manner in which the customer made a payment. Depending on your company's configuration, displays one of the following:
* These options appear if your company is subscribed to Payment Services. |
| Receipt date | The date the payment type was applied. |
| Document no. | Any number, such as a cheque number, associated with the payment type. |
| Amount | The amount of the payment type. |
| Currency | The currency in which the Amount is expressed. |
| Base amount | The Amount expressed in your company's base currency. This field is only applicable to multi-currency companies. |
| Posting date | The date the payment type was posted in the system. |
Project contract billing details tab
Use the Project contract billing details tab to see the totals for the billing and line items. This tab appears on AR sales invoices that are enabled for project contract billing and requires the Construction subscription. These fields are read-only.
| Button | Description |
|---|---|
| Update billing details |
Select to recalculate and update the totals for the Project contract billing. Billing calculations are based on the invoice's billing through date. If needed, prior to recalculation, you can edit the invoice to change the billing through date (on the Transaction tab, Project contract billing section). |
| Project contract ID | The identifier for the project contract. |
| Project contract name | The name of the project contract. |
| AR AR sales invoice number | The associated Accounts ReceivableAR sales invoice number. |
| Document ID | The identifier for the document. |
| Document number | The project contract AR sales invoice document number. |
| Original contract amount | The amount of the original contract. |
| Total changes approved in prior months (additions) | The total of addition changes approved in prior months. |
| Total changes approved in prior months (deductions) | The total of deduction changes approved in prior months. Calculations are based on the invoice's billing through date. |
| Total changes approved this month (additions) | The total of addition changes approved this month. Calculations are based on the invoice's billing through date. |
| Total changes approved this month (deductions) | The total of deduction changes approved this month. Calculations are based on the invoice's billing through date. |
| Total net changes | The total of net changes. Calculations are based on the invoice's billing through date. |
| Revised contract amount | The amount of the revised contract. Calculations are based on the invoice's billing through date. |
| Total completed from prior applications | The total completed amount from prior applications. Calculations are based on the invoice's billing through date. |
| Total completed to date | The total completed for the AR sales invoice. Calculations are based on the invoice's billing through date. |
| AR sales invoice amount retained | The amount retained from the AR sales invoice. Calculations are based on the invoice's billing through date. |
| AR sales invoice retainage billed | The retainage billed from the AR sales invoice. Calculations are based on the invoice's billing through date. |
| Net change retainage held | The retainage held for net changes. Calculations are based on the invoice's billing through date. |
| Retainage held to date | The retainage held to date. |
| Retainage billed to date | The retainage billed to date. |
| Retainage balance to date | The amount of the retainage balance. |
| Previous retainage balance | The previous retainage balance. Calculations are based on the invoice's billing through date. |
| Total earned less retainage | The total earned to date minus retainage held to date. Calculations are based on the invoice's billing through date. |
| Less previous billings | The total of previous billings. Calculations are based on the invoice's billing through date. |
| Current amount due | The current amount that is due for the AR sales invoice. Calculations are based on the invoice's billing through date. |
| Balance to finish | The balance to finish paying the AR sales invoice. Calculations are based on the invoice's billing through date. |
| Taxes | The tax on the AR sales invoice. Calculations are based on the invoice's billing through date. |
| Discount | The discount on the AR sales invoice. Calculations are based on the invoice's billing through date. |
| Charges | The charges on the AR sales invoice. Calculations are based on the invoice's billing through date. |
Project contract billing tab: Invoice detail entries
| Field | Description |
|---|---|
| Project contract ID | The identifier for the project contract. |
| Project contract line ID | The identifier for the project contract line. |
| Project contract line name | The name of the project contract line. |
| External reference no. | The external reference identifier. |
| Internal reference no. | The internal reference identifier. |
| Project ID | The identifier for the project. |
| Task ID | The identifier for the task. |
| Task name | The name of the task. |
| Original contract amount | The amount of the original contract. |
| Total changes approved in prior months (additions) | The total of addition changes approved in prior months. |
| Total changes approved in prior months (deductions) | The total of deduction changes approved in prior months. |
| Total changes approved this month (additions) | The total of addition changes approved this month. |
| Total changes approved this month (deductions) | The total of deduction changes approved this month. |
| Total net approved changes | The total of approved net changes. |
| Total revised contract line amount | The total amount of the revised contract line. |
| Completed from prior applications | The amount completed from prior applications. |
| Completed this period | The amount completed this period. |
| Stored materials | The price of stored materials. |
| Total completed to date | The total amount completed. |
| Percentage complete to date | The amount of the percentage completed. |
| Retainage percentage | The percentage of the retainage. |
| AR sales invoice amount retained | The amount retained from the AR sales invoice. |
| AR sales invoice retainage billed | The retainage billed from the AR sales invoice. |
| Taxes | The tax on the AR sales invoice. |
| Charges | The charges on the AR sales invoice. |
| Discounts | The discount on the AR sales invoice. |
Project contract billing tab: Expandable details section
| Field | Description |
|---|---|
| Description | The description of the AR sales invoice. |
| Net change retainage held | The retainage held for net changes. |
| Retainage held to date | The amount of retainage held. |
| Retainage billed to date | The amount of retainage billed. |
| Retainage balance to date | The amount of the retainage balance. |
| Previous retainage balance | The previous retainage balance. |
| Balance to finish | The balance to finish paying the AR sales invoice. |
| Line amount due | The line amount due. |
Fulfillment tab
This tab appears if the transaction definition for the transaction is enabled for fulfillment.
Fulfillment tab: Fulfillment summary
| Field | Description |
|---|---|
| Fulfillment document |
Document number of the Order Entry transaction in fulfillment. The document number might be displayed multiple times if the line items in the document need to be grouped for different warehouses and fulfillment statuses. |
| Order date |
The date the transaction was created. |
| Fulfillment status |
The status of the transaction in fulfillment:
|
| No. of lines |
The number of lines in the transaction. |
| Percent fulfillable |
The percentage of the transaction for which there’s enough available quantity to fulfill all the items in the transaction. The percentage is calculated by how many of the line items in the transaction are fulfillable. |
| Warehouse |
The warehouse for the transaction. |
| Assigned to |
The employee who is assigned to the transaction. The value is Multiple if different employees are assigned to different line items. |
Fulfillment tab: Fulfillment history
The following table shows a log of the fulfillment activity against the lines in the transaction.
| Field | Description |
|---|---|
| Order line number |
The line number of the line item in the transaction. |
| Item |
The identifier for the item. |
| Warehouse |
The warehouse from which to fulfill the item. |
| Quantity |
The quantity of the item ordered. |
| Status |
The status of the line item in fulfillment:
|
| Assigned |
The employee who is assigned to the line item entry in fulfillment. |
| Active |
Indicates whether the entry for the line item is the most current and shows the most recent fulfillment changes:
|
| Pick list printed |
Date and time the line item entry was printed in a pick list. |
| Pack list printed |
Date and time the line item entry was printed in a pack list. |
| Reserved |
The quantity that's reserved for the line item entry. |
| Allocated |
The quantity that's allocated for the line item entry. |
| Hold |
Whether the line item entry is on hold in fulfillment:
|
| Created by |
The user ID of the user who caused the line to be created in the history. For example, changing the status of a line item entry or assigning some one to the line item entry causes a line to be created. |
| Created date |
Date and time the line in the history was created. |
| Modified by |
The user ID of the user who caused the line in the history to be changed. |
| Modified date |
Date and time the line in the history was changed. |
| Quantity picked | The actual quantity of the item that has been picked. This field appears on the All orders and Pick tabs. You can only enter a value on the Pick tab. |
| Quantity packed | The actual quantity of the item that has been packed. This field appears only on the All orders and Pack tabs. You can only enter a value on the Pack tab. |
| Change in reserve | Shows the reserved quantity increase based on the ordered quantity. |
| Change in allocation | Shows the allocated quantity increase based on the picked quantity. |
| Pick container | For information about the containers for picking the item. For example, when the quantity of the item is pulled from warehouse shelves, the quantity might be placed in a cart or on a table. |
| Pack container | For information about the containers for packing the item. |
| Shipping tracking | |
| Additional info | Any additional information provided. |
| Group | |
| Originating document | The original workflow transaction. |
| Notes | Any notes provided. |
| Bundle |
This field only appears if Revenue Management is configured to Enable MEA allocations and the transaction definition has Enable Revenue Recognition set to Post or Display Only. Type a numeric value to group items into bundles for MEA allocation. For example, type 1 to include the corresponding item in Bundle 1. Learn more about adding an MEA to a sales transaction. |