For CIOs and CFOs: keep SAP B1 as the untouched finance system of record. Worldover runs above it. No shadow spreadsheets, no monthly CSV reconciliation, no risk of one team's data quietly diverging from the other's.

For IT leads: no per-tenant custom code. Field mappings are configuration. Upgrades to SAP B1 don't break the connector.

• Items: created in Worldover from the substance and formula record, pushed to SAP B1 as inventory items.
• Business partners: customers and suppliers sync both directions, with SAP B1 as the master where finance already runs.
• Purchase orders: raised in either system, mirrored in the other with goods-in against the PO in Worldover.
• Sales orders: raised in Worldover for manufacturing-driven flows, in SAP B1 for pure trading flows, mirrored either way.
• Stock movements: batch and lot movements owned by Worldover, financial stock value posted to SAP B1.
• Invoices: raised in SAP B1 from the shipped sales order.

SAP B1 stays the general ledger and consolidated financial reporting layer. Worldover owns the substance master, formula, BOM, batch record, QC results, deviations, CAPA, regulatory documentation and customer document portal. The split is deliberate: SAP B1 is a good finance tool and a mediocre substance database; Worldover is the reverse.

The connector deploys in 2 to 4 weeks alongside a Phase 1 Worldover implementation (typically 12 to 16 weeks). Field mappings are configuration, not code, so scope changes during implementation don't extend the timeline.

SAP B1 on-premise (SQL and HANA) and SAP Business One Cloud are both supported. The connector uses the SAP B1 Service Layer API where available and DI Server where not, so authentication and change tracking are standard SAP-supported patterns.