Adapter Summary
The Reports > Adapter Summary screen is the queue of everything Fusionware is sending — or trying to send — to your connected accounting/ERP system. It isn’t a financial statement; it’s a troubleshooting view for the sync itself, showing what’s queued, what’s stuck, and why.
This page covers what an “adapter” is, what the report shows, how to resolve stuck items, and a general overview of what Fusionware sends to accounting systems and how it gets matched to the right accounts.
On this page:
- What Is an Adapter?
- The Adapter Summary Screen
- Resolving Stuck Items
- What Gets Sent to Accounting
- How Records Get Matched to Your Accounts
- Settings That Affect What Gets Sent
- Permissions
What Is an Adapter?
An adapter is the configured connection between your Fusionware account and one external accounting or ERP system — QuickBooks Online, QuickBooks Desktop, Microsoft Dynamics GP, Sage, Odoo, or a few other supported platforms. It’s set up once, during integration onboarding, and from then on Fusionware uses it to push financial activity out automatically (or on request) so you don’t have to re-key orders, invoices, or settlements into your accounting system by hand.
Each customer account normally has one adapter, though AR (customer invoices) and AP (vendor/grower payables) can be routed to two different connections if your setup calls for it — see Settings That Affect What Gets Sent.
The Adapter Summary Screen
Reports > Orders > Adapter Summary opens /reports/adaptersummary.
This screen lists every item currently in the outbound sync queue for your account — anything that hasn’t finished sending successfully yet, plus anything that’s stalled or failed.
| Column | Description |
|---|---|
| Order | Links back to the order on the Order Board, when the queued item is tied to one |
| Type | What kind of record this is — new order, customer invoice, grower/vendor settlement, adjustment, etc. (see What Gets Sent to Accounting) |
| Status | Where the item is in the sync process (see below) |
| Message | A short description of what happened — useful for spotting why something failed |
A search box at the top filters the list by order number or record type.
Status Meanings
| Status | What It Means |
|---|---|
| Not sent yet | Queued, waiting to be picked up |
| Running | Currently being sent |
| Item taking longer than normal | It’s been running for a while without finishing — usually worth investigating |
Once an item sends successfully, it drops off this list — the report only shows items that are still pending or that failed, not your full sync history.
Row Actions
| Action | What It Does |
|---|---|
| Resend | Puts the item back at the front of the queue to try again |
| Delete | Removes the item from the active queue. This does not undo anything on the accounting-system side — use it to clear out an entry you don’t need retried, not to reverse a transaction. |
Resolving Stuck Items
A typical scenario: an order was placed or invoiced, but it’s still sitting in Adapter Summary instead of showing up in your accounting system.
- Open Reports > Adapter Summary and search for the order number.
- Check the Status and Message columns:
- “Not sent yet” with no message usually just means it hasn’t been picked up yet — give it a moment.
- “Item taking longer than normal” or an explicit error message means something needs attention.
- A common cause of failures is a missing mapping — a customer, product, vendor, or location on the order that hasn’t been linked to its counterpart in your accounting system yet. Add the missing link under Settings > Order > Mappings, or check Settings > Order > Unmapped for a record flagged as unresolved.
- Once the underlying issue is fixed (mapping added, account corrected, etc.), click Resend on the row. It goes back into the queue and tries again.
- If it keeps failing after the mapping looks correct, contact support with the order number and the message shown — it may point to a configuration issue on the adapter itself.
What Gets Sent to Accounting
Fusionware doesn’t replace your accounting system — it summarizes the financial side of each order and pushes it over so it doesn’t have to be entered twice. As a general rule of thumb, these are the kinds of entries that get queued and sent:
| Entry Type | What It Represents |
|---|---|
| New Order | The order itself, once placed |
| Customer AR | The customer invoice for the order — accounts receivable |
| Grower AP | Grower settlement payables |
| Vendor AP / Freight AP | Vendor and freight payables tied to the order, one entry per vendor |
| Freight Advance | An advance payment issued to a carrier |
| Customer / Vendor Adjustment | Manual financial adjustments made against a customer or vendor |
| Product Protest | Quality-claim credits/adjustments |
The General Flow
- A financial event happens in Fusionware — an order is placed, a settlement is created, an adjustment is saved.
- Fusionware builds a package of the relevant lines: the AR side billed to the customer, and a separate AP block for each vendor or grower involved, along with the reference IDs your accounting system needs to recognize the customer, product, and vendor.
- That package is placed in the sync queue — the same queue shown on the Adapter Summary report.
- Your accounting system’s connection picks it up, creates the matching entry on that side, and reports back success or failure.
- On success, the entry drops off the Adapter Summary report and the order is marked as synced. On failure, it stays on the report with a message explaining what went wrong, and can be resent once resolved.
When Entries Are Sent
Fusionware doesn’t have a built-in “accrual” or “cash-basis” setting — there’s no toggle that changes timing based on your accounting method. What actually determines timing is the specific event each entry type is tied to, and that differs by entry:
- Customer AR (the invoice) — Queued automatically at one specific point in the order lifecycle: when the order’s status changes to Invoiced (
Pending → ... → Delivered → Ready to Invoice → Invoiced → Paid in Full). It is not sent when the order is placed, and not sent automatically at Delivered — Invoiced is a distinct, later step. It fires once per order this way; sending again after that requires a manual resend (Send to ERP on the order, or Resend on this report). - Grower AP, Vendor AP, and Freight AP — Not tied to any automatic order-status event. Each is sent when someone clicks the corresponding button on the order’s Accounting Summary tab — Save Grower AP, Create Freight AP, or the per-vendor Send AP. Nothing about delivery, receiving, or order completion pushes these out on its own. Exception: if your adapter has AR/AP Separate turned on, any AP lines that haven’t been sent yet are automatically bundled in alongside the Customer AR entry the moment the order hits Invoiced — see Settings That Affect What Gets Sent.
- Freight Advances, Adjustments, and Product Protests — Same pattern as AP: each is sent when the corresponding action is taken (issuing the advance, saving the adjustment, recording the protest), not on any automatic schedule.
If you book on an accrual basis, keep in mind:
- Revenue lands in your accounting system on a fixed schedule tied to the Invoiced step — not order date, not ship date. If your policy expects revenue recognized earlier (e.g., at delivery), expect a gap between delivery and when the invoice entry actually syncs, since Invoiced is a separate, manual/administrative step from Delivered.
- Expenses (grower/vendor/freight AP) depend entirely on when your team sends them — there’s no automatic trigger tied to receiving product or completing the order. Recording the liability as soon as it’s incurred depends on your team sending the AP entry promptly.
- Each entry carries both the original order date and the invoice date (see below), so your accounting system has both available — but which one it actually posts as the transaction/GL date depends on how your integration is configured on the accounting side, not on Fusionware. If a specific GL date matters, confirm that mapping with support for your adapter.
What’s Included in Each Entry
Every entry includes an order header block and one or more line items. Field availability varies slightly by accounting system, but in general:
Order Header
| Field | Notes |
|---|---|
| Order Number, PO Number | |
| Customer | Includes the customer’s mapped ERP account reference |
| Origin / Destination | Location name, address, and mapped ERP reference |
| Carrier | Name, SCAC, DOT number, and mapped ERP reference |
| Sales Terms / Pay Terms | |
| Order Date | The date the order was originally placed |
| Invoice Date | The date the order reached Invoiced status — set once, at that transition |
| Load / Ship / Delivery Dates | |
| Salesperson / Booked By | |
| Commodity |
Line Items — Customer AR / Invoice Entries
| Field | Notes |
|---|---|
| Product | Mapped to your accounting system’s item/product reference and GL account |
| Order Qty, Shipped Qty, Delivered Qty, Invoiced Qty | Tracked separately — these can differ if quantities were adjusted after the order was placed |
| Rate / FOB, Total |
Line Items — Grower/Vendor/Freight AP Entries
| Field | Notes |
|---|---|
| Vendor | Mapped to your accounting system’s vendor reference |
| Product or Item | Mapped to the item’s GL account |
| Quantity, Rate, Total |
Quantities, rates, and totals reflect what’s on the order at the moment the entry is sent — if a line item is adjusted after an entry has already synced, that change doesn’t retroactively update the entry that already went out. A new adjustment entry is what carries the change over.
How Records Get Matched to Your Accounts
Two things work together to make sure a Fusionware order lands in the right place in your accounting system:
- Mappings (Xrefs) — translate a Fusionware customer, vendor, product, location, carrier, etc. into the matching record your accounting system expects. This is the same mapping system behind Settings > Order > Mappings; it’s what generates the “missing mapping” errors seen on the Adapter Summary report.
- ERP Account — a reference on a product or item record that ties it to a specific account in your accounting system, so revenue and cost from that product post to the right place. This is set on the product/item itself, separately from the Mappings screens.
If either is missing for something referenced on an order, the sync for that order will typically fail with a message pointing at the missing link.
Settings That Affect What Gets Sent
These live on the adapter configuration itself (set up during onboarding — contact support to change them):
| Setting | Effect |
|---|---|
| Send to ERP | Master switch — whether this adapter is allowed to receive pushes at all |
| Manual Push Only | When on, entries don’t queue automatically as events happen — someone has to manually send or resend them |
| AR/AP Separate | When on, customer invoices (AR) and vendor/grower payables (AP) are routed to two different accounting connections instead of one |
Permissions
| Permission | What It Controls |
|---|---|
| Reports > Adapter Summary | Access to the Adapter Summary report |