The Accounts Receivable and Payable application manages the financial tran­sac­tions (invoices, payments, etc.) of your clients and suppliers.

Many of the transactions are auto­ma­ti­cal­ly generated from the other CMStrade applications (e.g. invoices) while others are input directly (e.g. payments).

Since theoretically an auxiliary accoun­ting, we do not confuse ARAP’s data into the General Accounting and the Cost Accounting but only integrate with them (note, ARAP concerns only a small part of the GA account structure).

This separation is important because:

■ Transactions and operations are dif­fe­rent (due date, open posts, …).

■ Transaction life does not correspond to the annual GA cycle.

■ ARAP has its own very specific bu­si­ness in­for­ma­tion and control needs.

Integration with the GA, on the other hand, ensures the accounting re­qui­re­ment for coherence and completeness.

Finally, separation and integration allow ARAP to play its different roles for many ap­pli­ca­tions (credit lines, broker ac­coun­ting, cash management, etc.) eliminating the inefficient substitute me­cha­nisms other­wi­se created in these applications and the resulting wasteful duplicate data input.

Two examples illustrate this sy­ner­gy: credit line employs ARAP ac­counts for its ac­coun­ting; physicals benefit from ARAP's open posts.

● Conforms to classical auxiliary accounting principles.

● Account structure is independent of the general accounting.

● The client/supplier data is the root of the account.

● Account definitions customise to business needs.

● Definition also attributes balance sheet risk classification and reconciliation.

● Accommodates trade client/supplier’s debit/credit duality and local regulation.

● Multi currency accounts.

● Multiple sub accounts.

● Multi currency accounting: transaction, functional, local, reporting currency basis.

● Relation to functional currency handled automatically per user specification.

● Account cycle (even many years) in­de­pen­dent of the general accounting cycle.

● Different data retention durations for accounts.

● Blocking an account for further postings.

● Full validation of vouchers before posting.

● Many transactions (e.g. trade invoices) generated from other applications.

● Other (miscellaneous) transactions input directly.

● Supply relevant costs and revenues to cost accounting application.

● Absolute and relative booking period limits.

● Currency revaluation simulation and pos­ting, periodic and ad hoc.

● Currency conversion in reports using ac­cou­n­ting or ad hoc rates.

● Balances and details, i.e. movements, for any period, starting-ending any day.

● Current and anterior balances and details with/without open post situation.

● Period analysis of open balances with drill-down to movement details.

● Reminder statement with interest.

● Extensive options tailor the contents of all reports.

● Accounts as current account with "open post" facility.

● Open posts partially or fully matched.

● Many-to-many open-post matching e.g. a payment for several invoices some of which are already partially paid.

● Drag-n-drop open-post matching under control.

● Matches can be undone and re-assigned differently.

● Various movement arrangements to fa­ci­li­ta­te matching.

● Account to account transfers.

● Assign accounts for use in other re­le­vant applications.

● Supply relevant costs and revenues to cost accounting application.

● Suppression of obsolete movements on a per account or grouped basis.

● Suppression retains open-post movements or creates a single open-post balance (as in bank-balance).

For information on Operations, Output

and Transactions, please see Data.