Accounts payable invoices with coding and approvals

Accounts payable records that pair vendor invoices with how the finance team coded them (GL account, cost center, tax), who approved them, which exceptions came up and when they were paid. Labs use them to train invoice-processing and finance-operations agents on real coding decisions.

Last updated October 3, 2026

What a record contains

One invoice: the document, extracted fields, GL and cost-center coding, matching to purchase order and receipt, approval steps, exceptions and payment status.

Field	What it holds
`invoice_id, document_ref`	Pseudonymous ID and the invoice file
`vendor`	Pseudonymous vendor with category
`lines[]`	Description, amount, GL account, cost center, tax code
`po_match`	Two- or three-way match result
`approvals[]`	Role, action and date
`exceptions[], paid_at`	Holds, disputes and payment

Illustrative record. The values are made up to show the shape of the data.

{
  "invoice_id": "AP-30417",
  "vendor": {"id": "V-288", "category": "freight"},
  "lines": [{"description": "Linehaul LAX-PHX", "amount": 1840.00,
             "gl_account": "5120 Freight-in", "cost_center": "DC-West"}],
  "po_match": "three_way_matched",
  "approvals": [{"role": "ops_manager", "action": "approved", "at": "2025-04-08"}],
  "exceptions": [],
  "paid_at": "2025-04-22"
}

How AI labs use it

Invoice coding agents: Real GL and cost-center decisions as labels.
Document extraction: Varied real invoice layouts with verified fields.
Exception handling: When invoices get held, disputed or escalated, and why.

Typical preparation requirements

Agreed with the supplier before any work begins. Typical requirements include:

Bank details, tax IDs and signatures removed
Vendor names pseudonymized where contracts require it
Employee expenses excluded unless scoped

Every dataset has a documented owner and confirmed licensing rights. See data governance on sourcex.si.

What makes a strong package

A stable chart of accounts, or mapped changes
Exceptions and their resolutions recorded
Purchase order and receipt matching data

Compared with public datasets

Public sets such as RVL-CDIP and SEC EDGAR filings are useful references, but limited as enterprise training data. The finance and accounting category page compares them with licensed data.

Who typically holds it

Mid-sized companies
Accounting firms, with clients’ permission
Outsourced AP providers

Know a company like this?

Introduce the company to SourceX. If its data deal closes, you can earn up to $100,000 in referral fees, paid after the buyer accepts the data and SourceX receives payment.

Refer a company

Questions

Can accounting firms license client invoices?

Only with the client’s permission. Client data belongs to the client, and accountants have confidentiality duties.

Need this data for a model?

Describe what you need: domain, volume, history, format and licensing terms. SourceX looks for companies that hold it and can license it.

Request data Talk to SourceX