Merchant Processor Statement Extraction for Lenders
For Lender revenue review analysts
Prepare sales, refunds, fees and net settlements from a processor settlement statement with fields you can edit. Revenue analysis is downstream.
25 free credits/month · No card needed
See the workflow and review checksInspect a document example.
Synthetic documents · Expected output- merchant name
- Example Harbor Repair - synthetic
- merchant reference
- DEMO-MERCHANT-0042
- period start
- 2026-09-01
- period end
- 2026-09-30
- gross sales
- 1250
- refunds
- 0
- processing fees
- 0
- net settlements
- 1250
- settlements
- [ { "settlement_date": "2026-09-30", "reference": "Example reference - synthetic", "gross_sales": 1250, "refunds": 0, "fees": 0, "net_settlement": 1250 } ]
{
"merchant_name": "Example Harbor Repair - synthetic",
"merchant_reference": "DEMO-MERCHANT-0042",
"period_start": "2026-09-01",
"period_end": "2026-09-30",
"gross_sales": 1250,
"refunds": 0,
"processing_fees": 0,
"net_settlements": 1250,
"settlements": [
{
"settlement_date": "2026-09-30",
"reference": "Example reference - synthetic",
"gross_sales": 1250,
"refunds": 0,
"fees": 0,
"net_settlement": 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 processor settlement statement arrives for lender revenue review analysts. The next step needs sales, refunds, fees and net settlements, recorded under the correct document reference before the information enters your loan intake worksheet.
A processor reports gross card sales and net bank funding in adjacent columns. Keep refunds and fees separate so an analyst does not treat the net funding figure as gross revenue. 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
- Processor settlement statement PDFs
- Scanned or photographed processor settlement statement 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 merchant name, merchant reference, period start, your application maps the reviewed record into your loan intake worksheet. Keep the original document reference with the result. Revenue analysis is downstream. 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 |
|---|---|---|
merchant_name | string | Merchant name exactly as printed in this processor settlement statement. Preserve identifiers and qualifiers; do not look up or infer missing information. |
merchant_reference | string | Merchant reference exactly as printed in this processor settlement statement. Preserve identifiers and qualifiers; do not look up or infer missing information. |
period_start | date | Opening date printed for the reporting period, separate from the issue date. |
period_end | date | Closing date printed for the reporting period, separate from payment or posting dates. |
gross_sales | currency | Gross sales explicitly labeled in this processor settlement statement. Preserve its sign and stated currency; do not calculate a missing amount. |
refunds | currency | Refunds explicitly labeled in this processor settlement statement. Preserve its sign and stated currency; do not calculate a missing amount. |
processing_fees | currency | Processing fees explicitly labeled in this processor settlement statement. Preserve its sign and stated currency; do not calculate a missing amount. |
net_settlements | currency | Net processor settlements as printed, kept distinct from sales, fees and refunds. |
settlements | array | Every visible settlements row in this processor settlement statement. Preserve separate rows, labels and qualifiers; do not merge entries or reconstruct missing ones. |
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 processor reports gross card sales and net bank funding in adjacent columns. Keep refunds and fees separate so an analyst does not treat the net funding figure as gross revenue.
- Check period start, period end against their own printed labels; leave an unstated date empty instead of deriving it.
- Check gross sales, refunds, processing fees, net settlements for signs, decimal placement and stated currency before any downstream calculation or posting.
- Compare every settlements row with the source, including continuation pages, separate categories and repeated table headings.
Prove the fit on a representative batch.
Test processor settlement statement examples from the layouts your team actually receives. Include the exception described here: A processor reports gross card sales and net bank funding in adjacent columns. Keep refunds and fees separate so an analyst does not treat the net funding figure as gross revenue. Compare the extracted merchant name, merchant reference, 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 processor settlement statement 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 lender revenue review analysts. Bring difficult processor settlement statement 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 merchant processor statement revenue intake
Which fields can I capture from a processor settlement statement?
The starter schema contains merchant name, merchant reference, period start, period end, gross sales, refunds, processing fees, net settlements, settlements. 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 merchant processor statement revenue intake?
A processor reports gross card sales and net bank funding in adjacent columns. Keep refunds and fees separate so an analyst does not treat the net funding figure as gross revenue. 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 loan intake worksheet?
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. Revenue analysis is downstream.
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.