Excerpt | ||
---|---|---|
| ||
Find out how to create a new Financial TransactionsLearn to work with Financial Transactions |
Back to Financial Transactions Main Page
Panel | ||||
---|---|---|---|---|
| ||||
Table of Contents
|
Navigating to Financial Transactions
Info |
---|
FINANCE > FINANCIAL TRANSACTIONS > MANAGE FINANCIAL TRANSACTIONS |
Using Financial Transactions
FieldsInvoices
Name | Description | ||||||
---|---|---|---|---|---|---|---|
Number | The transaction number of the invoice which is automatically generated on posting the invoice | ||||||
Reference number | The reference number of the invoice which is automatically generated on creating the invoice | ||||||
Accounts receivable* | The related accounts receivable | ||||||
Financial transaction type* | The financial transaction type. Only financial transaction types classified as invoices can be applied | ||||||
Life cycle state | The life cycle state of the invoice | ||||||
Rejection reason | The reason that the transaction was rejected. Mandatory on conditions: It is mandatory only if the transaction is rejected while being in draft life cycle state | ||||||
Category | The category of the invoice. Only categories listed as allowed on the related financial transaction type can be applied | ||||||
Issued on | The date that the invoice was issued | ||||||
Posted on | The date that the invoice was posted | ||||||
Due on | The date that the credit period for that specific invoice is ending. Mandatory on conditions: If the invoice is posted | ||||||
Shared Notes | Shared notes for the invoice | ||||||
Back Office Code
| A code which is used by external systems in order to refer to the specific financial transaction. | ||||||
Invoice Items* | A list of items which are invoiced by this financial transaction. The following aggregated amounts are also calculated dynamically:
It is mandatory to specify at least one invoice item | ||||||
Credit note
Name | 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 related accounts receivable | ||||||
Financial transaction type* | The financial transaction type. Only financial transaction types classified as credit notes can be applied | ||||||
Life cycle state | The life cycle state of the credit note | ||||||
Rejection reason | The reason that the transaction was rejected. Mandatory on conditions: It is mandatory only if the transaction is rejected while being in 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 | ||||||
Posted on | The date that the credit note was posted | ||||||
Issue reason | A description of the reason that the credit note is issued | ||||||
Shared Notes | Shared notes for the credit note | ||||||
Back Office Code
| A code which is used by external systems in order 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:
|
Payment
Name | Description | ||||||
---|---|---|---|---|---|---|---|
Number | The transaction number of the payment which is automatically generated on posting the payment | ||||||
Reference number | The reference number of the payment which is automatically generated on creating the payment | ||||||
Accounts receivable* | The related accounts receivable | ||||||
Financial transaction type* | The financial transaction type. Only financial transaction types classified as payment can be applied | ||||||
Life cycle state | The life cycle state of the payment | ||||||
Rejection reason | The reason that the transaction was rejected. Mandatory on conditions: It is mandatory only if the transaction is rejected while being in draft life cycle state | ||||||
Payment method* | The payment method of that payment. Only payment methods listed as allowed on the related financial transaction type can be applied | ||||||
Payment amount* | The amount of the payment | ||||||
Category | The category of the payment . Only categories listed as allowed on the related financial transaction type can be applied | ||||||
Issued on | The date that the payment was issued | ||||||
Posted on | The date that the payment was posted | ||||||
Received on* | The date that the payment was received. | ||||||
Received by user* | The user who actually received the payment. | ||||||
Received by unit* | The unit who actually received the payment. | ||||||
Shared Notes | Shared notes for the payment | ||||||
Back Office Code
| A code which is used by external systems in order to refer to the specific financial transaction. | ||||||
Invoices to pay | The invoices that were intended to be paid | ||||||
Bills to pay | The bills that were intended to be paid | ||||||
Voucher | The voucher that was used and resulted into creating and posting the payment. This information is available only if the payment was created by using a voucher |
Refund
Name | Description | ||||||
---|---|---|---|---|---|---|---|
Number | The transaction number of the refund which is automatically generated on posting the refund | ||||||
Reference number | The reference number of the refund which is automatically generated on creating the refund | ||||||
Accounts receivable* | The related accounts receivable | ||||||
Financial transaction type* | The financial transaction type. Only financial transaction types classified as refund can be applied | ||||||
Life cycle state | The life cycle state of the refund | ||||||
Refund amount* | The amount to be refunded | ||||||
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 | ||||||
Posted on | The date that the refund was posted | ||||||
Issue reason | A description of the reason that the refund is issued | ||||||
Shared Notes | Shared notes for the refund | ||||||
Back Office Code
| A code which is used by external systems in order to refer to the specific financial transaction. |
Creating & Saving, Validations & Restrictions
Action | Validations | Restrictions |
---|---|---|
CREATE |
|
|
SAVE INVOICE |
|
|
SAVE CREDIT NOTE |
|
|
SAVE PAYMENT |
|
|
SAVE REFUND |
|
|
Creating an Invoice
MAIN INFORMATION
- Accounts Receivable: Search and add the account for which the invoice is for
- Type: Select a type of invoice from the drop down list, if different than the default
- Due On: Click on the Calendar icon to select the due date (if not defined it will be automatically calculated by the system)
- Category: Search and add a category
ITEMS
- Click on ADD to open Products modal and search for a product to add as an item of the invoice
- In the record added provide the following information
- Product Code: Automatically added by the system
- Quantity: Set the quantity to charge for the product
- Unit Price: Set the cost of the product
- Discount: Select whether you would like to add a discount amount or a Discount Percentage
- According to the selection the respective field will be made editable while the other will remain read only
- Discount percentage: Apply a percentage discount
- Discount amount: Apply a fixed amount
- VAT rate: The VAT rate that is default for the selected product will be loaded by the system. If you would like to change the rate then you can choose another one from the drop down list.
The default VAT rate is specified on each product - VAT percentage:The VAT percentage that is applied, based on the selected VAT rate
- VAT Amount will be automatically calculated based on the Selected VAT rate
- Sub Total:The total amount that will be invoiced for the specified product
Every time an item is added and its details completed the system will automatically calculate the following aggregate amounts based on the information provided in the items fields
- Discount amount: Total Discount Amount
- VAT amount: Total VAT amount
- Net amount: Total NET amount
- Total amount : Sum of all of the Subtotals in the section
LOG INFORMATION
The following information is automatically set by the system on saving the Financial Transactions
Creating a Credit Note
MAIN INFORMATION
- Accounts Receivable: Search and add the account for which the credit note is for
- Type: Select a type of credit note from the drop down list, if different than the default
- Category: Search and add a category
- Issue Reason: Provide the reason the credit note is created
ITEMS
- Click on ADD to open Products modal and search for a product to add as an item of the credit note
- In the record added provide the following information
- Product Code: Automatically added by the system
- Quantity:Set the quantity to charge for the product
- Unit Price: Set the cost of the product
- Discount: Select whether you would like to add a discount amount or a Discount Percentage
- According to the selection the respective field will be made editable while the other will remain read only
- Discount percentage: Apply a percentage discount
- Discount amount: Apply a fixed amount
- VAT rate:The VAT rate that is default for the selected product will be loaded by the system. If you would like to change the rate then you can choose another one from the drop down list.
The default VAT rate is specified on each product - VAT percentage:The VAT percentage that is applied, based on the selected VAT rate
- VAT Amount: will be automatically calculated based on the Selected VAT rate
- Sub Total: The total amount that will be invoiced for the specified product
Every time an item is added and its details completed the system will automatically calculate the following aggregate amounts based on the information provided in the items fields
- Discount amount: Total Discount Amount
- VAT amount: Total VAT amount
- Net amount: Total NET amount
- Total amount : Sum of all of the Subtotals in the section
INVOICES TO CREDIT
- Click on ADD to open Invoices modal of the specified account and search for an invoice to add
LOG INFORMATION
The following information is automatically set by the system on saving the Financial Transactions
Info |
---|
|
Creating a Payment
MAIN INFORMATION
- Accounts Receivable: Search and add the account for which the payment is for
- Type: Select a type of payment from the drop down list, if different than the default
- Category: Search and add a category
- Amount: Enter the amount of the payment
- Received on: Select the date that the payment was received. It defaults to the issued date if not specified
- Received by user: Search and add the user who actually received the payment. It defaults to the logged in user if not specified
- Received by unit: Add the he unit who actually received the payment.
PAYMENT INFORMATION
LOG INFORMATION
The following information is automatically set by the system on saving the Financial Transactions
Info |
---|
|
Creating a Refund
MAIN INFORMATION
- Accounts Receivable: Search and add the account for which the refund is for
- Type: Select a type of refund from the drop down list, if different than the default
- Category: Search and add a category
- Amount: Enter the amount of the refund
- Issue Reason: Provide the reason for the refunding
LOG INFORMATION
The following information is automatically set by the system on saving the Financial Transactions
System Processing
Invoice
- SAVE AS DRAFT
- Life cycle state is set to draft
- Issued date is set
- Reference number is set
- Invoice Items sub amounts and total amounts are calculated
- Back Office Code Validation -
Status colour Red title Available from CRM.COM R9.0.0 - If the back office code is specified then:
- System will validate that the back office is unique for that kind of financial transaction type
- If a back office code is not specified then
- No validation is applied
- If the back office code is specified then:
- SAVE (POSTED)
If the invoice is created and posted at the same time then- Life cycle state is set to posted
- Posted date is set
- Transaction number is set
- Due date is calculated and set, if not set
- Unallocated credit notes are allocated against this invoice based on the allocation principle specified in the active accounts receivable definition
- Invoice Items sub amounts and total amounts are calculated
- Back Office Code Validation -
Status colour Red title Available from CRM.COM R9.0.0 - If the back office code is specified then:
- System will validate that the back office is unique for that kind of financial transaction type
- If a back office code is not specified then
- No validation is applied
- If the back office code is specified then:
Credit Note
- SAVE AS DRAFT
- Life cycle state is set to draft
- Issued date is set
- Reference number is set
- Credit Note Items sub amounts and total amounts are calculated
- Invoice Items sub amounts and total amounts are calculated
- Back Office Code Validation -
Status colour Red title Available from CRM.COM R9.0.0 - If the back office code is specified then:
- System will validate that the back office is unique for that kind of financial transaction type
- If a back office code is not specified then
- No validation is applied
- If the back office code is specified then:
- SAVE (POSTED)
If the credit note is created and posted at the same time then- Life cycle state is set to posted
- Posted date is set
- Transaction number is set
- Credit note is allocated against any unallocated invoices based on the allocation principle specified in the active accounts receivable definition
- Invoice Items sub amounts and total amounts are calculated
- Back Office Code Validation -
Status colour Red title Available from CRM.COM R9.0.0 - If the back office code is specified then:
- System will validate that the back office is unique for that kind of financial transaction type
- If a back office code is not specified then
- No validation is applied
- If the back office code is specified then:
Payment
- SAVE AS DRAFT
- Life cycle state is set to draft
- Issued date is set
- Reference number is set
- Invoice Items sub amounts and total amounts are calculated
- Back Office Code Validation -
Status colour Red title Available from CRM.COM R9.0.0 - If the back office code is specified then:
- System will validate that the back office is unique for that kind of financial transaction type
- If a back office code is not specified then
- No validation is applied
- If the back office code is specified then:
- SAVE (POSTED)
If the payment is created and posted at the same time then- Life cycle state is set to posted
- Posted date is set
- Transaction number is set
- Payment is allocated against any unallocated invoices based on the allocation principle specified in the active accounts receivable definition
- Invoice Items sub amounts and total amounts are calculated
- Back Office Code Validation -
Status colour Red title Available from CRM.COM R9.0.0 - If the back office code is specified then:
- System will validate that the back office is unique for that kind of financial transaction type
- If a back office code is not specified then
- No validation is applied
- If the back office code is specified then:
Refund
- SAVE AS DRAFT
- Life cycle state is set to draft
- Issued date is set
- Reference number is set
- Invoice Items sub amounts and total amounts are calculated
- Back Office Code Validation -
Status colour Red title Available from CRM.COM R9.0.0 - If the back office code is specified then:
- System will validate that the back office is unique for that kind of financial transaction type
- If a back office code is not specified then
- No validation is applied
- If the back office code is specified then:
- SAVE (POSTED)
If the refund is created and posted at the same time then- Life cycle state is set to posted
- Posted date is set
- Transaction number is set
- Invoice Items sub amounts and total amounts are calculated
- Back Office Code Validation -
Status colour Red title Available from CRM.COM R9.0.0 - If the back office code is specified then:
- System will validate that the back office is unique for that kind of financial transaction type
- If a back office code is not specified then
- No validation is applied
- If the back office code is specified then:
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 which is automatically generated on posting the Invoice |
Reference Number | The reference number of the Invoice which is automatically generated by creating the Invoice |
Accounts Receivable* | The Accounts Receivable that the Invoice is created for |
Financial Transaction Type* | The Financial Transaction Type. Only Financial Transaction Types classified as Invoices can be applied |
Life 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 is rejected while being in a 'Draft' Life Cycle State. |
Category | The category of the Invoice. Only Categories listed as 'Allowed' on the related Financial Transaction Type can be applied. |
Issued On | The date that the Invoice was issued on |
Posted On | The date that the Invoice was 'Posted' on |
Due On | The date on which the credit period for a '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 by this Financial Transaction. The following aggregated amounts are also calculated dynamically:
Invoices must contain at least one item |
Log Information | The standard set of Log Details information available in all entities |
Credit Note Attributes
Name | 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 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:
|
Log Information | The standard set of Log Details information available in all entities |
Payment Attributes
Name | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Number | The transaction number of the Payment which is automatically generated on posting the Payment | ||||||||
Reference Number | The reference number of the Payment which is automatically generated by creating the Payment | ||||||||
Accounts Receivable* | The Accounts Receivable that the Payment is created for | ||||||||
Financial Transaction Type* | The Financial Transaction Type.Only Financial Transaction Types classified as Payment can be applied | ||||||||
Life 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 is rejected while being in a 'Draft' Life Cycle State | ||||||||
Payment Method* | The method of Payment for the specific Transaction. Only Payment methods listed as 'Allowed' in the Financial Transaction Type can be applied. | ||||||||
(Payment) 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. Only Categories listed as 'Allowed' on the related Financial Transaction Type can be applied. | ||||||||
Issued On | The date that the Payment was issued on | ||||||||
Posted On | The date that the Payment was 'Posted' on | ||||||||
Received On* | The date on which the Payment was received | ||||||||
Received By User* | The user who received the Payment | ||||||||
Received By Unit* | The unit that received the Payment | ||||||||
Shared Notes | Notes for the payment. 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 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 in its creation and posting. This information is available only if the 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 which is automatically generated on posting the Refund |
Reference Number | The reference number of the Refund which is automatically generated by creating the Refund |
Accounts Receivable* | The Accounts Receivable related to the Refund |
Financial Transaction Type* | The Financial Transaction Type. Only Financial Transaction Types classified as Refund can be applied. |
Life Cycle State | The Life Cycle State of the Refund which can be any of the following:
|
Refund Amount* | The amount to be Refunded |
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. 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
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 for which the Payment Cancellation is issued | ||||||||
Shared Notes | 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 one Accounts Receivable 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 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Helpful Links
|