Reconcile orders across sources

One sale can appear in more than one connected system. For example, a marketplace may record the customer order while an ERP records its fulfillment. Balta Labs links matching source records to a single order so that authoritative order views can count the sale once. Original source events remain available for investigation.

Read how duplicate matching works for the principles, then create and manage a deduplication rule for the exact steps.

Inspect an order

1. Open Orders → Dashboard. Choose a period and, if needed, filter by source, country, or currency.
2. Search an order number and open the row.
3. In Order details, compare the linked Source records. The primary badge identifies the selected record used for the canonical order view.
4. Review gross, net, tax, status, and any capability gaps. A missing amount or field is not necessarily a value of zero.

Amazon orders can wait for financial data after the order itself arrives. Balta Labs marks those records as awaiting pricing. Review them again after the financial import completes.

Review matching rules

Open Orders → Configuration → Dedupe to see the active rules. A rule defines which source records should be matched and what action to take. Before activating or changing a rule, use its preview to inspect examples and counts. The preview does not change the underlying orders. Active rules are applied automatically as successful order fetches cover new dates. A manual scan of recent stored orders is available when you need to recheck them.

Keep a rule specific to the identifiers and accounts it is intended to match. Review its matched orders after activation. If two unrelated orders are linked, or one sale remains split, revise the rule and recheck the results before using the related totals.

Choose the right export view

The OSS Tax summary and Individual orders bases use the selected authoritative record for each matched order. All source events includes each original sale or refund event and can contain duplicates. Compare sources is useful for identifying amount differences between matched records. Do not sum the original source-event view as though it were a deduplicated sales total.

Correct reporting data

In an order’s side panel, choose Resolve / edit reporting data. Select a reason, then confirm a warehouse or country, change the reporting treatment, or mark the selected period reviewed. The suggested reason appears first; it does not change amounts automatically. A note, document link or private attachment is optional.

Expand Amounts and refunds by VAT rate to correct an existing sale or refund. For a partial refund, edit the recorded refund or add only the missing amount, separately for each VAT rate. Refund amounts are negative. Keep a refund’s actual reporting date even when it falls after the sale’s reporting period. Changing sale totals does not reprice the original product lines.

Save to refresh the report and exports. Corrections survive later imports; Reset to imported data restores the latest imported values and keeps the change history. If a later import changes the event grouping or brings in a refund that may duplicate a manual one, the order needs review again. You can keep the manual refund as additional or exclude a duplicate event.

The review count opens reason links and Show all in a side panel. Open full details keeps the table behind it; returning restores the same filters, sort and scroll position.