Connect existing AP, accounting, ERP, treasury, and banking sources once. We link available commercial evidence and return configured context downstream without replacing those systems or moving money.
Card networks stop at the authorization. ACH entries carry a routing number, an amount, and a memo field someone typed. Wire confirmations carry even less. None of them tell you what was procured, which cost center it belongs to, whether the vendor is 1099-reportable, or how it maps to your chart of accounts. That gap is where your finance team lives — every month.
This is not a workflow problem. Coupa, SAP Ariba, and Oracle have solved the workflow layer. The problem is the purchase data layer underneath: the structured record that says what was purchased, at what item-level detail, with what commodity code, from which verified vendor, on which rail. That record does not exist when the payment arrives. Your team creates it by hand.
The result is a month-end close that is fundamentally manual: GL coding by hand, vendor TIN collection at tax season, duplicate payment detection through spreadsheet matching, and commodity-code assignment that takes days. All of it is work that a normalized purchase record should eliminate before it reaches your team.
Configured connections can ingest available commercial-card data, ISO 20022 messages, ACH entries, and vendor invoices, then return source-aware Purchase Objects downstream. Fields, GL classifications, and comparison signals depend on source availability and organization configuration.
{
"object": "purchase",
"id": "pur_vc_4b7c2a19",
"rail_source": "commercial_card",
"merchant": {
"name": "Grainger Industrial Supply",
"category": "industrial supplies",
"tin": "36-1551918",
"lei": "5493001KJTIIGC8Y1R12"
},
"items": [
{
"name": "3M Nitrile Gloves - Case",
"price": 148.00,
"commodity_code": "46181500",
"gl_code": "6400",
"unit": "CS",
"quantity": 2
},
{
"name": "Safety Data Sheet Cabinet",
"price": 312.00,
"commodity_code": "44122011",
"gl_code": "6400",
"unit": "EA",
"quantity": 1
}
],
"amounts": { "subtotal": 460.00, "tax": 36.80, "total": 496.80, "currency": "USD" },
"gl_codes": ["6400"],
"iso20022_ref": "GRNGR20260626T144512"
}
Review effort depends on source availability, existing controls, configuration, and team processes. Item-level purchase evidence can provide more context to downstream workflows where connected sources supply it.
Illustrative workflow only. We do not promise cost savings or replace customer review and approval controls.
Request a demo to see AP reconciliation in action — or start with the sandbox for free.