EDGEBIC + QuickBooks Integration FAQ: 12 Questions Shops Ask First

These are the questions QuickBooks shops ask in the first conversation, answered without hedging: there is no certified connector, the interface is your existing exports, the routing model that QuickBooks lacks is built once inside EDGEBIC, and nothing you import can disturb an order already running. Each answer stands on its own, so skip to whichever one you came for.

EDGEBIC by User Solutions is a finite capacity scheduling platform that sits beside your accounting system. The full walkthrough is the complete QuickBooks integration guide, and the field-level detail lives in the QuickBooks to EDGEBIC mapping reference.

Is there a certified QuickBooks connector?

No, and it is a design decision rather than a gap. EDGEBIC integrates through reusable import masks that read Excel, CSV, delimited text, or a database source. You map your export's columns onto EDGEBIC's fields once and save the mask; every run after that is two clicks. The same architecture serves QuickBooks, SAP, NetSuite, and home-grown systems identically, so there is no per-ERP connector to certify, version-match, or repair when either side upgrades. A connector is a dependency. A file is not.

Does EDGEBIC replace any part of QuickBooks?

No. QuickBooks stays the book of record for items, invoicing, purchasing, and financials. EDGEBIC reads exports, builds a finite capacity schedule against real shift hours and real machine counts, and hands dates and dispatch lists back as Excel. Order entry and accounting keep running exactly as they do today. The general case for that split is in why ERP needs a scheduling add-on, and the head-to-head is on the RMDB versus QuickBooks page.

QuickBooks has no routings. How does EDGEBIC schedule without them?

By building the routing model once inside EDGEBIC. This is the one real difference from an ERP that carries operations. Work centers are entered directly or loaded from a small spreadsheet, and routings are drawn in the graphical designer or imported from a routing file you write, one row per operation. After that one-time build, every QuickBooks order for that item reuses its routing automatically, so the effort never repeats.

What exactly has to come out of QuickBooks?

Two exports carry everything QuickBooks can contribute, and a third is optional. Items (an identifier is the only mandatory column). Open sales or work orders (item, quantity, and a date). Optionally, confirmations if you record hours in QuickBooks (job number, work center, date, and hours or pieces). Any report or list in QuickBooks that saves to Excel or CSV is a valid source.

How long until the first real schedule?

Most shops see a first finite capacity schedule from their own data in the first working session once one routing exists, and a tuned one inside two weeks. The documented benchmark in the User Solutions lineage is the Plastilite integration: 5 days, Monday to Friday, from first export to a complete optimized schedule with dates synchronized back to the ERP. That figure belongs to that case rather than being a blanket guarantee, but the method is what repeats: export, build routings once, map, schedule, tune.

Do we have to clean our item data first?

No, and trying usually costs a month. Import what QuickBooks holds today, build the routings, schedule, and compare the dates with what your planner believes. The disagreements are your defect list and they arrive specific: a wrong hours-per-unit shows up as an order finishing implausibly early, a missing setup time shows up as a machine that appears to change over for free.

What happens when QuickBooks is upgraded?

Nothing, in almost every case. The integration reads files rather than calling an interface, so there is no connector version to track and nothing to re-certify. If an upgrade renames a column heading in an export, you re-map that column in the mask once, which takes minutes. If the export is unchanged, the masks keep running exactly as they did.

Our times are per lot, not per piece. Do we rebuild the routings?

No. Put a conversion factor of 0.01 on the hours column in the routing mask, and a cell of 2.5 hours per 100 pieces lands as 0.025 hours per piece. Setup minutes on the same file use 0.016667 on their own column, so one file can carry two different units and land correctly in both. The factors are saved with the mask, which makes the conversion permanent and auditable through the per-run log.

Do imported orders schedule themselves?

No, and the separation is deliberate. An import changes data; the scheduler changes the plan. Newly imported orders appear as unscheduled demand and stay there until you run the scheduler. Before the run starts, a confirmation states the scope in plain numbers: how many jobs are being scheduled for the first time and how many existing jobs are being rescheduled. An import can therefore never silently rearrange a plant. The modes are covered in EDGEBIC scheduling modes explained.

Can an import disturb orders already running?

No, for two independent reasons. Every scheduled job carries a frozen snapshot of the routing it was planned with, so a routing change affects future jobs and leaves work in progress alone. And recorded work is never moved by any run: an operation with an actual start and an actual end is historical fact, and no reschedule, mode, or setting will shift it. On top of both, imports never schedule anything.

What if someone runs the same file twice?

Nothing bad happens, on any entity type. Master data comes back Reused (matched and deliberately left untouched) unless you explicitly enabled updates for that run. Routing imports wipe and recreate an item's steps rather than appending, so steps never accumulate. Actuals always overwrite the days a file carries, so a double import never double-counts. The import system assumes files get re-run, because in real shops they do.

What can import never bring across?

The settings that most change what a schedule looks like, because QuickBooks has no source for them. Work center groups (machine pools re-shopped on every reschedule, with per-member efficiency factors). The sequence-dependent setup matrix that lets the optimizer sequence work to cut changeover. Operator skills and rosters. Bottleneck anchoring. Lot streaming with transfer batches. Each is configured once inside EDGEBIC and then applies to every imported order afterwards. The EDGEBIC product overview maps them.

Who runs this day to day?

The planner, in about twenty minutes each morning, without IT. Involve IT exactly once, to turn the two QuickBooks exports into saved reports that land in a known folder with stable names. After that the routine is export, run the saved masks, run the scheduler, publish the dispatch lists. For the same questions answered for other platforms, the Fishbowl and Odoo FAQs follow the same shape.

Still deciding?

The fastest way to settle any of this is your own export. Pull 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 shop scheduled against its own capacity.