Start with a definition of done

Choose one operation with a visible finish line

Start with an operation whose result can be checked in the system that owns the work. The staging pilot creates one draft from supported USD invoice text after checking its source fields, arithmetic, existing supplier, and spending limit, then confirms the saved record through read-back.

List the actions that are excluded. A draft bill does not imply accounting posting, approval, or payment. This distinction determines which credentials are needed, which checks are mandatory, and what a receipt may truthfully report.

Map the evidence before the model

1. Identify the source document and the authoritative records needed to verify it. An extracted supplier name is a candidate; the supplier master provides the identity.
2. Define required fields, permitted currencies, rounding rules, and matching tolerances. Record who owns those policies and how changes should be versioned.
3. Specify the smallest permitted write and the query that can confirm it. Check whether the destination supports an operation identifier or a unique external reference.
4. Choose the treatment of missing evidence. A missing receipt, ambiguous supplier, or unsupported document should produce an explainable unresolved result.

Identify the task, input, and connection

The pilot uses contract invoice.create_draft@1.0.0 with connection_id erpai-staging. Its input contains document_text, the provisioned 24-character lowercase hexadecimal supplier_id, currency USD, and max_total_minor in cents.

Send a provisioned key in the Authorization: Bearer header and a stable Idempotency-Key header. The API reference provides the exact invoice text format, request body, curl examples, limits, and response fields. Start there when preparing a runnable request.

Design the difficult cases first

A useful pilot includes a valid invoice, an arithmetic mismatch, an inactive supplier, concurrent duplicate submissions, and a lost response after a successful write. Evaluate the resulting record, status, evidence, and model usage independently. A happy-path screenshot cannot establish safe retry behavior.

Before connecting a destination, agree the authentication method, permitted operations, data policy, limits, and commercial terms. Exercise the workflow with synthetic fixtures first, including cases that fail before a write and cases that require reconciliation afterward.