Give receivables analysts usable allocations when remittance arrives
For Accounts receivable and cash application teams
Extract the customer’s payment reference and stated invoice allocations from a remittance document. Use the result to prepare an AR review alongside your bank and open-invoice records.
25 free credits/month · No card needed
See the workflow and review checks{
"payer_name": "Example Buyer Co. — synthetic",
"payment_reference": "DEMO-REMIT-88",
"payment_date": "2026-08-12",
"currency_code": "USD",
"payment_amount": 1450,
"invoice_allocations": [
{
"invoice_reference": "DEMO-INV-100",
"allocated_amount": 1000,
"deduction_reason": ""
},
{
"invoice_reference": "DEMO-INV-101",
"allocated_amount": 450,
"deduction_reason": "Customer states a 50.00 pricing deduction"
}
]
}Synthetic data, not a live extraction. Real responses also include confidence, validation, and result status.
When this work lands on your desk
A customer sends remittance advice for a payment covering several invoices, and the cash application team needs to understand the intended allocation.
A payment total alone does not explain short pays, discounts or the invoices a customer intended to settle. Remittance tables may mix current allocations with historical balances. A dedicated schema preserves the document’s stated breakdown so your team can reconcile it against cash actually received and the receivables ledger.
Start with the documents you already collect
- Remittance advice PDFs
- Scanned payment allocation notices
- Customer payment statement attachments
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
Your AR system matches the payer and invoice references, confirms the bank receipt and checks allocation totals. Analysts resolve unapplied cash and deductions before your system posts any application.
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 schemaStarter fields are optional until you choose which are required. Nested line items need a defined structure if you want validation of their individual values.
| Field | Type | What to capture |
|---|---|---|
payer_name | string | Customer or payer as identified in the advice. |
payment_reference | string | Customer’s transfer, check or remittance reference. |
payment_date | date | Stated payment date; not verified bank settlement. |
currency_code | string | Explicit currency of the advised payment. |
payment_amount | currency | Total payment amount stated in the advice. |
invoice_allocations | array | Invoice reference, allocated amount and any stated deduction reason. |
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
- Stated payment has not appeared in bank records
- Customer reference does not match an open invoice
- Allocation sum differs from the payment amount
- Deduction explanation requires commercial follow-up
Prove the fit on a representative batch.
Use remittances with one invoice, multiple invoices and an unexplained deduction. Check each allocation against the source, then evaluate your ledger-matching rules independently.
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 paid capacity as payment advice becomes a daily queue. Additional schemas can cover customer statement variants and invoice documents needed for exception investigation.
For a tailored implementation
Discuss custom volume and schema setup for high-volume receivables teams working across multiple entities.
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 remittance cash application preparation
Does remittance prove payment was received?
No. It records the payer’s advice. Confirm settlement using your bank records before applying cash or marking an invoice paid.
Will it automatically match open invoices?
Matching requires your customer and receivables data. Your integration uses the extracted references and amounts to find candidates and route exceptions.
Can it approve deductions?
No. The schema captures a stated reason where present. Your team determines whether a deduction is valid and how it should be recorded.
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.