CertiReplica and B1 InterCompany
An alternative to B1 InterCompany for master data replication
Boyum's B1 InterCompany is the usual choice for replicating master data between SAP Business One companies. Its manual was read page by page before a line of CertiReplica was written. This page sets the two side by side for master data, says where each stops, and says what CertiReplica does not do.
How to read this. The left column describes B1 InterCompany's master data replication as its own manual describes it, as we read it in November 2026. Products change: check the current documentation of both before you decide. B1 InterCompany also covers document scenarios between companies (invoice to invoice, drop-ship, consolidation), which CertiReplica does not: see what CertiReplica does not do.
| B1 InterCompany | CertiReplica | |
|---|---|---|
| Objects | Five: items, business partners, equipment cards, bills of materials, G/L accounts | 32 objects in the catalogue, 29 of them proven on a real system. An object is one description, not new code: items, business partners, price lists, special prices, bills of materials, G/L accounts, and the setup tables they depend on. The list |
| Setup data | Item groups, price lists, payment terms and the like are never created in the target. Someone creates them by hand in every company, then maps them | Replicated like any other object, or created on the way: an item brings its missing item group and manufacturer along |
| Landscape | All databases on one SQL Server instance; one setup per server; test and production on separate servers | Any mix of servers, on premise and hosted: each company only needs a Service Layer address. Test and production live side by side as landscapes that a rule can never cross |
| Footprint and privileges | An add-on started in every company; a database superuser (sa or SYSTEM); the right to create databases; Transaction Notification turned on; user-defined fields in every company | None in the company. One dedicated SAP user per company, whose authorisations are the limit of what can be written |
| Branches, different system currencies | Not supported | Nothing in the engine depends on either |
| Direction | One source and one target per setup row; one way | One rule feeds many targets; any company can be a source. A rule can be two-way, field by field, and for the rows of lists too |
| Codes | Must be the same in both companies | May differ: a key template such as B-{key}, and a cross-reference per record |
| Mapping | A fixed list of lookups; no units of measure, distribution rules or projects | One mechanism for every object: a mapping and a replicated record are the same kind of link |
| Field control | On or off, add or add-and-update, other property, constant | Replicate, on creation only, leave alone, constant, copy from another field, template; patterns such as U_*; all fields or only listed fields |
| Which records | One "IC Synchronize" checkbox and a hand-written SQL condition | A condition builder, with no SQL to inject; {target} lets one field on the record decide which companies get it |
| Lists (addresses, contacts, prices) | Addresses are never removed | Merge (add and update) or Mirror (remove what the source no longer has), per list |
| A renamed contact person | Needs a manual "IC Key" to avoid duplicates | Followed automatically: CertiReplica remembers which target row each source row became |
| Before writing | Nothing: the change is made | Simulation: record by record and field by field, before and after, with nothing written. Optional approval per rule; new records can be created on hold |
| A change made in the target | Silently overwritten | Recognised, because CertiReplica remembers what it wrote: the source wins, the target keeps its change, or the record waits for a decision |
| A record removed in the source | Not noticed | Noticed. Reported for a decision, or the target record is put on hold by itself. Never deleted |
| After writing | A log with rerun and hide | The target is read back; the history keeps before and after per field; a job can be rolled back |
| Failures | A log entry and an internal message | A sentence that says what is missing and what to do; unreachable companies are tried again with growing waits; refusals wait for a person |
| A user-defined field the target lacks | Must be created by hand in every company | Left out of the record and named, instead of failing it; a rule for user-defined fields creates the definitions in the target |
| Telling people | An internal SAP message per event, set up per database and scenario | E-mail, a webhook (Microsoft Teams, Slack) or an internal SAP Business One message, per rule and kind of event, gathered into one message per interval |
| Configuration changes | Restart the service | Take effect at once; every version of a rule is kept with who changed it |
| Installation | An add-on per company, a service on the database server, a database superuser | One setup program with a wizard, or unattended; one Windows service; nothing in SAP Business One. The same setup program upgrades, repairs and changes the settings |
| Every setting described | In the manual | On the screen: label, description, example |
Which one fits
Two honest shortlists
CertiReplica fits when
- Your need is master data, and you want to see every change before it is written
- Nothing may be installed in the SAP Business One companies, and no database superuser is on offer
- The companies sit on different servers, or are hosted
- Codes differ between companies, or setup data does not exist in the targets yet
- Branches change data too, and their changes must not be overwritten
What CertiReplica does not do
- Documents between companies: invoice to invoice, purchase order to sales order, drop-ship, consolidation. That is a different job
- A window inside the SAP Business One client. It is a web app; Find a record gives every record an address you can link to
- Delete records in a target company, ever
- Companies without a Service Layer
- Claim proof it does not have: SAP HANA yes, Microsoft SQL Server not yet. See what is still open
Coming from another tool, or from scripts
Existing records are adopted, not duplicated
Companies that were kept the same by hand, by a script or by another product already hold the same records. CertiReplica does not need them to be empty.
- A record with the same code, or for records SAP numbers itself the same name, is recognised as the counterpart and remembered, without being written
- Automatic mapping proposes pairs for a whole object; a person corrects the exceptions on one screen
- The Compare screen shows, before the first run, what differs, what the target is missing and what only the target has
- Update only brings existing records in line without creating anything; create only does the opposite

See it on your own data
Compare two of your companies before you change anything
The trial works in full for 30 days. A comparison and a simulation write nothing, so you can measure the distance between your companies on day one.
SAP and SAP Business One are trademarks or registered trademarks of SAP SE. Boyum and B1 InterCompany belong to their owner. CertiReplica is not affiliated with or endorsed by either. The comparison reflects our reading of the manual of B1 InterCompany; corrections are welcome at info@certicons.com.