Commission statement payout preparation
For Sales compensation operations teams
Prepare salesperson, deal reference, basis and stated commission from a commission statement with fields you can edit. Payout approval external.
25 free credits/month · No card needed
See the workflow and review checksInspect a document example.
Synthetic documents · Expected output- payee name
- Example Payee - synthetic
- statement period
- September 2026
- commission rows
- [ { "deal_reference": "DEMO-DEAL-0042", "transaction_type": "Example transaction type - synthetic", "commission_basis": 1250, "commission_amount": 1250, "adjustment_amount": 0 } ]
- gross commission
- 1250
- adjustments
- 0
- stated net commission
- 1250
{
"payee_name": "Example Payee - synthetic",
"statement_period": "September 2026",
"commission_rows": [
{
"deal_reference": "DEMO-DEAL-0042",
"transaction_type": "Example transaction type - synthetic",
"commission_basis": 1250,
"commission_amount": 1250,
"adjustment_amount": 0
}
],
"gross_commission": 1250,
"adjustments": 0,
"stated_net_commission": 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 commission statement arrives for sales compensation operations teams. The next step needs salesperson, deal reference, basis and stated commission, recorded under the correct document reference before the information enters your accounting review queue.
A commission statement reverses an earlier deal payment. Preserve the reversal sign and deal reference before applying payout rules. 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
- Commission statement PDFs
- Scanned or photographed commission 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 payee name, statement period, commission rows, your application maps the reviewed record into your accounting review queue. Keep the original document reference with the result. Payout approval 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 |
|---|---|---|
payee_name | string | Payee name exactly as printed in this commission statement. Preserve identifiers and qualifiers; do not look up or infer missing information. |
statement_period | string | Statement period exactly as printed in this commission statement. Preserve identifiers and qualifiers; do not look up or infer missing information. |
commission_rows | array | Every visible commission rows row in this commission statement. Preserve separate rows, labels and qualifiers; do not merge entries or reconstruct missing ones. |
gross_commission | currency | Gross commission explicitly labeled in this commission statement. Preserve its sign and stated currency; do not calculate a missing amount. |
adjustments | currency | Adjustments explicitly labeled in this commission statement. Preserve its sign and stated currency; do not calculate a missing amount. |
stated_net_commission | currency | Stated net commission explicitly labeled in this commission statement. 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 commission statement reverses an earlier deal payment. Preserve the reversal sign and deal reference before applying payout rules.
- Check gross commission, adjustments, stated net commission for signs, decimal placement and stated currency before any downstream calculation or posting.
- Compare every commission rows row with the source, including continuation pages, separate categories and repeated table headings.
Prove the fit on a representative batch.
Test commission statement examples from the layouts your team actually receives. Include the exception described here: A commission statement reverses an earlier deal payment. Preserve the reversal sign and deal reference before applying payout rules. Compare the extracted payee name, statement period, commission rows 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 commission 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 sales compensation operations teams. Bring difficult commission 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 commission statement payout preparation
Which fields can I capture from a commission statement?
The starter schema contains payee name, statement period, commission rows, gross commission, adjustments, stated net commission. 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 commission statement payout preparation?
A commission statement reverses an earlier deal payment. Preserve the reversal sign and deal reference before applying payout rules. 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. Payout approval 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.