When you set up master data synchronization between companies in Business Central, you will eventually run into records that fail to sync. The good news is that Business Central tells you exactly why. The error message points to the missing piece of data, and from there you have two clear options for fixing it.
If a customer record fails to synchronize because it references a payment terms code that does not exist in the subscriber company, you can either create that payment term manually in the subscriber company or synchronize the payment terms table from the master company.
The error messages you get during synchronization are standard Business Central messages. They tell you precisely what the cause of the failure is, so you do not have to guess.
Checking the synchronization result in the subscriber company
After running the synchronization in a subscriber company, you should check the record data to confirm everything came across. In this example, the synchronization completed, but one record was left behind. Reviewing the record data showed one customer that had not been synchronized.
The next step is troubleshooting to find out what caused that single record to fail.
Reading the error message
Business Central provides an error message for the failed record. In this case, the message explained that the customer could not be synchronized because its payment terms code contained the value CM+19 days (current month plus 19 days), and that value could not be found in the related Payment Terms table in the subscriber company.
In other words, the customer record pointed to a payment term that simply did not exist in the company you were syncing into. Business Central will not create the missing related record on its own, so the synchronization stops for that record.
Two ways to fix a missing related record
When a record fails because a related value is missing, you have two practical options:
- Create the payment term manually in the subscriber company so the value the customer references exists.
- Go back to the master company and make sure the Payment Terms table is included in the synchronization, so the related data flows into the subscriber company automatically.
The second option is usually the cleaner long-term choice. If your customer records depend on payment terms, then payment terms should be part of what you synchronize. Otherwise you will keep hitting the same wall every time a new customer with that payment term appears.
Why the error messages are easy to act on
The error messages you see during master data synchronization are the standard Business Central error messages. They name the exact field, the exact value, and the table where the value is missing. That makes troubleshooting straightforward. You are not left interpreting a vague failure. You know what is missing and where, and you can decide whether to create the data manually or extend your synchronization setup.
Q&A
Why does a customer record fail to synchronize between companies in Business Central?
A common cause is a missing related record. If the customer references a value, such as a payment terms code, that does not exist in the target company’s related table, the synchronization fails for that record. Business Central displays a standard error message naming the field, the value, and the missing table.
How do I fix a synchronization error caused by a missing payment terms code?
You have two options. You can create the missing payment term manually in the subscriber company so the referenced value exists. Or you can include the Payment Terms table in the synchronization from the master company so the data flows in automatically.
What information does the Business Central synchronization error message give me?
It uses the standard Business Central error messages, which tell you the exact field, the exact value that is causing the problem, and the related table where that value cannot be found. This makes it clear what is missing and where, so you can act on it directly.