Re: Interest, Amortization and Financial Functions via SDK?

Daniel,

I'm confused as to why you are considering flexibility in conflict with SOX compliance. Sure, Excel is a large target in any audit because most larger corporations have hundreds of legacy Excel spreadsheets that have not been set up with SOX compliance in mind; the violations are usually numerous and severe. Once policies and procedures are in place, Excel remains a strong SOX compliant tool. Among other policies, it supports:

1. Controled access to both the spreadsheet and linked data soures via integrated authenication.
2. Auditability - who accessed what and when.
3. Hidden implementation - code and all other project properties can be restricted via encryption. This is not the same as "protected cells".
4. SDLC contollability - can accomodate SOX-compliant policies in place using automated source control and application verification and validation.

I would very much like to know what we're missing. Having participated in a pre-IPO SOX audit, the above policies were the only ones of consequence determined by our audit firm.

• Bill

"DA Morgan" <damorgan_at_psoug.org> wrote in message news:1172264403.959760_at_bubbleator.drizzle.com...
> AlterEgo wrote:
>> Jimmy,
>>
>> What about Excel linked to the Oracle database? There is a great deal of
>> flexibility if you start programming Macros, which in later versions is
>> really Visual Basic for Applications.
>>
>> -- Bill
>
> In the US there is a name for that flexibility ... we call it a
> violation of Sarbanes-Oxley. I think in Canada they call it a violation
> of PIPEDA and in Europe of Basel II.
> --
> Daniel A. Morgan
> University of Washington
> damorgan_at_x.washington.edu
> (replace x with u to respond)
> Puget Sound Oracle Users Group
> www.psoug.org
Received on Mon Feb 26 2007 - 17:47:11 CST