Skip to main content

Transactions

What a Transaction is in iPaaS.com: the order/sale header, the money totals and buyer it carries, the child records, and why it's the canonical order everything reconciles against.

How iPaaS.com Thinks About Transactions

A Transaction is the order/sale document header - a single commercial event such as an order, invoice, quote, return, or job. Other systems call it an Order, Sales Order, Sale, Invoice, Receipt, Quote, or Document.

The transaction header carries the money totals (subtotal, tax, shipping, discount, total), a type and status, timestamps, and the buyer it belongs to. Everything else is a child record of it: Lines (what was bought), Addresses (ship-to and bill-to), Taxes, Payments, Tracking, Notes, and Discounts.

The transaction is the canonical order record iPaaS.com sits in the middle of. A storefront captures the order, an ERP invoices and fulfills it, a 3PL ships it, a POS rings it - and they all reconcile against the one iPaaS.com transaction rather than against each other. Order sync is the highest-value flow in most integrations. Every transaction resolves to a buyer: it must carry a customer, a company, or at least an email address.

iPaaS.com also has the concept of a related or child transaction that can be used to link a return, refund, invoice or other independent transaction to the parent.

Did this answer your question?