Payment confirmation remittance record
For Treasury receipt recording teams
Prepare sender, recipient, reference and stated amount from a payment confirmation with fields you can edit. Bank settlement not verified.
25 free credits/month · No card needed
See the workflow and review checksInspect a document example.
Synthetic documents · Expected output- sender name
- Example Sender - synthetic
- recipient name
- Example Recipient - synthetic
- payment reference
- DEMO-PAYMENT-0042
- payment date
- 2026-09-30
- stated amount
- 1250
- currency code
- USD
- stated status
- Submitted for review
{
"sender_name": "Example Sender - synthetic",
"recipient_name": "Example Recipient - synthetic",
"payment_reference": "DEMO-PAYMENT-0042",
"payment_date": "2026-09-30",
"stated_amount": 1250,
"currency_code": "USD",
"stated_status": "Submitted for review"
}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 payment confirmation arrives for treasury receipt recording teams. The next step needs sender, recipient, reference and stated amount, recorded under the correct document reference before the information enters your accounting review queue.
A payment document says scheduled rather than settled. Keep that status as printed and do not treat the confirmation as bank verification. 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
- Payment confirmation PDFs
- Scanned or photographed payment confirmation 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 sender name, recipient name, payment reference, your application maps the reviewed record into your accounting review queue. Keep the original document reference with the result. Bank settlement not verified. 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 |
|---|---|---|
sender_name | string | Sender name exactly as printed in this payment confirmation. Preserve identifiers and qualifiers; do not look up or infer missing information. |
recipient_name | string | Recipient name exactly as printed in this payment confirmation. Preserve identifiers and qualifiers; do not look up or infer missing information. |
payment_reference | string | Payment reference exactly as printed in this payment confirmation. Preserve identifiers and qualifiers; do not look up or infer missing information. |
payment_date | date | Payment date explicitly printed in this payment confirmation. Keep it distinct from other dates; leave it empty if no calendar date is stated. |
stated_amount | currency | Stated amount explicitly labeled in this payment confirmation. Preserve its sign and stated currency; do not calculate a missing amount. |
currency_code | string | Currency explicitly stated in this source; leave empty when it is not stated. |
stated_status | string | Status exactly as the document describes it. Do not infer authorization, settlement, completion or current validity. |
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 payment document says scheduled rather than settled. Keep that status as printed and do not treat the confirmation as bank verification.
- Check payment date against their own printed labels; leave an unstated date empty instead of deriving it.
- Check stated amount for signs, decimal placement and stated currency before any downstream calculation or posting.
Prove the fit on a representative batch.
Test payment confirmation examples from the layouts your team actually receives. Include the exception described here: A payment document says scheduled rather than settled. Keep that status as printed and do not treat the confirmation as bank verification. Compare the extracted sender name, recipient name, payment 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 payment confirmation 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 treasury receipt recording teams. Bring difficult payment confirmation 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 payment confirmation remittance record
Which fields can I capture from a payment confirmation?
The starter schema contains sender name, recipient name, payment reference, payment date, stated amount, currency code, stated status. 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 payment confirmation remittance record?
A payment document says scheduled rather than settled. Keep that status as printed and do not treat the confirmation as bank verification. 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 accounting review queue?
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. Bank settlement not verified.
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.