Property utility allocation statement capture
For Property utility billing coordinators
Prepare property, tenant, utility period, units and charges from an allocation statement with fields you can edit. Allocation fairness external.
25 free credits/month · No card needed
See the workflow and review checksInspect a document example.
Synthetic documents · Expected output- property name
- Example Property - synthetic
- tenant name
- Example Tenant - synthetic
- unit reference
- DEMO-UNIT-0042
- billing period start
- 2026-09-01
- billing period end
- 2026-09-30
- utility rows
- [ { "utility_type": "Example utility type - synthetic", "period_label": "September 2026", "metered_units": 100, "unit_of_measure": "each", "allocation_basis": "Example allocation basis - synthetic", "stated_charge": 1250 } ]
- stated total
- 1250
{
"property_name": "Example Property - synthetic",
"tenant_name": "Example Tenant - synthetic",
"unit_reference": "DEMO-UNIT-0042",
"billing_period_start": "2026-09-01",
"billing_period_end": "2026-09-30",
"utility_rows": [
{
"utility_type": "Example utility type - synthetic",
"period_label": "September 2026",
"metered_units": 100,
"unit_of_measure": "each",
"allocation_basis": "Example allocation basis - synthetic",
"stated_charge": 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
An allocation statement arrives for property utility billing coordinators. The next step needs property, tenant, utility period, units and charges, recorded under the correct document reference before the information enters your property administration register.
An allocation statement reports common-area charges separately from metered use. Retain the allocation basis as printed; calculations remain external. 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
- Allocation statement PDFs
- Scanned or photographed allocation 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 property name, tenant name, unit reference, your application maps the reviewed record into your property administration register. Keep the original document reference with the result. Allocation fairness 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 |
|---|---|---|
property_name | string | Property name exactly as printed in this allocation statement. Preserve identifiers and qualifiers; do not look up or infer missing information. |
tenant_name | string | Tenant name exactly as printed in this allocation statement. Preserve identifiers and qualifiers; do not look up or infer missing information. |
unit_reference | string | Unit reference exactly as printed in this allocation statement. Preserve identifiers and qualifiers; do not look up or infer missing information. |
billing_period_start | date | Billing period start explicitly printed in this allocation statement. Keep it distinct from other dates; leave it empty if no calendar date is stated. |
billing_period_end | date | Billing period end explicitly printed in this allocation statement. Keep it distinct from other dates; leave it empty if no calendar date is stated. |
utility_rows | array | Every visible utility rows row in this allocation statement. Preserve separate rows, labels and qualifiers; do not merge entries or reconstruct missing ones. |
stated_total | currency | Stated total explicitly labeled in this allocation 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
- An allocation statement reports common-area charges separately from metered use. Retain the allocation basis as printed; calculations remain external.
- Check billing period start, billing period 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 utility rows row with the source, including continuation pages, separate categories and repeated table headings.
Prove the fit on a representative batch.
Test allocation statement examples from the layouts your team actually receives. Include the exception described here: An allocation statement reports common-area charges separately from metered use. Retain the allocation basis as printed; calculations remain external. Compare the extracted property name, tenant name, unit 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 allocation 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 property utility billing coordinators. Bring difficult allocation 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 property utility allocation statement capture
Which fields can I capture from an allocation statement?
The starter schema contains property name, tenant name, unit reference, billing period start, billing period end, utility 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 property utility allocation statement capture?
An allocation statement reports common-area charges separately from metered use. Retain the allocation basis as printed; calculations remain external. 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 property administration register?
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. Allocation fairness 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.