For distributors running Acumatica
Stop quoting away your margin on Acumatica.
PIE connects to the Acumatica book you already run, reads the trading history in it, and checks every new quote line against your own margin floor before it goes out — then reports the margin that held. Your ERP keeps the records; PIE decides nothing you did not set a policy for.
One sign-in, checked when you save it
A session sign-in as a dedicated integration user against the contract-based REST API, from your site URL, the tenant's login name and — if you use them — a branch and an endpoint version. A connection check and a quote write each sign out the moment they finish — Acumatica counts live sessions against your licence, and a leaked session is a seat you are paying for and nobody is sitting in.
What your administrator does first
The rights are granted on the integration user's role, at User Security → Access Rights by Role, and one of them is easy to miss: Web Service Endpoints → Default, without which the sign-in succeeds and every request comes back 403. Sales Orders (SO301000) with Insert is what allows a quote to be sent and is optional — View Only is enough for everything else. A self-hosted Acumatica has to be reachable on a public hostname: PIE refuses a source address that resolves inside a private range, when you save it and again on every fetch.
What the first pull reads
The first pull is offered from the first day of the month 18 months back, and you choose the date before it starts. It runs as a background job that commits as it goes, so you can watch it move rather than wait on a spinner — and what the screens then report is the span the rows actually cover, not the window that was asked for.
Exactly this, and nothing else
The list below is not a summary of the integration — it is the integration. Each line is a permission the Acumatica connector declares and a method that reads it, and a test holds the two against each other in both directions, so a capability cannot be claimed here and missing in the code.
- CustomersCustomer
- VendorsVendor
- Stock items, with quantity on hand and availableStockItem
- Sales invoices, with their linesSalesInvoice
- Bills, with their linesBill
- Payments, with the documents they apply toPayment
- Sales ordersSalesOrder
- Purchase ordersPurchaseOrder
What PIE creates in Acumatica
A quote built in PIE can be created in Acumatica as a sales quote — a sales order of type QT — and that is the only thing PIE ever creates in Acumatica. Acumatica's PUT always inserts, so it is not idempotent on its own; PIE reads the reference back before it sends, so a second press cannot make a second quote. It refuses rather than guessing: no customer, no priced lines, or a line with no price or quantity, and nothing is sent.
What PIE does not read from Acumatica
- Quotes already in Acumatica are not imported — no ERP's are — so a win rate has no denominator until you start quoting here.
- Vendor payments are not read from any ERP, Acumatica included, so what has actually been paid out is outside what PIE can see on this book.
- Credit notes are not read from Acumatica in this version, so a returned or credited line still counts as sold until you say otherwise.
- Salespeople are not imported, so every decision routes to management until accounts are assigned inside PIE.
Three things, on your own numbers
Every figure is deterministic arithmetic over the rows above, stamped with the version of the margin policy that judged it. The AI on this platform reads those numbers and phrases them; it never produces one.
Every quote line, against your own floor
Cost comes off the stock item's own last and average cost and off your bills. PIE checks each new line against the policy you set, routes a breach for sign-off, and — where the grant allows it — creates the agreed quote back in Acumatica as a QT sales order.
Margin drift, with stock in the picture
Acumatica is the connector that gives PIE quantity on hand and available outright, alongside line-level history, so what a line returns on the cash it ties up is computable rather than absent — and every figure carries the policy version that judged it. Business Central reports stock only where its API version does; the rest report none at all.
Decline, and who actually pays late
Payments come with the documents they apply to, so days-to-pay is measured rather than approximated on an Acumatica book, and quiet decline is on the attention list from the first sync.
Why it can be trusted
The AI never computes a single number.
Your Acumatica data and your rules determine the number. AI explains it.
Same inputs, same answer, every time — with a paper trail.
- Deterministic calculations — every figure is arithmetic on your own records; turn AI off and every number still works
- Auditable decisions — each number names the policy that produced it, so a price you quoted last quarter still explains itself
- Your data — read from your own books, used for you alone, exportable and erasable on request; AI runs on your own account
- Your rules — you set the floors and thresholds, and PIE holds every quote to them
- Provenance — every row carries the connector, the connection and the id it came from, so nothing in PIE claims a source it did not have
Your Acumatica book already knows where the margin went.
30–45 minutes, your own numbers on the screen, and an honest answer about what PIE can and cannot see in Acumatica.