# What teams build in Prowork for reconciliation > What reconciliation flows in Prowork actually do: inventory across ERP, WMS and storefront, cash against open invoices, card spend against the ledger. Source: https://parabola.io/reports/reconciliations --- ## What gets built After general reporting and system connectivity, reconciliation is the most-built category in Prowork, and the shape of it is consistent: two or more systems hold a version of the same record, and somebody has to decide which one the business should act on. Of the 139 companies whose usage went into this study, 109 run some version of this work in Prowork, spread across 1,633 flows that were active in the last 90 days. Grouping those flows by what each one actually does gives the breakdown below. Flows by build patternInventory Reconciliation & Reporting1,130Cash Reconciliation337BOM Reporting & Reconciliation86Deferred Revenue Reconciliation42Three-Way PO Match38flows active in the last 90 days Inventory Reconciliation & Reporting is the largest of those patterns at 1,130 flows across 97 companies, with Cash Reconciliation accounting for another 337 across 43 companies. The grouping follows what a flow does rather than which team happens to own it, which is why one company often turns up in several of these rows at once, and the businesses building the most of them work in health and beauty, apparel, and food and beverage. ## Three of them in detail Three of those flows in more detail, described by what each one does rather than by who built it. Company names are withheld, so each is identified only by the size and category of the business running it. **A $50M+ logistics provider.** Maintains up-to-date stock, dispatch, and shipment reporting for customer-specific warehouse inventory. Gives operations teams a clean view of inventory status, weights, storage aging, dispatch activity, and shipment documentation so they can track fulfillment and share accurate status updates. Built on Google Sheets, Smartsheet. **A $25M+ consumer goods brand.** Unifies warehouse, virtual inventory, order, inbound shipment, forecast, and cost data into a single SKU-level inventory view. Built on API, Google Sheets. **A $100M+ software company.** Captures bank ACH confirmation details and standardizes the key totals needed for reconciliation. Helps finance verify cash movement files faster, confirm expected totals and item counts, and reduce manual review of bank notifications. Built on API, email attachments. ## What they have in common Read enough of these flows and the same shape keeps appearing. A flow pulls the same records from each system that holds a version of them, standardizes whatever identifiers are needed before those records can be joined at all, applies the comparison or the calculation as explicit logic, and then labels every row with an outcome so that the handful needing attention can be routed to whoever is able to act on them. What differs from one flow to the next is which single step genuinely calls for interpretation. Reading a supplier PDF, resolving a merchant name that never quite matches the ledger, or deciding which category a vague line description belongs in are all handled by AI steps inside the flow, while the matching rules, the tolerances and the thresholds around them stay explicit, since those are the parts a controller or an auditor will eventually want to read for themselves. Most of these run on a schedule or fire from a trigger rather than waiting for someone to remember to open them, and that is largely what separates a report describing what happened last month from a process that surfaces the problem while there is still time to do something about it. The sources they read from are worth noting, because they are rarely the tidy ones. Across the documented flows in this category the most common inputs look like this: Systems these flows read fromEmail attachments122Google Sheets69NetSuite42Direct API31SharePoint17Email12Slack11FTP / SFTP9documented flows reading each source Email attachments and spreadsheets sit at the top of that list on most pages, which is a fair description of where operational data actually lives once it leaves a system of record. ## Reconciliation prompts to start from - [Multi-warehouse inventory consolidation](https://parabola.io/use-cases/multi-warehouse-consolidation) — Multi-warehouse consolidation combines the stock positions of every location into one table, so a SKU has a single total available quantity across the network rather than a… - [Ramp to NetSuite reconciliation](https://parabola.io/use-cases/ramp-netsuite-reconciliation) — Card spend reconciliation proves that every transaction on the corporate card platform has a matching entry in the general ledger, and that every entry in the ledger traces back… - [Cash reconciliation](https://parabola.io/use-cases/cash-reconciliation) — Cash reconciliation matches money that landed in the bank against the invoices it was meant to pay, then applies each payment so the receivable clears. - [Deferred revenue reconciliation](https://parabola.io/use-cases/deferred-revenue-reconciliation) — Deferred revenue is money collected for something not yet delivered. - [Digitize CIPLs & validate them against your POs](https://parabola.io/use-cases/cipl-digitization-validation) — The commercial invoice and packing list — the CIPL — is the document pair that travels with an international shipment. - [Flexport inventory reconciliation](https://parabola.io/use-cases/flexport-inventory-reconciliation) — Inventory reconciliation is the process of comparing the on-hand quantity for every SKU across each system that claims to know it — the forwarder or 3PL, the ERP, the storefront —… - [Inventory reconciliation](https://parabola.io/use-cases/inventory-reconciliation) — Inventory reconciliation is the process of comparing the on-hand quantity for every SKU across each system that claims to know it — the ERP, the storefront, the warehouse system,… - [Marketplace delivery date audit](https://parabola.io/use-cases/marketplace-delivery-date-audit) — A delivery date audit compares the delivery date a marketplace promised the customer against the date the carrier actually delivered, order by order, and counts the misses by… - [Sales channel consolidation](https://parabola.io/use-cases/order-consolidation) — Sales channel consolidation normalizes orders from every place you sell — direct storefront, marketplaces, retail, wholesale — into one schema, then stacks them into a single… - [Three-way PO matching](https://parabola.io/use-cases/three-way-po-match) — Three-way matching compares three records of the same transaction before a vendor gets paid: the purchase order that says what you asked for, the receipt that says what arrived,…