Sage Intacct with DigiOS.
Each client's statement becomes an invoice in Sage Intacct, and where you run order entry and inventory control, orders and stock move with it.
What moves each way
- Customers: Out of DigiOS
- Invoices: Out of DigiOS
- Order entry documents: Into DigiOS
- Shipments: Out of DigiOS
- Stock changes: Out of DigiOS
| What | Direction | Documents and data | When |
|---|---|---|---|
| Customers | Out | A customer for each client, created or matched before its first invoice | Before a client's first invoice |
| Invoices | Out | One A/R invoice per client statement, with each charge as a line | When a statement is issued |
| Order entry documents | In | Sales order transactions (SODOCUMENT) with lines, customers and warehouses, where you use order entry | On a schedule you set |
| Shipments | Out | Shipper documents against sales orders, with shipped quantities | When the shipment closes on the floor |
| Stock changes | Out | Inventory transactions and warehouse transfers, where you use inventory control | When a count or a move is approved |
On your floor
Orders and item lists in. Receipts and stock levels out.
RESTLast exchange 10:40Charges for the work out, to be invoiced.
RESTLast exchange 10:15Orders in. Shipment confirmations and stock levels out.
RESTWebhooksLast exchange 10:41Orders in. Shipment confirmations out.
RESTLast exchange 10:39Labels and pickup bookings out. Tracking numbers back.
RESTLast exchange 10:42Labels and pickup bookings out. Tracking numbers back.
RESTLast exchange 10:36Purchase orders and advance notices in. Shipment notices out.
X12 850, 856, 945AS2Last exchange 09:58The 09:58 purchase order (850) was turned back: ship-to code 4471 is not in your list of retailer stores.
Sam can actOpen the orderJobs out to each handheld. Scans back. Labels printed in ZPL.
ZPLLast exchange 10:42Scale weights and line signals in. Sort instructions out.
EtherNet/IPOPC UALast exchange 10:42How DigiOS works with Sage Intacct
DigiOS connects through the Sage Intacct web services, signed in with a web services user and sender credentials issued for your company. Which documents move depends on which modules you run: accounting alone, or order entry and inventory control too.
- Where it stands
- Planned1 Nov 2026
- About Sage Intacct
- Sage Intacct is a cloud financial management system with modules for accounting, order entry and inventory control.
- Your account
- You keep your Sage Intacct account and its licenses. DigiOS signs in with the integration access you give it, and you can take that access away at any time.
- If a document is rejected
- A document Sage Intacct refuses, such as an unknown item or a closed period, goes to one queue with Sage Intacct's own message. Fix it there or in the mapping and send it again. It never makes a second document.
What posts to your books
- What posts
- Customers and A/R invoices, and order entry and inventory documents where you run those modules.
- At what grain
- One invoice per client statement, with each charge as a line.
- How a charge becomes a GL line
- Each kind of charge is mapped to a GL account and your dimensions, with the client, during onboarding.
Questions about Sage Intacct
We only use Sage Intacct for accounting. Is that enough?
Yes. Then DigiOS sends customers and invoices, and orders come from wherever you take them today.
Does DigiOS use the XML or the REST API?
Whichever Sage Intacct supports for the objects we need. We tell you which in the mapping sheet.
Can we use more than one entity?
Yes. Each client statement goes to the entity you choose, and the mapping sheet lists each one.
Related systems
Ask about Sage Intacct.
Tell us what you run and what you want Sage Intacct to do. A person answers in writing.