Acumatica

Every order in Acumatica, without the keying

Your customers send POs as PDFs and emails, and someone finds the customer and location in Acumatica, picks the branch location, keys every service and part and checks the account before saving. Zaqa prepares every order that way, against your live Acumatica data, and your team approves each one before it goes in.

Not on Acumatica? See the ERPs Zaqa connects to

The builder's email

purchasing@masonridgehomes.com

PO 77-0142, Oakview Lot 42

Hi, PO attached for the garage door install at Oakview, Lot 42. Please schedule for the week of the 17th. Thanks!

PO-77-0142.pdf

Service order for Acumatica, 6 lines

1 to review
  • Ready: Customer and locationMason Ridge Homes · Oakview, Lot 42Matched to the customer and its location in Acumatica. The PO carried neither ID.
  • Ready: Branch location, order type, customer order, dateNORTH · Install · PO 77-0142 · Requested week of Nov 17Branch location from the customer location, the PO number and date as written. Acumatica numbers the order.
  • Ready: Checked live, just before savingCustomer active, location active, all items saleableRead from Acumatica a moment before the write, not from last night's copy.

Lines

  • Matched: Install garage door + openerINSTALL (service)1 EA
  • Matched: 16x7 insulated steel door, whiteGD-1607-INS-WH1 EA
  • Needs review: 1/2 HP belt opener2 possible items, flagged for your team1 EA
  • Matched: Vinyl trim kit, whiteTRIM-16-WH1 EA
  • Matched: Wireless keypadKP-WL-011 EA
  • Matched: RemotesRM-3BTN2 EA

Prices come from Acumatica. Saved on hold until your team releases it.

Illustration with made-up names, codes and numbers: a builder's emailed PO, prepared as an Acumatica service order and waiting for your team's approval.
Door Pro America

Built with Door Pro America, which runs its installation business on Acumatica Field Service, from builders' purchase orders to service orders.

The details

What Acumatica expects, and Zaqa delivers

Checked live, just before it's written

A moment before saving, Zaqa reads the customer, the location and every item from Acumatica again: still active, not on credit hold, still saleable. An order is never built on yesterday's data.

Customer, location and branch

A PO rarely carries your customer or location IDs. Zaqa finds them in Acumatica the way your team would, takes the branch from the location, and shows your team the likely matches when two accounts look alike.

Every line, matched to your items

Stock items, non-stock items and services, matched from the customer's own description or part number, using the cross-references already in Acumatica, and converted to your unit of measure. A line that matches nothing is flagged for your team, never invented.

Prices stay Acumatica's

Acumatica prices each line from its own price rules, the same as an order your team enters. Sending the price from the PO instead is a choice you make, not a default.

Never entered twice

If an order with the same customer and PO number is already in Acumatica, Zaqa sends it to your team instead of creating a second one. A resend of an order Zaqa already entered is recognized, and a resend with changes goes to your team as a change.

Through the API, nothing installed

Zaqa uses Acumatica's own REST API with a dedicated API user that can do only what order entry needs. No customization package, no screen automation, nothing to maintain inside Acumatica.

FAQ

Acumatica questions

No. Zaqa connects through Acumatica's standard REST API, so there's nothing to publish in your instance and nothing to re-test when you apply a customization of your own.
Field Service service orders, in the service order type your team uses today, with the customer's PO number in the customer order field. Acumatica assigns the order number itself.
Zaqa uses a small, fixed number of API sessions, set below your licence's limit so your other integrations keep their share. When Acumatica answers that it's busy, Zaqa waits and tries again instead of failing the order.
Two ways. To prepare an order quickly, Zaqa works from a synced copy of your items, cross-references, customers and locations, refreshed through the day and reconciled every night. Then, just before saving, it checks that order's customer, location and items against Acumatica live. Acumatica stays your system of record.
Zaqa uses the API version your site runs, set for your site. When you upgrade, the connection moves to the new version with you.
The order comes back to your team in Zaqa with a clear reason, such as an inactive item or a missing field, to fix and send again. Temporary problems, like Acumatica being busy, are retried on their own.
Yes. Your team reviews each order beside the email and attachments it came from, with anything uncertain flagged, and nothing reaches Acumatica before a person approves it. Orders are saved on hold by default, so your team releases them as it does today.
Orders and reference data are encrypted in transit and at rest, kept separate from every other customer's data, and never used to train models for other customers. Zaqa's API user has only the permissions order entry needs, and you can revoke it at any time. How Zaqa protects your data

See your orders go into Acumatica

Bring a few real POs and we'll show you what Zaqa reads from each one and exactly what it would enter in Acumatica.