RE: XFRML, ebXML, and the root ledger

["Coffin, Zachary P" <zcoffin@kpmg.com>]

Hi, A few notes may help contextualize what we are doing in XFRML.  As Liv
said, we are very interested in working with fellow XML initiates.

1) Right now, XFRML is focused on financial reporting, specifically
Financial Statements.  At present the work-in-progress specification is U.S.
GAAP for Consumer and Industrial products, but that's first only because
it's the largest bucket of users.  XFRML is in no way intended to be
U.S.-centric.  By July 1st, the public release of the XFRML for General
Financial Statements specification will encompass multiple GAAP.  The
International Accounting Standards Council is an active member of XFRML, as
are several other accounting organizations from around the world; and next
month I will be meeting with the French and others to invite their
participation.

2) XFRML eventually will focus on other forms of financial reporting:
regulatory filings, tax filings, etc.

3) XFRML ultimately may tackle "business performance" reporting, which might
include such things as "cost per cycle" or "employee turnover" or etc.

4) There also is active discussion about XFRML's role in G/L or journal
entry reporting, which is viewed suspiciously by some as the first step in
creating a chart of accounts.  All I can say about this is that a few of us
just presented XFRML to about fifty CFOs/CAO/SVPs of Fortune 100 companies
(GE, GM, IBM, Microsoft, JP Morgan, American Express, etc.) and they voted
to accept our invitation to join the XFRML Steering Committee.   One of the
main topics of discussion was this root ledger issue.  This issue is by no
means resolved, but their joining our effort is indicative of their desire
to shape XFRML--and XML initiatives in general--in a way that they can fully
endorse.  XFRML is pleased to have their participation.

Perhaps a meeting should be scheduled between XFRML and ebXML to nip any
issues in the bud and avoid duplication of effort.  I believe KPMG's
representative to ebXML is John Petit, and I have cc:ed him on this note.  I
also have cc:ed Eric Cohen, who serves as XFRML's segment manager for XML
liaison relationships.  Who with ebXML would be the appropriate people to
meet with?

Thanks for your interest, and please don't hesitate to call if we can answer
any questions you may have or assist in any way.

Regards to all,

Zack Coffin

XFRML, Liaison Chair



Zachary Coffin
Director of Intellectual Capital
Director, Digital Media Institute
KPMG Consulting LLC
355 South Grand Avenue, Suite 2000
Los Angeles, CA  90071-1568
Tel: (213) 955-8508  -  Fax: (213) 630-5196
Pgr (~50 chars.): 2138647772@messaging.sprintpcs.com



-----Original Message-----
From: Liv A. Watson [mailto:liv1@wworld.com]
Sent: Sunday, March 05, 2000 7:38 AM
To: 'Glover, Roger'; tboyle@rosehill.net;
ebxml-core@lists.oasis-open.org
Cc: Zachary P Coffin (E-mail); Walter. Hamscher (E-mail)
Subject: RE: XFRML, ebXML, and the root ledger


Hi,

My name is Liv Watson and I serve on the XFRML Steering Committee
representing the Institute of Management Accountants. We are very interested
in working together with all the XML initiatives to ensure success.  We are
also very interested in your feedback as soon as our spec group release
them.  I have cc Walter Hamscher and Zachary  Coffin (XFRML liaison Chairs)
on this   e-mail since they will  be able to answer some of the questions
that you have with regards how we can be working together.  Please keep in
touch and direct any other questions to either Walter, Zachary, or myself
and we will make sure they are answered.  Thanks for your interest, Liv

-----Original Message-----
From: owner-ebxml-core@lists.oasis-open.org
[mailto:owner-ebxml-core@lists.oasis-open.org]On Behalf Of Glover, Roger
Sent: Thursday, March 02, 2000 1:38 PM
To: 'tboyle@rosehill.net'; ebxml-core@lists.oasis-open.org
Subject: RE: XFRML, ebXML, and the root ledger


Todd <tboyle@rosehill.net> wrote:
> The XFRML workgroup http://www.xfrml.org is nearing release of its
> vocabulary for financial reporting.  (I am not associated with XFRML.)
>
> This is XML for GAAP (Generally Accepted Accounting Principles)
> for financial statements in the U.S. i.e. for statutory reporting
> for publicly listed companies as well as SMEs.  See the website for
> draft tag sets and demo applications.
>
> I understand XFRML workgroup are actively considering at this time,
> the issue of flatness vs. hierarchic structure in their schema.  Any
> comments on that?

Last month I attended an XFRML presentation by John Woodburn, one of the
leaders of the XFRML effort.  He did not mention "depth of hierarchy" as one
of the major outstanding issues, but the talk was not really pitched toward
XML experts.


> The significance of the XFRML release may be far reaching. For example,
> it will be inevitable that definitions or usage of the vocabulary
> must be forthcoming from the AICPA in some fashion; in the past
> the definitions of GAAP terminology (although legally binding), were
> copyrighted by FASB and cost hundreds of dollars.
>
> Financial data in XFRML format may enable automation of downstream
> processes such as tax returns, and all kinds of boutique financial
> analyses beyond the financial statements. The need to publish and
> manipulate financial statements in multiple formats (.doc's, .html,
> edgar, excel, .txt, .ppt and so forth) will certainly be reduced.
>
> ASPs and accounting systems that can effectively store transactions
> in a way that is mapped to XFRML tags, will obviously deliver better
> reports out of the box.

In the Q & A session, John disavowed any near-term goals for the XFRML group
itself beyond those directly linked to financial reporting (and USA
financial reporting at that).  However, he did say that they consciously
aimed for broad applicability, in the hope that their effort would be
influential in other financial DTD/Schema standardization efforts.


> ebXML workgroups should consider the interrelationship between your
> XML Schema for General Ledger and downstream XML such as XFRML that
> emanate from the resulting transactions.

Again, it sounds like this sort of consideration is exactly what the XFRML
team is hoping would happen.


> I don't claim to have any easy answers but suppose you release, as
> did OAG, an XML spec calling for an Account Code (here are the OAGIS
> elements in JELINE with their content models:)
>
> GLNOMACCT, BUSNAREA?, COSTCENTER?, DEPARTMENT?, DESCRIPTN?, DIVISION?,
> ELEMENT*, FUND?, GEOGRAPHY?, GLENTITYD?, ITEM?, PRODCTLINE?,
> PRODORDER?, PROFITCTR?, PROJACTVTY?, PROJECT?, PROJRESEL*,
> REASONCODE?, REF*, SALESORDID?, UNIT?, WAREHOUSE?, WORKORDER?
>
> The notion of an "Account Code" may be obsolete; the Chart of Accounts
> has historically been overloaded with multiple uses. It has often been
> an intricate, denormallized table combining values such as org. structure
> and department, with accounting classifications.  Chart of Accounts
> has served multiple needs including ease of keypunching, internal
> control, reconcilation with external entities, and downstream
> reporting.  No wonder Charts of Accounts are an unmanageable mess.
>
> Account codes need to be burst out into several different attributes
> representing their real uses. General Ledgers should not have
> "Charts of Accounts" in future.  Chart of accounts is supposed to
> be the classification choices for the GAAP domain. That's called
> XFRML, in the U.S. now isn't it?  Do you see what I mean?

I am not an accountant, but I believe I am catching the highlights.
Nonetheless, a little more exposition on the "Chart of Accounts" mess would
be useful.  Especially I would like to see an enumeration of the processes
facilitated in the paper document world, and suggestions for better serving
those processes in the XML world.

[remainder snipped, because I had no comments]


-- Roger Glover
   Norstan Consulting
   * E-mail: Roger.Glover@NorstanConsulting.com
   * Office: +1-612-352-5718
   * FAX:    +1-612-238-5718

*****************************************************************************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter.         
*****************************************************************************