• Email: contact@microwaresolutions.com
  • Contact us: +234-1-2900770, +234-8039755073

Acumatica Announces Acumatica 2017 R2

Product News from Acumatica Cloud ERP

We are thrilled to make three major product announcements in September 2017:

  • Acumatica 2017 R2 Release
  • Acumatica Manufacturing Edition
  • More Integrations with Partners

Acumatica 2017 R2 Release

This fall release is the scheduled update to Acumatica 2017 R1 (previously known as 6.1), which was released in February 2017.

Acumatica 2017 R2 release was developed around the pillars of “Insights,” “Productivity,” and “Technology.” Here are descriptions of each pillar.


New User Interface

At the center of Acumatica 2017 R2 is a new, more flexible and personalized user interface. In addition to using workspaces that supplement the traditional suites and modules, you can tailor your navigation for preferred processes and individual tendencies. You now have greater control over personalized dashboards and can create role-defined views from preconfigured templates.

Based on your company’s specific business processes, you can flexibly configure navigation. Personalized navigation helps you easily access forms you use frequently. In the new user interface, suites and modules are replaced with workspaces. A workspace includes forms and reports consolidated for a specific function.

New User Interface of Acumatica 2017 R2

  1. Navigation pane with workspaces
  2. Links to forms
  3. Tiles (links with additional parameters to forms)

The Administrator can configure navigation in the new user interface, pin and unpin workspaces on the navigation pane, add and remove links to forms and reports in a workspace, and manage tiles in a workspace. Every user can personalize the user interface by adding forms to Favorites and configuring Quick Menu items.

Reporting Enhancements

You can create your own custom online reports using the Acumatica Generic Inquiries functionality. This query tool can display exactly the set of data you need, provided you have the appropriate level of security to view it. You can see tables and field names, easily join the data together, and then apply filtering, sorting, and grouping options. Acumatica also supports the Microsoft Power BI online analytics tool.

With this release, pivot tables can now aggregate data for very specific periods of time, such as one month. Administrators can set the default column configuration for all users or configure table layouts for a subset of users at any time. The Administrator configures the required table layout, including specific columns and order of columns to be displayed.


Acumatica 2017 R2 release includes enhancements to almost every product suite, including Customer Management, Financial Management, Distribution Management, Project Accounting, and Field Service Edition. Here are highlights of the changes:


The enhancements to Acumatica CRM focus on marketing. We’ve improved marketing lists and campaigns for greater user efficiency in marketing tracking and analysis. This includes improvements to List Building where generic inquiry forms work with contact records. We’ve also enhanced both dynamic and static marketing lists.

For Lead Tracking, the previous “statuses” have been enhanced to “stages” (prospect through deploy).  You can now create activities associated with campaigns. The system will associate a new lead with its marketing campaign.

For companies that use Salesforce CRM as their primary CRM system, Acumatica has a tool to allow bi-directional real-time synchronization between Acumatica ERP and Salesforce CRM.

Learn more: https://www.acumatica.com/cloud-erp-software/customer-management/

Financial Management:

Acumatica 2017 R2 includes significant enhancements to Customer Statement Processing. Also, multiple branches that use the same Acumatica tenant can configure separate tax periods and close the periods independently of one another.

For Outgoing Cash Transactions, the approval process in Accounts Payable and Accounts Receivable now lets you purchase goods or services from one vendor and pay for those going to a different vendor.

For companies that use Authorize.Net, a new API plug-in provides PCI DSS-compliant integration with Authorize.Net. Sensitive credit card information is not stored in the Acumatica ERP database.

Learn more: https://www.acumatica.com/cloud-erp-software/financial-management/

Distribution Management:

Acumatica Distribution Management includes changes in Unit of Measure and Pricing.

For the Item Class Hierarchy, Acumatica now supports item classes using a tree-like hierarchy with parent-child relationships. You can also define the default class for stock and non-stock items.

New Unit of Measure (UoM) functionality includes the new feature that while creating a sales order, the user can specify inventory items by their alternate IDs. If the default item’s UoM is different from the alternate item’s UoM, the alternate’s UoM will be used.

You can specify sales and purchasing prices by warehouse and alternate IDs. The Price Adjustment can now update prices for other units of measure automatically.

Learn more: https://www.acumatica.com/industries/wholesale-distribution/

Project Accounting:

Acumatica Project Accounting also features numerous enhancements, beginning with simplified budget structure and reporting.

We’ve enhanced project billing with Proforma invoices and Project-Specific Invoice Formats. We’ve also added progress billing on fixed amount and time and material contracts. Enhanced project rates allow you to bill a project by prices that are defined in the Accounts Receivable sales price lists, including foreign currency prices.

For project costing, the system will now track project comments through purchasing, sales, and external systems.

Learn more: https://www.acumatica.com/cloud-erp-software/project-accounting/

Field Service Edition:

Acumatica ERP 2017 R2 provides enhancements in the Equipment Management module that will help you track components and warranties. When a piece of equipment is a stock item sold to a customer, and preventive maintenance or warranty handling (or both) is performed, these services are tracked in the system. Also, you can track any component that’s a part of that equipment, including the component’s separate warranty information, serial number, and preventive maintenance.

The Scheduling feature now lets you clone an appointment multiple times. You can also specify a default salesperson for service orders that require certain services. With the new Contracts functionality, you can generate Service Order appointments with a defined frequency and schedule start time.

The web mapping service within Field Services is now provided by Microsoft Bing Maps. This will allow Acumatica to accommodate additional functionality in the future.

There is also a major enhancement in mobility. See “Mobile GPS Framework” in the technology section below.

Learn more: https://www.acumatica.com/cloud-erp-software/field-service-management/


REST API and Swagger

Acumatica has further enhanced its REST APIs and announced the availability of Open API 2.0 specification (formerly known as Swagger Specification) for Acumatica Contract-Based APIs. Swagger is the world’s largest framework of API developer tools for the OpenAPI Specification (OAS). It enables development across the entire API lifecycle—from design and documentation to testing and deployment. Applications implemented based on OpenAPI interface files can automatically generate documentation of methods, parameters, and models. This helps keep the documentation, client libraries, and source code in sync.

Mobile GPS Framework

Acumatica 2017 R2 includes the new GPS location framework for mobile applications. For example, Field Service Edition provides GPS location tracking. This new feature allows you to record the exact location of your service technicians, at the time they started and completed each appointment and route. You can click the “View On Map” button for each location to open the Google Map link with the exact address.

Push Notifications Sent by Acumatica ERP

External applications that worked with data in previous versions of Acumatica ERP needed to continually poll for the data to find out whether there were any changes. This could slow down the performance of the external application. In Acumatica ERP 2017 R2, external applications can track data changes by processing push notifications sent by Acumatica ERP.

Localization of Acumatica Self-Service Portals in Multiple Languages

Acumatica has extended its multilanguage support to include self-service portals. A self-service portal can be localized in the application interface, through user input boxes, or through translation of wiki articles.

New Industry Edition

Acumatica Manufacturing Edition, formally known as JAMS, is being released as part of Acumatica 2017 R2. This platform has been co-developed, implemented, and supported in partnership with JAAS Systems over the course of several years. Acumatica Manufacturing Edition is the latest fully integrated vertical solution from Acumatica, joining the Field Service Edition and eCommerce Edition solutions announced earlier in 2017.

Manufacturing Edition includes BOM and Routing Management, Production Management, and MRP (Material Requirements Planning). Optional applications include Estimating, Product Configurator, and APS (Advanced Planning and Scheduling). Because they’re built on the Acumatica xRP platform, all the financial and distribution applications are integrated. For more information: https://www.acumatica.com/cloud-erp-software/manufacturing-management/

New Integrations with Partners

Adobe Sign

Adobe Sign makes it fast and easy for Acumatica users to securely sign and manage documents across devices from within Acumatica Cloud ERP. With Adobe Sign, your team can prepare and send documents such as sales orders and contracts to be e-signed with a few clicks. Your customers sign and return it on any device, and each step is tracked from beginning to end.

Visual Resource Scheduling Integration with Smartsheet

Smartsheet is a popular project management tool used for visual resource scheduling. Like Acumatica, it is a fully cloud and mobile solution. Any new project you set up in Acumatica Project Accounting can automatically set up a new project in Smartsheet and populate it with the tasks and dates. As you make changes in the field, updates will be sent back to Acumatica Project Accounting.

Visual Resource Scheduling Integration with Smartsheet

Building a Project Overview Report

This series of posts will show you how to use the Report Designer utility to build a project overview report. This tutorial assumes a working knowledge of the Acumatica Report Designer, but it is also designed to give those who don’t have that knowledge a glimpse of what Acumatica Cloud ERP Software can do to transform business processes.
Over three posts, we’ve been building a project report designed to provide a project-at-a-glance view with drill-downs to several source documents that make up the project.

Business Purpose

The Acumatica Cloud ERP project module is linked to almost all other modules in Acumatica. This makes the project module extremely powerful, but presents the need to create a report that shows an overall view of a project.

We will use the Sub-Report feature in the Acumatica Report Designer to create a project report that includes:

  • An overview of project information, including custom attributes
  • Purchase Orders (open and closed) related to a project
  • Invoices related to a project
  • Activities and tasks related to a project
  • Real-time profitability and budget comparisons

Technical Process Overview

In Part 1 of this post series, we covered the first steps in building the report:

1. Create the main project report, pmsummary.rpx

a. Add the report to the site map

b. Add attributes to the project and put them on the report

c. Include a picture on the report

2. Create a sub-report showing all invoices related to a specific project, pminvoices.rpx

a. Add the report as a sub-report to the main report

Yesterday in Part 2, we covered:

  1. Create a sub-report showing all invoices related to a specific project, pminvoices.rpx
    1. Add the report as a sub-report to the main report
  2. Create a report showing open and closed purchase orders related to a project (pmpos.rpx)
    1. Add the report as a sub-report to the main report
  3. Create a report showing activities related to a project (pmactivities.rpx)
    1. Add the report as a sub-report to the main report

And today in Part 3, we’ll look at how to supplement the report with Budget and Actual expense reporting:

  1. Create a report showing comparing budget and actual expenses (pmbudgetgraph.rpx)
    1. Add the a graph to the budget report
    2. Add the report as a sub-report to the main report


The final report will be similar to the one pictured below. As needed, additional sub-reports and features can be added, and we’ll address some of the most commonly-needed in the last post tomorrow.


Create the budget comparison report and graph

Open the Report Designer and select the option to build a schema.

Schema Details

The main table used for this report is the PMProjectStatus table. The PMProject table is required for capturing the project ID used as a reference to the report:

  • PMProjectStatus: the data access class that contains summary information about all released project transactions as well as project budget. This table makes it easy to compare budgets to actuals.
  • PMProject: the data access class that provides top level project level information. This includes all the system projects and summary data about each.

To relate the tables, enter the information below into the Relationships tab of the Schema Builder.


After setting up the report relationships, go to the Parameters tab.

  • Define a parameter called Project as illustrated below. Use the ContractID field from the PMProject table.


Next go to the Filters tab and select records from a single selected project as illustrated below.


I explicitly list the expense account groups that I want to include in my report. You could also include project revenues, but this would impact the totals we will compute for the report.

Budget Comparison Report Grouping

Creates groups based on project ID and Account Group:

  1. The ProjectID allows us to break out totals by project. Since a project is passed from the main report, this is important for displaying the proper information.
  2. The Account Group allows us to compute totals by Account Group allowing us to provide an additional level of detail to our report.

The values for the Group Collection Editor and the GroupExp Collection Editor are shown in the screen shot below.


Box Name GroupExp Collection Editor DataField Other Info
projectID Grouping =[PMProject.ContractID]
AccountGroup Grouping =[PMProjectStatus.AccountGroupID]


Budget Comparison Variables

After creating the groups, define 4 variables by clicking the Variables Collection in the details Section of the report. Two variables store the amounts for each account group while 2 variables store amounts for the entire project so we can include a total amount. The values for these variable are provided in the table below.

Variable Name Reset Group ValueExpr
BudgetGroup AccountGroup =$BudgetGroup+[PMProjectStatus.Amount]
ActualGroup AccountGroup =$ActualGroup+[PMProjectStatus.ActualAmount]
BudgetProject projectID =$BudgetProject+[PMProjectStatus.Amount]
ActualProject projectID =$ActualProject+[PMProjectStatus.ActualAmount]

An image that shows adding the first variable is shown below.


Budget Comparison Report Field Selection

After creating the groups, there are 7 sections available for our report. We will add text fields to these sections as shown below. The table contains details regarding the text boxes.


Box Name Location Value
Category Field Footer of AccountGroup =[PMProjectStatus.AccountGroupID]
Budget Sub-Total* Footer of AccountGroup =$BudgetGroup
Actual Sub-Total* Footer of AccountGroup =$ActualGroup
Remaining Sub-Total* Footer of AccountGroup =$BudgetGroup-$ActualGroup
Budget Total** Footer of projectID =$BudgetProject
Actual Total** Footer of projectID =$ActualProject
Remaining Total** Footer of projectID =$BudgetProject-$ActualProject

* Set the Format = #,###,###,##0.00 for proper number formatting

** Set the StyleName = Header1 to add emphasis for the total column. This requires setting the StylesTemplate of the main report to TemplateForm.rpx. We also added a dotted line above the Footer of projectID section.

Sidebar 1: Add a graph to the budget comparison report

Adding graphs to your report provides visual appear to the data that you collect. In this section, we add a simple bar graph to compare the total budget to the total expenses for the project.

To do this, follow these steps:

  • Click the Chart icon, then click the location in the Footer of projectID where the graph will be located.
  • Set ChartType = Bar in the Properties area of the Chart
  • Create two data points and set the values for them as shown below


  1. Click the Series collection in the Chart properties
  2. Click the Points collection in the MSChartSeries Collection Editor
  3. Click Add a member in the MSChartDataPoint Collection Editor
  4. Set the YValueExpr to =$ActualProject and the AxisLabel = Actual in the properties area of the first data member
  5. Set the YValueExpr to =$BudgetProject and the AxisLabel = Budget in the properties area of the first data member
  • Select other field values for proper formatting of your report
    • Delete the legend in the Properties area of the Chart.
    • Set the Axis colors = White to hide them as necessary in the Properties area of the Chart
  • Open the ExternalParameter Collection Editor by clicking the Parameters icon

The nuances of the graph tool are beyond the scope of this article.

Sidebar 2: Add budget comparison sub-report to the main report

To add the purchase orders report to the main report, perform the following actions:

  • Open the PMsummary.rpx report in the Report Designer
  • Drag a sub-report object to the location in the details section of the PMsummary report where you want the sub-report to appear.
  • Set the properties as shown in the screen shot below
    • ReportName: make sure that you match the name that you gave to the sub-report when you saved it to the server
    • Size: the size of the report is important if you want all the columns to show
  • Open the ExternalParameter Collection Editor by clicking the Parameters icon

Add the projectID as a parameter, set the ValueExpr as =[PMProject.ContractID]. This will pass the current project to the sub-report so the proper data is gathered.


The project report summarizes several elements of a project on a single overview report. Each area provides drilldown to quickly gain insights to individual documents.

Several other enhancements could be added to this report. Some suggestions:

  • Add a sub-report listing bills related to a project (easy)
  • Add a sub-report listing hours an employee worked on the project (easy)
  • Add a sub-report with details of expense reports related to a project (easy)
  • Add additional charts and graphs for rapid visualization (moderate)
  • Add drilldown capabilities to the budget and actuals on the comparison report (advanced)

Acumatica Projects can include data from virtually every other module in Acumatica. This makes the project summary report valuable in providing at a glance data describing the overall project.

Create a presales support request if you would like to receive the report and sub-reports referenced in this document.

Got questions or report-building tips on Acumatica? Ask in the comments below, and be sure to subscribe to get these posts in your inbox!

Demo Built in Acumatica Environment: 5.20.1227

Data: SalesDemo data from Acumatica’s Partner Portal

Setting up a Recurring Billing Project in Acumatica

Recurring Billing Using Projects

Are recurring charges stacking up every month? This post will walk you through how to bill recurring charges using an Acumatica project in two widely-used variations: a fixed recurring charge and a fixed recurring charge plus additional usage.

Environment: 5.10.0600

Scenario Overview

Business Problem

Each month, you receive an invoice from a vendor who provides support services for your company. This support is provided for different customers (detailed by line item on the invoice). The support fees from the vendor need to be re-billed to your customers. The cost of the support needs to be tracked against a project.

There are different customer billing scenarios that need to be addressed. Some customers pay a fixed hourly rate, other customers pay a recurring fee for unlimited support, and some pay a fixed recurring fee for some included hours and pay an additional hourly fee on top of that.

Demonstration Scenario

We are illustrating an example with three different customer billing options:

Vendor Payments

  • Vendor 1: $40 / hour for support provided to our customers

Customer Invoicing

  • Customer 1: $50 / hour for support
  • Customer 2: $200 / month includes 5 hours, $50 / hour for each additional hour
  • Customer 3: $600 / month for unlimited support
Vendor Invoicing scenario chart

Vendor Invoicing scenario

Expected Result

The software will highlight the fact that the unlimited support plan is not profitable.

Acumatica Implementation

Using the recurring billing feature in the Acumatica project, we can use the allocation rules to apply the appropriate rate to the SUPPHOURS non-stock item. The rate for support hours can vary by project, so we need to decide on a strategy to define that rate:

  • Rate Strategy 1: Different rate tables (optimal when there are only a few rates)
  • Rate Strategy 2: Define rates in attributes (optimal with different rates for each project/customer)
  • Rate Strategy 3: Different inventory items (optimal when rates can be linked to inventory items)

In this example, we will use rate strategy 2, but we also included some information on the other strategies below.

Step 1: Implement Allocation Rates and Rules

In this section we briefly discuss how to set up allocation rules and rate tables in Acumatica for the three different rate strategies:

Rate Strategy 1: Different rate tables (optimal when there are only a few rates)

Rate Strategy 1: Different rate tables (optimal when there are only a few rates)

  • Strategy 1: Different rate tables. This is best if there are a limited number of different customer prices. This involves creating different rate tables in the billing settings area of the project.


  • Strategy 2: Attributes. This is optimal if the billing rate is non-standard and is negotiated for each project. This involves:
    • (a) creating an attribute,
    • (b) linking the attribute to projects, and
    • (c) setting up allocation rules to include the attribute in your allocation rules (replaces the @rate construct).

An example allocation rule for using an attribute is illustrated below.

Create the attribute

Step 1: Create the attribute

Link attribute to projects

Step 2: Link attribute to projects

Modify allocation rule

Step 3: Modify allocation rule

Note: since I defined the attribute as a text field, I used the CDec() function to convert it to a number before using it in my calculation.

  • Strategy 3: Different inventory items. This is optimal if you want to use different inventory non-stock items to drive expenses and revenues. This involves
    • (a) creating different non-stock items for different rates you want to charge,
    • (b) Creating rate lookup rules driven by inventory (see below), and
    • (c) assigning rates in the rate tables,
    • (d) selecting the proper inventory item when paying/billing.
Different inventory items.

Different inventory items.

Step 2: Project Implementation

For this implementation, we will create three customers as well as a project for each customer. The project setup will vary slightly depending on our contract arrangement with the customer.

Pay as you Go

Customer 1 pays for all the support hours consumed during each billing period. This project is set up by selecting the appropriate allocation rules and assigning the proper rate to the attribute:

Customer 1 pays for all the support hours consumed during each billing period.

Customer 1 pays for all the support hours consumed during each billing period.

Fixed recurring charge with included hours and overage

Customer 2 pays a fixed recurring charge for included support hours and pays an overage rate for additional hours. This project is set up by selecting the same allocation rule as pay-as-you-go, assigning the overage rate to the project attribute, and adding the non-stock item SUPPHOURS to the Recurring Billing tab of the Project Task as illustrated below.

Project setup for a recurring charge of 200 dollars and 5 included support hours

Project setup for a recurring charge of 200 dollars and 5 included support hours

When the bill is created there will be two lines. One for the fixed recurring fee with 5 hours, a zero charge, and the ‘bill complete’ flag set. A second line with 5 additional hours charged at $50 per hour.

Fixed monthly Fee

Customer 3 pays a fixed monthly fee. This is accomplished by adding a line for the fixed recurring fee to the Recurring Billing tab of the Project Task as illustrated below. The allocation rules and attribute are not needed.

Customer 3 pays a fixed monthly fee.

Customer 3 pays a fixed monthly fee.

Step 3: Monthly Processing

Input Vendor Invoice

The vendor invoice that includes hours for each project is illustrated below.

Vendor invoice includes hours for each project

Vendor invoice includes hours for each project

After releasing the bill, the projects have the costs $400, $400, and $800 associated with them. Project 3 is shown below.

Project 3

Project 3

Run Project Allocations

After running project allocations, the appropriate rate is applied to the support hours that have been received on the vendor invoice.

Note that charges for customer 2 are fully allocated ($50/hour x 10 hour = $500) even though at billing time only $200 + $250 will be billed.

Run Project Billing

At the end of the month, run project billing. Here\’s how your invoices will look:

Project 1 Invoice

Project 1 Invoice

Project 2 invoice

Project 2 invoice

Project 3 invoice

Project 3 invoice

Questions or comments? Feel free to ask away in the comments, we\’d love to hear from you. If you\’d like to try this process to see how it works for you, you can always give Acumatica\’s Cloud ERP Software a whirl on with a full software test drive!

How to update item prices using sales price worksheets

How to update item prices using sales price worksheets

This Knowledge Base article reviews the process for mass updating Sales Prices for Stock & Non-Stock items. The following scenario uses Markup % and Avg. / Std. Cost to update the prices of Stock & Non-Stock Items in Acumatica.


Article Outline

  • Reviewing Item Prices & Costs
    • Reviewing Price Types
    • Stock Items – IN.20.25.00
    • Non-Stock Items – IN.20.20.00
    • Creating Item Price Classes – IN.20.90.00
  • Reviewing Sales Prices
    • Sales Prices Screen – AR.20.20.00
    • Reviewing Base Price Information
  • Updating Sales Prices using Sales Price Worksheets – AR.20.20.10
    • Creating the Sales Price Worksheet – AR.20.20.10
    • Using Calculate Pending Prices
    • Verify Pending Prices
    • Releasing the Sales Price Worksheet – AR.20.20.10
    • Verifying the Sales Prices – AR.20.20.00


reviewing item prices & costs

reviewing price Types

The Sales Prices in Acumatica are organized by Default, Base, Customer Price Class, and Customer pricing levels. The default price provides a simple mechanism to manage item prices by individual item, but does not provide retention of historical price changes. The Base, Customer Price Class & Customer pricing levels are part of the Acumatica price list functionality, and provide the ability to create sophisticated pricing strategies for stock & non-stock items. In this scenario, we will use Sales Price Worksheets to update the Base price using the Avg. / Std. Cost + Markup % defined in the items.


Stock Items – IN.20.25.00

In preparation for the sales price update, we will review the relevant configuration settings in the Stock Item.

1. Open the Stock Items screen. (IN.20.25.00)

Distribution > Inventory > Manage > Stock Items

2. Select the General Settings tab.

3. Note the Valuation Method to use in validating the Pending Price.

4. Note the Base Unit & Sales Unit to use in validating the Pending Price.


5. Select the Price / Cost Info tab.

6. Review the Item Price Class for the Pending Price calculation. Note: We will use the Item Price Class = TEST.

7. Note the Current Cost for the Pending Price calculation. Refer to Step 3.

8. Note the Markup % for the Pending Price calculation.


Non-Stock Items – IN.20.20.00

In preparation for the sales price update, we will review the relevant configuration settings in the Non-Stock Item.

1. Open the Non-Stock Items screen. (IN.20.20.00)

Distribution > Inventory > Manage > Non-Stock Items

2. Select the General Settings tab.

3. Note the Base Unit & Sales Unit to use in validating the Pending Price.

4. Select the Price / Cost Information tab.

5. Note the Item Price Class for the Pending Price calculation. Note: We will use the Item Price Class = TEST.

6. Note the Current Cost for the Pending Price calculation.

7. Note the Markup % for the Pending Price calculation.


Creating Item Price Classes – IN.20.90.00

1. Open the Item Price Classes screen. (IN.20.90.00)

2. Click + to create a new Line in the table.

3. Select the Price Class ID field & Enter TEST.

4. Select the Description field & Enter Test Price Class.

5. Click Save to create the Item Price Class = TEST.


reviewing sales prices – AR.20.20.00

Sales Prices Screen – AR.20.20.00

1. Open the Sales Prices screen. (AR.20.20.00)

Finance > Accounts Receivable > Work Area > Manage > Sales Prices

2. Select the Price Type field & Choose Base.

3. Select Price Class field & Enter TEST.

4. The Stock & Non-Stock Items in the TEST price class appear in the table.


Reviewing BASE price information

1. Note the Price Type = Base. We will be updating Base prices.

2. Note the UOM field for effect on Pending Price.

3. Note the Price field for Current Base Price.


updating sales prices using sales Price worksheets – AR.20.20.10

creating the sales price worksheet – AR.20.20.10

The Sales Price Worksheet can be created from the Sales Prices screen we prepared in the last step, or directly via the Acumatica menu. In our scenario, we will use the Sales Prices screen to access the Sales Price Worksheet.

1. On the Sales Prices screen in the previous step, click Create Price Worksheet.

2. The Sales Price Worksheet opens with the selected Items.

Note: The Sales Price Worksheets screen supports loading Items via Excel as an alternative to using the Sales Prices screen.

Using calculate pending prices

1. Click Calculate Pending Prices.

2. The Calculate Pending Prices screen opens.

3. Select the button Avg. / Std. Cost + Markup %.

4. Click Update to Calculate Pending Prices.


Verify pending prices

1. The Sales Price Worksheet has been updated with Pending Price, and is On Hold.

2. Verify the Pending Price calculation against the Cost, Markup% & Unit of Measure information.


releasing the sales price worksheet – AR.20.20.10

1. Upon verification of the Pending Prices, Uncheck Hold.

2. Click Release to update the Base Prices for the selected items base on the Pending Price.


Verifying the Sales Prices – AR.20.20.00

1. Open the Sales Prices screen. (AR.20.20.00)

Finance > Accounts Receivable > Work Area > Manage > Sales Prices

2. Select the Price Type field & Choose Base.

3. Select Price Class field & Enter TEST.

4. The Stock & Non-Stock Items in the TEST price class appear in the table.

5. Verify the updated Prices.