Skip to main content

Acumatica Stampli Package Updates

Written by Phillip Reid

When updating your Stampli/ Acumatica package, it is important to verify that the Access Rights and Permissions are all in place and correct for the Stampli Role & User.
​
First, Navigate to User Security → Roles, then:

  1. Find the role used for Stampli access.

    1. Recommended Role Name: StampliRole

    2. Recommended Description: StampliAPI

  2. Open the role and select the Stampli User used for the Integration.

    1. This is often "StampliUser"

Verify Access Rights for the Role

Access must be granted at the top organizational level (Company Level - top level will match your company name). See this document’s appendix for a detailed list of all access rights.

  1. Grant Access to These 12 Entities

    1. Ensure the role has access to each of the following workspaces/modules:

      • Banking

      • Configuration

      • Currency Management

      • Customization

      • Data Views

      • Finance

      • Inventory

      • Payables

      • Projects

      • Purchases

      • Taxes

      • Units of Measure

  2. Set Detailed Permissions for Each Module

    1. For each module below, assign the highest available permission (typically Delete) to the listed screens:

      • Configuration - Branches, Companies, Company Groups, Units of Measure

      • Currency Management - Currencies

      • Customization - All screens

      • Data Views - All screens

      • Finance - Financial Year, Chart of Accounts

      • Integration - Web Service Endpoints, Web Service

      • Payables - All Vendors & 1099 fields, all Billing fields

      • Projects - Project Tasks, Projects

      • Purchases - Purchase Orders, Purchase Receipts

      • Taxes - Tax Zones, Taxes, Tax Details

    2. Important: Permissions to RetrieveCashAcctPayInstr - STM00019 and CashAccountList - CA202000 must also be added — specific module may vary.

Appendix

Access Rights Required

Stampli Entity - Acumatica Screen ID

  • CashAccountList - CA202000

  • Check - AP302000

  • QuickCheck - AP304000

  • PurchaseOrder - PO301000

  • PurchaseReceipt - PO302000

  • InterBranchAccountMapping - GL101010

  • AccountLocation - CR303010

  • VendorHistory - AP405000

  • Bill - AP301000

  • BillToPayment - STM00007

  • RetrievePaidBills - STM00011

  • TenNintyNineList - STM00005

  • CashAccount - STM00006

  • CashAccountPaymentInstructions - STM00019

  • POOrderToPOReceipt - STM00001

  • VendorLocation - AP303010

  • TaxRate - STM00014

  • PurchaseReceiptWithQty - STM00012

  • AccountsPayablePreferences - AP101000

  • BranchList - CS102000

  • Vendor - AP303000

  • CustomizationProjects - SM204505

  • PaymentMethod - CA204000

  • CurrencyList - CM202000

  • AccessibleBranchList - STM00009

  • PRDetailsForPoMatching - STM00008

  • NonStockItem - IN202000

  • GetClosedPosForPoMatching - STM00010

  • GetClosedPRsForPoMatching - STM00017

Default (inherited) OData types the integration also uses:

  • Account

  • StockItem

  • SubAccount

  • Project

  • ProjectTask

  • FinancialPeriod

  • UnitsOfMeasure

  • WarehouseCostCode

  • ProjectBudget

  • AttributeDefinition

  • VendorPricesInquiry

  • DeletedVendors

Did this answer your question?