Are some of your employees spending most of their business hours on data entry? System Integrations built using best practices reduces data entry time and manual errors, while improving audit and compliance issues. Attend this session to understand best practices and considerations for building effective system integrations. We’ll walk you through a number of our systems to ensure your in compliance with the best practices for seamless system integration throughout your organization.

1. System Integrations
Presented By:
- Bharti Meisuria
- Paraman Srivatsalan

2. Agenda
When
What
 What is System Integration
11:30 – 12:25
 Integration by Example
 Interface Case Studies
 Best Practices

3. What is System Integration
A software system integration allows application systems to “talk” to each
other and exchange data based on pre-defined business logic.
Source
Staging
Audit reports
Target

4. SINGLE System of Truth
Operations
Which one is your System
of Record?
Data flow – one way or
both ways?
Finance

5. Integration Components
Business Logic
Exception Handling
Writing Data
Audit Compliance

6. Business Logic
The source & target applications are designed to perform different functions,
hence the database structures of the source & target systems will not necessarily
match.
Business logic:
 Data transformation rules should be parameterized
o If Customer group = “ON”; default price list = “ONRETAIL”

7. Exception Handling
What happens when the source data does not fall into the business logic
created to support the business rules?
 Exception Log
o Include warnings – the target system
will accept data with no errors (e.g.
Vendor does not exist in target
system)
 Error Log
o Include errors – the target system will
NOT accept data and will generate
errors

8. Writing Data
 Wherever possible, use the
Application Programming Interface
(API) to write data to target systems to
eliminate the risk of data integrity
issues
As part of your testing
procedure, incorporate the step
to run data integrity checks on
your system

9. Audit Compliance
 Only authorized users should be able to
access the appropriate integration
functions
 Users should be able to print the audit
reports to show what data was
transferred from source to target system
– and be able to group the changes.

10. Integration by Example

11. Integration by Example
Operations
Finance
AR invoices

12. Integration by Example
Operations
Business Logic
Finance
Customer Invoice
Examples:

If it’s a new customer, send an alert to AR

If the customer is from region X, assign territory “WEST”

13. Integration by Example
Operations
Exception Handling
Examples:

Invoice number already exists
Finance
Customer Invoice

14. Integration by Example
Operations
Writing data
Finance
Customer Invoice

Various mechanisms may be available to protect data integrity in your target system
o Import process
o Write data directly using API

Real-time versus scheduled update
o Update target system in real-time – apply change as it occurs in source system
o OR Schedule the data update process

15. Integration by Example
Audit reports

Customer invoices created
in operations system are all
available in the financial
system

16. Integration by Example
HRIS
Payroll
Employee Data
(required for payroll
calculation)

17. Integration by Example
HRIS
Business Logic
Payroll
Employee Data
(required for payroll
calculation)
Examples: For when an Employee in HRIS:

Is hired; create new hire in Payroll

Is terminated; update last pay cheque date in Payroll

Home province is changed; update TAX group in Payroll

18. Integration by Example
HRIS
Business Logic
Examples: For when an Employee in HRIS:

Is hired; create new hire in Payroll
o Default values for mandatory data in Payroll
o Mapping table for data values
Payroll
Employee Data
(required for payroll
calculation)

19. Integration by Example
HRIS
Exception Handling
Examples:

Employee Address for new hire is not populated
Payroll
Employee Data
(required for payroll
calculation)

20. Integration by Example
HRIS
Writing data
Payroll
Employee Data
(required for payroll
calculation)

Various mechanisms may be available to protect data integrity in your target system
o Import process
o Write data directly using API

Real-time versus scheduled update
o Update target system in real-time – apply change as it occurs in source system
o OR Schedule the data update process

21. Integration by Example
Audit reports

Check the counts for each
activity

22. Summary
 Business Logic – parameterize / easy to maintain
 Writing data to target system – format mechanism to protect data integrity
 Exceptions & Error logs
 Audit compliance – generate reports to confirm all records that were “added”
or “changed” in source system were appropriately processed in the target
system

23. Integration Bridges
 Timesheet to Payroll
 HRIS to Payroll
 Payroll to Benefits Provider
 Payroll to Finance
 Finance to Budgeting & Forecasting
 Operations Systems to Finance

24. Integration Bridges
We offer integration engagements and empower you to
implement reliable system integrations
(http://www.baass.com/services/system-integrations )
o Your Organizational needs
o Your Operations and Finance needs
o Your environment
o Your resources
o Future vision & goals
o Much more…

25. Thank you!
Talk to your Account Manager,
email or visit our booth for more
information