Business Rules, Source Data, and Code Synchronization

This week’s episode discusses how (1) source or transactional data, (2) reference data and rules, and (3) the application engine must be synchronized to arrive at the desired answers.

To produced ledgers, metric engine environments or reports that contain meaningful results, the source data must be created in ways that are very consistent; that typically means bringing together all of the elements listed above.

If they are not in sync, then business rules may be missing or wasted if source data never executes them.  If the code used to apply the rules to the source data is incorrect, the outputs will not be correct.

The result will be any combination of source data being (1) dropped if the code is not correct, (2) suspended or (3) rejected if the rules are not correct, and thus (4) the resulting ledger will not be complete or accurate.

Development and testing requires bringing all these elements together in a coordinated way to properly build a metric engine.

This is Episode 177 of Conversations with Kip, the best financial system vlog there is. Literally learn more–about ledgers and financial systems–at

Last week’s entry: Business Rules and ERP Integration

This is the end of the Reference Data Series of videos.

One thought on “Business Rules, Source Data, and Code Synchronization

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s