arapXML
Home  Research Discussion  Requirements Use Cases Specification Test interface About arapXML
Use Cases - previous versions and working drafts

As stated in the scope, arapXML is intended to enable a root general ledger to provide a consolidated view of economic events conducted on multiple software applications or web hosts.  This includes a consolidated view of AR and AP. 

The full implications of a centralized management of AR/AP include numerous use cases within these types:

- read, write, update General Journal (GL)
- read, write, update Accounts Receivable (Sales, receipts of payments)
- read, write, update Accounts Payable (Purchases, payments)

- Maintain Chart of Accounts
- Maintain Party (Customer, Vendor, etc.)
- Maintain Inventory Items List

An initial set of use cases is found on the sidebar.

Most use cases for the ArapXML are derived from the following pattern: 

    Use Cases

1.  3rd Party submits GL entry 
2.  Interco. book settlement
3.  further interco. settlement
4.  payment within interco settlement  
5.  AR/AP Cloud 
6.  AR/AP settlement 

Classic double entry accounting (CDEA) is a semantic system for expression of economic events and commitments in balanced format, i.e. it includes both of the movements within an exchange of economic resources.  ArapXML uses this rigorous system of notation and accountability as the foundation for A2A (application to application) integration between the AR/AP user and the BSP.

From the viewpoint of the AR/AP user, the BSP is thus, a subledger within his/her own company, which generates double entry accounting entries, and can be addressed in the same language to communicate increases and decreases in resources such as inventory and cash.  The advantage of this arrangement is that it draws upon a deep reservoir of established practices and solutions for maintenance of internal control and accounting consistency among diverse applications and remote operations.  It enables the utilization of large numbers of trained bookkeepers and accountants when necessary.

B2B messages are offer-response dialogs with sovereign third parties.  The language for B2B interactions is commercial law.  Application to application integration (A2A) is the nervous system connecting the components inside a company.  The language for logging economic events from the internal viewpoint is accounting; it has been stable for a long time.

One of the goals of ArapXML is to improve the communications and reconciliation between corresponding payables and receivables balances between sovereign 3rd parties, by standardizing the naming for general ledger and AR/AP data elements.