Skip to content

Gift card settlement statement capture

For Retail gift card accounting teams

Prepare issuer, period, redemptions and fees from a gift card settlement with fields you can edit. Liability reconciliation external.

25 free credits/month · No card needed

See the workflow and review checks

Inspect a document example.

Synthetic documents · Expected output
Standard documentPDF
gift card settlement statement captureFictional sample · For demonstration
issuer name
Example Issuer - synthetic
statement period
September 2026
settlement reference
DEMO-SETTLEMENT-0042
redemption rows
[ { "transaction_reference": "DEMO-TRANSACTION-0042", "redemption_date": "2026-09-30", "redeemed_value": 1250, "adjustment_text": "Adjustment text explicitly printed in the original synthetic source for reviewer context." } ]
stated redemptions
1250
stated fees
0
net settlement
1250
{
  "issuer_name": "Example Issuer - synthetic",
  "statement_period": "September 2026",
  "settlement_reference": "DEMO-SETTLEMENT-0042",
  "redemption_rows": [
    {
      "transaction_reference": "DEMO-TRANSACTION-0042",
      "redemption_date": "2026-09-30",
      "redeemed_value": 1250,
      "adjustment_text": "Adjustment text explicitly printed in the original synthetic source for reviewer context."
    }
  ],
  "stated_redemptions": 1250,
  "stated_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 gift card settlement arrives for retail gift card accounting teams. The next step needs issuer, period, redemptions and fees, recorded under the correct document reference before the information enters your accounting review queue.

A settlement includes expired-value adjustments separately from redemptions. Preserve the labels before a finance team reconciles the liability. 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

  • Gift card settlement PDFs
  • Scanned or photographed gift card settlement 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 issuer name, statement period, settlement reference, your application maps the reviewed record into your accounting review queue. Keep the original document reference with the result. Liability reconciliation 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
issuer_namestringIssuer name exactly as printed in this gift card settlement. Preserve identifiers and qualifiers; do not look up or infer missing information.
statement_periodstringStatement period exactly as printed in this gift card settlement. Preserve identifiers and qualifiers; do not look up or infer missing information.
settlement_referencestringSettlement reference exactly as printed in this gift card settlement. Preserve identifiers and qualifiers; do not look up or infer missing information.
redemption_rowsarrayEvery visible redemption rows row in this gift card settlement. Preserve separate rows, labels and qualifiers; do not merge entries or reconstruct missing ones.
stated_redemptionscurrencyStated redemptions explicitly labeled in this gift card settlement. Preserve its sign and stated currency; do not calculate a missing amount.
stated_feescurrencyStated fees explicitly labeled in this gift card settlement. Preserve its sign and stated currency; do not calculate a missing amount.
net_settlementcurrencyNet settlement explicitly labeled in this gift card settlement. 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 settlement includes expired-value adjustments separately from redemptions. Preserve the labels before a finance team reconciles the liability.
  • Check stated redemptions, stated fees, net settlement for signs, decimal placement and stated currency before any downstream calculation or posting.
  • Compare every redemption rows row with the source, including continuation pages, separate categories and repeated table headings.

Prove the fit on a representative batch.

Test gift card settlement examples from the layouts your team actually receives. Include the exception described here: A settlement includes expired-value adjustments separately from redemptions. Preserve the labels before a finance team reconciles the liability. Compare the extracted issuer name, statement period, settlement 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 gift card settlement 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 retail gift card accounting teams. Bring difficult gift card settlement 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 gift card settlement statement capture

Which fields can I capture from a gift card settlement?

The starter schema contains issuer name, statement period, settlement reference, redemption rows, stated redemptions, stated fees, net settlement. 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 gift card settlement statement capture?

A settlement includes expired-value adjustments separately from redemptions. Preserve the labels before a finance team reconciles the liability. 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. Liability reconciliation 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.