What syncs today

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

The connector keeps a store's iVendNext and a customer's Acumatica in step. This page says what crosses in each direction, what waits for a person and what does not cross. For the limits you may meet, read Limits to expect.

How things move

Acumatica owns items, units, prices, vendors, warehouses, customer identity and all accounting. Where both sides have a field Acumatica owns, Acumatica's value stays. iVendNext's own ledger entries have no financial standing.
iVendNext owns what the till collected. A sale, a return and a tender cross as tendered, and a till document's tax crosses as the till charged it. Acumatica owns the released document's number.
Within about 2 minutes for a sale, a return, a tender and a customer made in Acumatica. Item and vendor changes go on the same one-minute run, and a first load takes longer. The connector runs every minute.
Overnight for prices, costs, units, conversions, item and vendor groups, warehouses, sales persons, kit recipes and opening counts. You can choose faster prices.
One tenant, one company. One iVendNext tenant connects to one Acumatica company, and nothing crosses between tenants.

From Acumatica to your stores

Items

The connector brings in stock and non-stock items, including size and color matrices. A matrix arrives as a template with its variants. Acumatica owns the ID, description, units, class, tax category and cost. iVendNext owns its till-only attributes and never sends them back.

An item whose unit has no UOM Mapping row waits. A non-stock item waits until Non-Stock UOM is set.
Items arrive not returnable, unless you set the default first.
Items from before Cut Over At do not arrive.
An item made only in iVendNext does not cross, and a sale of it waits.
An item whose tax category is exempt or zero-rated takes the matching template once Tax Zone Mapping has a row for it. A taxable item takes the store's rate.

Barcodes cross both ways, and only ever get added. Acumatica's barcodes are added to the item. One added at a store reaches Acumatica's item overnight. The connector never deletes a barcode, and it never puts back one a person removed.

Item cost

A nightly pass writes Acumatica's cost to the item. A cost of zero means unknown, so nothing is carried.

Units and conversions

Units and conversions arrive overnight. Creating conversions needs a Custom DocPerm row for the application user's role. An Acumatica unit that is not mapped keeps its items waiting, and the waiting record names the roles that may save the row.

Prices

Prices arrive overnight, unless you choose faster. The connector brings in each of these.

The Base prices, into one list the connector owns, Acumatica <connection name>.
Each customer price class.
Each store's own prices.
Each named customer's prices. The connector marks these, so a person's own customer price is never touched.
The item's Default Price, where no Base row prices that unit.
For a non-stock item, a price per its sales unit.

These carry nothing, and the connector counts and names them.

Break-quantity rows.
Warehouse rows for a store that has no prices of its own.
Rows in a foreign currency.
Rows in a unit that is not mapped.

Acumatica's price is net, and an inclusive till sells it as gross. A store that does not point at the list reads none of these prices. A promotion's end date is not carried, so the regular price comes back at the next nightly pass.

Vendors

A new or changed vendor becomes a Supplier on the one-minute run. A vendor deleted in Acumatica disables its Supplier, but never while it has open purchase orders. The application user needs Purchase Master Manager, or every vendor waits. A Supplier made only in iVendNext does not cross.

Customers

Customers go both ways. Acumatica owns the ID, name, class and terms. iVendNext owns loyalty, till groups and any price list override.

A customer made at the till is sent once, with a key the connector makes from its prefix and a number.
After that, phone, email and address go both ways, and the latest change wins. The same field changed on both sides goes to a person.
A customer in a group with no Customer Class Mapping row waits.
A sale to a named customer waits until that customer is in Acumatica.
A change of group after the customer is created does not cross.

Credit

iVendNext's own credit limit decides an on-account sale at the till. Acumatica's own credit check applies when the document posts, and a document it stops is named for a person. Acumatica's terms, limit and live balance are not copied.

Warehouses

Every warehouse of the connection's company arrives each night with its row on Warehouse Mapping. It is never ticked as a store. An unticked warehouse is central: no count, no store purchase order and no store price list. A warehouse that turns inactive or disappears is listed on Integration Core's differences list, and is never disabled or deleted.

Item groups, vendor groups and sales persons

These arrive overnight. An item class becomes an item group, and existing items move to it. A vendor class becomes a supplier group. A salesperson becomes a sales person. Set tax templates and promotion exclusions on the class groups before the first night, because that night moves items still in the default group.

Stock movements made in Acumatica

A receipt, issue, transfer, adjustment or kit assembly released in Acumatica reaches the store once, as a stock entry.

Stock levels never cross. The one exception is each warehouse's opening count, which runs once on the first nightly pass after a person ticks Start Stock.

The application user needs Stock User, and Stock Manager for the opening count. The company needs a Temporary (opening) account.
A movement into a warehouse not started yet waits for its start. Nothing is skipped.
A warehouse iVendNext moved stock in first gets no count. The differences list names it, once. See A store did not get Acumatica's stock.
An Acumatica issue that would take a store below zero waits.
The store's own sales, receipts, transfers and counts are never read back.

Purchase orders raised in Acumatica

An open order whose lines deliver to a mapped warehouse arrives, so that the store can receive it. It needs Purchase User. An Acumatica edit after the store received goes to a person. A Drop-Ship or Blanket order does not arrive.

From your stores to Acumatica

A till sale

A till sale becomes a released Sales Invoice in Acumatica, with one Payment for each payment method. It is not a Cash Sale, because a Cash Sale line carries no warehouse or unit on Acumatica's API, and its header takes one payment method.

The lines go at the net price, with any discount, and each line issues from the store's mapped warehouse.
The tax goes as the till charged it, with the store's zone.
The till and the time ride on the invoice Description.
A walk-in sale goes to the store's walk-in account, or else to POS Customer.
A document charge goes as a line on its Acumatica Charge item.
The sale's first sales person goes on every line, if that sales person came from Acumatica.

These wait, and the record says why.

A template with no Tax Zone Mapping row.
A gift card line with no Gift Card Account Mapping row.
A charge with no Charge Account Mapping row.
A line in a unit whose conversion differs from Acumatica's.

These go to a person: a non-stock kit, loyalty points redeemed on the document, a tender discount, an advance consumed and an unpaid balance.

Whether a discount was manual or a promotion, and a voided line, do not cross.

A lot- or serial-tracked item

Where both sides track an item, the connector sends the numbers.

A till sale names the number the till sold, with one Acumatica line for each number. A return puts the number back.
Receipts, counts, transfers and deliveries carry their numbers and expiry dates.
Acumatica's own movements arrive with theirs. A number received is made in iVendNext, and the application user needs Item Manager for that.

A sale naming a lot Acumatica has too little of is refused, and its record names the lot to receive. Where Acumatica tracks an item and iVendNext does not, a count or receipt goes to a person, and a sale goes without a number. Acumatica then picks the lot.

An on-account sale

An on-account sale becomes an invoice on that customer, left open, with no payment. A customer's later payment becomes a payment applied to that invoice. The customer must already be in Acumatica.

A return or refund

A return becomes a Credit Memo and a Refund, with one refund for each mode and the tax reversed. A return whose original customer can no longer be read goes to a person, so that a credit is never posted to a guessed customer.

A till day posted as a roll-up

With One roll-up per shift, the connector sends the day's documents when the day closes.

One invoice per customer, with walk-in sales together.
One credit note per customer for the returns.
One payment or refund per mode.
An on-account sale on its own invoice.

A ticket Acumatica cannot take inside one invoice makes that day post per ticket, and the differences list names it. A sale of a tracked item is the usual case. Expect a day's documents in the hours after closing.

Tenders

Each payment mode becomes one Payment applied to the sale's invoice. Cash, card, store credit and gift certificate all go through Tender Mapping.

A tender waits until its invoice is released.
A mode with no row waits.
A foreign-currency tender goes in its own currency, and any change becomes a Refund.
A foreign note beside a second tender, with change, goes to a person.
An On Account tender sends no payment. Loyalty and gift card balances stay in iVendNext.

A till closing

A closing becomes one Journal Transaction, with a debit and credit pair for each counted tender that is over or short, and for each paid-in and paid-out. A store expense is its own journal. A closing with no difference sends nothing.

A closing waits whole until its accounts exist. An amended closing whose journal Acumatica already has goes to a person, who reverses the batch the record names.

An expired gift card's unused balance

This is an option, Release Expired Gift Cards, off by default. Each expired card becomes one released journal the night after it expires. The journal debits the liability its sale booked and credits your income account. A card that expired before you switched this on is never released. The Setting's notice counts those cards.

Customer orders

Customer orders post as decides what Acumatica gets. The question for a business is whether head office ships or manages store orders inside Acumatica.

Standard sends the money.

A deposit becomes a prepayment.
A delivery, or an invoice made before any delivery, becomes a released invoice that applies the deposit.
A balance becomes a payment on that invoice.
A cancel refunds each deposit off its own prepayment.
There is no Acumatica order, so head office cannot ship, change or cancel it there.

Advanced sends the order itself.

The order becomes a Sales Order. Each store's delivery becomes a shipment and an invoice, and the deposit becomes a prepayment.
Head office may ship from Acumatica. Its released invoice comes back as a Delivery Note and Sales Invoice, marked as head office's, and is never sent back.
Head office closing, cutting or removing a line, or changing the ship date, is made in iVendNext too.
Head office's money changes and its cancel stop for a person, and so do both sides delivering one order.
Before the store submits a delivery, an invoice or a payment, the connector asks Acumatica. A delivery of goods head office already shipped is refused on the screen, and so is a payment head office was already paid.

See Head office's actions on an Advanced order.

Orders and sales that did not start at a till

Orders and invoices from the desk or an online shop follow the same routes. A desk or online invoice is released. Its return becomes a credit memo, and a customer refund is sent too. An invoice made on the POS Invoice form in Desk, a debit note, an opening invoice and an advance with no reference go to a person. Do not also post an online shop's sales to Acumatica another way.

Store purchase orders and receipts

A store order becomes a Purchase Order, and it arrives Pending Approval where Acumatica has an approval map. A receipt becomes a PO Receipt. A receipt against an order that is not open is refused, and the record says to approve it first. The AP bill stays Acumatica's and is never created from iVendNext. A rejected line sends the accepted quantity.

Stock transfers and counts

A transfer between two mapped warehouses becomes a Transfer Order. A count becomes an Inventory Adjustment. Stop keying these by hand in Acumatica, or the same move goes in twice. An amended or canceled document Acumatica already has is not reversed.

Kits

A store's Kitting or De-Kitting becomes a released Kit Assembly. A stock kit's recipe arrives as its default BOM only where Manufacturing is licensed. A recipe changed later in Acumatica is listed, not applied. A non-stock kit sold at a till goes to a person. Ring it as a customer order, which also goes to a person, or have it made a stock kit.

A store kit of a tracked component goes to a person too. Record it in Acumatica with the Description its record gives, so that it does not come back as a second kit.

The Acumatica number

The document number and whether it is released show on Integration Activity. The number is not written on the store document.

What you can set

Flows: a switch and a frequency for each flow. See Flows.
The masters lock: on by default. See Lock masters Acumatica owns.
How documents post: Till sales post as and Customer orders post as.

Fields the connector adds to your screens

The connector adds these fields to forms your staff already use. The connector fills them, and a person cannot edit them.

Acumatica Kit

On Item. It shows that the item is a kit in Acumatica. A kit that is not a stock item is not sent on a sale, because Acumatica takes one only from a sales order.

Acumatica Requires Shipment

On Item. It shows that Acumatica ships this non-stock item on a shipment, so it ships like a stock line.

Acumatica Tax Category

On Item. It shows the item's tax category in Acumatica.

Acumatica Exempt Template

On Item. It shows the tax row the connector wrote for an exempt or zero-rated Acumatica item. Only a row the connector wrote is ever taken away, so your own row stays.

Acumatica Lot/Serial Class

On Item. It shows the item's lot or serial class in Acumatica, which decides whether the item is tracked.

Acumatica Lot/Serial Number

On Batch and Serial No. It shows this number in Acumatica, where it differs from the name in iVendNext.

Acumatica Head-Office Shipment

On Delivery Note. It shows that head office shipped this in Acumatica, with its invoice and shipments. A delivery with this mark is never sent back.

Acumatica Connection

On Item Price, on a customer's price. It shows the connection that keeps this price. The connector updates and removes only the prices with this mark.

What does not cross

Tax on a desk, web or delivered invoice. Acumatica works that out from the customer's tax zone.
Acumatica's credit terms and limit, and its live balance.
Stock levels. Only movements cross, plus each warehouse's one opening count.
Exchange rates. Keep them in iVendNext's Currency Exchange.
Items and suppliers made in iVendNext.
Layaway.
A sales person's commission, whether a discount was manual or a promotion, and a voided line.
A cancel of a document Acumatica has. iVendNext refuses it and says what to do instead.
Break-quantity prices.