EDGEBIC + QuickBooks: The Complete Scheduling Integration Guide

Integrating QuickBooks with EDGEBIC means exporting the items, customers, and open orders QuickBooks already holds to Excel or CSV, mapping those columns once with a reusable import mask, and letting EDGEBIC schedule the work against finite capacity: real shift hours, real machine counts, and sequence-dependent setups. Because QuickBooks is an accounting system rather than a manufacturing one, the routing model (work centers, operation sequence, run and setup times) is built once inside EDGEBIC and reused on every order after that. Executable dates then export back for your team and your customers. There is no add-in inside the company file and no certified connector to maintain through an upgrade.

EDGEBIC by User Solutions is the newest generation of a scheduling line that has integrated with business systems this way since 1991. Across 35+ years the same file-based approach has fed schedules for the US Navy, GE, BAE Systems, and Cummins, including Cummins scheduling across 33 locations from AS400-era data. This guide covers the QuickBooks case specifically: what to export, where the routing model comes from, what the engine does with the result, and what a realistic first two weeks looks like.

Where QuickBooks stops and detailed scheduling starts

QuickBooks is very good at being the book of record. Items, invoicing, purchase orders, customer balances, and financial reporting all belong there and should stay there. QuickBooks Enterprise even carries inventory assemblies with a bill of materials. What it does not carry is the manufacturing layer a planner needs every morning:

• Which of these open orders actually fits on the constraint machine this week?
• If the rush job jumps the queue, which promised dates slip and by how much?
• Is the CNC cell loaded to 80 percent or 140 percent next Tuesday?

Those are finite capacity questions, and answering them means modeling shifts, machine instances, changeover sequences, and operator skills against every open order at once. QuickBooks has no work-center or operation concept to answer them with, which is exactly why a dedicated scheduling layer beside it is the standard pattern. The general argument is in finite versus infinite capacity scheduling, and the wider comparison of the two products is on the RMDB versus QuickBooks page.

The integration in one table

The EDGEBIC ERP integration architecture is identical for every system, QuickBooks included:

An import mask is a saved recipe. It remembers which kind of data you are importing, what format it arrives in (an Excel workbook, or comma, semicolon, tab, or space delimited text), whether the first row carries headings, and how each column of your file maps onto an EDGEBIC field. You build it once by dragging your file's column headings onto EDGEBIC's target fields. Every run after that is two clicks: pick the mask, press Do It.

Every row in your file produces exactly one outcome: Created, Updated, Reused (found and deliberately left alone), or Failed (rejected, with the reason recorded). A result dialog shows the counts and a per-run log file records every row. Nothing half-imports silently.

Step 1: export items and open orders from QuickBooks

Two exports carry everything QuickBooks can contribute to a schedule.

1. Items. The item name or number, description, unit of measure, and any cost or price columns you want visible. The identifier is the natural key and matching is case-insensitive, so PUMP-A in the file finds Pump-A in the database.
2. Open sales or work orders. Item, quantity, order reference, and dates. In QuickBooks Enterprise these come from the open sales order report or the assembly build list, whichever your process uses.

Any report or list in QuickBooks that saves to Excel or CSV is a valid source. You are not writing an add-in, not touching the company file directly, and not asking anyone for a new interface. The file is the interface, which is why nothing here enters your accounting system.

Step 2: build the routing model once

This is the step that is different for QuickBooks, because the routing data does not exist in the ERP. You supply it one time, and you have two clean options:

• Draw it. In the graphical routing designer you place each operation on a work center, set hours per unit and setup time, and connect the steps in order. Best for a handful of products or when engineering wants to see the flow.
• Import it from a spreadsheet. Write one row per operation (end product, work center, sequence number, hours per unit, setup time) and load it through the BOR mask. Best for dozens or hundreds of routings you can lay out in Excel.

Either way, number sequences in gaps of 10 so inserting a deburr step next quarter becomes 25 and nothing renumbers. Work centers are entered the same two ways: typed in directly, or loaded from a small spreadsheet that carries the field that matters most, Number_Of_Instances, the count of identical machines each center holds.

Step 3: why the routing import takes two passes

Routings are the hardest data to build because operations reference each other: step 10 feeds step 20 feeds step 30. A naive row-by-row import cannot wire those links, because step 20 does not exist yet when step 10 is written.

EDGEBIC's routing import therefore runs in two passes. Pass one reads and validates every row, auto-creates any work center or product the file names that does not exist yet, and buffers the steps. Pass two groups the buffered rows by end product, sorts them by sequence number, writes them, and then wires the chain: 10 to 20, 20 to 30, and the terminal step to the finished product so the routing renders as one connected flow.

Two conventions save time later. Keep all of one product's steps in one file, because a routing import wipes and recreates that product's steps once per run, which is what makes re-imports idempotent. And re-importing is safe for running orders, because every scheduled job carries a frozen snapshot of the routing it was planned with, so a routing change applies to future jobs and leaves work in progress untouched.

Step 4: orders in, then run the scheduler

The order import maps item, quantity, reference, and dates. When your export carries an order reference, rows sharing that reference group under one sales order and their jobs auto-number as {Ref}-{line}, which keeps a multi-line order together instead of scattering it.

One rule matters more than any other: imports never schedule anything. After the run, imported orders sit as unscheduled demand. You then run the scheduler, which states its scope before it plans (how many jobs are new and how many existing jobs are being rescheduled), and the new work slots around everything already committed on the floor. Data movement and planning stay separate on purpose, so an import can never silently rearrange a plant. The modes are covered in EDGEBIC scheduling modes explained.

Once the data is in, the whole engine applies to your QuickBooks work: finite capacity across multiple shifts and machine instances, work center groups that re-shop the machine pool on every reschedule, a sequence-dependent setup matrix, lot streaming with transfer batches, operator skills, and mathematical optimization with a proven optimality gap. The EDGEBIC product overview maps the engine.

Step 5: sending executable dates back

The return trip is Excel. The Job View grid exports the job schedule as a workbook with colored cells and a legend sheet. The work center schedule exports the same way, and every report dialog exports to Excel or PDF using the column layout you saved, which turns a dispatch list into a saved report rather than a document someone rebuilds each morning.

From there, revised dates go back into QuickBooks through whatever date field your order process already uses. There is no automated write-back, which is deliberate: your accounting data stays under your team's control and inside your existing process. The category framing for this split is on the ERP scheduling add-on page.

A realistic first two weeks

The method behind this guide has a documented benchmark in the User Solutions lineage: at Plastilite Corporation the ERP vendor itself recommended User Solutions scheduling, and the team went from first export to a complete optimized schedule with ERP integration in 5 days. QuickBooks shops usually spend the extra runway on the routing build rather than on the exports, because the item and order files are trivial to map.

If you are starting from an empty database, the green-field setup walkthrough covers the sequence in detail, and the QuickBooks to EDGEBIC data mapping reference is the field-level lookup you keep open while building masks.

Prove it with your own export

The fastest evaluation is not a feature list, it is your own file. Export this week's open orders and your item list, then bring them to a demo. Mapping them live takes minutes, and once one routing exists you leave having watched your own plant scheduled against its own capacity. Shops weighing several systems can also read the Fishbowl and Odoo versions of this guide: the method is identical, which is the point.