Excerpt | ||
---|---|---|
| ||
Find out how to create a new Financial Transactions |
Learn to work with Financial Transactions |
Back to Financial Transactions Main Page
Panel | ||||
---|---|---|---|---|
| ||||
Table of Contents
|
Navigating to Financial Transactions
InvoicesInfo |
---|
Explaining Financial Transactions Fields
FINANCE > FINANCIAL TRANSACTIONS > MANAGE FINANCIAL TRANSACTIONS |
Using Financial Transactions
Use Financial Transactions to manage transactions that will either debit or credit the customer's Accounts Receivable.
There exist six different Classifications of Financial Transactions, each with its distinct characteristics and behaviour. Four of the Classifications can be manually created.
- Invoice - Debits the Accounts Receivable
- Credit Note - Credits the Accounts Receivable
- Payment - Credits the Accounts Receivable
- Refund - Debits the Accounts Receivable
The other two are automatically generated by the system when Payment or an Invoice is cancelled.
- Payment Cancellation- Debits the Accounts Receivable
- Invoice Cancellation - Credits the Accounts Receivable
Financial Transactions have a Life Cycle State which determines whether the transaction affects the Accounts Receivable Balance.
- Draft transactions can be 'Posted', 'Rejected' and edited and do not affect the Accounts Receivable Balance.
- Posted transactions are permanent, cannot be edited and affect the Accounts Receivable Balance.
- Rejected transactions cannot be edited and do not affect the Accounts Receivable Balance.
- Navigate to Financial Transactions and explore existing records via the Summary page.
- Click on the number of the record of your interest to enter the Data Entry page and see more detail.
- Use the Actions Menu to create a NEW Financial Transaction or modify (EDIT) an existing one. Financial Transactions cannot be deleted but can be rejected or cancelled, depending on their Life Cycle State.
- Use the PRINTOUTS link to extract or email information related Financial Transactions to the customer.
- Use BACK to return to the Summary page and CANCEL to revert any unwanted changes made to the Financial Transactions.
- Click on ACTIONS to discover other possibilities available for Financial Transactions.
Check the Validations & Restrictions Table below for a list of available Actions when working with Financial Transactions including each Action's related restrictions, validations and a description of its system process. View the Attributes Table for a comprehensive description of Financial Transactions fields.
Anchor | ||||
---|---|---|---|---|
|
Action | Restrictions | Validations | System Processing | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Create |
|
|
| ||||||||
Save Invoice |
|
|
| ||||||||
Save Credit Note |
|
|
| ||||||||
Save Payment |
|
|
| ||||||||
Save Refund |
|
|
| ||||||||
Edit |
|
|
| ||||||||
Delete |
|
| |||||||||
Post |
|
|
| ||||||||
Reject |
|
|
| ||||||||
Cancel Payment |
|
|
| ||||||||
Move Payment |
|
|
| ||||||||
Cancel Invoice |
|
|
| ||||||||
Quick Pay (Invoices) |
|
|
|
Anchor | ||||
---|---|---|---|---|
|
An * indicates a field is mandatory
Invoice Attributes
Name | Description | ||||||
---|---|---|---|---|---|---|---|
Number | The transaction number of the invoice Invoice which is automatically generated on posting the invoiceInvoice | ||||||
Reference numberNumber | The reference number of the invoice Invoice which is automatically generated on by creating the invoiceInvoice | ||||||
Accounts receivable Receivable* | The related accounts receivable | Financial transaction typeAccounts Receivable that the Invoice is created for | |||||
Financial Transaction Type* | The financial transaction type Financial Transaction Type. Only financial transaction types Financial Transaction Types classified as invoices Invoices can be applied | ||||||
Life cycle state | The life cycle state of the invoice | Rejection reason | The reason that the transaction was rejected.Cycle State | The Life Cycle State of the Invoice which can be any of the following:
| |||
Rejection Reason | The Rejection Reason is mandatory only if the transactionTransaction is rejected while being in draft life cycle statea 'Draft' Life Cycle State. | ||||||
Category | The category of the invoiceInvoice. Only categories Categories listed as allowed 'Allowed' on the related financial transaction type Financial Transaction Type can be applied. | ||||||
Issued onOn | The date that the invoice Invoice was issued on | ||||||
Posted onOn | The date that the invoice was postedInvoice was 'Posted' on | ||||||
Due onOn | The date that on which the credit period for that specific invoice is ending. Mandatory on conditions: If the invoice is posted | Shared Notes | Shared notes for the invoicea 'Posted' Invoice ends. | ||||
Shared Notes | Notes for the Invoice. Each time the notes are amended, the user and the date are logged. | ||||||
Back Office Code | A code which is used by external systems to refer to a specific Financial Transaction. | ||||||
Invoice Items* | A list of items which are invoiced Invoiced by this financial transactionFinancial Transaction. The following aggregated amounts are also calculated dynamically:
Invoices must contain at least one invoice item |
Credit note
item
| ||||||
Log Information | The standard set of Log Details information available in all entities |
---|
Credit Note Attributes
PaymentName | Description |
---|---|
Number | The transaction number of the |
Credit Note which is automatically generated on posting the |
Credit Note |
Reference |
---|
Number | The reference number of the |
---|
Credit Note which is automatically generated on creating the |
Credit Note |
Accounts |
---|
Receivable* | The |
---|
Accounts Receivable that the Credit Note is created for | |
Financial Transaction Type* | The |
---|
Financial Transaction Type. Only |
Financial Transaction Types classified as |
Credit Notes can be applied |
Life |
---|
Mandatory on conditions:
Cycle State | The Life Cycle State of the Credit Note which can be any of the following:
|
---|---|
Rejection Reason | The Rejection Reason is mandatory only if the |
Transaction is rejected while being in |
a 'Draft' Life Cycle State | |
Category | The category of the |
---|
Credit Note. Only |
Categories listed as |
'Allowed' on the related |
Financial Transaction Type can be applied. |
Issued |
---|
On | The date that the |
---|
Credit Note was issued on |
Posted |
---|
On | The date that the |
---|
Credit Note was 'Posted' on |
Issue |
---|
Reason | A description of the reason that the |
---|
Credit Note is issued |
Shared Notes |
---|
Notes for the Credit Note. Each time the notes are amended, the user and the date are logged. | |
Back Office Code | A code which is used by external systems to refer to the specific Financial Transaction. |
---|---|
Invoices to credit | The |
Invoices that were intended to be credited | |
Credit Note Items* | A list of items which are credited by this |
---|
Financial Transaction. The following aggregated amounts are also calculated dynamically:
It is mandatory to specify at least one |
Credit Note item
| ||||||
Log Information | The standard set of Log Details information available in all entities |
---|
Payment Attributes
Name | Description | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Number | The transaction number of the payment Payment which is automatically generated on posting the paymentPayment | |||||||||||
Reference numberNumber | The reference number of the payment the Payment which is automatically generated on by creating the paymentPayment | |||||||||||
Accounts receivable Receivable* | The related accounts receivable | Financial transaction typeAccounts Receivable that the Payment is created for | ||||||||||
Financial Transaction Type* | The financial transaction type Financial Transaction Type.Only financial transaction types classified as payment Financial Transaction Types classified as Payment can be applied | |||||||||||
Life cycle state | The life cycle state of the payment | Rejection reason | Cycle State | The Life Cycle State of the Invoice which can be any of the following:
| ||||||||
Rejection Reason | The Rejection Reason is mandatory only if the transaction Transaction is rejected while being in draft life cycle statea 'Draft' Life Cycle State | |||||||||||
Payment method Method* | The payment method of that paymentPayment for the specific Transaction. Only payment Payment methods listed as allowed on the related financial transaction type 'Allowed' in the Financial Transaction Type can be applied. | |||||||||||
(Payment amount ) Amount* | The amount of the Payment | |||||||||||
Payment Preference
| The Accounts Receivable Payment Preference that will be used to process the payment.
| |||||||||||
Category | The category of the payment Payment. Only categories Categories listed as allowed 'Allowed' on the related financial transaction type Financial Transaction Type can be applied. | |||||||||||
Issued onOn | The date that the payment the Payment was issued on | |||||||||||
Posted onOn | The date that the payment was postedthe Payment was 'Posted' on | |||||||||||
Received on On* | The date that on which the payment Payment was received. | |||||||||||
Received by user By User* | The user who actually received the payment.Payment | |||||||||||
Received by unit By Unit* | The unit who actually that received the payment.Payment | |||||||||||
Shared Notes | Shared notes Notes for the payment. Each time the notes are amended, the user and the date are logged. | |||||||||||
Back Office Code | ||||||||||||
Invoices to pay | The invoices that were intended to be paid | |||||||||||
Bills to pay | The bills that were intended to be paidA code which is used by external systems to refer to the specific Financial Transaction. | |||||||||||
Invoices To Pay | The Invoices that the Payment was intended for | |||||||||||
Bills to Pay | The Bills that the Paymentwereintended for | |||||||||||
Voucher | The voucher that was used for the Payment and resulted into creating in its creation and posting the payment. This information is available only if the payment Payment was created by using a voucher. | |||||||||||
Payment Gateway Information
| Provides information related to the Payment Gateway Provided that processed the Payment.
| |||||||||||
Log Information | The standard set of Log Details information available in all entities |
Refund
Attributes
Name | Description | ||
---|---|---|---|
Number | The transaction number of the refund Refund which is automatically generated on posting the refundRefund | ||
Reference numberNumber | The reference number of the refund the Refund which is automatically generated on by creating the refundRefund | ||
Accounts receivable Receivable* | The related accounts receivableAccounts Receivable related to the Refund | ||
Financial transaction type Transaction Type* | The financial transaction type Financial Transaction Type. Only financial transaction types classified as refund Financial Transaction Types classified as Refund can be applied. | ||
Life cycle state | The life cycle state of the refund | Refund amountCycle State | The Life Cycle State of the Refund which can be any of the following:
|
Refund Amount* | The amount to be refundedRefunded | ||
Category | The category of the Refund. Only Categories listed as 'Allowed' on the related Financial Transaction Type can be applied. | ||
Issued On | The date that the Refund was issued on | ||
Posted On | The date that the Refund was 'Posted' on | ||
Issue reason | A description of the reason for the Refund | ||
Shared Notes | Notes for the refund. Only categories listed as allowed on the related financial transaction type can be applied | ||
Issued on | The date that the refund was issued | ||
Posted on | The date that the refund was posted. Each time the notes are amended, the user and the date are logged. | ||
Back Office Code | A code which is used by external systems to refer to the specific Financial Transaction. | ||
Log Information | The standard set of Log Details information available in all entities |
Invoice Cancellation Attributes
Name | Description |
---|---|
Number | The transaction number of the Invoice Cancellation which is automatically generated on posting the Invoice Cancellation |
Reference Number | The reference number of the Invoice Cancellation which is automatically generated on creating the Invoice Cancellation |
Accounts Receivable* | The Accounts Receivable related to the Invoice Cancellation |
Financial Transaction Type* | The Financial Transaction Type. Only Financial Transaction Types classified as Invoice Cancellations can be applied |
Life Cycle State | The Life Cycle State of the Invoice Cancellation which can be any of the following:
|
Rejection Reason | The reason that the Transaction was rejected. It is mandatory only if the Transaction is rejected while being in a 'Draft' Life Cycle State. |
Invoice Cancelled | The Invoice that is cancelled |
Category | The category of the Invoice Cancellation. Only Categories listed as 'Allowed' on the related Financial Transaction Type can be applied. |
Issued On* | The date that the Invoice Cancellation was issued on |
Posted On* | The date that the Invoice Cancellation was 'Posted' on |
Issue Reason | A description of the reason for which the Invoice Cancellation is issued |
Shared Notes | Notes for the Invoice Cancellation. Each time the notes are amended, the user and the date are logged. |
Back Office Code | A code which is used by external systems to refer to the specific Financial Transaction. |
Invoice Items | The list of items which were included in the cancelled Invoice |
Log Information | The standard set of Log Details information available in all entities |
Payment Cancellation Attributes
System Processing
Name | Description | ||||||
---|---|---|---|---|---|---|---|
Number | The transaction number of the Payment Cancellation which is automatically generated on posting the Payment Cancellation | ||||||
Reference Number * | The reference number of the Payment Cancellation which is automatically generated on creating the Payment Cancellation | ||||||
Accounts Receivable* | The related Accounts Receivable | ||||||
Financial Transaction Type* | The Financial Transaction Type. Only Financial Transaction Types classified as Payment Cancellation can be applied. | ||||||
Life Cycle State* | The Life Cycle State of the Payment Cancellation which can be any of the following:
| ||||||
Rejection Reason | The reason that the Transaction was rejected. It is mandatory only if the transaction is rejected while being in a 'Draft' Life Cycle State. | ||||||
Payment Cancelled | The payment affected by the Payment Cancellation | ||||||
Payment Amount | The amount of the cancelled Payment | ||||||
Category | The category of the Payment Cancellation. Only Categories listed as 'Allowed' on the related Financial Transaction Type can be applied. | ||||||
Issued On* | The date that the Payment Cancellation was issued on | ||||||
Posted On* | The date that the Payment Cancellation was 'Posted' on | ||||||
Issue reason | A description of the reason | that the refundfor which the Payment Cancellation is issued | |||||
Shared Notes | Shared notes for the refund |
Creating & Saving, Validations & Restrictions
Action | Validations | Restrictions | Additional Information |
---|---|---|---|
Create | |||
Save |
Creating an Accounts Receivable
ATTACHMENTS
LOG INFORMATION
The following information is automatically set by the system on saving the Financial Transactions
Notes for the Payment Cancellation. Each time the notes are amended, the user and the date are logged. | |||||||||
Back Office Code | A code which is used by external systems to refer to the specific Financial Transaction. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Payment Gateway Information
| Provides information related to the Payment Gateway Provided that processed the Payment Cancellation
| ||||||||
Log Information | The standard set of Log Details information available in all entities |
Anchor additional additional
Additional Actions for Financial Transactions
additional | |
additional |
The following actions are used to perform additional amendments on Financial Transactions that cannot be achieved using EDIT. Some of the actions are available for all Financial Transaction Classifications, while others are only available for specific Classifications.
Anchor post post
Posting Draft Financial Transactions
post | |
post |
Follow the steps below to Post an existing 'Draft' Financial Transaction
- Navigate to MANAGE FINANCIAL TRANSACTIONS
- Search for the Financial Transactions with a 'Draft' Life Cycle State
- Click on the number/name of the record you would like to access, to go to the Data Entry page
- From the Action Menu click on ACTIONS > POST. A confirmation message is shown to confirm the Posting.
- Click on YES to Post the Transaction
Anchor reject reject
Rejecting Draft Financial Transactions
reject | |
reject |
Follow the steps below in order to reject an existing 'Draft' Financial Transaction
- Navigate to MANAGE FINANCIAL TRANSACTIONS
- Search for the 'Draft' Financial Transaction you would like to Reject
- Click on the number/name of the record you would like to access, to go to the Data Entry page
- From the Action Menu click on ACTIONS > REJECT to open the Reject Financial Transaction modal. Select a reason for the rejection from the drop-down list.
- Click on SAVE
Anchor cancel_inv cancel_inv
Cancelling Invoices
cancel_inv | |
cancel_inv |
Follow the steps below to cancel an Invoice that has already been 'Posted'
- Navigate to MANAGE FINANCIAL TRANSACTIONS
- Search for the Invoice you would like to cancel
- Click on the number/name of the record you would like to access, to go to the Data Entry page
- From the Action Menu click on ACTIONS > CANCEL to open the Invoice Cancellation modal. Provide the required information.
- Click on SAVE
Anchor cancel_pay cancel_pay
Cancelling Payments
cancel_pay | |
cancel_pay |
Follow the steps below to cancel a Payment that has already been 'Posted'
- Navigate to MANAGE FINANCIAL TRANSACTIONS
- Search for the Payment you would like to cancel
- Click on the number/name of the record you would like to access, to go to the Data Entry page
- From the Action Menu click on ACTIONS > CANCEL to open the Payment Cancellation modal. Provide the required information.
- Click on SAVE
Anchor | ||||
---|---|---|---|---|
|
CRM.COM allows the automatic movement of a Payment from oneAccountsReceivable to another. Moving Payments can be accomplished through either customer or system accounts.
View /wiki/spaces/WIP/pages/10010218 for more information
- Navigate to MANAGE FINANCIAL TRANSACTIONS
- Search for the Financial Transactions you would like to relocate to another account
- Click on the number/name of the record you would like to access, to go to the Data Entry page
- From the Action Menu click on ACTIONS > MOVE TO ACCOUNT to open 'Move Payment From.'
- Select the Destination Accounts Receivable you wish to move the Payment to
- Click on SAVE
Anchor quick_pay quick_pay
Paying an Invoice using Quick Pay
quick_pay | |
quick_pay |
Quick Pay is a process used to quickly pay the unsettled amount of Bills and Invoices. Follow the steps below:
- Navigate to MANAGE FINANCIAL TRANSACTIONS
- Search for the Invoice you would like to pay
- Click on the number of the Invoice to go to the Data Entry page
- From the Actions Menu click on ACTIONS > QUICK PAY to open the Quick Pay modal
- The Amount is set to be equal to the unsettled amount of the Invoice.
- The following information can be updated:
- Payment Type
- Payment Method
- Issued On
- Category
- Received By User
- Received by Unit
- Click on SAVE
Note |
---|
View Understanding Financial Transactions for related business examples |
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Related Areas
|
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Popular Labels | ||||||||||||
spaceKey | V4Manual | style | heatmap||||||||||
Helpful Links
|