For distributors running Sage 100
Know what your Sage 100 book can tell you before you quote.
PIE connects to the Sage 100 book you already run and reads the trading history in it: what each customer paid for each item, what they pay at this quantity, and which accounts have gone quiet. What Sage 100 does not hold is item-level purchase cost — so on this book PIE reports margin as unknown rather than estimating one, and says so on every screen that would have used it.
One sign-in, checked when you save it
A sign-in as a Sage 100 user with SData access, against the server your eBusiness/SData provider runs on, scoped to one three-character company code. The feed is Atom XML and PIE parses it with the standard library, by local name, so a provider namespace revision does not break the read. The connection is checked when you save it, so a wrong company code or password fails there rather than on the first nightly sync.
What your administrator does first
Granted on the Sage 100 user's role, at Library Master → Main → Role Maintenance: SData access — without it the credential is accepted and no resource is served — and inquiry rights on each module above. Both invoice-history resources are needed rather than one: headers alone import totals with nothing under them, which is a book with revenue and no lines. And because a Sage 100 SData provider usually sits on your own network, it 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 Sage 100 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.
- CustomersAR_Customer
- VendorsAP_Vendor
- The item masterCI_Item
- Invoice history, with its linesAR_InvoiceHistoryHeader · AR_InvoiceHistoryDetail
- Sales ordersSO_SalesOrderHeader
- Purchase ordersPO_PurchaseOrderHeader
PIE writes nothing to Sage 100
The Sage 100 connector is read-only: there is no method in it that creates anything, and the platform refuses to send a quote to a Sage 100 customer rather than pretending it can. A quote is built and approved in PIE and entered in Sage 100 by whoever enters them today.
What PIE does not read from Sage 100
- Purchase cost is not read, and this is the gap that decides what the platform can do for you here. Sage 100's AP invoice history records GL distributions, not item lines, so there is no per-item cost to read anywhere in the book. Margin, the margin floor, margin drift and everything derived from them are reported unknown on a Sage 100 book — not estimated from a list price, not defaulted to zero, and never quietly passed as within policy.
- Customer payments are not read from Sage 100, so payment timing, the collections worklist and days-to-pay have nothing to read on this book.
- Stock levels are not read from Sage 100 in this version, so the stock and GMROI screens stay empty on this book.
- Credit memos are not read from Sage 100 in this version, so a returned or credited line still counts as sold until you say otherwise.
- Quotes are not imported from any ERP, Sage 100 included, so a win rate has no denominator until you start quoting here.
- Vendor payments are not read from any ERP, so what has actually been paid out is outside what PIE can see on this book.
- 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.
What this customer has actually paid
The price references on a quote line — what this customer last paid for the item, what they pay at this quantity, what comparable customers pay — are arithmetic over invoice lines and need no cost at all, so they are on the screen on a Sage 100 book. The two references that are derived from cost are absent rather than approximated, and the line says which.
The accounts that went quiet
Decline is measured from the invoice history the first pull brings in: a customer's recent revenue against a comparable earlier window, with an activity floor and a minimum history so a quiet fortnight is not an alarm. It needs no cost and no payments, so it works on this book from the first sync.
Unknown, said out loud
Every screen that would have needed cost reports UNKNOWN and names what is missing. That is the product working, not failing: a platform that answered “within policy” because it found no cost would be worth less than nothing on a book like this one. If your item-level purchase cost lives somewhere Sage 100 does not — a second system, or an AP process that could record item lines — that is the conversation worth having before you connect.
Why it can be trusted
The AI never computes a single number.
Your Sage 100 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 Sage 100 book already knows what your customers pay.
30–45 minutes, your own numbers on the screen, and an honest answer about what PIE can and cannot see in Sage 100.