When something looks wrong

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

This page covers what is particular to the Acumatica connector. Each entry says what you see, what it means, what to do and when to call support. For a symptom every connector shares, read the Integration Core page Something looks wrong first. The states and words are defined once, in What each state means.

Two rules apply everywhere on this page.

• Never key a document into Acumatica by hand while the Hub shows it as Failed, Waiting or Unverified, until you have read its record. A hand copy goes in twice.
• Never press Retry on a record you have not read.

A Failed record shows what failed and the one thing to do on its first line. Read the Error field below it for the rest.

A sale that reads Retrying for a short time means Acumatica's screen is busy. Do nothing, and do not key the sale by hand. The connector sends it again by itself.

Find your symptom

A sale is waiting

What you see. A sale, its tender or a return reads Waiting, and its row says "Waiting on:" followed by a sentence.

What it means. Nothing was lost and nothing was sent. The connector checks what it needs before it sends, and something is missing. It checks again every minute. The sentence says who must act.

What to do. Find the sentence, and do what it asks. The record goes by itself on the next run.

When to call support. The sentence names something you cannot find, the same sale waits for more than a day after you fixed it, or the row says "for a reason this connector does not model". Send the document number and the sentence, copied exactly.

A record needs a decision

What you see. A record reads Needs a decision, and its first line says what to do by hand.

What it means. The connector cannot settle this by itself, and it sends nothing more for this record. Usual cases are a non-stock kit sold at a till, a tender discount, loyalty points, an advance, an unpaid balance, a document Acumatica no longer lists, and a document canceled or voided in Acumatica.

What to do.

1. Read every open decision on the same record.
2. Do what the first line says. If you record the document in Acumatica by hand, put the iVendNext document number in External Ref.
3. Press Keep iVendNext Version with a note. That button records your decision and does nothing else.

Never press Retry to see whether it goes. Do not cancel or amend a sale a person kept in order to send it again.

When to call support. A record has no sentence, or the same decision comes back after you decided.

Head office's actions on an Advanced order

What you see. A record whose title names head office or an order Acumatica shipped. These exist only when Customer orders post as reads Advanced. Head office can then ship, change or cancel the order in Acumatica.

What it means. Some of head office's actions come back by themselves. A shipment and its invoice, a closed or cut line, and a changed ship date all come back by themselves. These stop for a person, and nothing is applied until someone decides.

• Head office changed the money on an order. Its title reads "Head office changed the money of an order in Acumatica".
• Head office canceled an order. Its title reads "Head office cancelled an order in Acumatica".
• Both sides delivered one order. Its title reads "Head office and the store both delivered".
• One head-office invoice bills several orders. Its title reads "Head office's invoice of several orders".
• The store changed or canceled an order Acumatica already shipped.

What to do. Line 1 of the record is the one thing to do. The lines below it are the account, and the last line usually says what Keep iVendNext Version does on this record. Do what line 1 says, then press Keep. Some records also offer Re-check, which reads the order again.

Where head office cut an order so that the customer is owed money back, the cut is applied, and the Hub's Differences lists the amount. Pay it back with Pay back at the till, not with a desk Pay entry. Where line 1 asks you to cancel the store's invoice, do that before anything else it names. Never void a delivery's invoice in Acumatica, because its shipment is confirmed.

When to call support. You cannot do what line 1 says, or a refund still waits one run after both records are kept.

The financial period is inactive

What you see. A sale reads Failed: "Acumatica refused … its financial period is not open there". A bell may have rung before this, because the hourly check warns when today, or the date 31 days ahead, falls in no open period.

What it means. Acumatica refuses every document dated in a period that is not open. Nothing was created there.

What to do. In Acumatica, a person with ledger rights opens the period on Manage Financial Periods (GL503000). That screen opens the shared calendar for every company in the tenant. Then press Retry on each Failed record, and read the record again. It must say Applied with an Acumatica number.

A Closed period does not stop a user allowed to post to closed periods, so a back-dated document can post there. A Locked period refuses everyone.

When to call support. A record is still Failed after the period reads Open and you pressed Retry.

A document is waiting to be released

What you see. A sale reads Unverified, and its sentence says a document exists in Acumatica and is not released. It ends: release it in Acumatica and the record closes on the next run.

What it means. Acumatica has the document, but it never reached Open. For about a minute after a sale this is normal, and the connector does not ask anyone until about five minutes have passed.

What to do.

1. Read the row for an amount or currency warning. If it says the figures differ or could not be compared, do not release the document as it stands. Correct it in Acumatica first.
2. If the sentence names Credit Hold, take the invoice off Credit Hold in Acumatica first.
3. Release it. The record settles by itself on the next run, and nothing is sent again.

When to call support. The document stays unreleased after you release it, or the sentence says "DUPLICATE POST".

API Login Limit

What you see. Records stop moving, and Throttled Until on the Setting is filled in.

What it means. Acumatica's license allows only so many API users at once, and no seat was free. Every open Acumatica session takes a seat, including a person's browser. The connector backs off and tries again by itself. Nothing is lost.

What to do.

• Wait. Every record is tried again.
• Close Acumatica browser sessions nobody is using.
• Check whether a second connection is on against the same Acumatica. Never switch one on to share the load.
• Have the Acumatica administrator read License Monitoring Console (SM604000).

When to call support. It lasts more than an hour with nobody else on Acumatica.

A 403

What you see. An alert: "Acumatica: not running — it refused one of our requests".

What it means. Acumatica answered and would not allow one particular request. The sign-in worked, so this is not a password problem. Nothing is delivered while it stands, because the connector reads Acumatica before it sends.

What to do. The alert ends with Acumatica's own answer, which usually names the screen. The Acumatica administrator then checks three things: the license covers that module, the integration user's rights cover that screen, and nothing in front of Acumatica blocks the connector's address. Do not change the password. Do not give the user more rights than that one screen needs.

When to call support. Acumatica's answer names a screen you cannot identify, or the problem stays after those three checks.

Acumatica refused a sale for stock

What you see. A sale reads Failed: "Acumatica refused this sale for stock". Nothing was created in Acumatica.

What it means. The sale would take an item below zero in its Acumatica warehouse. The two systems' stock differ, or that item may not go negative. This record does not retry by itself, because a receipt can take days.

What to do. Get the stock into Acumatica with a receipt. Then press Retry on the sale's record, or use Retry selected on the Integration Activity list for several records.

If the first line names a lot, receive or correct that lot in Acumatica first. If it says to make a customer Active, do that on Customers (AR303000), then press Retry.

When to call support. The same refusal returns after you fixed what it named. Send the document number and the time.

A sale waits for a tax template, or a tax difference shows

What you see. A sale waits with "Add a row for … to the Setting's Tax Zone Mapping". Or a row on the mapping shows a ⚠. Or the Hub's Differences reads "Tax Total differs".

What it means. A sale waiting for a row is not lost. A ⚠ on a row says what the two sides differ on. A row on Differences means the sale reached Acumatica and its money is taken, so nothing is waiting. iVendNext has what the till charged, and Acumatica has what it keeps.

What to do.

• Add the row. If it exists, read its Check. The sale goes by itself on the next run.
• On a ⚠ about rates, correct whichever rate is wrong. Tonight's check clears the ⚠.
• On a ⚠ about a tax category, add a category in Acumatica that contains those taxes.
• On a difference, settle it in Acumatica as you would any open balance, then press Mark resolved.

When to call support. The difference has no cause you can find.

A cent of difference

What you see. The till's total and Acumatica's Amount differ by a few cents, or the two tax figures differ by a cent, or a balance of 0.01 stays open on the customer.

What it means. A till document carries the till's own tax, so rounding leaves no cent on it. A desk, web or delivered invoice is different, because Acumatica taxes it. Each side may round a tie its own way, and iVendNext works tax out per line while Acumatica adds it on top. A store that rounds its cash totals also collects a different total from what Acumatica bills.

What to do. Set iVendNext's Rounding Method to the one Acumatica uses. Read tax from Acumatica, not from the till's closing. Ask whether Acumatica writes small balances off. Do not edit a document to remove a cent. The connector never writes one off, so your finance team clears small balances in Acumatica with its own write-off.

When to call support. A difference larger than 0.05, on a sale with no cash rounding, that no "Tax Total differs" row explains.

A price differs from Acumatica's

What you see. A price at the till is not the price on Acumatica's Sales Prices screen.

What it means. Check these in order.

1. The price has not arrived yet. Prices arrive overnight, unless you chose faster. The Prices from Acumatica notice says when the last pass ran.
2. The store does not point at the connector's list. Read the row Stores read the Acumatica price list, then set the warehouse's Selling Price List.
3. Acumatica's price is net, and an inclusive till sells it as gross. This is a question about shelf pricing, not a fault.
4. A customer's own price list overrides the till's.
5. A withdrawn price stays live while any price row cannot be mapped.
6. The item has no price row for its unit. Those rows are counted and named.

What to do. Fix the first cause that fits. Two nightly Error Log rows titled "acumatica price refresh" are the pass's reports. A title that says it did not complete, or could not run, is a failure.

When to call support. The price is still wrong the next morning, and the store points at the list.

A movement waits for its warehouse's start

What you see. A receipt, issue or transfer released in Acumatica reads Waiting: the warehouse "has not been started", or it "is marked to start". A head-office shipment from that warehouse waits the same way.

What it means. Nothing is lost. A warehouse's stock starts once, when a person ticks Start Stock. The next nightly pass copies Acumatica's on-hand at one moment. After that, only later movements apply. A movement released before that moment is already in the copied figure, so it reads Skipped the next morning.

What to do. Tick Start Stock on the warehouse's row the evening it goes live. Do not record the movement by hand. Ring no sale there before the count.

When to call support. The warehouse has had its count, and a new movement still does not arrive.

A movement waits about a lot

What you see. An Acumatica receipt, issue, transfer or adjustment of an item iVendNext tracks by batch or serial number reads Waiting, and its sentence names a lot or serial number. Or it reads Needs a decision.

What it means. The number is not in iVendNext yet, or the connector's user may not make it. On a decision, the numbers do not add up or are missing.

What to do. A waiting record clears by itself once the batch arrives, is created in iVendNext with its expiry, or the application user is given Item Manager. Never record that movement by hand, or it moves twice. On a decision, record the movement in iVendNext by hand, naming the numbers, then press Keep iVendNext Version.

When to call support. The record still waits after the batch exists and the role is granted.

A store did not get Acumatica's stock

What you see. On the differences list: "Store … has never had Acumatica's stock for warehouse … copied".

What it means. iVendNext moved stock at the store before its first count, so the connector copied nothing. A level written over those movements would erase them. A store whose level is right needs nothing, so resolve the row.

What to do. Do a manual Opening Stock count, for one store, in one sitting.

1. Choose a quiet moment, with no till open at the store. Wait for the connection's next run.
2. Settle any waiting or failed sale of that store. Note any Acumatica movement still waiting there.
3. Read Acumatica's on-hand for the warehouse on Inventory Summary (IN401000).
4. At once, post a Stock Reconciliation of purpose Opening Stock for the warehouse, with the Temporary (opening) account as the difference account. Count lot by lot for a tracked item. For an item a waiting movement moves, add what it takes out, or subtract what it brings in. Never use the purpose Stock Reconciliation, because that one is sent to Acumatica as a count.
5. Resolve the difference row.

An Opening Stock entry is never sent to Acumatica.

When to call support. The figures still differ after the count.

A new customer's sales are waiting

What you see. A customer made at the till or arriving from the web reads Waiting, and every sale to that customer waits behind it. Its record says the customer has no Customer Group, or that the group has no row.

What it means. A customer is sent to Acumatica only if its group has a row in Customer Class Mapping. This is on purpose.

What to do. Set the group. A cashier can do this at the till under Edit customer, More details. Set Selling Settings, default customer group, and add the Customer Class Mapping row.

A customer that already exists in Acumatica must be linked by hand from Record Links, Link manually. If the record says its key is already an Acumatica customer that is not this one, either link it, or tick Retired on the key row. The connector then makes a new key.

When to call support. The customer still waits after the group has its row.

A cancel is refused

What you see. You press Cancel on a document, and iVendNext refuses with a message titled Kept in Acumatica. Line 1 says what to do instead, such as "Make a return of POS Invoice … at the till instead: the return reaches Acumatica as a credit memo."

What it means. Acumatica has the document, and a cancel in iVendNext never reaches it. Acumatica would keep the sale, payment or stock move that iVendNext had reversed.

What to do. Make the correction line 1 names. If a line says the correction is not sent to Acumatica, correct it there by hand as well.

If line 1 says to press Not recorded in Acumatica, a person kept that document earlier. Reverse anything recorded in Acumatica first, then press that button on the record, and the cancel goes ahead.

A POS Closing Entry may still be canceled and run again. That day's invoices stay in Acumatica.

When to call support. The cancel is refused for a document you are sure never reached Acumatica.

An item cannot be returned

What you see. The till refuses the return and calls the item "non-returnable".

What it means. Items arrive from Acumatica not returnable, unless you set the default before the first poll.

What to do. Tick Returnable on the item. For later items, set Returnable and Return Days in Customize Form, on Item.

When to call support. The till still refuses after the tick. The till keeps its own copy of the item, so check again after it refreshes.

The connection switched itself off

What you see. Connections reads Switched off, and nobody pressed it. The Integration Manager's bell rang once when it happened, and no email goes out. Records arriving meanwhile wait.

What it means. An upgrade registered the connection again, and Integration Core refused. The usual cause is an Integration Core release older than the connector expects.

What to do. Compare the two releases. If Integration Core is older, upgrade it first. Then press Register Connection on the Setting and Switch on in Integration Core.

When to call support. You cannot tell the cause, or the releases match and it stays off.

Sign-in refused, or Acumatica cannot be reached

What you see. The Connections list reads "Sign-in refused by Acumatica" or "Cannot reach Acumatica", with how long it has lasted. Records are Set aside, not failed.

What it means. A refused sign-in means Acumatica refused the password. It may have been changed or have expired, or the user may be disabled. Cannot reach means Acumatica did not answer. If the customer upgraded Acumatica, the endpoint must still be published at 24.200.001 or later.

What to do. For a refused sign-in, ask a System Manager to enter the new password on the Setting. For Cannot reach, ask the Acumatica owner, and check the Base URL. Work starts again by itself.

When to call support. It stays after the sign-in is renewed and Acumatica is up.

Nothing is arriving

What you see. No record has crossed.

What it means. Work down this list, and stop at the first that is true.

1. The connection is off. Look on Connections.
2. It reads Not reported yet. The connector's scheduled jobs have not run. Ask whoever hosts the site to check the three scheduled jobs.
3. An alert is open. See API Login Limit, A 403 or The financial period is inactive.
4. The record predates Cut Over At. Nothing already in Acumatica loads unless that date was set back first.
5. A flow is switched off. Look at Flows on the Setting.

What to do. Fix the first one that is true.

When to call support. All five are clear, and nothing has crossed in an hour.