Use Acumatica

Connect Multiple Systems with an Acumatica Web Services Integration

One of the things we hear from customers is how much it has helped them to have integrated software. When multiple systems can “talk” it means people have fewer places to hunt for information. And customers already know that we love to ballyhoo about Acumatica’s prowess for integration.

The most common integration our customers do is with a data import. We call these “import scenarios”. For example, our customers start their Acumatica implementations with import scenarios. They allow you to import data to Acumatica via spreadsheets. For example, you may use them to migrate data from a legacy ERP system. They can also involve data manipulation and are quite powerful.

But what about when you’re ready for something real-time and no touch?

We can help with this “next level” option, too. How is this accomplished? By creating a Web Service integration between Acumatica and your other business systems.

In 2020 alone, DataQuest helped four different customers develop an Acumatica Web Services Integration with these system types:

  • Mobile Notary Signing: This integration sends Vendor records, AP Bills, and AR invoices to Acumatica for aging, management, and payment
  • Point of Sale: This integration sends General Ledger Journal Entries to Acumatica to summarize transactions from daily operations.
  • Service Management: This integration includes bi-directional data sharing with Acumatica. Data includes Customers, Location, Projects, Purchase Orders, Purchase Receipts, and AP Bills.
  • Transportation Management: In this integration, we share data with Acumatica related to Customers, AR Invoices, AR Payments, Vendors, AP Bills, and AP Payments

Sounding good but asking yourself what this all means?

What is a Web Services Integration? Is it right for you?

A web services integration is a way to share information through an Application Programming Interface (API). The API is like a formal business entrance. It allows Acumatica to connect with other business systems. Through these connections, the systems can talk. Furthermore, they can talk without you having to initiate the conversation.

Think of it as a door at one end of a hallway. The hallway allows Acumatica to accept information. It also allows Acumatica to send information. You design the hallway with your own rules around what can be shared.

Acumatica has a robust and flexible API. Other modern business systems have similar web APIs. And if they don’t have them already, they are scrambling to create them. As a result, they can communicate with leading-edge solutions like Acumatica.

So – building a successful integration is something we do together.

DataQuest helps by putting on our hardhats, toolbelts, and steel-toed boots. We suit up to build that hallway. And we build it not just to connect the doors. We furnish the hallway, light it properly, and build navigation.

For example: Do you just want one door at the opposite end of the hallway? Or are there others along the way? Should the information flow only into Acumatica? Or should we just extract information? Should it flow in both directions? What information should be shared? And how frequently should it happen?

How do you know if you are ready for an Acumatica Web Services integration?

Ask yourself:
• Would you like your business systems to share information with your ERP system?
• Would you like this information sharing to happen automatically?
• Do your other business systems already have a web API?

If yes, yes, and yes … then you are ready to explore a Web Services Hallway of Results. Contact us to get started with the conversation.