ABSTRACT
The degree of consistency is important especially for transactions with financial impact processed in Software as a Service (SaaS), and in many ways. It becomes even more important when the company puts the same transaction through multiple SaaS, so creating a requisition in one SaaS, and receiving it in another, before billing and paying it out of a third SaaS. The same phenomenon applies to the development of internal controls for SaaS. Precisely because we can integrated it with other best-in-breed SaaS in tracing a transaction from cradle to grave, attention needs to be paid to the "links and tensions" among various interconnected SaaS. Even without layering in an additional SaaS or two, mistakes can happen within any one given SaaS. It is perhaps ironic that because not all SaaS is built the same, the same controls that address accuracy, completeness, validity, access, or audit trails for transactional data may not be available for setup or master data.
