ERP integration · Intuit
QuickBooks EDI and B2B integration
Invoice, bill and payment integration for QuickBooks, with mapping, validation and reconciliation.
- Integration supported
- Implementation services available
- Cloud, on-premises or hybrid
Overview
Connecting QuickBooks with your trading partners
Connect QuickBooks with customers, suppliers and the applications that support your business. ECOM defines integration at the transaction and data level: the record to create or update, the fields to exchange, the business rules to apply, and the evidence that processing completed.
The scope below describes integration functions and controls that can be included in an ECOM project. Coverage is confirmed for your product version, licensed modules and business requirements. We explain ECOM’s specific connection path and deployment architecture during a live meeting.
This page sets out the scope for QuickBooks: the systems involved, the records and transaction flows, field mapping and validation, error recovery, reconciliation and rollout, with diagrams of who owns what and how a document moves through processing.
Methods
Integration approaches for QuickBooks
EDI
X12 or EDIFACT documents exchanged with customers, suppliers, carriers and banks under each partner's implementation guide, mapped to and from the QuickBooks records in scope.
PRISM-WebEDI
Web-based EDI collaboration and document processing, subject to the same QuickBooks validation and business controls as other channels.
PRISM-SmartConvert
Converts business documents into structured integration data that is validated and applied to QuickBooks under the agreed rules.
PRISM-WebConnect
Automation of trading partner portals and workflows, brought under the same QuickBooks validation and business controls.
Document mapping
How EDI documents map to QuickBooks
Typical mappings between common X12 documents and QuickBooks business objects. Actual designs depend on your configuration and partners.
| EDI document | QuickBooks object | Direction |
|---|---|---|
| 810 Invoice | Invoice | Into QuickBooks |
| 820 Payment Order/Remittance Advice | Payment | Into QuickBooks |
| 850 Purchase Order | Purchase Order where supported | From QuickBooks |
| 810 Supplier Invoice | Bill | Into QuickBooks |
Planning
Implementation considerations
Identify Online or Desktop first
Identify Online versus Desktop before defining objects. Do not assume that a sales order, stock receipt or shipment object is available in the chosen product and edition.
Preserve the record version
For Online records, preserve the current record version during changes so a stale update cannot overwrite a newer user correction. Business document number and record ID serve different purposes.
Agree who controls tax and accounting
Agree whether the source system or QuickBooks controls tax, discounts and item accounting. Preserve separate invoice, bill and payment relationships rather than treating a remittance notice as a bank payment.
Integration design
QuickBooks: scope, flows, controls and tests
The scope below describes integration functions and controls that can be included in an ECOM project. Coverage is confirmed for your product version, licensed modules and business requirements. We explain ECOM’s specific connection path and deployment architecture during a live meeting.
Editions and versions we integrate
ECOM scopes QuickBooks integration for the edition and release you run. Coverage, permitted actions and record availability are confirmed for your version, licensed modules and business requirements.
- Hosted QuickBooks Desktop / Enterprise
- QuickBooks Online (QBO)
Each edition is scoped on its own release, licensed modules and business requirements; coverage is confirmed for your environment.
The ERP environment we integrate around
QuickBooks includes distinct Online and Desktop products with different capabilities. Purchasing, inventory and sales order availability depends on product, edition, country and subscription; these cannot be assumed across all QuickBooks environments.
The design identifies QuickBooks Online company or Desktop company file, country edition and enabled features. These values determine transaction routing, record validity, ownership and the financial or operational context in which a document is processed.
Systems and ownership
| System or participant | Integration responsibility |
|---|---|
| QuickBooks | Maintain the approved ERP records, business rules, stock and financial results within the agreed module scope. |
| Customer or supplier systems | Supply orders, revisions, forecasts, invoice details and partner reference numbers; receive agreed business responses. |
| Warehouse or fulfillment application | Own physical pick, pack, dispatch and receipt facts where separately deployed. Return actual quantities and shipment references. |
| ECOM integration services | Coordinate agreed document exchanges, business data mapping, validation and processing visibility across the defined systems. |
QuickBooks keeps the approved records, business rules and results; partners supply and receive agreed business documents; a separate warehouse application owns physical facts where one is deployed; and ECOM coordinates document exchange, mapping, validation and visibility. A system of record is decided for each data group.
A system-of-record decision is made for each data group. For example, partner purchase order numbers can originate externally while ERP order numbers are assigned by the ERP. External instructions do not automatically authorize changes to item masters, tax settings, accounting periods or payment details.
Input channels can include EDI, PRISM-WebEDI, PRISM-SmartConvert documents and PRISM-WebConnect portal activity, each subject to the same agreed ERP validation and business controls.
ERP records in the proposed scope
- Customer
- Vendor
- Product or service Item
- Invoice
- Credit Memo
- Bill
- Payment
- Purchase Order where supported
Record availability and permitted actions are checked against the installed environment; the list is a functional scope inventory rather than a claim that every record is enabled in every edition.
Transaction flows and processing rules
Direction is relative to QuickBooks. Each flow is defined by its source, target business record, release condition and successful result. Creation, update, cancellation and enquiry are scoped separately.
Each flow has a source, a target business record, a release condition and a successful result. Creation, update, cancellation and enquiry are scoped separately for QuickBooks.
| Business flow | Direction | Processing and completion rule |
|---|---|---|
| Customer invoice | Into ERP | Use the approved billing event from the source system. Map customer, item or account lines, currency, tax, discounts and external order references. |
| Invoice state | Out of ERP | Return assigned record ID, document number, amount and processing result. A created invoice is not proof of shipping or payment. |
| Supplier bill | Into ERP | Validate vendor, supplier invoice number, dates, account or item lines, totals and PO references where supported. |
| Purchase order | Out of ERP where supported | Publish the approved purchasing document and subsequent authorized revisions; retain the ERP document reference. |
| Customer payment | Into ERP where scoped | Apply an authorized payment record to the correct invoice and customer. Distinguish remittance advice from actual bank settlement. |
| Credit or correction | Both as scoped | Use the appropriate credit, void or adjustment workflow for the product and posting state. Reconcile the remaining balance. |
| Order and stock context | Both where supported | Exchange sales order, item and availability information only for supported features; retain physical fulfillment in the responsible system. |
Partner documents and business meaning
X12 examples include 850 orders, 860 order changes, 855 order acknowledgments, 856 shipment notices, 810 invoices and 820 payment or remittance advice. Relevant EDIFACT messages can be scoped for international partners. A 997 or 999 technical acknowledgment is tracked separately from business acceptance. Document selection follows the partner’s implementation guide, not the ERP product name.
A small supplier needs retailer-facing EDI while keeping QuickBooks for bookkeeping. ECOM can separate the retailer document process from the accounting records that QuickBooks actually supports.
Data mapping and validation
We define a mapping specification at header, line and related-document level. It records source meaning, target business field, transformation, required condition, default ownership and rejection behavior. Partner identifiers remain traceable after ERP identifiers are assigned.
| Data group | ERP fields or business attributes | Validation rule |
|---|---|---|
| Organization | Company, Class or Location where enabled | Validate QuickBooks Online company or Desktop company file, country edition and enabled features. Reject unknown or unauthorized combinations. |
| Trading party | CustomerRef, VendorRef | Resolve partner identifiers to approved ERP accounts and locations. Do not match solely on a free-text name. |
| Product identity | ItemRef, AccountRef as applicable | Map buyer and supplier item aliases to the correct ERP product. Check variants, revisions and active status where relevant. |
| Quantity and unit | Line Quantity, Unit Price, Linked Amount | Keep each quantity distinct. Apply approved pack or unit conversion, precision and rounding rules; reject an unknown conversion. |
| Dates | TxnDate, DueDate | Preserve meaning, time zone and date-only values. Reject invalid formats and identify stale revisions. |
| Price and money | CurrencyRef, Tax Detail, Discount, Total Amount | Define the authoritative price and tax calculation. Reconcile line extensions and document totals within approved tolerances. |
| References | Id, DocNumber, LinkedTxn, SyncToken for Online updates | Use stable line references across splits and updates. Retain original order, shipment, invoice and correction links. |
| Extensions | Supported custom transaction fields | Agree field ownership, allowed values and length. Do not silently truncate values or discard unmapped required data. |
Field labels above identify business attributes; exact technical names, availability and allowed write actions are verified for your release. They do not disclose ECOM’s connection method.
Identity and duplicate control
The business identity starts with company + source system + source transaction ID + document type. The final rule also distinguishes a new document, a retransmission and a legitimate revision. ERP-assigned IDs are recorded after successful creation. A retry reuses the same business identity instead of creating a second order or invoice.
Processing control and error recovery
Business state controls the next action
For QuickBooks, the design evaluates draft or approved source transaction, accounting record creation, payment application and controlled correction. A document is not considered complete simply because it arrived or passed a format check. Completion requires the intended ERP business result and its returned reference.
| Processing stage | Required evidence and next action |
|---|---|
| Received | Assign a correlation reference, retain the source identity and record receipt time. Check whether this is a duplicate or new revision. |
| Validated | Confirm required fields, authorized organization, master data, quantities and business rules. Reject or hold a failed document before unintended posting. |
| Submitted | Record the intended target action and processing attempt. Submission is an intermediate state, not evidence of ERP acceptance. |
| Accepted or held | Capture the ERP business record ID or a specific rejection or hold reason. Distinguish a business hold from an unavailable system. |
| Completed and reconciled | Confirm the agreed milestone, expected line results and outbound response. Reconcile source identity to ERP and partner references. |
For QuickBooks, the design evaluates draft or approved source transaction, accounting record creation, payment application and controlled correction. A document is not considered complete simply because it arrived or passed a format check. Completion requires the intended ERP business result and its returned reference. Held or rejected documents are corrected and replayed with the same business identity, so a retry never creates a second order or invoice.
Changes and sequencing
Process a dependent change against the correct original record and current revision. If a change arrives before the order exists, retain it for controlled review or dependency handling. Define a cut-off state after which quantity, price or ship-to changes require an exception or formal correction. Posted financial history is corrected through the authorized business process.
Safe retry and uncertain results
Temporary availability failures can be retried under an agreed retry limit and escalation policy. Invalid items, closed periods and missing approvals need correction rather than blind retries. When a submission times out, first determine whether the ERP already created the record. An unknown result must not be converted immediately into a new create request.
For multi-step flows, retain completed steps and resume only the incomplete authorized action. An order created successfully must not be recreated because its acknowledgment failed. Recovery should retain original references, corrected values, attempt history and the responsible user or process.
Reconciliation and operational ownership
Reconcile document counts, line counts, quantities, monetary totals and business references at the agreed interval. Identify documents received without ERP results, shipments without required notices, invoices without partner delivery results and aging exceptions. Assign an owner and response target for each exception category. Set the interval and service targets from business deadlines and measured ERP capacity.
QuickBooks-specific integration requirements
Design requirement 1: Identify Online versus Desktop before defining objects. Do not assume that a sales order, stock receipt or shipment object is available in the chosen product and edition.
Design requirement 2: For Online records, preserve the current record version during changes so a stale update cannot overwrite a newer user correction. Business document number and record ID serve different purposes.
Design requirement 3: Agree whether the source system or QuickBooks controls tax, discounts and item accounting. Preserve separate invoice, bill and payment relationships rather than treating a remittance notice as a bank payment.
Example integration sequence
A small supplier needs retailer-facing EDI while keeping QuickBooks for bookkeeping. ECOM can separate the retailer document process from the accounting records that QuickBooks actually supports.
- Receive an approved transaction from the responsible order or billing system and retain its source reference.
- Resolve customer or vendor and item or account coding in the correct company or organization.
- Validate tax ownership, dates, currency and totals before the accounting action.
- Capture the resulting accounting record ID and document number, then return a processing result to the source.
- Apply authorized payments or credits to the original record and reconcile the remaining balance.
Security, testing and production rollout
Security and access requirements
Define access by business action and organizational scope. Separate permissions for reading masters, creating documents, changing open records, releasing transactions and viewing financial data. Use dedicated integration identities and approved credential management; avoid shared administrator access. Keep customer environments and partner configuration boundaries explicit.
Agree protection of data in transit and at rest, secret rotation, audit retention and masking of sensitive logs. Restrict test datasets and exception screens to authorized users. Changes to payment details or sensitive master data require separate business authorization; ordinary transaction processing must not silently update them.
Acceptance tests
| Test condition | Expected evidence |
|---|---|
| Valid transaction | One intended ERP result with correct organization, party, lines, quantities, amounts and external references. |
| Replay and duplicate | A replay does not create a second business record or duplicate a stock or financial movement. |
| Invalid master data | An unknown item, location or account produces a clear exception and no unintended posting. |
| Partial transaction | The completed quantity and remaining quantity reconcile across the original and related records. |
| Revision conflict | A stale or late revision does not overwrite newer or completed business activity. |
| Uncertain submission | A timeout after submission is resolved by checking the business outcome before another create action. |
| Volume and cut-off | Representative peak volume meets agreed deadlines with measured backlog, processing duration and recovery behavior. |
| Authorization | An identity cannot access another company or perform an unapproved release, master-data change or finance action. |
Controlled rollout
Approve the transaction list, mapping rules and success criteria first. Test representative partner documents in the agreed nonproduction environment, then complete partner certification where required. Reconcile opening references and queued documents before production cutover. Start with a defined partner or transaction set and monitor actual results before expanding coverage.
The rollout plan identifies who can pause processing, how queued work is retained, how already posted documents are corrected, and when operations resume. ERP upgrades, cloud releases, new partner requirements and mapping changes require impact review and regression tests for affected flows.
Initial synchronization and cutover data
Define the initial data population separately from ongoing transaction processing. Identify which active customers, suppliers, products, locations and reference values are required before the first live document. Include only the open orders, balances or historical references that the agreed business scope needs. Record source ownership, extraction time and the reconciliation totals for the opening population.
During cutover, distinguish transactions already processed in the previous environment from transactions waiting to be processed. Preserve original partner references and ERP identifiers for open documents. Establish how changes made during the cutover window are captured and reconciled. A historical document used for reference must not accidentally be replayed as a new stock or accounting transaction.
Processing frequency and capacity
Assign a frequency to each flow rather than one timing promise for the entire integration. Urgent order changes, periodic inventory availability, shipment notices and financial reconciliation have different deadlines. Agree the peak document rate, typical and largest line counts, permitted backlog, ERP maintenance windows and the oldest acceptable unprocessed transaction.
Measure acceptance time, business completion time and partner response time separately. Test the effect of an ERP outage and the rate at which accumulated work can safely resume. Publish operating targets only after representative testing; a successful small sample does not establish peak-volume capacity or a guaranteed near-real-time service level.
QuickBooks integration FAQs
How quickly are transactions processed?
Timing is defined by business need, ERP capacity and partner deadlines. The design distinguishes event-driven business triggers, scheduled processing windows and bulk reconciliation requirements without promising an unmeasured latency.
What happens when the ERP rejects a transaction?
The operating design identifies the failed document, relevant fields, business reason and responsible owner. Correction and replay must preserve the original identity and prevent duplicate posting.
What will ECOM explain during the live meeting?
We review the actual connection path, hosting and deployment requirements, environment prerequisites and detailed technical responsibilities after understanding your ERP and scope.
Keep exploring
Related
Solution
ERP Integration
Connect your ERP to trading partners through EDI, APIs, IDocs, files and connectors.
Service
ERP Implementation
ERP implementation for SAP, Oracle, Microsoft, NetSuite, Infor, Epicor, QAD and Sage, with B2B integration built in.
Solution
EDI Integration
Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.
Integrating or implementing QuickBooks?
Bring your QuickBooks version, installed modules, priority transactions, sample documents and known exceptions. ECOM will review the required systems integration, explain the specific integration path during a live meeting and define a practical implementation scope with your team.