Sage Intacct New Features

Transcription

1 Sage Intacct New Features 2017 Release 4 Sage Intacct Release Date: November 10, 2017 Document Date: November7, 2017 Prepared by The Resource Group 600 SW 39 th Street, Suite 250 Renton, WA

2 Table of Contents Administration: Audit Trail Enhancements... 3 Administration: Sage Intacct to Disable Support for TLS Contracts: On-Hold: Billing and Revenue Schedules Cut the Cord... 5 Contracts: Permissions to Generate Invoices Become More Secure... 6 Contracts: Automatic Bundling and Other MEA Enhancements... 7 Contracts: Adjustment to Straight Line Revenue Calculation Inventory: Getting and Keeping Inventory Costs up to Date Just Got Easier Inventory: New Transition Definition Validations Bring Posting Under Control Inventory: Warehouse Transfer for Multi-Entity with Multiple Base Currencies Inventory: More Efficient Kit Costing Reports Order Entry: Miscellaneous Print/ Enhancements Salesforce Integration: Never Miss a Renewal Opportunity Projects: Observed Percent Complete Insight for Projects and Contracts Web Services: What s New? Workflow: Purchasing Approval Policy Validations to Facilitate Submitting Transactions Workflow: Streamline Your Workflow with Multiple Ship-to Contacts on Invoices Workflow: Close GL Books Faster! No More Processing Offline Workflow: A Faster Way to Map in Spend Management More: Additional Changes in 2017 Release More: AP Workbench More: Sage Intacct Action UI Beta More: Improved Setup for Sage Intacct s That Come From You Page 2 of 37

3 Administration: Audit Trail Enhancements Your time is valuable, and Sage Intacct understands that, so we've added two new features to the audit trail for increased usability, convenience, and control. Now you can: Export the audit trail report to PDF format. Enjoy some peace of mind ensure your audit trail report is accurate and reliable by exporting it to PDF format and sending it straight to them. Now, anytime you can generate the audit trail report for a record, you can export it to PDF format, which ensures the report cannot be edited, increasing the usability and control of your reporting. View the audit trail for a financial report or graph from the Reports Center. Keep control and save some clicks now, in the Reports Center, we've added a View audit trail button for Financial Reports and Financial Graphs for users with View only permissions to increase your usability, convenience, and control. Page 3 of 37

4 Requirements Requirements Description Subscription Permissions No subscription is required for audit trail. To view the audit trail report for financial reports and financial graphs from the Reports Center, you must have List as well as View permissions to Financials and Graphs in the General Ledger application. Administration: Sage Intacct to Disable Support for TLS 1.0 As early as December 15, 2017, Sage Intacct will disable support for TLS 1.0 and below. Sage Intacct takes the security of our customers very seriously. To enhance security and meet compliance requirements, we are mandating the use of TLS 1.1 (and later) encryption technologies to access our cloud software. What is TLS? Transport Layer Security (TLS) is a protocol that provides security and privacy by encrypting data shared over a network. TLS is typically used by web browsers and other applications that must securely exchange data. The current support versions of TLS are 1.0, 1.1, and 1.2. Currently, TLS 1.1 and 1.2 are considered secure by various security standard organizations. How does Sage Intacct use TLS? Sage Intacct uses TLS to secure both browser and Web Services (API) access to our application. How will users be impacted? Once Sage Intacct disables support for TLS 1.0, any browser access from a resource that does not support TLS 1.1 or above will fail. If you are a developer, learn more about the TLS impact on the developer site. Page 4 of 37

5 What do you need to do? Verify that your browser supports TLS 1.1 and above (most modern browsers do). You can use the following third-party resource to test your browser's compatibility: Contracts: On-Hold: Billing and Revenue Schedules Cut the Cord You asked for it, you got it we've separated the hold/resume functions for billing and revenue schedules for a contract line. You can now place a billing schedule on hold independent of the associated revenue schedule, and vice versa, and you can resume them separately as well, giving you more precise control over managing your schedules. To place a contract schedule on hold: 1. In the applicable Contract line pop-up window, click More Actions and then click Hold contract line. 2. Select one or more of the schedules and click OK. The hold takes effect on the date on which you place the contract schedule on hold. To resume a contract schedule: 1. In the applicable Contract line pop-up window, click More Actions and then click Resume contract line. Page 5 of 37

6 2. Use the calendar tool to select a Resume date, select the applicable schedule(s), and click OK. To assign different Resume dates to different schedules, open the Resume dialog box, enter a Resume date, select one schedule, and click OK. Then repeat the procedure for the other applicable schedule(s). Contracts: Permissions to Generate Invoices Become More Secure Prior to this release, all Contracts users who had the Contract permission set were able to preview and generate invoices. To allow you to better protect these responsibilities, we've added the following Generate Invoices permissions to Contracts: Preview - lets the user access the Generate Invoices page to preview invoices and create preview snapshots. This permission is applicable to users where User type = Business or Project Manager. Generate - lets the user access the Generate Invoices page to create invoices. This permission is only applicable to users where User type = Business. What's changed After November 10, 2017, users who previously had permission to preview and generate invoices via the Contract permission set will no longer have these permissions. The new Generate Invoices: Preview and Generate permissions will be disabled by default. Page 6 of 37

7 What you need to do After November 10, 2017, do the following: If your company uses role-based permissions: update all applicable Roles to include Generate Invoices: Preview and/or Generate. If your company uses user-based permissions: update all applicable Users to include Generate Invoices: Preview and/or Generate. If your company uses the Sage Intacct API for an integration that accesses the Generate Invoices page: update the API permissions as applicable. Contracts: Automatic Bundling and Other MEA Enhancements Contract Advanced Revenue Management users, take heart. With this release, we've simplified the MEA bundling process and added validations to help reduce errors in complex revenue contracts. Automatic MEA bundling In a multiple element arrangement (MEA) contract, typically all or most of the contract lines in the contract will be included in the same allocation bundle. Previously, you would need to manually indicate which items should be included in a bundle when you created the allocation. Now, the system will automatically include all items specified as "Default bundle" in the bundle when you create the first allocation and subsequent reallocations. Page 7 of 37

8 Here's how it works We've added a Default bundle checkbox to the Contract default section of the Item Information page: Selecting this checkbox indicates that this item should be included in the default bundle when you create an MEA allocation that includes this item. You can choose to exclude the item when you create the MEA allocation. For example, let's say we have an MEA contract with three contract lines. All of the items have the Default bundle checkbox selected in the Item Information page. When we add the MEA allocation, all three line items are included in the default bundle #1: Page 8 of 37

9 In unique cases where you have more than one bundle on the contract, you can change the bundle number. Click in the Bundle field, delete the 1, and type a new value. To remove an item from the default bundle, click in the Bundle field and delete the 1. Do not type another value leave this field blank. New validations Every contract line will be accounted for in an allocation process Previously, Sage Intacct allowed more than one allocation associated with the same journal that had the same effective date but with different selected line items. For example, a contract with four lines could have one allocation associated with Journal 1 effective 01/01/2017 that bundled items 1 and 2, and another allocation associated with Journal 1 effective 01/01/2017 that bundled items 3 and 4. Now there will be one allocation in effect per associated journal(s) per effective date and all contract lines will be accounted for in that allocation process. If you create two allocations for the same journal with the same effective date, the allocation last created will be the effective allocation. If a contract line does not have a bundle assignment within the allocation, Sage Intacct assumes that contract line's total revenue schedule amount will be equal to its billing schedule amount. Removing a contract line from an MEA in a subsequent reallocation resets its revenue schedule amount to 100% When you remove a contract line from an MEA and reallocate the revenue, Sage Intacct resets the removed contract line's revenue schedule amount to 100%. Any amounts posted prior to the new allocation's effective date in all associated revenue schedules remain posted. Sage Intacct will adjust all schedules associated with the prior allocation with the net difference between the total revenue schedule amount and any previously posted allocated revenue schedule amount according to the Adjustment type (Catch up or Walk forward) that you selected in the new allocation. Requirements Use the following checklist to review the basic requirements for using the automated MEA bundle feature in your organization: Requirement Subscription Description Requires: Contract Advanced Revenue Management Permissions List, View, Add, Edit, Delete Contracts List, View, Add, Edit, Delete Items List, View, Add, Edit, Delete Contract MEA Price Lists Implementation 1. Select the Default bundle checkbox on each item that should be included in the default bundle when an MEA allocation that includes this item is created. Page 9 of 37

10 2. Ensure each item has a fair value price specified in the applicable MEA price list. CSV Import Dependencies or other requirements Use the Item CSV import template to quickly update the CNDEFAULTBUNDLE field for all applicable items. The MEA process currently does not support revenue templates where Recognition method = Predefined percentages. Look for this in an upcoming release. Contracts: Adjustment to Straight Line Revenue Calculation With this release, we more closely aligned the calculation used for periodic revenue with industry norms to be more consistent with typical accountant expectations for the straight line recognition method when partial periods exist in the first and last periods. Previously, Sage Intacct calculated all partial periods in the straight line recognition term as follows: total schedule amount / total # of days in the recognition term = daily allocation rate # of days in the partial period(s) * daily allocation rate = amount of partial period(s) This produced somewhat unexpected results when both the initial period and last period were partial periods. What's changed Calculations for the following two partial period scenarios have changed: When there are partial periods in the first and last period When the revenue start date is the last day of the month and the last period is a whole period In these scenarios, Intacct will calculate the partial periods as follows: total schedule amount / # of recognition periods= periodic amount (periodic amount / # of days in the partial period(s) = daily allocation rate # of days in partial period * daily allocation rate = amount of partial period Example: When there are partial periods in the first and last period Say you have a contract line for $1, with a recognition term of 01/15/2017 to 01/14/2018. The revenue schedule will now be calculated as follows: Page 10 of 37

11 $1, / 12 periods = $ $100 / (17 days + 14 days) = $ * $ = $54.84 (initial period) 14 * $ = $45.16 (last period) Example: When the revenue start date is the last day of the month and the last period is a whole period Intacct considers revenue terms that start on the "end of the month" and end on the "end of the month" as full periods in between. Say you have a contract line for $1, with a recognition term of 01/31/2017 to 12/31/2017. Intacct counts 11 full recognition periods. The revenue schedule will be calculated as follows: $1, / 11 periods = $ $ / (31 days) = $ $ * 1 day = $ ($1, $ ) / 11 = $ What's the same The straight-line calculation will remain the same as currently implemented for the following scenarios: When the initial period is a partial period the last period is a whole period When the initial period is a whole period and the last period is a partial period total schedule amount / total # of days in the recognition term = daily allocation rate # of days in the partial period(s) * daily allocation rate = amount of partial period(s) How does this affect existing revenue schedules? This calculation change will only affect new revenue schedules where the recognition method = Straight line. There is no change to in progress straight line revenue schedules. If you want to use the new calculation in existing straight line revenue schedules, do the following: 1. If the schedule has started and there is posted revenue, clear the posted revenue as allowed by your company's business process. Page 11 of 37

12 2. In the contract line, change the revenue template start date and/or end date and save the contract line. This action resets the template information in the contract line. If you want to use the original revenue template dates, change them back and save the contract line again. Requirements Contract Standard or Advanced Revenue Recognition subscription Revenue template where Recognition method = Straight line Inventory: Getting and Keeping Inventory Costs up to Date Just Got Easier An accurate picture of your inventory costs is crucial to managing your profitability. With this release, we ve increased your power to identify inventory costing issues and bring and keep your inventory valuation, current unit costs, and cost of goods sold (COGS) up to date. When you recalculate inventory costs, Sage Intacct runs a process that: Recalculates the costs using all of the relevant transactions (purchase, sales, adjustments, and returns), processing them in transaction-date order using the current transaction definitions. Generates CSV files that highlight where the recalculated costs differ from the originally recorded costs. This process differs slightly depending on whether you recalculate costs with the Analyze or Update option. While the costs are always recalculated with either option, the costs are only changed and brought up to date with the Update option. What's new? Specifically, we've added the following enhancements for recalculating inventory costs: Support for all cost methods previously, only inventory items with the average cost method were supported Ability to filter items by Item group Automatic selection of the costs to recalculate you no longer need to choose because we ll always recalculate inventory valuation, current item costs, and cost of goods sold (COGS) in transactions Removal of the Recalculate from date field we ll always recalculate costs starting from the date of the very first transaction More details in the results of the cost recalculations to facilitate problem diagnosis more easily find misconfigured transaction definitions and workflow, costing differences caused by transactions entered in out-of-date order, and differences between the GL and inventory reports (Item Activity and Inventory Valuation) Support for the changes to the automatic reversal of On Hold and On Order quantities introduced in this release we now look back two levels to the parent and grandparent transactions in your workflow to determine whether to automatically decrease these quantities Page 12 of 37

13 Use of the last purchase price for an average, FIFO, or LIFO item when a cost doesn t exist no longer worry about zero or negative inventory skewing your costing because we have that covered now A scheduling feature after you ve brought your historical costs up to date, scheduling the costs to be updated on a regular basis helps keep them current An audit trail when you view a cost recalculation, see who ran it and when Page 13 of 37

14 The most visible changes are on the Recalculate Inventory Costs page: Best practice Use an approach like the following to keep your inventory costs in good shape: Page 14 of 37

15 1. Assess and resolve the costing issues in your historical data, using the following steps (repeating them as necessary): a. Recalculate the costs with the Analyze option and review the results in the systemgenerated CSV files. b. Make any necessary adjustments for the issues you found in the results of the analysis, such as changing misconfigured transaction definitions, and run another Analyze. c. Recalculate the costs with the Update option and review the results in the systemgenerated CSV files to ensure the costs were updated the way you anticipated. 2. After you've brought your historical costs up to date, schedule the costs to be updated on a regular basis, such as every day or at the end of each fiscal period. Requirements Use the following table to review the basic requirements for recalculating inventory costs: Requirement Subscription Permissions Description Inventory Control, Order Entry, and Purchasing Requires: Admin user privileges List, Add, Edit, View, and Delete transaction definitions if workflow problems are found in Order Entry, Purchasing, or Inventory Control Dependencies or other requirements Costs can only be updated in open periods. Tips The Analyze option does not change any costs. Costs are simply recalculated starting from the date of the first transaction. Use the results of analyzing the costs to determine the effect of updating them. The Update option changes the costs. Existing costs that differ from the recalculated costs are updated starting from the Update start date, using the values that are recalculated starting from the date of the first transaction. (See the next row for details on which costs are updated.) Fix the costs in your historical data. Then, run the tool with the Update option on a regularly scheduled basis to maintain the health of your inventory costs. Other When you use the Update option, the costs are updated as follows: Inventory valuation. We change the internal cost tracking with the recalculated costs so that the Inventory Valuation report is accurate when run with any As of Date. Page 15 of 37

16 Current item costs. We change the internal cost tracking with the recalculated costs. COGS in transactions. We change the Inventory Control subledger and update the COGS journal entries for the recalculated COGS. Inventory: New Transition Definition Validations Bring Posting Under Control Inventory and Order Entry transaction definition configuration just got easier! We've added several validations to Inventory and Order Entry transaction definitions to help ensure your Inventory values more accurately reflect your asset balance. What's new for Inventory transactions that post to the GL Previously, you could define COGS or GL account mapping on the Posting configuration tab of an Inventory transaction definition, and only the presence of the account mapping indicated that the transaction would affect the GL. If a user created an Inventory transaction that included an Inventory or Stockable Kit item that had no account mapping defined in the transaction definition, no GL posting occurred for that item and the user did not receive an error message when they posted the transaction. We've added a new Transaction posting field to the Inventory transaction definition - General tab to clearly specify what should occur for transactions containing Inventory or Stockable Kit items. Field options are: General Ledger the transaction post process must create a GL entry for this transaction. You must add at least one debit/credit account pair to the COGS account mapping table in order to save the transaction definition. If the Inventory or Stockable Kit item selected in the transaction does not have a mapping entry in the COGS account mapping table, the user will receive an error and will not be able to post the inventory transaction. Don't post the transaction post process will not create a GL entry and will ignore any mapping entries in the COGS account mapping table. What's new for Order Entry transactions that affect ONHAND Value or Quantity & Value Previously, you could define an Order Entry transaction definition to affect ONHAND Value or Quantity & Value and you were not required to enter account mapping in the COGS/Inventory account mapping table. We've added a validation to Order Entry transaction definitions so that if you define the transaction definition to affect ONHAND Value or Quantity & Value, you must add at least one debit/credit account pair to the COGS account mapping table in order to save the transaction definition. In a future release, users will not be able to save Inventory or Order Entry transactions that affect inventory value if they contain Inventory or Stockable Kit items that do not have an entry in the applicable COGS account mapping table. Page 16 of 37

17 What will change The data migration for this validation will do the following: All inventory transaction definitions that have mapping entries in the COGS mapping table will have Transaction posting set to General Ledger by default. All inventory transaction definitions that do not have mapping entries in the COGS mapping table will have Transaction posting set to Don't post by default. What you need to do After November 10, 2017, users won't be able to save certain Order Entry or Inventory transactions containing Inventory or Stockable Kit items if the transaction definitions are not configured correctly. Perform the following tasks prior to November 10, 2017 to avoid user disruption. Edit Inventory transaction definitions that should post to the GL to add the required account mapping to the COGS mapping table for all applicable item GL groups. This will allow the data migration to correctly set the new Transaction posting field to General Ledger. Edit Inventory and Order Entry transaction definitions that are defined to affect ONHAND Value or Quantity & Value to add the required account mapping to the COGS mapping table for all applicable item GL groups. Page 17 of 37

18 Best practices The following are some Sage Intacct best practices for configuring transaction definitions that pertain to Inventory or Stockable kit items. Configure the sales invoice to affect ONHAND Quantity & Value and handle all the GL posting for inventory, COGS, AR, and revenue. In the sales invoice, debit the COGS account and credit the Inventory account. Intacct multiplies the unit item cost by item quantity when it posts the journal entry. If you set Transaction posting to General Ledger, define both a debit account and a credit account for each applicable item GL group. Requirements Use the following checklist to review the basic requirements for incorporating the new transaction definition validations in your organization: Requirement Subscription Description Requires: Inventory Control Order Entry Permissions List and Edit Inventory Transaction Definitions List and Edit Order Entry Transaction Definitions Implementation Edit Inventory transaction definitions that should post to the GL to add the required account mapping to the COGS mapping table for all applicable item GL groups. This will allow the data migration to correctly set the new Transaction posting field to General Ledger. Edit Inventory and Order Entry transaction definitions that are defined to affect ONHAND Value or Quantity & Value to add the required account mapping to the COGS mapping table for all applicable item GL groups. Data migration The data migration for this validation will do the following: All inventory transaction definitions that have mapping entries in the COGS mapping table will have Transaction posting set to General Ledger by default. All inventory transaction definitions that do not have mapping entries in the COGS mapping table will have Transaction posting set to Don't post by default. Page 18 of 37

19 Tips Import transaction definitions from a CSV file to quickly create new transaction definitions with the correct posting configuration. Please note that you can't use CSV file import to update existing transaction definitions. Inventory: Warehouse Transfer for Multi-Entity with Multiple Base Currencies One-step warehouse transfer to simplify transferring inventory continues to evolve! We first introduced warehouse transfer between warehouses within the same entity. Then, we added support for transfers between entities with the same base currency. Now, we re enabling transfers between entities with different base currencies. With any of these transfers, after you save the information entered on the Warehouse Transfer page, Sage Intacct completes the rest of the work. It automatically creates a transfer-out transaction and immediately converts it to a transfer-in transaction, updates the quantities on hand and costs, and posts to the GL. For inter-entity transfers, Intacct posts to the GL using a combination of the system-specific transaction definitions and due-to and due-from accounts, with currency conversion where necessary. What's new? In a multi-entity shared environment enabled for multiple base currencies, the Configure Inventory Control page has a new field in the Warehouse Transfer subsection to specify the default exchange rate type. This value appears as the default exchange rate type on the Warehouse Transfer page when you transfer items between warehouses in entities with different base currencies. The Warehouse Transfer page also includes several new fields. The costs of average, FIFO, and LIFO items are converted from the base currency of the Out entity into the base currency of the In entity when the items are transferred. Currency conversion is not required for standard cost items, which are always transferred in using the standard cost in effect at the From warehouse. New fields in the Transfer out and Transfer in subsections display the base currency of each entity and the exchange rate information you can use to specify the exchange rate for converting the base currency of the Out entity to the base currency of the In entity: Page 19 of 37

20 And, new columns in the Entries section display the cost of the items converted from the base currency of the Out entity to the base currency of the In entity the costs used for the GL postings: Page 20 of 37

21 Example Assume you are a distributor who transfers 10 units of Item A001 (an average cost item) at a cost of $100 each from a warehouse in the United States (base currency USD) to a warehouse in India (base currency INR). The USD to INR exchange rate on the specified exchange rate date is The GL entry for transfer-out transaction from the warehouse in the United States entity would be: GL account Debit Credit Due from (from IET account setup) 1, (USD) Inventory (from transfer-out transaction definition) 1, (USD) Note: The amount is calculated as 10 units * 100 USD. The GL entry for the transfer-in transaction to the warehouse in the India entity would be: GL account Debit Credit Inventory (from transfer-in transaction definition) 65, (INR) Due to (from IET account setup) 65, (INR) Note: The currency conversion is calculated as 10 units * 100 USD * exchange rate. Setup Any Intacct user with administrator privileges can set up warehouse transfer in a multi-entity shared environment enabled for multiple base currencies: 1. From the top level, go to the Configure Inventory Control page and select: o Enable warehouse transfer. After warehouse transfer is enabled, system-generated transfer-out and transfer-in transaction definitions automatically appear. o Sequence number. The sequence number is used for the warehouse transfer records. o Default exchange rate type. This determines the default value for the Exchange rate type field on the Warehouse Transfer page, which you can override. (This field appears only in multi-entity shared environments enabled for multiple base currencies.) 2. Go to the inventory transactions list, and edit these system-generated transfer-out and transfer-in transactions definitions: SYS-Warehouse Transfer Out and SYS-Warehouse Transfer In. For each transaction definition, enter the GL posting information. 3. Ensure your entities have accounts for inter-entity transactions (IETs) set up. 4. Give business users permission to Warehouse Transfer in Inventory Control. Requirements Use the following checklist to review the basic requirements setting up and using warehouse transfer between entities with different base currencies: Page 21 of 37

22 Requirement Subscription Permissions Description Inventory Control Requires: Admin privileges for Inventory Control setup List and Edit Inventory Transaction Definitions List, Add, Edit, View, and Delete Warehouse Transfers Implementation Requires: Inventory Control configured for Warehouse Transfer System-generated transfer-in and transfer-out transaction definitions edited to set up GL postings Accounts for inter-entity transactions (IET) defined for each entity Permission granted to use Warehouse Transfer Dependencies or other requirements To transfer items between two entities with different base currencies: Your multi-entity shared environment must be enabled for multiple base currencies. The transfer must be created at the top level. Tips CSV Import Only inventory items and stockable kits can be transferred; non-inventoried items cannot be transferred. Work with warehouse transfers from the Warehouse Transfer list page and not with the underlying system-generated transfer-out and transfer-in transactions. CSV file to import warehouse transfers requires: Subscription to Company Permission to run Company Setup Checklist Other The costs of the transferred items are automatically propagated based on their cost method, and you cannot change them: Average, FIFO, and LIFO the cost of an item at the time it is transferred out of the source warehouse and converted to the base currency of the destination warehouse is the cost assigned when it is transferred in to the destination warehouse. For FIFO and LIFO, if the quantity transferred out includes more than one cost layer, then the underlying transfer-out and transfer-in transactions have separate rows for each cost layer. Page 22 of 37

23 Standard an item is transferred out using the standard cost in effect at the source warehouse and transferred in using the standard cost in effect at the destination warehouse. Currency conversion is not applicable Inventory: More Efficient Kit Costing Reports A Kit Costing custom report is a great resource for looking at your inventory costing. In this release, you can use these new enhancements to create more efficient, easier to analyze reports: Create reports for specific time periods We ve added the standard date fields that are available in other custom reports. Now, you can filter your Kit Costing reports based on either a reporting range or range of dates. Identify the source of a transaction at glance Each row in a Kit Costing report comes from the Order Entry, Purchasing, or Inventory Control application. Previously, you could use the In/Out column to guess which application was the source of the transaction. Now, you can use the new Source Module column to quickly see the application for each transaction. See dimensions in a single column Previously, the dimensions were only available under the Order Entry, Purchasing, and Inventory Control Transaction Detail objects. We ve added the dimension fields directly into the Kit Costing object. Now, you can see the dimensions in a single column, which also makes it possible to subtotal by dimension. Here s just one example of using some of these new options when you create Kit Costing reports: Page 23 of 37

24 To add a Kit Costing report: 1. Go to Customization Services or Platform Services > All > Setup and click the + sign beside Custom Reports. (For non Action UI, go to Customization Services or Platform Services and click the + sign beside Custom Reports). The Custom Reports wizard opens. 2. Select the Kit Costing object as the primary data source in Step Follow the remaining steps in the wizard to select the desired columns, the column sequence, and so on. Requirements Use the following checklist to review the basic requirements for using custom reports: Requirement Subscription Permissions Dependencies or other requirements Description Customization Services or Platform Services List, Add, Edit, View, and Delete Custom Reports Subscription to Inventory Control, Order Entry, and Purchasing Permission to view drillable objects in the report Tips Review any existing Kit Costing reports and, where appropriate, edit them to take advantage of the new enhancements. Order Entry: Miscellaneous Print/ Enhancements We've added several small but helpful enhancements to the Order Entry print and functions. Print/ Documents page The Print/ Documents page lets you print and/or multiple Order Entry documents at the same time. We've added more filters and details to let you narrow the focus of the transactions on which you want to act. Page 24 of 37

25 Customer filter we've removed the old From Customer/To Customer fields and replaced them with one Customer field that now lists customer dimension groups in addition to customers. Use this field to select either a customer or a customer group. Customer type filter use this field to filter the results by a particular category of customers. Sorting preference now you can decide the sort order for the displayed results by selecting an option in this new field. Choose to sort by Customer ID, Customer name, Date (transaction date), or Transaction number. Document template the results page now identifies the document template that will be used when printing the corresponding invoice. Sales transactions Print/ button this button is now accessible when a sales transaction is in Edit mode. Previously this button was only accessible when a transaction was in View mode. Page 25 of 37

26 Document template the History tab now displays the document template associated with the sales transaction. Document templates can be assigned to transaction definitions or customers. A document template assigned to a customer has precedence over the document template assigned on the transaction definition. Salesforce Integration: Never Miss a Renewal Opportunity The Sage Intacct Advanced CRM Integration now enables your sales teams to manage the contract renewal process in Salesforce. You can now automate the creation of opportunities in Salesforce for contract renewals. This allows the sales team to apply pricing options from Intacct-based renewal templates directly to the renewed contract, as well as track line level upgrades or downgrades. This enables your sales team to effectively manage the renewal process in Salesforce before synchronizing the contract to Intacct. With Intacct handling the financials, the renewed contract is accurate and available quickly, either on the renewal template schedule, or created manually by the people who know your customers best: the sales team. Projects: Observed Percent Complete Insight for Projects and Contracts Now, a more detailed way to track and log observed percent complete data for your projects and tasks. What's new? Introducing a new table in which Project managers can enter and maintain a history of observed percent complete values, providing details of progress over the lifetime of the project or task. Previously, this information was tracked using a single field losing valuable project insight. "As of dates" for tracking and revenue recognition Page 26 of 37

27 "As of dates" let you associate each percent complete value with an effective date, thus providing a complete log of what happened and when for improved project and task history. For revenue recognition templates based on observed percent complete, the "As of dates" correspond to the effective posting dates for the revenue schedule. The "As of dates" create a row within the schedule and assigns the As of date as the Scheduled posting date for that row. This date overrides all other considerations, so you don't have to go back and revise any revenue schedules. The observed percent complete table is used for both Project/Order Entry revenue recognition and Projects/Contracts revenue recognition. Example: If the first entry in the table is 33.33% for 01/31/17, and the second entry is 66.66% for 04/30/17, then 2 separate revenue schedules are created: the first for 01/31/17 for 33.33% and the second for 04/30/17 for 33.33%. Check it out To add, edit, or view a project's observed percent complete data: 1. Go to Projects > All menu > Setup > Projects > Projects > [Edit/View]. 2. On the Additional info tab, locate the Observed Percent Complete table. 3. Enter an As of date along with your observed % complete as a line item. 4. Click Save. To add, edit, or view a task's observed percent complete data: 1. Go to Projects > All menu > Setup > Tasks > [Edit/View]. Page 27 of 37

28 2. On the Additional info tab, locate the Observed Percent Complete table. 3. Enter an As of date along with your observed % complete as a line item. 4. Click Save. Requirements Requirements Subscription Description Projects Web Services: What s New? Watch the Sage Intacct Developer site blog for information about great new features in Web Services. Highlights include: New functions that support approvals for purchasing. Ability to transfer inventory from a warehouse in one entity to a warehouse in a different entity with a different currency using the warehouse transfer object. Support for multiple Ship to contacts on contracts. New functions for Contracts. With this release, you can post all contract expense schedule entries and/or contract revenue schedule entries before a given date. You can also post individual entries according to their record numbers, and more. Workflow: Purchasing Approval Policy Validations to Facilitate Submitting Transactions We ve introduced validations to ensure your purchasing transactions flow more smoothly through the approval workflow. By checking the completeness of the configuration required by an approval policy, these validations help prevent issues when users submit purchasing transactions. What's new? When you save an approval policy, we validate that managers exist when any of the following rule types are specified: Employee Manager Approval. If any employee who is a user and has permission to add purchasing transactions doesn t have a manager, we issue a warning. Department Approval or Transaction Department Approval. If any department doesn t have a manager, we issue a warning. Transaction Location Approval. If any location doesn t have a manager, we issue a warning. In addition, for Value Approval - Department and Value Approval - Transaction Department, we perform the same validations if the rule sets include Employee Manager or Department Manager. When you click to save the approval policy, the policy is saved even if there are warnings. The warnings enable you to easily investigate whether missing managers need to be assigned: Page 28 of 37

29 When you click Assign in the warnings, a specialized list that shows the employees, departments, or locations without a manager appears. From these lists, you can edit the records to assign a manager as appropriate. Ensure the managers you assign have permission to approve purchasing transactions. Example Assume you create an approval policy for the transaction definition for Purchase Requisition and select Employee Manager Approval as one of the rule types: If John Smith creates a purchase requisition and he doesn t have a manager assigned, he can't submit the purchase requisition. You can use the new validation information to help users avoid issues when creating purchasing transactions because of incomplete configurations. In this example, some employees, including John Smith, don t have a manager assigned. So, when you save the approval policy, you see this warning: Page 29 of 37

30 When you click Assign, the list of Employees without a Manager appears. From this list, you can edit each employee to add a manager as appropriate: Requirements Use the following checklist to review the basic requirements for using purchasing approval policies and editing employees, departments, and locations to add managers: Requirement Subscription Permissions Description Purchasing Requires: Page 30 of 37

31 Admin privileges for adding or editing approval policies List and Edit Employees List and Edit Departments List and Edit Locations Dependencies or other requirements Purchasing configuration is enabled for approvals. Appropriate users have approval permission. When you edit an employee, department, or location to add a manager, ensure the manager has purchasing approval permission. Workflow: Streamline Your Workflow with Multiple Ship-to Contacts on Invoices Understanding when we automatically reverse On Hold and On Order quantities has always been important so that your Order Entry and Purchasing workflows and transaction definitions preserve the integrity of your inventory quantities. Before this release, when a transaction was converted into a transaction that affected the On Hand quantity, either Quantity only or Quantity & Value, we looked back one level to the parent transaction (the converted from transaction). If the parent transaction affected the On Hold or On Order quantity, we automatically reversed the On Hold or On Order quantity. With this auto-reversal logic to go back one level, let s look at how some Order Entry workflows work, depending on how the inventory totals are configured in the transaction definitions: Order Entry workflow 1 This workflow results in an accurate On Hold quantity. When the Sales Order is converted to a Shipper, the On Hold quantity is automatically decreased because the Shipper affected the On Hand quantity and the Sales Order, which is one level back, affected the On Hold quantity. Page 31 of 37

32 Order Entry workflow 2 This workflow results in an overstated On Hold quantity. When the Sales Order is converted to a Shipper, the On Hold quantity is unaffected because the Shipper doesn t affect the On Hand quantity. When the Shipper is converted to a Sales Invoice, the On Hold quantity remains unaffected. Although the Sales Invoice affects the On Hand quantity, the transaction one level back (the Shipper) has no inventory effect so the On Hold quantity isn t automatically decreased. Examples for Purchasing workflows would be similar. What's new? To support more workflows and the recommended best practice to keep the effect of the inventory subledger for quantity and value on the same transaction definition, usually the invoice, we ve changed automatic reversal to now look back two levels. When you convert a transaction into a transaction that affects the On Hand quantity, we look back first to the parent transaction and then to the grandparent transaction. If the parent transaction or the grandparent transaction affects the On Hold or On Order quantity, we automatically reverse the quantity. With this change in auto-reversal logic, the Order Entry workflow 2 example from above now results in an accurate On Hold quantity: When the Shipper is converted to a Sales Invoice, the On Hold quantity is automatically decreased. Looking at the inventory totals specified in the transaction definitions, because the Sales Invoice affects On Hand quantity, we look back one level to the Shipper and see that it doesn t affect On Hold. Next, we look back a second level to the Sales Order, which does affect On Hold. So, we automatically decrease the On Hold quantity. Page 32 of 37

33 Details Automatic reversal of On Hold or On Order quantities goes back only two levels: If your Sales Order increases On Hold quantity and a transaction in the workflow three or more levels away decreases the On Hand quantity, configure the transaction definition for that transaction to reduce On Hold. If your Purchase Order increases On Order quantity and a transaction in the workflow three or more levels away increases the On Hand quantity, configure the transaction definition for that transaction to reduce On Order. To prevent double counting, automatic reversal is not applied if transaction definitions after the Sales Order or Purchase Order are manually configured to reduce On Hold or On Order quantities. The following workflows illustrate when On Hold or On Order quantities are not automatically decreased: Order Entry workflows with explicit On Hold decreases Page 33 of 37

34 Purchasing workflows with explicit On Order decreases Requirements Use the following checklist to review the basic requirements for defining transaction definitions: Requirement Subscription Permissions Description Inventory Control, Order Entry, Purchasing Requires: List, View, Add, Edit, and Delete Order Entry Transaction Definitions List, View, Add, Edit, and Delete Purchasing Transaction Definitions Other Permission to Run inventory reports, especially the Inventory Status report, which displays the On Order, On Hand, and On Hold quantities for each item in your warehouses Workflow: Close GL Books Faster! No More Processing Offline Companies who normally close large numbers of books usually process the closings offline in order to minimize the performance impact. In some cases, it could take hours to close all the books. Dramatic improvements in performance remove the need for offline closing. Now, closing the books is lightning fast. As a result, we removed the option to close books offline. No more waiting for the letting you know that closing books is finally done...it happens instantly. To close books: 1. Point to General Ledger > Activities, and then click Close Books or Books > Close, depending on the UI you're using. The Close Books page appears. Page 34 of 37

35 2. Click the To the end of the period drop-down list, and then click the period you want to close. If you are a top-level user in a multi-entity shared company, you'll see the Entity/Entity Group dropdown list. Click the Entity/Entity Group drop-down list, and then click a single entity, entity group, or all subordinate entities. This option only appears for top-level users. 3. Click Close or Close books. An onscreen message appears confirming that the books are closed. Workflow: A Faster Way to Map in Spend Management Whether you have a dozen or two hundred mappings, add or update the item GL group to GL account map for your Spend Management setup faster than ever before via CSV import. On the Spend Management configuration page, you can now download an import template that you populate with existing data from your company. After you populate the template, you save it as a CSV file, then you import the template into Sage Intacct to create or update as many item GL group to GL account mappings as you want. Requirements Requirements Description Subscription Prerequisites Permissions Spend Management, General Ledger, Purchasing Item GL groups and GL accounts must already exist in Sage Intacct. Creation of these objects through import isn't currently supported. To import this mapping, you need the following permissions: Page 35 of 37

36 General Ledger - Account Groups - List, View, Add, Edit Purchasing - Item Groups - List, View, Add, Edit Admin - Application Subscriptions - List, View, Configure CSV Import Tips When you click Mapping template on the Import Item GL Group To GL Account Map page, you download the Item GL Groups Map template. Not only can you add new mappings, but you can update any existing mappings via import as well. More: Additional Changes in 2017 Release 4 Each quarter we release full-bodied features and enhancements, and we also release smaller changes, which although more minor, may be important to your company. Below is a list of the smaller changes we've added in this release: More: AP Workbench Last release we showcased our new AP Workbench for paying bills. This release we're enhancing Pay Bills a bit more. Applying inline credits: No more exceptions. You can now auto-apply inline credits for cash and multi-book companies. Filtering: We've added Group by Entity and Pay Source Entity filtering for paying bills. o Group by Entity - Filter the list to view bills for specific entities that have a relationship with the source entity o Pay Source Entity - Filter the list to view bills from all entities that have a defined relationship with a particular source entity You can create and save the customized filters and share them with others. More: Sage Intacct Action UI Beta Your feedback asked for it, we listened, and here are the updated features to Action for this release. Spacing: See more information using less real estate. We've tightened up vertical spacing across our new user interface, including spacing in add and list pages and reports. Reconciliation pages: Returned these pages to Coming Soon status so they can get a facelift. Audit Trail is now converted to Action. Dialog boxes: Enhanced to enable o Printing or sending to XML o Closing with ease Keep sending feedback! Page 36 of 37