Connect your Acumatica

iVendNext Acumatica connector · version 2.0.0.108 · checked 2026-11-03

This page takes you from a customer's Acumatica to a working connection with iVendNext. It explains each field of the iVendNext Acumatica Setting form. The connector is in beta, so read it with the limits to expect beside it. To see what crosses between the two systems, read What syncs today. Before you switch the connection on, work down the go-live checklist.

This page does not repeat Integration Core's pages. For the Hub, the states of a record and the Switch on button, read Set it up.

What the connector does

The connector carries a store's sales, returns and payments from iVendNext to Acumatica as released documents. It carries Acumatica's items, prices, customers, vendors and stock movements to the store.

Acumatica owns accounting. iVendNext owns what the till collected. One iVendNext tenant connects to one Acumatica company, and nothing crosses between tenants.

Who uses it

A System Manager starts the connection, enters the sign-in details and presses Register Connection the first time.
An Integration Manager does the rest of the setup and watches the connection every day.
The customer's Acumatica administrator and finance team answer the questions on the go-live checklist.
Cashiers and store managers keep working on the till and in Desk as usual.

Where it shows

Integrations Hub: the Acumatica card opens the list of Settings. Every record the connection moves shows on Integration Activity.
Forms you already use: on Item, Batch, Serial No, Delivery Note and Item Price, the connector adds read-only fields to these forms. They are listed under Fields the connector adds to your screens.
The till and Desk: a cancel of a document Acumatica has is refused, and the message says what to do instead.

What leaves your shop

The connector talks to one place: the Acumatica address in Base URL. It sends these things there.

Sales, returns, payments, refunds and till closings.
Customer orders with their deposits, deliveries and invoices.
Store purchase orders, receipts, transfers, counts and kits.
Customers made in iVendNext, with their name, phone, email and address, and later changes to the phone, email or address of any linked customer.
Store expenses, and the journals for expired gift cards if you switch that option on.
Barcodes added to an item at a store.

The sign-in details are stored on your site and sent only to that address. The connector sends nothing elsewhere. Integration Core can email a person a daily summary.

Check Acumatica first

Do these checks before anyone enters a password. None of them needs the connector. A customer's Acumatica will differ from any other, so read each row as something to check.

What to check	Where in Acumatica	Why it matters
The web-service endpoint is published at 24.200.001 or later.	Web Service Endpoints (SM207060)	The Setting refuses an older version.
The sign-in name of the tenant.	The login screen	The connector needs the tenant's login name, not its number.
Which company and branch the store belongs to.	Companies (CS101500), Branches (CS102000)	A connection reaches one company, the one its Branch belongs to. On a tenant with several companies, you must name the Branch, or no warehouse arrives.
The company's base currency equals the iVendNext company's currency.	Companies (CS101500)	A sale in another currency is refused before release, and nothing is posted.
The current financial period is open, and next year's is open before January 1.	Manage Financial Periods (GL503000)	Acumatica refuses a document dated in an inactive period.
Each tax is Exclusive where shelf prices include tax.	Taxes, Tax Zones	Acumatica must add its tax on top of the net price the connector sends.
Which tax zone charges the same tax as each till tax template.	Tax Zones, Tax Categories	You enter this in Tax Zone Mapping. For each template, one tax category must contain all its taxes. One category with no taxes must exist for untaxed lines.
Which rounding method each side uses.	iVendNext: System Settings, Rounding Method. Acumatica: the customer's own setting	A desk, web or delivered invoice can differ by a cent on a tie. Ask the customer to set iVendNext to the method their Acumatica uses.
A customer class with Credit Verification set to Disabled, for the POS customer and every walk-in customer.	Customer Classes	A class with a credit limit puts the walk-in on Credit Hold, and the invoice is not released.
The default country of that class.	Customer Classes	A customer sent with no address arrives with Acumatica's default country.
How long an Inventory ID can be, and the CustomerID mask.	Segmented Keys	A longer item code is refused. The connector builds a customer's key with 10 characters, so another width needs a change first.
Stock in the warehouse a sale issues from, or that negative available-for-issue is allowed.	Warehouses, Item Classes	Acumatica refuses a sale that takes the item below zero, and nothing is created.
Which items are tracked by lot or serial number.	Item Classes	See A lot- or serial-tracked item.
The POS customer has no automatic document discount or freight terms.	Customers	Either one changes Acumatica's amount, and an inclusive sale is then refused before release.
How many API users the license allows.	License Monitoring Console (SM604000)	A person must read this on the screen. Each Acumatica browser session takes a seat too.
A dedicated integration user.	Users (SM201010)	The connector signs in as this user. Rights it does not have show as a 403. Never send credentials by email.
The address uses https.	The customer's hosting	The Setting refuses plain `http://` unless you tick the box for it.

Prepare the iVendNext site

Take a backup first. Install Integration Core, then the connector. Version 2.0.0.108 was tested with Integration Core 2.1.0.185, so install that release and not simply the newest.

Create the company before the stores open. iVendNext refuses to create a company while any till day on the site is open.

Then set up the first store in this order.

Choose the connection's name. The connector's price list is called Acumatica <connection name>.
Create that Price List as a selling list in the company's currency. A till profile needs it first.
On the store's Warehouse, set Selling Price List to that list. Tick Is Retail Store. Set Cash Customer and Company Currency.
Add a clearing account for cards. On Mode of Payment, add an account row for the company for each tender the store takes.
Create a walk-in customer for the store.
Create the POS Profile with its company, warehouse, customer, currency, price list and tenders.
On the POS Terminal, tick Has Cash Drawer before the first day opens. A day already open keeps taking no cash.
Set up the till user: Is POS User, a shift profile, a store access row, a cashier's roles, Stock User and Stock Manager.

Set these before the first poll as well.

The default customer group, on Selling Settings. If it is blank, every new customer waits.
The site's time zone. Set it before you press Register Connection. Press that button again after any later change.
Returnable and Return Days on Item, in Customize Form. Items arrive from Acumatica not returnable. The default reaches only items that arrive after you set it.
The tax at the till. Give the store's warehouse a default item tax template. Leave Tax Category blank on the POS Profile, so that a customer's tax category counts.
Voids. Save Voided Transaction, on Retail Setting, is off when you install. A voided sale then leaves no record.

Start the connection

A System Manager starts the Setting. Open Connections, then Connect a system, then Acumatica, and press Start. The form has credentials on it, so an Integration Manager is told to ask a System Manager.

Save before you press Test Connection, because the test uses the saved details.

Once the connection is registered, where it points cannot change. A new Base URL host or path, Branch, Company or tenant is refused: "Add a new connection to reach another Acumatica: this connection is registered, so where it points cannot change." Every record the connection linked names a document in the company it reaches now.

The sign-in may still change. So may http:// to https:// on the same host, and a move between Legacy Session and OAuth 2.0 on the same tenant.

Connection

Connection Name

Enter a short name. It cannot be changed afterward, and it cannot contain a bracket. It also names the price list.

Base URL

Enter Acumatica's address, such as https://erp.example.com/AcumaticaERP, with no slash at the end.

I accept plain HTTP for this connection

Tick this for a demo or a lab only. Over plain HTTP, the password and every document cross the network unencrypted.

Endpoint Name

Leave the default, Default, unless the customer publishes another endpoint.

Endpoint Version

Leave the default, 25.200.001, or enter the version on SM207060. It must be 24.200.001 or later.

Acumatica Tenant/Company

Enter the tenant's login name.

Branch

Enter the Acumatica branch every request is sent under. Name it before you press Register Connection. If you leave it blank, you can name it once afterward, while the connection has linked only items, vendors and customers.

Authentication

Auth Mode

Use Legacy Session for now. OAuth 2.0 also works, and it needs a client from Connected Applications (SM303010). With OAuth, each session of the connection takes its own license seat.

Username

Enter the integration user. Both modes need it.

Password

Enter that user's password. Both modes need it, because OAuth here uses the password grant.

OAuth Client ID

Only for OAuth. The @tenant part of the ID names the tenant.

OAuth Client Secret

Only for OAuth. Enter the secret from SM303010.

Integration Core Registration

Company

Enter the iVendNext company this connection belongs to. Only one connection can be on per company.

Acumatica Environment ID

Enter an id you choose once and write down. Do not enter the address, the host or the tenant name.

Country

Enter the company's country.

Registered Application and Runs As (pinned at registration) are filled when you press Register Connection. Do not edit them.

Polling

Cut Over At

Decide this before the first run. If you leave it blank, nothing already in Acumatica flows in. Only records created or changed after switch-on arrive, and the choice is fixed after the first run. To load the masters in full, set the date back to before the oldest record you want.

Before a full load, name each store's walk-in account on its Warehouse Mapping row. Otherwise the load brings those accounts in as real customers.

Poll Overlap (seconds)

Leave the default, 120. Keep it at 5 or more.

Page Size

Leave the default, 200.

Resolution Reads per Cadence

Leave the default, 50.

Throttled Until

The connector sets this when Acumatica asks it to wait. See API Login Limit.

Last Polled At

The connector sets this at each poll.

Default Item Group

Choose a group for new arrivals. Items stay there until the nightly pass creates their Acumatica item class's group. This group shows on every till that shows all groups.

Lock masters Acumatica owns

This is on by default. While it is on, a person cannot add, rename or delete an item, item group, unit, supplier, supplier group, sales person, customer group or the company's warehouse. A gift card item is the exception. Editing other fields is never refused.

The lock starts once the connection is switched on or has ever run. Untick it only while someone must create masters by hand, and tick it again at go-live.

Flows

Add a row only for a flow you want to change, either switched off or every N minutes. With no row, a flow is on. A flow name reads <entity> (from Acumatica), <entity> (to Acumatica) or <pass> (nightly).

A flow switched off starts nothing new, and what is already on its way finishes. When you switch it back on, it sends each record once.

The form refuses a flow it does not know, a flow listed twice and negative minutes. It also refuses a flow left on while a flow it waits for is off. customer (to Acumatica) may be off while sales run, and a sale to a named customer then waits. A flow money waits on rings one bell a night while it stays off.

Prices from Acumatica

By default, prices arrive overnight. You can make them faster in two ways.

A released price worksheet starts a price pass at the next run. To stop this, add a row for released price worksheets (from Acumatica) and untick Enabled.
Every N minutes. Give prices (nightly) a number below 1440 in Every (minutes). The form refuses less than 15.

Each pass reads every Acumatica price and uses one Acumatica sign-in while it runs. That takes seconds for hundreds of prices and minutes for tens of thousands. On a site with one long background worker, each pass delays sales to Acumatica by its own length. Add a long worker, or keep prices nightly and switch the worksheet flow off. The Prices from Acumatica notice shows the last pass.

A price edited straight on Sales Prices (AR202000) arrives at the next scheduled pass. A price Acumatica stops publishing is removed only overnight.

What the store sends

POS Customer (Acumatica CustomerID)

Enter the Acumatica customer a walk-in sale is invoiced to when the store has no walk-in account of its own. Check that the ID exists in Acumatica first. A wrong ID fails every walk-in sale with an error that names no field.

POS Warehouse (Acumatica WarehouseID)

Enter the warehouse a line is issued from when its store has no Warehouse Mapping row. Sales wait until it is set.

Disassembly Reason Code (Acumatica)

Enter a reason code from Acumatica. You need it only where a store breaks up kits.

How documents post

Acumatica Order Type

The default is SO. It applies to Advanced orders only. A dedicated order type keeps these orders apart from the back office's.

Till sales post as

One document per ticket is the default. Each till sale, return and tender is its own Acumatica document.
One roll-up per shift sends the invoices iVendNext makes when a POS day closes: one per customer per closing, with one payment per payment mode. It needs the company's own POS Invoice posting set to Roll up posting-On Shift Closure first.

A day posts the way it was opened. A day Acumatica cannot take as one invoice falls back to one document per ticket at its closing, and the list of differences names it. You cannot change this while a POS day is open or a till document is still on its way.

Customer orders post as

Standard sends the money only, with no Acumatica sales order. A deposit becomes a prepayment, and a delivery becomes a released invoice. It creates about 3 documents for a one-store order with a deposit.
Advanced sends the Acumatica sales order, its shipments and payments. It creates about 5 documents. Head office may ship the order in Acumatica, and what it ships comes back.

A new connection starts on Standard. An order keeps the choice it started under. You cannot change this while an order document is on its way, so choose before go-live. Read the notice beside the field before you choose Advanced.

Customers

Customer Key Prefix

Enter 1 to 4 letters, unique to this site. A customer's CustomerID is this prefix plus a number. A second site on the same Acumatica company must use a different prefix.

Customer Class Mapping

Each row pairs an Acumatica customer class with an iVendNext Customer Group. A row is added by itself for each class a customer arrives in. Map at least the group a till-made customer goes to.

A customer whose group has no row waits. To send no customers at all, switch customer (to Acumatica) off in Flows. Walk-in sales still go.

UOM Mapping

Each row pairs an Acumatica unit, spelled exactly as Acumatica spells it, with an iVendNext unit. Case and spacing count. One Acumatica unit may not sit on two rows. The nightly pass fills most rows by itself.

The person who saves a row needs a role that reads units: Item Manager, Stock Manager or Stock User. Without one, the save is refused with No permission for UOM.

Non-Stock UOM

Choose the one iVendNext unit that Acumatica non-stock items are kept in. Those items wait until it is set. A sale or order line in this unit is sent with no unit, so Acumatica bills it in the item's own unit. It needs no UOM Mapping row.

Tax Zone Mapping

Each row pairs an iVendNext Item Tax Template with the Acumatica Tax Zone that charges the same tax. Add one row per template the till uses, including the store's default.

When you save a row, the connector reads the zone in Acumatica and shows the result in Check: Sent as, No tax or Zone only. Zone only means a tax service works out the tax, so the till's tax is not sent and each difference shows on the Hub.

A ⚠ in Check tells you what to fix.

The row says	What happens
The rates differ	The till's tax is still sent. Correct whichever rate is wrong.
No Acumatica category admits the tax	The tax is not sent, and each sale shows a difference. Add a category in Acumatica.
No category lists no taxes	An untaxed line is taxed by its item's own category.
The zone was not found, or Acumatica could not be read	That zone's sales wait.

The save goes through either way. The connector reads every row again each night, and a corrected rate clears its ⚠ then. A sale whose template has no row waits, and it goes by itself once you save the row.

The person who saves a row needs the right to read tax templates. The waiting sale names the roles, or a System Manager can save it.

Tender Mapping

Each row pairs a Mode of Payment with an Acumatica payment method and cash account. Check each pair in Acumatica before you save. A wrong pair that Acumatica accepts is created, applied and released into that cash account, and nothing can see it.

The method must be active for receivables. An On Account tender has no row, because an on-account sale sends no payment.

For a till closing, each counted tender also needs Acumatica GL Account and Acumatica Over/Short Account. Its subaccounts and GL branch are optional. A closing waits whole until the accounts exist, and its record names every missing account. Where a tender's GL branch differs from the connection's, Acumatica also needs that pair in Inter-Branch Account Mapping (GL101010).

Gift Card Account Mapping

Enter the customer's liability account for gift cards, never a revenue account. A gift card sale, recharge or cashback line waits until its row exists.

Release Expired Gift Cards

This is off by default. When you tick it, a card's unused balance moves to an income account the night after the card expires. Read the notice beside it first, because it counts the cards that expired before. Those cards are written off by hand.

The Gift Certificate payment method must clear to the liability account, through a Cash Account for each store's branch.

Expired Gift Cards: Acumatica Income Account

Enter the income account. Acumatica accepts any account it has, so check that this one is an income account.

Expired Gift Cards: Subaccount

Enter this where your Acumatica uses subaccounts.

Charge Account Mapping

Each row pairs an account a document charge is booked to with a non-stock Acumatica Charge item, such as FREIGHT. Create the Charge item in Acumatica first, then clear Require Shipment on it (Non-Stock Items, IN202000). Acumatica refuses a charge item that requires shipment on a customer order.

A till surcharge needs no row. Give the iVendNext Surcharge the code of its Acumatica Charge item.

On a desk or web document, Acumatica taxes the charge by the item's tax category, so set that to match how the shop taxes delivery. On a till document, its tax goes as the till charged it. A Tax account is refused.

Before you add a row, check that nobody recorded a waiting sale in Acumatica by hand. Each one is sent as soon as the row exists.

Till Cash-up Accounts

Reason Account Mapping

Enter the account for each paid-in and paid-out reason. A closing waits whole until every account it needs exists.

Paid-in With No Reason: Acumatica Account

Enter the account for a paid-in with no reason, and its subaccount where your Acumatica uses them. By default, iVendNext asks for no reason, so every paid-in goes here.

Paid-out With No Reason: Acumatica Account

Enter the account for a paid-out with no reason, and its subaccount where your Acumatica uses them.

Warehouse Mapping

The connection's Acumatica warehouses arrive by themselves each night, each with a row here. A row pairs the Acumatica warehouse with an iVendNext warehouse. You add two things.

Acumatica Walk-in Customer. This is the store's own account for walk-in sales. If it is blank, those sales post to POS Customer. Use an account whose class has credit verification off.
Start Stock. Tick this the evening the warehouse goes live. The next nightly pass copies Acumatica's on-hand there once. Until then, its Acumatica movements wait. Ring no sale there before the morning.

A warehouse that arrives is never ticked as a store. A store is a warehouse you tick Is Retail Store. The person who ticks it needs Item Manager, plus read access to Selling Price List, Cash Customer and Item Tax Template.

Release Imported Walk-in Accounts

A full load may bring a walk-in account in as a customer. Naming that account on a row is then refused, and the message names the Customer the load made. Tick this box and save again. The save makes the link inactive, disables the imported Customer, and says so. The tick lasts one save.

Check the name first, because a real customer released by mistake stays disabled. An account whose Customer already has documents in iVendNext stays refused. Create a new walk-in account in Acumatica instead.

Test, register and switch on

Press Test Connection. When it works, it says "Signed in to Acumatica and read stock items through endpoint", followed by the endpoint.
A System Manager presses Register Connection the first time, because that press needs the right to grant roles. Anyone who can edit the Setting may safely press it again.
Open Connections in Integration Core, then your connection. The top of the form lists what it still needs.
Give the application user its roles by hand: Purchase Master Manager, Sales Master Manager, Purchase User, Stock User, and Stock Manager for the opening counts. Add Item Manager where iVendNext tracks items by batch or serial number, and Manufacturing User where Manufacturing is licensed. Never give it System Manager.
For unit conversions, a System Manager adds a Custom DocPerm row that gives the user's role Create on UOM, UOM Category and UOM Conversion Factor. A site that declines this still gets items, prices and units.
Press Switch on. Ring no sale until Where outbound sales start reads Ready. The first run only fixes where each flow starts.
Wait for a record to cross. A real record on Integration Activity shows that the connection works, whatever color a word shows.

You can switch on while rows still read Still needed. They are things to finish, not a block. Configuration owed gathers what is left in one row.

Point each store at its prices

The connector fills Acumatica <connection name> every night, but it cannot point a store at that list. Set each warehouse's Selling Price List yourself. A store that skips this has Acumatica prices in a list nothing reads, with no error. The row Stores read the Acumatica price list names the stores still pointing elsewhere.

A warehouse with its own prices in Acumatica gets its own list, Acumatica <connection name> (store <warehouse>). Point that store at that list instead.

What to expect after you switch on

What	When	Where you read it
An item, customer or vendor made or changed in Acumatica	On the one-minute run. A customer took seconds when measured, and a first load of many items takes longer.	Integration Activity reads Applied, and the record exists in iVendNext.
Prices	Overnight, or sooner if you chose it under Prices from Acumatica	The Item Price in `Acumatica <connection name>`, and the Prices from Acumatica notice.
Costs, opening counts, units, conversions, item groups	Overnight	The item's cost, stock, units and group.
A till sale, return or tender	Within about 2 minutes	Integration Activity reads Applied once Acumatica has released it.
A till closing	On the next run	A journal only if a counted tender is over or short, or cash moved in or out. A closing with no difference sends nothing.

A sale may read Unverified for one run, because Acumatica answers a release with "accepted, in progress". It reads Applied on the next run.

Check a document on Acumatica's screen

Open the document in Acumatica and compare it with iVendNext.

What	Acumatica screen	Compare
A sale or return	Invoices (SO303000)	Customer, branch, each line, Detail Total, Tax Total, Amount, Balance, Status and each stock line's warehouse
Its payment or refund	Payments and Applications (AR302000)	Method, cash account, amount and unapplied balance
A till closing	Journal Transactions (GL301000)	Debit over/short, credit cash, status Posted
A customer	Customers (AR303000)	Class and tax zone
An item	Stock Items (IN202500), Non-Stock Items (IN202000)	ID, default price, class and tax category

Acumatica overwrites Payment Ref on a cash payment, so every cash payment can show the same number. Match them by External Ref, which shows the POS Invoice name.

What the connector keeps on your site

The connector keeps six kinds of record for its own work. A person does not work in them. They are listed here so that you know what you see when you search Desk.

Record	What it keeps
iVendNext Acumatica Attended Delivery	One row for each delivery a person finished in Acumatica, after the connector asked them to release a document.
iVendNext Acumatica Barcode Sync	The barcodes an item had on each side at their last sync.
iVendNext Acumatica Customer Key	The CustomerID the connector made for a till customer.
iVendNext Acumatica Customer Sync	A linked customer's phone, email and address on each side at their last sync.
iVendNext Acumatica Order Line	How each order line matches its line in Acumatica.
iVendNext Acumatica Posting Stamp	The posting choice each customer order, POS day and roll-up invoice started under.

There is one exception, on Customer Key. When a record says a key is already an Acumatica customer that is not this one, tick Retired on the key row. The connector makes a new key on the next run.

Connect a second site to the same Acumatica company

Use a different Customer Key Prefix and a different Acumatica Environment ID. A key Acumatica already has for another customer is refused.