Connect your own landscape
IT and integration teams linking Finance & Operations to CRM, e-commerce, WMS and 3PL, PIM, BI and document systems, without waiting on scarce X++ developers for every new connection.
Who it's for
Built for the people who connect Dynamics.
Deliver projects, not plumbing
Systems integrators who build and run customer integrations, and would rather spend the budget on the business outcome than on rebuilding the same services and entities for every client.
Embed F&O access in your product
Software vendors whose products read from or write to Finance & Operations, who need a stable, documented surface that stays put across Microsoft's releases.
Use cases
Customers and sales
◆Real-time CRM customer sync
A new or changed customer is pushed to the CRM the moment it commits, and a credit hold flags the account and alerts the sales owner, so nobody quotes a customer who can no longer buy. The CRM's own account id travels with each event, so its connector never has to look one up.
Business eventsCross-reference keys
◆Online orders straight into Dynamics
The storefront creates sales orders using its own order numbers. Lines priced outside tolerance are held for review, clean orders confirm themselves, and confirmed orders are locked against edits for a set time. Stock and catalog flow back out through lean, change-tracked feeds, and a back-in-stock event tells the shop the moment an item can sell again.
Integration operationsCross-reference keysData entitiesBusiness events
◆Credit and collections escalation
An exceeded credit limit alerts the credit controller with the full exposure before an order is released, and dunning, collection letter and collection case events drive the follow-up cadence in a collections tool, without nightly extracts.
Business events
Use cases
Supply chain and manufacturing
◆Shipping notices and carrier handoff
When a load ships, the event carries the shipment and carrier, and an Azure function builds the advance ship notice and tells the carrier and the customer. Transfer order shipments feed the same flow, so the receiving warehouse sees stock in transit straight away.
Business events
◆Warehouse and 3PL stock sync
The external warehouse reads on-hand stock as an incremental feed and hears about every change as it happens. Counts, adjustments and transfers come back as posted inventory journals, and receipts and shipments as posted transfer orders, each safe to retry.
Data entitiesBusiness eventsIntegration operations
◆Manufacturing execution handshake
The production lifecycle is mirrored into the MES without polling: scheduled and started orders trigger material staging, and report-as-finished quantities update yield and available-to-promise. In the other direction the MES starts orders, posts picking lists and route cards, and reports output through the production services.
Business eventsIntegration operations
◆Quality holds and stock release
A passed quality order releases held stock and records the result in the quality system. A failed one opens a non-conformance workflow and keeps the affected quantity from shipping, closing the inspection loop in real time.
Business events
Use cases
Finance
◆Journals from other finance systems, exactly once
External platforms post general ledger journals through one service. Each request is previewed first if you like, then posted with its own request id, so a timeout, a redelivered message or a rerun can never post the same journal twice, and a sweep resolves anything a crash interrupted.
Integration operationsOperations
◆Payments posted and settled automatically
Customer receipts and vendor payments from a payment platform are posted as payment journals and settled against open invoices through the payment services. Vendor payment proposals can be generated on demand, and bank reconciliation and vendor payment events tell treasury what has cleared.
Integration operationsBusiness events
◆An event-driven period close
Each posting streams to a reporting ledger as it happens, and inventory closing completed acts as the gate that starts the next set of close tasks in an orchestration tool, turning a manual checklist into a pipeline. Ledger entries, the trial balance and settlements are ready to read as entities.
Business eventsData entities
Use cases
Data and platform
◆Partner files to posted documents
A partner drops order or journal files on SFTP or Azure storage. Lattice pulls each one, skips duplicates, reshapes every record with a Liquid template and posts it through the matching service. A record that fails lands in the dead-letter queue to be fixed and resubmitted, never re-keyed.
File ingestionIntegration operationsOperations
◆Analytics without the hand-built layer
Finance, inventory, order and warehouse data reach the data platform through ready-made entities, exported incrementally where volume demands it. A data management completed event tells the pipeline the moment an export has finished, instead of a timer guessing.
Data entitiesBusiness events
◆Attachments by business key
The document system files invoices, receipts, certificates and drawings against the right order, invoice, production order or quality order using keys it already holds, including on posted documents, and reads them back the same way.
Data entities
◆A governed API front door
The APIM configurator turns the services you choose into a deployable API Management bundle, with JWT validation, rate limits, IP restrictions and logging policies already set, so partners get a managed, documented gateway instead of direct access.
Integration operationsOperations
Try it
Prove your use case in a sandbox.
Every use case on this page runs on the one Lattice package. Install it free in any non-production environment, wire up the connection you care about first, and subscribe only when it goes to production.