Source Transactions: Difference between revisions
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
* [[Sales Invoices]] | * [[Sales Invoices]] | ||
* [[Sales Invoice Credit Notes]] | |||
* [[Bank Deposits]] | * [[Bank Deposits]] | ||
* [[Supplier Bills]] | * [[Supplier Bills]] | ||
* [[Supplier Bill Credit Notes]] | |||
* [[Payments]] | * [[Payments]] | ||
* [[Purchase Orders]] | * [[Purchase Orders]] |
Revision as of 21:09, 2 March 2017
Source transactions store financial data as a set of master/child details. Examples include:
- Sales Invoices
- Sales Invoice Credit Notes
- Bank Deposits
- Supplier Bills
- Supplier Bill Credit Notes
- Payments
- Purchase Orders
- Quotations
These source transactions can be generated manually or automatically via business processes. For example, a purchase order my be generated when a work task is approved. The approval of the purchase order may generate a supplier's bill which may be paid to generate a payment cheque and a corresponding electronic funds transfer.
Posting to The Ledger causes the source transaction to be registered in the General Ledger as Ledger Transactions. Unposting causes additional ledger transactions to be created which amount to a reversal of the previously posted amounts in each account.
Allocations are used to track payments between source transactions such as when a deposit is used to pay an invoice.