Critical Success Factors for net accounting hosts:

Problem Solutions Responsible party
Can't conduct business over the internet 1.  publish your existing interfaces in XML.
2.  migrate to standards-based XML interfaces.
3.  adopt EDI interfaces either directly or thru BSPs*
4.  establish integrations with BSPs		 1. core accounting developers build interfaces, inbox, outbox, etc. 
2.  XML integration team research and implement XML standards.
Inadequate Feature Depth 1. rely on BSPs and ISVs (independent software vendors for vertical markets/applications)
2. build better core features for accounting.		 1. developer teams
2. integration teams
Usability issues 1. apply better usability standards in coding.
2. invest time and money in specific usability issues.
3. rely on BSPs and ISVs who build most user-facing modules.		 1. architects guiding module teams.
2. dedicated usability teams.
3. integration teams connecting to BSPs and verticals.
Incremental Adoption. SME does not want to totally rip and replace existing systems. 1. design the net accounting system to run as a subledger alongside existing systems.
2. ensure the subledger has good interfaces for the supporting tables (account, party, etc.)
3. think and plan, on subledger management or control mechanisms..		 1. architects guiding core ledger design and XML interfaces
2. developers of consolidation and interface mechanisms.
SMEs don't trust GL hosts 1.  total value proposition, must exceed total user doubts
2.  minimize doubts by providing easy exit - avoid any lock-in by open XML interfaces. 
3.  make sure other GLs exist who can import the data of your subscribers.
4.  get technical and fiduciary certifications.
5.  adopt principles of user sovereignty, privacy, security, etc. 		1.  BSPs provide most core needs; GL provides five root ledger needs.
2.  integration teams build XML interfaces
3.  owners of net accounting host invest in certifications
4.  net accounting host documents trust principles, and enforces them.
SME's don't trust each other 1.  establish stronger authentication on the GL host
2. establish empirical reputation metrics to help SMEs prove they are good customers, privately, to each other.
3.  get services from credit bureaus for SMEs.
4.  assist SMEs to get their own credit reports free.
5.  implement XBRL financial reporting as richly as possible to enable lender to understand financial data
6.  establish good XML reporting capabilities so the SME or the lender can read/print rich reports. 		1. core accounting developers, and
2.  XML integration team research and implement reputation schemas.
SMEs fear hackers 1.  practice extreme vigilance (invest in security)
2.  reduce reliance on security. use unposted transaction batches (inbox paradigm)
3.  reassure Owners by displaying current net equity, working capital and other benchmarks at all times.		 1. GL's security team
2.  module developers,
3. core accounting engine developers, and
4.  XML integration team 
Slow connections 1. Offline net accounting client, and
2. XML adapters to desktop accounting software.		 1. Core accounting developers, and
2. XML integration team
Availability: SMEs fear the application will be unreliable or off-line sometimes 1. provide offline client.
2. provide data export to standard formats, and ensure dissatisfied users have real exit alternatives.  		 1. Core accounting developers, and
2. XML integration team
No Backup: SMEs fear data loss 1. provide data export to standard formats, and
2. provide offline client.		 XML integration team.
No Purge: SMEs fear data will be on your host forever. 1. design the GL for guaranteed expungement.
2. provide data export to standard formats, so that the SME can maintain long history themselves.		 1. Database administrators and developers, 
2. XML integration team.

Terms:

BSP -  Internet business service provider or web application.  In general this is something more than a "web service" as envisioned by WSDL.  It is a company providing a natural aggregation of business objects forming a coherent whole, having some natural boundary such as a web storefront.  A BSP aggregates functionality of a scope sufficient to pay for support and hosting costs-- a level of functionality below which, it is not practical or economic to subdivide the application, but greater than which the application either cannot get revenue or runs into excessive costs.