Reported operating use · Technology distribution
AI purchase order processing: StarLink example
StarLink, part of Infinigate Group, reports using IBM Bob and watsonx Orchestrate agents for purchase order intake, quote comparison and accounts payable coordination, connected to Oracle NetSuite, Docling and Automation Anywhere. It describes this as internal Client Zero use. Annual hours saved and partner rollout are projections.
Purchase order intake, quote comparison and accounts payable coordination
StarLink (Infinigate Group)
Client Zero internal operational implementation; wider partner rollout prospective.
A published third-party example, not a Nuvepro customer case or evidence of a partnership.
The workflow at a glance
StarLink (Infinigate Group) reported work
Illustrative summary of the published account
Reported work components. Their arrangement does not imply a fixed execution order or simultaneous work.
- Internal procurement
StarLink operated agents
Client Zero use is reported in its own workflows.
- Connected tools
NetSuite, Docling and Automation Anywhere
The solution links ERP and document-processing tools.
- Work covered
Orders, quotes and AP coordination
Document comparison supports procurement coordination.
What the source reports
The procurement solution connects Oracle NetSuite, Docling and Automation Anywhere. StarLink says it has developed and operated these agents in its own workflows. It reports shorter document comparison and agent implementation cycles. Annual hours saved and extension to partners remain projections.
Reported technology: IBM Bob / watsonx Orchestrate. Scope and outcomes are source-reported.
What the enterprise environment would need
The following is a proposed project design for an enterprise doing similar work. Published details are marked; the remaining systems, data and scenarios would be agreed for your project.
Proposed practice environment
Reconcile a purchase order, quote and AP record
Illustrative project design to scope with your enterprise.
- 1 · Set up the environment
Procurement transaction bundle
Fictional vendor quotes, customer orders, attachments and AP state share identifiers.
- 2 · Preparation and agent contributions
Prepare cross-record comparison
Parse documents, identify mismatches and draft allowed ERP changes.
- 3 · Independent checks
Reconcile commercial evidence
Independent checks verify amounts, IDs, tolerances and approval segregation.
- 4 · People decide acceptance
Procurement and AP owners
Resolve missing records and commercial exceptions before accepting practice scope.
A reviewable evidence package
A reconciled order/quote/AP packet with unresolved exceptions.
If a check fails → withhold acceptance.
Plausible documents carry conflicting identifiers or a duplicate purchase request. Withhold acceptance, repair, independently recheck and return to owner review.
Failure or owner rejection returns to review
- Hold
- → 2 · Revise work
- → 3 · Rerun independent checks
- → 4 · Owner review
Operating boundary. ERP sandbox only; no live order, supplier change, downstream payment or assumed partner rollout.
- Systems and tools
- Inferred test scope: ERP test tenant, document parser and controlled email intake.
- Data and state
- Inferred test scope: Vendor quote, customer order, internal record and AP status must reconcile.
- People and handoffs
- Inferred test scope: Sales and AP verify completeness and resolve commercial exceptions.
- Rules and authority
- Inferred test scope: Match tolerances, approval limits and segregation of duties.
- Normal and exception cases
- Proposed test cases: Missing attachment, quote mismatch, duplicate PO, unauthorized supplier change.
- Reset and replay
- Not reported. Proposed: Seed a transaction bundle and restore ledgers; replay without actual payment.
A proposed simulation
An illustrative practice design derived from this work, not an executed assessment.
Reconcile a vendor quote, customer order and AP record; handle a missing attachment, mismatch and repeated purchase request.
Review gate: Verify commercial amounts, identifiers, tolerances, approval segregation and downstream record consistency.
Challenge the result: Introduce individually plausible documents with mismatched identifiers. The assessor must catch cross-record inconsistency before downstream approval.
What needs checking
- Proposed: reconcile order/quote/document fields and inspect permitted ERP changes.
- Proposed: ensure incomplete or mismatched orders route to the right owner.
- Proposed: procurement/AP owners validate real tolerances and exception authority.
Review environment fidelity, human capability and agent performance separately. The enterprise’s accountable owners decide acceptance of the shared workflow and any operating use.
How an enterprise could build similar work
A proposed build order for an enterprise doing similar work, written by Nuvepro from the published account and our interpretation of the environment and checks above. It is not how StarLink (Infinigate Group) built or operates this work.
- Frame a proposed test projectThis is a proposed design for a similar project, not a description of how StarLink built its agents. The mission is to reconcile a vendor quote, customer order and AP record, handling a missing attachment, a mismatch and a repeated purchase request.
- Assemble the test systemsUse an ERP test tenant, a document parser and controlled email intake. Vendor quote, customer order, internal record and AP status must all reconcile, so the test data should link these records together.
- Assign people and authoritySales and AP verify completeness and resolve commercial exceptions. Build in match tolerances, approval limits and segregation of duties, so the workflow cannot approve its own exceptions or push a downstream record past the people who own it.
- Write the exception casesInclude a missing attachment, a quote mismatch, a duplicate purchase order and an unauthorized supplier change. Add documents that look plausible individually but carry mismatched identifiers across records, so the assessor must catch cross-record inconsistency.
- Reconcile and routeReconcile order, quote and document fields, and inspect which ERP changes were permitted. Verify commercial amounts, identifiers and tolerances, and that incomplete or mismatched orders reach the right owner before downstream approval.
- Seed and replay safelyThe source does not report a reset design. Seed a transaction bundle, restore the ledgers between runs and replay without any actual payment. Procurement and AP owners then validate the real tolerances.
Your systems, data, rules and accountable owners decide the real project. Agree acceptance criteria, escalation owners and operating responsibility with the people accountable for the work before anything runs on live records. Treat the first run as a rehearsal on test records: compare the draft output with an independently prepared answer, and record what the people reviewing it change.
Questions about this example
- What does StarLink use AI for in procurement?
- StarLink says it developed and operated agents in its own workflows for purchase order intake, quote comparison and accounts payable coordination. The solution connects Oracle NetSuite, Docling and Automation Anywhere, using IBM Bob and watsonx Orchestrate. It reports shorter document comparison and agent implementation cycles.
- Who approves or checks the procurement agents' work?
- The source does not publish a full authority model, so who approves what is not described. Nuvepro proposes that sales and AP verify completeness and resolve commercial exceptions, with match tolerances, approval limits and segregation of duties. That is a suggested design, not StarLink's reported practice.
- How strong is the evidence for this example?
- Reported use, as an internal Client Zero implementation. Wider partner rollout is prospective, and annual hours saved remain projections. An independent end-to-end reconciliation evaluation, a full authority model and realized annual savings are not supplied.
- What would an enterprise need to build something similar?
- Nuvepro's proposed design, not StarLink's, would use an ERP test tenant, a document parser and controlled email intake. Vendor quote, customer order, internal record and AP status must reconcile. Checks inspect permitted ERP changes and routing, with procurement and AP owners validating real tolerances.
Shape this around your enterprise
Bring a similar workflow and the people responsible for it. Together, define the records and systems to use, the result your team will build or configure, and how its owners will check it. Nuvepro scopes the simulation, environment and preparation. Agree any existing-agent evaluation, implementation assistance and production responsibilities separately.
Sources and limitations
Curation review: . This is the date this source example was reviewed, separate from source publication dates.
- An independent end-to-end reconciliation evaluation, full authority model and realized annual savings are not supplied.
- StarLink streamlines procurement with agentic AI, leveraging IBM Bob and IBM watsonxSource publication: 2026-09-10
More finance and accounting examples
- AI AP exception resolution: Varick pattern by Eyad KhraisVarick AP pattern (customer unnamed)
- AI billing discrepancy review: Telstra exampleTelstra
- AI cash application: Varick pattern by Eyad KhraisVarick cash-application pattern (customer unnamed)
- AI restaurant cash reconciliation: Ted Taylor exampleTed Taylor, independent restaurant franchisee