Demurrage and detention charge intake
For Container charge review analysts
Prepare equipment, free-time dates, billed days and amounts from a charge notice with fields you can edit. Validity calculations external.
25 free credits/month · No card needed
See the workflow and review checksInspect a document example.
Synthetic documents · Expected output- invoice reference
- DEMO-INVOICE-0042
- container number
- DEMO-CONTAINER-0042
- charge period start
- 2026-09-01
- charge period end
- 2026-09-30
- free time end
- 2026-09-30
- billed days
- 1
- charge rows
- [ { "charge_type": "Example charge type - synthetic", "start_date": "2026-09-30", "end_date": "2026-09-30", "billed_days": 1, "stated_rate": 1250, "stated_amount": 1250 } ]
- stated total
- 1250
{
"invoice_reference": "DEMO-INVOICE-0042",
"container_number": "DEMO-CONTAINER-0042",
"charge_period_start": "2026-09-01",
"charge_period_end": "2026-09-30",
"free_time_end": "2026-09-30",
"billed_days": 1,
"charge_rows": [
{
"charge_type": "Example charge type - synthetic",
"start_date": "2026-09-30",
"end_date": "2026-09-30",
"billed_days": 1,
"stated_rate": 1250,
"stated_amount": 1250
}
],
"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 charge notice arrives for container charge review analysts. The next step needs equipment, free-time dates, billed days and amounts, recorded under the correct document reference before the information enters your shipment or billing review system.
A notice distinguishes terminal demurrage from equipment detention. Preserve charge labels and dates before a reviewer checks contractual free time. 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
- Charge notice PDFs
- Scanned or photographed charge notice 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 invoice reference, container number, charge period start, your application maps the reviewed record into your shipment or billing review system. Keep the original document reference with the result. Validity calculations 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 |
|---|---|---|
invoice_reference | string | Invoice reference exactly as printed in this charge notice. Preserve identifiers and qualifiers; do not look up or infer missing information. |
container_number | string | Container number exactly as printed in this charge notice. Preserve identifiers and qualifiers; do not look up or infer missing information. |
charge_period_start | date | Charge period start explicitly printed in this charge notice. Keep it distinct from other dates; leave it empty if no calendar date is stated. |
charge_period_end | date | Charge period end explicitly printed in this charge notice. Keep it distinct from other dates; leave it empty if no calendar date is stated. |
free_time_end | date | Free time end explicitly printed in this charge notice. Keep it distinct from other dates; leave it empty if no calendar date is stated. |
billed_days | number | Billed days as reported in this charge notice. Preserve the labeled measure and its unit; do not estimate it. |
charge_rows | array | Every visible charge rows row in this charge notice. Preserve separate rows, labels and qualifiers; do not merge entries or reconstruct missing ones. |
stated_total | currency | Stated total explicitly labeled in this charge notice. 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
- A notice distinguishes terminal demurrage from equipment detention. Preserve charge labels and dates before a reviewer checks contractual free time.
- Check charge period start, charge period end, free time end against their own printed labels; leave an unstated date empty instead of deriving it.
- Check stated total for signs, decimal placement and stated currency before any downstream calculation or posting.
- Compare every charge rows row with the source, including continuation pages, separate categories and repeated table headings.
Prove the fit on a representative batch.
Test charge notice examples from the layouts your team actually receives. Include the exception described here: A notice distinguishes terminal demurrage from equipment detention. Preserve charge labels and dates before a reviewer checks contractual free time. Compare the extracted invoice reference, container number, charge period start 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 charge notice 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 container charge review analysts. Bring difficult charge notice 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 demurrage and detention charge intake
Which fields can I capture from a charge notice?
The starter schema contains invoice reference, container number, charge period start, charge period end, free time end, billed days, charge rows, 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 demurrage and detention charge intake?
A notice distinguishes terminal demurrage from equipment detention. Preserve charge labels and dates before a reviewer checks contractual free time. 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. Validity calculations 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.