Commercial invoice landed cost inputs
For Import cost accounting teams
Prepare goods, stated origin, incoterm, freight and item values from a commercial invoice with fields you can edit. Duty and landed-cost calculation external.
25 free credits/month · No card needed
See the workflow and review checksInspect a document example.
Synthetic documents · Expected output- supplier name
- Example Supply Company - synthetic
- buyer name
- Example Buyer - synthetic
- invoice reference
- DEMO-INVOICE-0042
- invoice date
- 2026-09-30
- currency code
- USD
- incoterm
- FCA - as stated
- item rows
- [ { "item_reference": "DEMO-ITEM-0042", "description": "Example document line - original synthetic data", "quantity": 1, "unit_of_measure": "each", "stated_origin": "US - as stated", "unit_price": 1250, "line_total": 1250 } ]
- freight amount
- 0
- stated total
- 1250
{
"supplier_name": "Example Supply Company - synthetic",
"buyer_name": "Example Buyer - synthetic",
"invoice_reference": "DEMO-INVOICE-0042",
"invoice_date": "2026-09-30",
"currency_code": "USD",
"incoterm": "FCA - as stated",
"item_rows": [
{
"item_reference": "DEMO-ITEM-0042",
"description": "Example document line - original synthetic data",
"quantity": 1,
"unit_of_measure": "each",
"stated_origin": "US - as stated",
"unit_price": 1250,
"line_total": 1250
}
],
"freight_amount": 0,
"stated_total": 1250
}A complete synthetic document with the visible values shown below. Real responses also include model-reported confidence, validation and result status. Test your own file with this schema.
When this work lands on your desk
A commercial invoice arrives for import cost accounting teams. The next step needs goods, stated origin, incoterm, freight and item values, recorded under the correct document reference before the information enters your shipment or billing review system.
An invoice states a country of dispatch separately from origin. Keep the stated origin for each line and leave tariff and duty decisions downstream. This schema keeps the source labels and values explicit so the reviewer can resolve the issue before downstream use.
Start with the documents you already collect
- Commercial invoice PDFs
- Scanned or photographed commercial invoice pages
PDF, JPEG, PNG, TIFF, or WEBP. Send one file per extraction call; create separate schemas when the document types need different fields.
Define the fields
Open the starter schema. Edit field descriptions, mark the values your process requires, and save it in your account.
Extract at intake
Send the document and saved schema slug to
POST /api/v1/extract, or collect the file through a branded upload site.Hand off reviewed data
After checking supplier name, buyer name, invoice reference, your application maps the reviewed record into your shipment or billing review system. Keep the original document reference with the result. Duty and landed-cost calculation external. Dokyumi processes one file with a saved schema; your application owns record matching, business rules and updates to other systems.
A schema shaped around the next step.
Start with these fields, then adjust them to match your documents and destination system. The example above shows the data object you are asking Dokyumi to extract.
Download editable starter schemaChoose required fields for your process. The starter schema preserves any defined nested fields; refine line-item structures and test them on representative files.
| Field | Type | What to capture |
|---|---|---|
supplier_name | string | Supplier name exactly as printed in this commercial invoice. Preserve identifiers and qualifiers; do not look up or infer missing information. |
buyer_name | string | Buyer name exactly as printed in this commercial invoice. Preserve identifiers and qualifiers; do not look up or infer missing information. |
invoice_reference | string | Invoice reference exactly as printed in this commercial invoice. Preserve identifiers and qualifiers; do not look up or infer missing information. |
invoice_date | date | Invoice date explicitly printed in this commercial invoice. Keep it distinct from other dates; leave it empty if no calendar date is stated. |
currency_code | string | Currency explicitly stated in this source; leave empty when it is not stated. |
incoterm | string | Incoterm exactly as printed in this commercial invoice. Preserve identifiers and qualifiers; do not look up or infer missing information. |
item_rows | array | Every visible item rows row in this commercial invoice. Preserve separate rows, labels and qualifiers; do not merge entries or reconstruct missing ones. |
freight_amount | currency | Freight amount explicitly labeled in this commercial invoice. Preserve its sign and stated currency; do not calculate a missing amount. |
stated_total | currency | Stated total explicitly labeled in this commercial invoice. Preserve its sign and stated currency; do not calculate a missing amount. |
Give exceptions a clear path to review.
Dokyumi returns a model-reported confidence map, validation details, and a completed or review status for produced results. Check required fields and your business rules before passing data onward.
A completed extraction describes the extraction result. Your application and reviewers own matching, approvals, routing, and updates to other systems.
Read the response contractChecks for this process
- An invoice states a country of dispatch separately from origin. Keep the stated origin for each line and leave tariff and duty decisions downstream.
- Check invoice date against their own printed labels; leave an unstated date empty instead of deriving it.
- Check freight amount, stated total for signs, decimal placement and stated currency before any downstream calculation or posting.
- Compare every item rows row with the source, including continuation pages, separate categories and repeated table headings.
Prove the fit on a representative batch.
Test commercial invoice examples from the layouts your team actually receives. Include the exception described here: An invoice states a country of dispatch separately from origin. Keep the stated origin for each line and leave tariff and duty decisions downstream. Compare the extracted supplier name, buyer name, invoice reference and any line rows with a reviewer's checked reference before enabling downstream actions.
Compare extracted values with a reviewer’s reference set. Record corrections, unresolved fields, review time, and credits used before connecting downstream actions.
The free plan’s credit limits apply. Assisted pilots are scoped with Dokyumi before work begins.
Expand when the next process is ready
Add recurring extraction capacity when commercial invoice intake becomes routine. Reuse this field contract for layouts that express the same information; create a separate schema when the next document has different fields or review requirements.
For a tailored implementation
Discuss document volume, page lengths and schema setup for import cost accounting teams. Bring difficult commercial invoice samples and the review requirements your implementation must preserve.
Talk through document mix and volumeStart small. Add capacity as intake grows.
All self-service plans include the REST API, upload-site webhooks, custom confidence thresholds, and schema inference. Choose by volume, schema count, and upload sites.
Each document uses one credit per 5 pages, rounded up. An 8-page file uses 2 credits. Self-service files can be up to 50 pages; larger files, custom-built schemas, and additional volume are quoted through Enterprise. Full pricing details
Questions about commercial invoice landed cost inputs
Which fields can I capture from a commercial invoice?
The starter schema contains supplier name, buyer name, invoice reference, invoice date, currency code, incoterm, item rows, freight amount, stated total. Edit those definitions and choose your required fields before saving. Array fields include defined sub-fields so row values have a validation structure.
What needs review in commercial invoice landed cost inputs?
An invoice states a country of dispatch separately from origin. Keep the stated origin for each line and leave tariff and duty decisions downstream. Check the original source alongside model-reported confidence and validation output; completion status describes the extraction result, not the business decision.
How does this data reach your shipment or billing review system?
Save the schema, then send one supported PDF or image to POST /api/v1/extract with its slug. The response contains the data, model-reported confidence, validation and result status. Your application maps reviewed values to the destination; upload-site submissions can use a configured webhook. Duty and landed-cost calculation external.
How do I test this workflow on my own documents?
Start free with 25 credits per month, 2 schemas, and 1 branded upload site. The starter schema opens in the schema builder after sign-up. Edit the fields, save it, and upload a representative file through your account or the extraction API. Account documents are stored according to Dokyumi’s privacy policy; contact hello@dokyumi.com for deletion requests and retention requirements.