ION Factory OS
  • Welcome to ION
  • Features
    • Procedures
      • Steps
        • Content
        • Datagrid
        • Fields
        • Attributes
      • Dependencies
      • Part-Procedure Relationship
      • Attributes
      • Standard Steps
      • Installation Requirements (Beta)
      • Nested Steps and Nested Standard Steps
      • Procedure Best Practices
    • Runs
      • Run Execution Overview
      • Runs And Step States
      • Batching Runs
        • Batching 2.0 Changes
      • Workcenter execution
      • Split Inventory on a Run
      • Redlines
      • Export run data
      • Scheduling runs
      • Time Tracking
      • Attributes
      • Outside Processing
      • Runs Best Practices
    • Parts Library
      • As-built Bill of Materials (aBOM)
        • Editing aBOM build requirements
        • aBOM Beta Changes
          • aBOM actions for developers
      • Inventory
        • Inventory status
        • Inventory splitting
        • Inventory merging
        • Inventory scrapping
        • Kitting
        • Inventory Movement Automations
      • Manufacturing bill of materials (mBOM)
        • mBOM versions
        • Made on Assembly (MOA)
        • Part Substitutes
        • Reference designators
      • Part Attributes
      • Part revision interchangeability
      • Supplier Part Numbers & Purchase Unit Conversions
    • Kitting and Inventory Fulfilment
      • Kit Statuses and Workflows
      • Inventory requests
      • Kitting and runs
      • Fulfilling Multiple Kits
      • Kanban Kitting
    • Purchasing
      • Purchase Orders
        • Types of Purchases
        • Purchase Order Approvals
        • Purchase Order FAQs
        • Supplier Part Numbers & Unit Conversions
        • PO Requirements, Terms, and Quality Clauses
      • Receiving/Inspection
      • Outside Processing
      • Consigned Parts
    • Barcode Labels
      • Templating
        • ION barcode minimum sizes
        • Sample templates
      • Printing
        • Configuring Zebra Browser Print
        • Server Based Barcode Printing (PrintNode)
      • Scanning
        • Scan barcodes from other systems
    • Quality
      • Issues
      • Further Actions - CAPA
      • Issues States, Dispositions, and Resolutions
      • Quality Best Practices
    • Tools
    • Locations
    • Attributes
    • Labels
      • Deleting labels
    • Notifications
    • Search
    • Settings
      • Role based access control
        • Full Glossary of ION Permissions
    • ION Actions
      • ION Actions examples for Quality
      • ION Actions examples for Runs and Procedures
      • ION ACTIONS examples for Supply Chain
  • Analytics
    • Inventory valuation
    • Part impact analysis
    • Users, Roles, Teams
    • Analytics FAQ
    • Data Connector
    • Data Products
  • Plans and Autoplan
    • Autoplan
    • Autoplan glossary
    • Preparing to use Autoplan
    • Clear to build reporting
    • Running Autoplan on a schedule
    • Firm and blocked plan items
    • Location constraints
    • Autoplan suggested suppliers and procedures
    • Reorder point
    • Plan input serial numbers
    • Applying a calendar
    • Plan Reservations
    • Independent schedules
    • Drive demand from kits
    • Drive demand below buy parts configuration
    • Group plan items with the same date
    • Manualy Changing Autoplan Status
  • API
    • How to create an App with ION
    • Access Tokens
    • About GraphQL
    • Interactive API explorer
    • API Keys
    • Examples
      • Notifications
      • Runs
      • Automatically updating fields in runs
      • Parts and Part Revisioning
      • mBOMs
      • Part Inventory and Kitting
      • aBOM (As-built Bill of Materials)
      • Edit time-tracking session data
    • Changelog
    • Webhooks
    • Pagination
  • Automations
    • Auto-checkout of Run Steps
    • Auto-Consumption of Lineside Inventory
    • Automatically Send Purchases to Suppliers
    • Set Close by Run Step on Issue Creation
    • Intent Management / Grade / Tier / Pedigree
      • Data Imprinting
      • ION Actions for Intent
    • Auto-Update mBOM Revision on Part Revision Update
    • Auto-approve part-procedure relationships
    • Purchase Order PDF and Versions
    • Auto Populate PO Line Attributes
    • Imprint Attributes from One Object to Another on a Desired Event
  • Integrations
    • Deploying Integrations and Automations
    • Arena
    • Cofactr
    • Datum
    • Duro
    • NetSuite
      • Purchasing in NetSuite, Receiving in ION
      • Work Order/Assembly Builds
    • Procurable
    • PDF Generator
    • Quickbooks
    • Ramp
    • Silkline Integration
    • Slack
    • Smartsheet
    • SOLIDWORKS
    • Teamcenter
  • Training
    • Standard Operating Procedures
      • Cycle Counting
      • Tool Utilization
    • Guided Flows
    • ION Sandbox
    • Chat Support for ION
  • Troubleshooting
    • Resetting your password
    • Resetting your Multi-Factor Authentication
    • You have no roles... error
  • Changelog
  • Adminstration
    • Security
      • Backups and Security FAQ
      • Single Sign-On (SSO)
        • Okta SAML connection setup
      • Export Control
      • Report Generator Disclaimer
    • Browser and Device Compatibility
    • Authentication
      • My company is new to ION, logging in for the first time.
      • I'm told I'm not authorized to access the application
      • My account has been deactivated
    • Login Page
  • Tickets Portal
Powered by GitBook
On this page

Was this helpful?

  1. Integrations

Quickbooks

Quickbooks Online (QBO) Integration

PreviousPDF GeneratorNextRamp

Last updated 8 months ago

Was this helpful?

Use the below for instructions on how to deploy this integration.

Sync details to Quickbooks where your accounting and finance teams can digest the data. Accurate bookkeeping allows leaders to track where spending is occurring in order to better direct their business towards success.

When a purchase in ION is set to 'Ordered', this will send changes to Quickbooks. The Quickbooks purchase order document number will match the ION purchase order ID so you can always match purchases across both systems. Below are the data fields that are being sent from ION to QBO.

  • Part Number

  • Purchase Order Line Unit Cost

  • Purchase Order Line Total Cost

  • Purchase Order Line Quantity

  • Purchase Order Line Description

  • Purchase Order Line Expense Account (As Required)

  • Purchase Order Line Class (As Required)

  • Purchase Order ID

  • Purchase Order Fee Name and Value

  • Purchase Order Currency

  • Purchase Order Shipping Address

  • Purchase Order Supplier

Inventoried Purchase Order Lines

Inventoried purchase order lines in ION are PO lines that have a part and quantity linked in ION and no expense code is specified. These result in inventory being created that shows up as On Order and then turns to available after being received.

For inventoried purchase order lines in Quickbooks, items in Quickbooks are matched with ION parts if the name includes the part number and revision with the following format:

  • ($partNumber) Rev ($revision)

  • i.e. "820412-001 Rev B"

If an item does not exist in QBO, then new inventoried items are automatically generated using the Income Account, Inventory Asset Account, and Expense Account as provided in the integration setup as seen below. Inventoried items are required to populate purchase order lines in Quickbooks that are not expensed/categorized.

In addition to being created on the fly when purchase orders are being synced, ION parts are also created in QBO as inventoried items when the ION part is created or updated in ION.

Non-Inventoried Purchase Order Lines

If no part is specified on the PO line, then this is a non-inventoried line that will create a categorized purchase line on the Quickbooks purchase order. If no part is associated with an ION PO line, then the default for the expense account is what your organization configures as the inventory expense account as seen below. If an expense code is specified on the PO line, then the categorized expense will utilize that account instead of the inventory expense account. For the scenario where you want to specify the expense account per line item, the expense accounts can be set up in ION as a Select custom attribute as seen below. The various accounts will need to be added to the custom attribute as options that can be selected on the PO line.

Fees and Secondary Expenses

For fees on a purchase order in ION, you can configure an Account for Fees as seen below which categorizes all fees (i.e. shipping and taxes) according to the account specified.

Please keep in mind that as an organization, you will need to ensure that your expense codes, classes, and suppliers will need to be kept in sync. This integration will handle errors and inform you when data is out of sync (i.e. an expense code exists in ION and not in QBO).

Setup

  1. Select the Quickbooks integration instance from the marketplace, and hit Configure.

  2. Add your ION API credentials. You can find documentation on API credentials here API Keys

    • IMPORTANT: Each API Key is associated with a specific environment, be sure to generate the API keys from the correct environment and configure the automation to the designated environment.

  3. Connect with Quickbooks and choose the company in Quickbooks Online to deploy this integration. A Quickbooks Online admin will be required to download the application.

  4. Type in the NAMES (not type) of the different accounts in your Quickbooks instance. The AP account will be associated with the purchase order. The Income Account, Inventory Asset Account, and Expense Account will be associated with new inventoried products that need to be created to match parts on purchases in ION. The Account for Fees will categorize all fees on an ION Purchase according to the account you set here.

  5. To recap step 5 these are the mandatory fields to fill in:

    1. Accounts Payable

    2. Income Account

    3. Inventory Asset Account

    4. Inventory Expense Account

    5. Account for Fees

  6. Finally, type in your ION Purchase Order Line Attribute names related to Class and Expense that you have set up in your ION organization settings. Please set up these attributes as Select types. This must be an exact match, case sensitive.

    1. The class attribute is the name of the PO line attribute in ION that will sync to the Quickbook class attribute.

    2. The expense attribute is the name of the PO line attribute in ION that will sync to the Quickbook Expense account for the line item.

  7. Press finish.

Navigate to the designated by the two arrows in the bottom left corner of your screen.

Integrations page
ION purchase order
Set Up
Demo of Quickbooks Integrations
Navigate to Products/Services > New > Inventory to See the List of Fields Required to Create an Inventoried Product
Select Integrations in the Bottom Left Hand Corner
Set your Environment According to Where the API Keys were Generated
Example account names from quickbooks COA