Skip to content

Supplier balance statement intake

For AP supplier statement reconciliation teams

Prepare invoice references, credits and outstanding balances from a supplier account statement with fields you can edit. Matching external.

25 free credits/month · No card needed

See the workflow and review checks

Inspect a document example.

Synthetic documents · Expected output
Standard documentPDF
supplier balance statement intakeFictional sample · For demonstration
supplier name
Example Supply Company - synthetic
statement date
2026-09-30
account reference
DEMO-ACCOUNT-0042
opening balance
0
statement rows
[ { "entry_date": "2026-09-30", "reference": "Example reference - synthetic", "entry_type": "Invoice", "description": "Example document line - original synthetic data", "debit_amount": 1250, "credit_amount": 0 } ]
closing balance
1250
{
  "supplier_name": "Example Supply Company - synthetic",
  "statement_date": "2026-09-30",
  "account_reference": "DEMO-ACCOUNT-0042",
  "opening_balance": 0,
  "statement_rows": [
    {
      "entry_date": "2026-09-30",
      "reference": "Example reference - synthetic",
      "entry_type": "Invoice",
      "description": "Example document line - original synthetic data",
      "debit_amount": 1250,
      "credit_amount": 0
    }
  ],
  "closing_balance": 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 supplier account statement arrives for ap supplier statement reconciliation teams. The next step needs invoice references, credits and outstanding balances, recorded under the correct document reference before the information enters your accounting review queue.

A supplier statement contains payments in transit and credit notes. Preserve each entry type before comparing the statement with the AP ledger. 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

  • Supplier account statement PDFs
  • Scanned or photographed supplier account statement pages

PDF, JPEG, PNG, TIFF, or WEBP. Send one file per extraction call; create separate schemas when the document types need different fields.

  1. Define the fields

    Open the starter schema. Edit field descriptions, mark the values your process requires, and save it in your account.

  2. Extract at intake

    Send the document and saved schema slug to POST /api/v1/extract, or collect the file through a branded upload site.

  3. Hand off reviewed data

    After checking supplier name, statement date, account reference, your application maps the reviewed record into your accounting review queue. Keep the original document reference with the result. Matching 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 schema

Choose required fields for your process. The starter schema preserves any defined nested fields; refine line-item structures and test them on representative files.

FieldTypeWhat to capture
supplier_namestringSupplier name exactly as printed in this supplier account statement. Preserve identifiers and qualifiers; do not look up or infer missing information.
statement_datedateStatement date explicitly printed in this supplier account statement. Keep it distinct from other dates; leave it empty if no calendar date is stated.
account_referencestringAccount reference exactly as printed in this supplier account statement. Preserve identifiers and qualifiers; do not look up or infer missing information.
opening_balancecurrencyOpening balance explicitly labeled in this supplier account statement. Preserve its sign and stated currency; do not calculate a missing amount.
statement_rowsarrayEvery visible statement rows row in this supplier account statement. Preserve separate rows, labels and qualifiers; do not merge entries or reconstruct missing ones.
closing_balancecurrencyClosing balance explicitly labeled in this supplier account 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 contract

Run a synthetic response through a review gate

Checks for this process

  • A supplier statement contains payments in transit and credit notes. Preserve each entry type before comparing the statement with the AP ledger.
  • Check statement date against their own printed labels; leave an unstated date empty instead of deriving it.
  • Check opening balance, closing balance for signs, decimal placement and stated currency before any downstream calculation or posting.
  • Compare every statement rows row with the source, including continuation pages, separate categories and repeated table headings.

Prove the fit on a representative batch.

Test supplier account statement examples from the layouts your team actually receives. Include the exception described here: A supplier statement contains payments in transit and credit notes. Preserve each entry type before comparing the statement with the AP ledger. Compare the extracted supplier name, statement date, account 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 supplier account 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 ap supplier statement reconciliation teams. Bring difficult supplier account statement samples and the review requirements your implementation must preserve.

Talk through document mix and volume

Start 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.

Free

$0/month

  • 25 credits/month
  • 2 schemas
  • 1 branded upload site
Test this workflow

Starter

$99/month

  • 500 credits/month
  • 10 schemas
  • 5 branded upload sites
Explore Starter

Growth

$499/month

  • 3,000 credits/month
  • 50 schemas
  • 25 branded upload sites
Explore Growth

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 supplier balance statement intake

Which fields can I capture from a supplier account statement?

The starter schema contains supplier name, statement date, account reference, opening balance, statement rows, closing balance. 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 supplier balance statement intake?

A supplier statement contains payments in transit and credit notes. Preserve each entry type before comparing the statement with the AP ledger. 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. Matching 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.