ParseParse
Use CasesDocsAPI Reference
Log InGet Started Free
Menu
  • How it works
  • Use Cases
  • Docs
  • API Reference
  • Contact
REST API · Remittance to JSON · 100 free pages/mo

Remittance Advice Extraction API

Turn remittance advice into structured JSON. Payer, payment reference, amount, and the full invoice-by-invoice breakdown with discounts and deductions - typed and ready to apply against your open receivables. Reads PDF, scanned, and emailed remittances.

Get an API Key FreeRead the Docs

Every Settled Invoice as Its Own Line

Send the remittance and a schema. The payment header and each invoice it settles, with the discount taken and the amount deducted, come back typed and ready to match against your open items.

request.sh
curl -X POST \
  https://api-parse.conversiontools.io/v1/extract \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "file=@remittance.pdf" \
  -F 'schema={
    "payer": "string",
    "payment_reference": "string",
    "payment_date": "string",
    "payment_method": "string",
    "currency": "string",
    "total_paid": "number",
    "invoices_paid": [{
      "invoice_number": "string",
      "invoice_date": "string",
      "gross_amount": "number",
      "discount": "number",
      "deduction": "number",
      "net_paid": "number"
    }],
    "unapplied_amount": "number"
  }'
response.json
{
  "status": "completed",
  "pages": 1,
  "data": {
    "payer": "Larkspur Retail Group",
    "payment_reference": "ACH-20260714-8842",
    "payment_date": "2026-07-14",
    "payment_method": "ACH",
    "currency": "USD",
    "total_paid": 18412.55,
    "invoices_paid": [
      {
        "invoice_number": "INV-2026-10488",
        "invoice_date": "2026-06-02",
        "gross_amount": 12400.00,
        "discount": 248.00,
        "deduction": 0.00,
        "net_paid": 12152.00
      },
      {
        "invoice_number": "INV-2026-10517",
        "invoice_date": "2026-06-09",
        "gross_amount": 6410.55,
        "discount": 0.00,
        "deduction": 150.00,
        "net_paid": 6260.55
      }
    ],
    "unapplied_amount": 0.00
  }
}

Built for Accounts Receivable

One payment can settle forty invoices. Cash application lives or dies on the line-level detail.

Invoice-level settlement lines

Each settled invoice comes back with its own gross amount, discount taken, deduction, and net paid, so a single incoming payment can be split across every open item it clears.

Short payments and deductions

When a customer pays less than the invoice, the gap is captured on that line as a discount or a deduction instead of vanishing into one lump total. Anything left over lands in the unapplied amount rather than going missing.

A different layout from every payer

No two customers format remittance the same way, and it arrives as a PDF attachment, a scan, or a portal printout. Schema-driven extraction reads all of them with OCR applied automatically, with no template per payer.

Frequently Asked Questions

Can one remittance settle many invoices?

Yes. Define invoices_paid as an array and every settled invoice comes back as a separate object with its number, date, gross amount, discount, deduction, and net paid - however many the payment covers.

Does it capture short payments and deductions?

Yes. Discount and deduction are extracted per invoice line, so a short payment shows up where it belongs instead of being buried in the payment total. Summing net_paid against total_paid then tells you immediately whether anything is unaccounted for.

What about remittances that arrive as scans or email attachments?

OCR is applied automatically, so scanned, faxed, and photographed remittances read the same as native PDFs. There is no separate pre-processing step to run first.

Can I reuse one schema across all my customers?

Yes. Save the schema once and reference it on every extraction. Layouts differ from payer to payer, but the field set you want back does not, so a single saved schema usually covers the whole customer base.

How is payment data handled?

Uploaded documents are deleted automatically within 24 hours. Extracted data is encrypted in transit and at rest and is never used to train models.

More document extraction use cases

The same schema-driven API works across every document type. Define a schema once, extract from thousands of files.

Data Extraction API

Extract structured JSON from any document with custom schemas.

PDF Parsing API

Parse any PDF into structured JSON, scanned or digital.

Invoice extraction

Vendor, line items, totals, tax, and dates from invoices.

Receipt parsing

Store, items, totals, and payment method from receipts.

Purchase order extraction

PO number, vendor, buyer, and SKU-level line items.

Bank statement to JSON

Transactions, running balances, and dates for reconciliation.

Tax form extraction

Box-level data from W-2, 1099, and other tax forms.

Contract data extraction

Parties, dates, governing law, and key clauses.

Bill of lading extraction

Carrier, parties, ports, containers, and cargo.

Credit note extraction

Credit amounts matched back to the original invoice.

Utility bill extraction

Meter readings, charges, and totals from any provider.

Financial statement extraction

Line items and periods from balance sheets and reports.

Quotation extraction

Vendor quotes in one shape so you can compare them.

Payslip extraction

Earnings, deductions, taxes, and year-to-date totals.

Resume parsing

Experience, education, and skills from any CV layout.

ID document extraction

Fields and MRZ from passports and ID cards.

Lease agreement extraction

Rent, term, deposits, and renewal deadlines.

Insurance claim extraction

Claim and policy numbers, dates, and claimed amounts.

Packing list extraction

Packages and SKU-level lines for receiving.

Delivery note extraction

Ordered versus delivered quantities and sign-off.

Automate Cash Application

Free tier covers your first 100 pages a month. No credit card to start.

Get Started FreeAPI Reference
Parse

AI-powered document data extraction

Conversion ToolsPowered by Conversion Tools

Use cases

  • Data Extraction API
  • PDF Parsing API
  • Invoice extraction
  • Receipt parsing
  • Purchase order extraction
  • Bank statement to JSON
  • Tax form extraction
  • Contract data extraction
  • Bill of lading extraction

Developers

  • How it works
  • Quickstart
  • Documentation
  • API Reference
  • n8n integration
  • Blog

Account

  • Log in
  • Contact
  • Security
  • Privacy Policy
  • Terms of Service
  • Refund Policy
© 2026 Conversion Tools