Versions Compared

Old Version 5

changes.mady.by.user Persia Xenopoulou

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Excerpt
hiddentrue

Understand the usage of Financial Transactions within CRM.COM

What does this section cover?

Back to Financial Transactions Main Page

Panel
nameblue

Table of Contents

Table of Contents
minLevel2

What are Financial Transactions?

Financial Transactions are statutory transactions, governed by the accounting standards of the country, carried out between two parties, the business and the customer, to exchange services or physical goods. The A Financial Transaction is an agreement between a buyer and a seller to exchange Services or Physical Goods for payment. The transaction’s nature is differentiated by its type Type (invoiceInvoice, credit noteCredit Note, paymentPayment, refund Refund etc.). Financial Transactions impact the balance of the customer's accounts receivable and the information kept on each of them depends on their typeIt involves a change in the status of the finances of the businesses or individuals involved, which is directly reflected on the customer's Accounts Receivable by updating its Balance.

Financial Transactions Glossary

Draft
TermsDescription
Financial Transaction Draft financial transactions are transactions which were not posted yet, and can be edited posted or rejected. Draft financial transactions do not affect accounts receivable balances.
Posted Financial TransactionPosted financial transactions are permanent and cannot be edited by any means. Posted financial transactions affect accounts receivable balance. The credit period of an accounts receivable starts from the date that the financial transaction is posted.
Rejected Financial TransactionRejected financial transactions are transactions that were draft and were rejected instead of being posted. Rejected financial transactions cannot be edited. Rejected financial transactions do not affect accounts receivable balances.
Issued DateThe date that a financial transaction was created, either in draft or posted life cycle state. The credit period of an accounts receivable is not calculated based on the issued date.
Posted DateThe date that a financial transaction was posted and started to affect the accounts receivable balance. The credit period of an accounts receivable starts from the date that the financial transaction is posted.

Financial Transactions Key Processes and Concepts

Processes / ConceptDescription
Cancelling Versus Rejecting Financial Transactions

Financial Transactions cannot be deleted. If they have been erroneously created then you can correct them by using either the Cancel or Reject action. Both actions will not be taken into consideration by any financial process of the system.

  • Use the Cancel action of you have already posted the invoice or the payment
    • Cancel action is available for Invoices and Payments
  • Use the Reject action if the transaction is still is Draft state
    • Reject action is available for all Financial Transaction Classifications
Posting of Financial TransactionsFinancial Transactions belong to an account of a customer or to a system account. In order for a Financial Transaction to affect the balance of the account, it needs to be Posted (Life Cycle State). The Posting process can be done directly when creating the Financial Transaction by using the SAVE button, or you have the option to create the financial transaction in state Draft, by using the Save as Draft button and use the Post action at a later stage.
Allocation of Credit Transactions on Invoices 

Financial Transactions Network Characteristics

Network Characteristics define the level of access for each record. i.e. Whether it will be available for selection, for viewing or editing etc.

EntityNetwork Characteristics

Financial Transaction Types

Financial Transactions

Financial Transactions Related Modules

Interaction EntityHow
Accounts ReceivableFinancial Transactions Posted against Accounts Receivable
BillsFinancial Transactions Included in Bills
Customer EventsFinancial Transactions can automatically purchase Customer Events (if configured accordingly)
Classification

The Classification determines the nature of the Financial Transaction, including its notation in the double-entry accounting system (debit or credit). Financial transaction type classifications are predefined in the system and cannot be overridden.

The following Classifications are available:

  • Payment : Used to credit the account. i.e. deduct money from balance
  • Invoice: Used to debit the account. i.e. add money to balance
  • Credit Note: Used to credit the account. i.e. deduct money from balance
  • Refund: Used to debit the account. i.e. add money to balance (Can only be created if a negative account balance exists)
  • Invoice Cancellation: Used to credit the account. i.e. deduct money from balance
  • Payment Cancellation: Used to debit the account. i.e. add money to balance
PaymentA Payment is a financial document issued by a customer to a business to settle an outstanding balance. Payments are crediting Accounts Receivable
InvoiceAn Invoice is a financial document that shows a list of services or physical goods and the prices to be paid for them. Invoices are debiting Accounts Receivable
Credit NoteA Credit Note is a financial document issued by a business to a customer to correct mistakes or adjust the amount that the customer was invoiced. Credit Notes are crediting Accounts Receivable
RefundA Refund is a financial document issued by a business to a customer in order to pay back a specific amount of money. Refunds are typically issued to customers who are not satisfied with the Services or Physical Goods that were provided to them and not to adjust or cancel specific Invoices. Refunds are debiting Accounts Receivable
Invoice CancellationAn Invoice Cancellation is a financial document which is issued to cancel a specific Invoice. Invoice Cancellations are crediting Accounts Receivable
Payment CancellationA Payment Cancellation is a financial document which is used to cancel a specific Payment. Payment Cancellations are debiting Accounts Receivable
Financial Transaction Life Cycle State: 'Draft'A 'Draft' Life Cycle State represents a Financial Transaction which is not yet posted, and can still be edited, posted or rejected in the future. Financial Transactions in a 'Draft' Life Cycle State do not affect the Accounts Receivable Balance.
Financial Transaction Life Cycle State: 'Posted'A 'Posted' Life Cycle State represents a Financial Transactions that can no longer be edited. Financial Transactions in a 'Posted' State affect the Accounts Receivable Balance.
Financial Transaction Life Cycle State: 'Rejected'A 'Rejected' Life Cycle State represents Financial Transactions that went from being 'Draft' to being ''Rejected'' instead of being 'Posted'. 'Rejected' Financial Transactions cannot be edited and do not affect Accounts Receivable Balance.
Due DateThe date by which an Invoice must be settled. Due Date is set either manually or automatically and must always meet predefined configurable system rules.
Issued DateThe date on which a Financial Transaction is issued, either in a 'Draft' or 'Posted' Life Cycle State.
Posted Date

The date on which a Financial Transaction is 'Posted'.

Financial Transactions Key Processes and Concepts

Processes / ConceptDescription

'Cancelling' Vs 'Rejecting' Financial Transactions

Financial Transactions cannot be deleted. If they have been created accidentally, then this can be corrected by using the 'Cancel' or 'Reject' action. Neither action will be taken into consideration by any of the system's financial processes.

  • Use the 'Cancel' action for Invoices and Payments that have already been 'Posted'. The Cancel action creates new Financial Transactions of the respective classification
    • Invoice Cancellation
    • Payment Cancellation 
  • Use the 'Reject' action for all Financial Transaction Classifications, if the Transaction is still is 'Draft' Life Cycle State.
    Reject action will change the Financial Transaction's Life Cycle State to Draft. 
Posting of Financial Transactions

Financial Transactions created in 'Draft' Life Cycle State by using the Save As Draft button can be posted at a later stage by using the ' Post' action.Alternatively, you can set the Life Cycle State of a Financial Transaction directly to 'Posted' by using the SAVE button instead of Save as Draft

  • Use the 'Save as Draft' to save as 'Draft', when you do not want the Financial Transaction to be taken into consideration by any System financial process, yet
  • Use Save to save as 'Posted' and have the Financial Transaction being taken into consideration by System Financial Processes
Allocation of Credit Transactions on Invoices

Allocations are used to allocate Credit Financial Transactions against Invoices, in order to settle any outstanding amount. Allocations are applied automatically by the System based on the allocation principle specified on the active Accounts Receivable Definition.

View Accounts Receivable as well as Understanding the Allocation Principles for a description of how the allocation principle works in CRM.COM

Financial Transactions Access & Viewing Controls

Business Network Characteristics define the level of access for each record. i.e., whether the record will be available for selection, viewing or editing.

EntityNetwork CharacteristicsDescription

Financial Transaction Types

  • A Type can be applied on a Financial Transaction, by users who belong to one of the Allowed Organisational Units defined in the Type,or by Users who belong to a Group that collaborates with the Allowed Organisational Units, or by Super Users.
Financial Transactions
  • Financial Transaction records can be accessed viewed and modified by Users who belong to the Group defined at the Owned By Group of the related Accounts Receivable, or that belong to a Group that collaborates with the specified Group or by Super Users

Financial Transactions Related Modules

EntityInteraction with the Entity
Accounts ReceivableFinancial Transactions are Posted against Accounts Receivable. The balance of the account is updated when Financial Transactions are posted
BillsFinancial Transactions are included in the Bill as Bill Lines
Wallet TransactionsFinancial Transactions can be related with Wallet Transactions via the Wallet related to the Accounts Receivable. i.e. if configured accordingly, whenever a Financial Transaction is created against the Accounts Receivable, a respective Wallet Transaction can be created against the Wallet.

Financial Transactions  - Business Examples

The following section provides business examples to help you understand how CRM.COM of how the Financial Transactions  module module is used in CRM.COM.

Posting Refunds after Bank

payment

Payment confirmation

Panel
nameblue
titlePosting Refunds after Bank payment confirmation

Business Requirement

Company ZX would like to create Refunds once a month for any its customers with a negative outstanding balance. The Refunds are paid out to the customers via through their bank account. Once the bank makes the payment out Payment to the customer's account, the bank sends a file back to Company ZX with all the successful paymentsPayments. Only then will Company ZX would like to can the update the customer's accounts balancebalances.

CRM.COM Solution

  • User Process
    All the Refunds should be created in life cycle state Draft and a 'Draft' Life Cycle State and be sent out to the bank. Once the file with the successful payments, Payments is received from the bank then each of those refunds , the Refunds should be accessed and updated to Posted. In this way the balance of the account will be automatically updated taking into consideration the Refund amount'Posted', (automatically) updating the Balance of the account by that amount.
Note

More Information on Posting Refunds can be found at : Posting Draft Managing Financial Transactions.

Cancelling

erroneously created Invoices

Invoices created by Error

 

Panel
nameblue
titleCancelling erroneously created Invoices

Business Requirement

Company ZX would like to cancel any invoices that are already posted and have been erroneously created'Posted' Invoices that were created by error.

CRM.COM Solution

  • Configuration
    An operations 'Operations' user should be responsible for cancelling such invoices. Admin Invoices created by error. 'Admin' users can configure different types of 'Invoice Cancellation classified transactionsClassified Transactions', in order to differentiate between different reasons for cancelling an invoiceInvoice. For example, Cancellation Error Invoices & Cancellation Complain Complaint Invoices.
  • User Process

    The user should select the invoice Invoice to be cancelled and create a Financial Transaction of the respective typeappropriate Type.

    In this way the invoice As a result, the Invoice will be available for future reference but it will not affect without affecting the account's balance, while any user can have a clear picture of why it was cancelled based on the FT Invoice Cancellation type and if more information is needed, then Balance. The Financial Transaction 'Invoice Cancellation Type' indicates the reason the Invoice was cancelled. More detailed information can be viewed through the Cancellation's transaction Issue Reason may be accessed by the detail page to get extra information.

 

Note

More Information on Cancelling Invoices can be found at : Cancelling Invoices Managing Financial Transactions.

 

Cancelling

erroneously created Payment

Payments created by Error

Panel
nameblue
titleProvide a title for the business example. (Keep simple and short)

Business Requirement

Company ZX would like to cancel any payments Payments that are already posted and 'Posted' that have been erroneously created by error.

CRM.COM Solution

  • Configuration
         An operations 'Operations' user should be responsible for cancelling such paymentsPayments. 'Admin' users can configure different types of 'Payment Cancellation classified transactionsClassified Transactions', in order to differentiate between different reasons for cancelling a paymentPayment. For example, Erroneous Payments Cancellation Payments & Erroneously Allocated Payments Cancellation Payments.
  • User Process

    The user should select the invoice Invoice to be cancelled and create a Financial Transaction of the respective type appropriate Type.

    In this way the payment As a result, the Payment will be available for future reference but it will not affect the account's balance, while any user can have a clear picture of why it was cancelled based on the FT Payment Cancellation classification and if more information is needed, then without affecting the account's Balance. The Financial Transaction 'Payment Cancellation Classification' indicates the reason the Payment was cancelled. More detailed information can be viewed through the Cancellation's transaction Issue Reason may be accessed by the detail page to get extra information.

 

Note

More Information on Cancelling Payments can be found at : Cancelling Payments Managing Financial Transactions.

 

Move Payments from Suspense Account to

customer accounts

Customer Accounts

 

Panel
nameblue
titleMove Payments from Suspense Account to customer accounts

Business Requirement

Company ZX imports payments Payments from the bank through an import file.
If the destination intended account is not found then the payment Payment will be created in Company ZX system Suspense account. Back office personnel are responsible to manually check and move the payments Payments to the correct customer account.

CRM.COM Solution

  • User Process

    BackOffice Back office operators should follow the process described below:

    Company's ZX backoffice Back office personnel should daily access Company's ZX suspense account . For each of the payments which the correct account has been found the daily. The action "Move to Account" should be executed for each of the Payments once the intended account has been determined.

     
Note

More Information on Move Payments from Suspense Account to customer accounts can be found at : Moving Payments to another Accounts ReceivableManaging Financial Transactions.

 

Company ZX issuing an

invoice with Discount

Invoice with a Discount

 

Panel
nameblue
titleCompany ZX issuing an invoice with Discount

Business Requirement

A customer of Company ZX has bought purchases 2 Cards. For both of the cards he received He gets a discount for both, 15% for the first one and 20€ discount from €20 for the other one. One of the two cards would be is charged with 0 VATa VAT rate of 0%.

CRM.COM Solution

  • User Process

    Create a new Financial Transaction of type Type Invoice. In the Items tab add 2 lines with the following information

    1. Card 1
      • Cost: 100
      • Quantity: 1
      • Discount
        • Discount Percentage: 15%
      • VAT Rate
        • VAT rate:15%
    2. Card 2
      1. Cost: 100
      2. Quantity: 1
      3. Discount
        • Discount Amount: 20€ €20
      4. VAT Rate
        • VAT rate: 0%

    System Calculations:

    1. Card 1
      1. VAT Amount: (100-15)*15/100 = 12.75
      2. Subtotal: (100-15+12.75) = 97.75
    2. Card 2
      1. VAT Amount: 0Subtotal: 80: 0
      2. Subtotal: 80

 

Note

More Information on Issuing Invoices can be found at Managing Financial Transactions.


 

Company ZX - Invoice Due Dates - Fixed Date

 

Panel
nameblue
titleCompany ZX - Invoice Due Dates - Fixed Date

Business Requirement

Company ZX would like to have the Due Date always fixed to wants the 15th day of the next month as the Invoice 'Due Date'.

CRM.COM Solution

  • Configuration 

    The Accounts Receivable Credit Rule should be set up defining the xnth day to be equal to 15 after x months to be are equal to 1.

  • User Process
    When Posting the Invoice:

    • If the user defined the date then according to the date provided the system will validate accordingly. For example if defines a date, the system either validates the date or returns an error message. e.g. In case the Date of Posting is 20th of on 20 May:
    • If the 'Due Date' is Set : to 21/05 System Message: an "Invalid Due Date" message is returned from the system
    • If the 'Due Date set: ' is Set to 16/06 System Message: an "Invalid Due Date" message is returned from the systemDue Date set:
    • If the 'Due Date' is Set to 15/06 no error message is returned and the 'Due Date Saved' is saved successfully
  • If the user leaves the 'Due Date' empty then the system will set the Due date automatically it to 15/06

 

Business Requirement

Company ZX would like to have the 'Due date to Date' always be set 10 days after the 'Posted dateDate'.

CRM.COM Solution

  • Configuration
         The Accounts Receivable definition 'Credit Rule' should be set up defining X Days after the transaction's 'Posted Date: ' ( X = 10)
  • User Process 

    When Posting the Invoice:

    • If the user defined the date then according to the date provided the system will validate accordingly. For example if defines a date, the system either validates the date or returns an error message. e.g. In case the Date of Posting is 20th of on 20 May:
      • If the 'Due Date Set: 28/05
        • System Message: Invalid Due Date
      • Due Date set: 31/05
        • System Message: Invalid Due Date
      • Due Date set: 30/06
        • Due Date Saved
    • If the user leaves the Due Date empty then the system will set the Due date automatically to 30/06

Business Requirement

Company ZX would like to allow agents to set the due date max to 10 days after the Posted date but the system should automatically set the due date to 5 days after posted date

CRM.COM Solution

  • Configuration

    The Accounts Receivable definition Credit Rule should be set up defining X Days after transaction's Posted Date: X= 10

    Proximity range should be set to -5

  • User Process

    When Posting the Invoice:

    • If the user defined the date then according to the date provided the system will validate accordingly. For example if the Date of Posting is 20th of May
      • Due Date Set: 28/05
        • Due date saved
      • Due Date set: 31/05
        • System Message: Invalid Due Date
      • Due Date set: 30/06
        • Due Date Saved
    • If the user leaves the Due Date empty then the system will set the Due date automatically to 25/05 (The smallest allowed dua date based on the Proximity Range set)
Note

More Information on Invoice Due Dates can be found at: Handling Invoice Due Dates

 

FIFO Versus FIFO & Against Item Principle

Creation of Invoice 2
      • ' is Set to 28/05 an "Invalid Due Date" message is returned from the system
      • If the 'Due Date' is Set to 31/05 an "Invalid Due Date" message is returned from the system
      • If the 'Due Date' is Set to 30/06 no error message is returned and the 'Due Date' is saved successfully
    • If the user leaves the 'Due Date' empty then the system will set it to 30/06

Business Requirement

Even though Company ZX would like to allow agents to set the 'Due Date' at a maximum of 10 days after the 'Posted Date', it requires the System to set the 'Due Date' to 5 days after the 'Posted Date'.

CRM.COM Solution

  • Configuration

    The Accounts Receivable definition 'Credit Rule' should be set up defining X Days after transaction's 'Posted Date' (X = 10)

    Proximity range should be set to -5

  • User Process

    When Posting the Invoice:

    • If the user defines a date, the System either validates the date or returns an error message. e.g. In case the Date of Posting is on 20 May:
      • If the 'Due Date' is Set to 28/05 no error message is returned and the 'Due Date' is saved successfully
      • If the 'Due Date' is Set to 31/05 an "Invalid Due Date" message is returned from the system
      • If the 'Due Date' is Set to 30/06 no error message is returned and the 'Due Date' is saved successfully
    • If the user leaves the 'Due Date' empty then the system will set it to 25/05 (the smallest allowed 'Due Date' based on the set 'Proximity Range')
Panel
nameblue
titleFIFO Versus FIFO & Against Item Principle

FIFO Principle

In the following example, we have one invoice which has already been allocated to a credit note using the FIFO model. A second invoice is created and then the first invoice is cancelled.

  1. Invoice 1: $20
  2. Invoice 2: $10
  3. Credit Note 1: $20
No
Action
Intended Invoices
Allocations
Allocation Type
Allocation amount
Unallocated Amount
1Creation of Invoice 1N/AN/AN/A  
2Creation of Invoice 2N/AN/AN/A  
3Creation of Credit Note 1N/ACredit Note 1 allocated on Invoice 1FIFO20 
4Cancellation of Invoice 1Invoice 1

 

 

   
4a

Credit Note 1 de-allocated from invoice 1

N/AN/ADe-allocation20 
4b

Creation of Cancellation Invoice 1

N/AInvoice 1 allocated on Cancellation Invoice 1Against Item20 
4cCredit Note 1 allocated on Invoice 2N/ACredit Note 1 allocated on Invoice 2FIFO1010

 

FIFO & Against Item Principle

In the following example, we have 3 invoices of which the 2 first are allocated from Credit Notes that were intended for them. Then the first invoice is cancelled.

  1. Invoice 1: $10
  2. Invoice 2: $20
  3. Invoice 2: $30
  4. Credit Note 1 : $20 (Intended Invoice: Invoice 2)
  5. Credit Note 1 : $10 (Intended Invoice: Invoice 1)
No
Action
Intended Invoice
Allocations
Allocation Type
Allocation amount
Unallocated Amount
1Creation of Invoice 1N/AN/AN/A  
2
Note

More Information on Invoice Due Dates can be found at Handling Invoice Due Dates.

 

FIFO Versus FIFO & Against Item Principle

 

 

Principle

In the following example, we have 3 Invoices of which the 2 first are allocated from Credit Notes that were intended for the invoices in question. The first Invoice is then cancelled.

  1. Invoice 1: €10
  2. Invoice 2: €20
  3. Invoice 3: €20
  4. Credit Note 1 : €10 (Intended Invoice: Invoice 1)
  5. Credit Note 2 : €20 (Intended Invoice: Invoice 2)
Panel
nameblue
titleFIFO Versus FIFO & Against Item Principle

FIFO Principle

In the following example, we have one Invoice which has already been allocated to a Credit Note using the FIFO model. After a second Invoice is created the first Invoice is cancelled.

  1. Invoice 1: €20
  2. Invoice 2: €10
  3. Credit Note 1: €20
 Creation of 1
No
Action
Intended Invoices
Allocations
Allocation Type
Allocation amount
Unallocated Amount
1Creation of Invoice 1N/AN/AN/A  
2Creation of Invoice 2N/AN/AN/A  
3Creation of Credit Note 1N/ACredit Note 1 allocated on Invoice 1FIFO20 
4Cancellation of Invoice 1Invoice 1

 

 

   
4a

Credit Note 1 de-allocated from Invoice 1

N/AN/AN/ADe-allocation20 
34b

Creation of Cancellation Invoice

2

1

N/AN/AN/A Invoice 1 allocated on Cancellation Invoice 1Against Item20 
44cCredit Note 1 Invoice 1allocated on Invoice 2N/ACredit Note 1 allocated on Invoice 2FIFO1010

 

FIFO

and

& Against Item

100
5Creation of Credit Note 2Invoice 2Credit Note 2 allocated on Invoice 2FIFO and Against Item200
4Cancellation of Invoice 1 

 

 

 4b 3
No
Action
Intended Invoice
Allocations
Allocation Type
Allocation amount
Unallocated Amount
1Creation of Invoice 1N/AN/AN/A  4a

Credit Note 1 de-allocated from invoice 1

2Creation of Invoice 2N/AN/ADe-allocation100N/A  
3Creation of Cancellation Invoice 13 Invoice 1 allocated on Cancellation Invoice 1Against Item2004cCredit Note 1 allocated on Invoice 3 N/AN/AN/A  
4Creation of Credit Note 1Invoice 1Credit Note 1 allocated on Invoice 1FIFO and Against Item10100
Note

More Information on FIFO Versus FIFO & Against Item Principle can be found at: Using the Allocation Principles

 

Restrict rights to cancel Payments to certain users

More Information on Restrict rights to cancel Payments can be found at: Configuring Financial Transaction Types
Panel
nameblue
titleRestrict rights to cancel Payments to certain users

Business Requirement

Company ZX would like to be able to cancel payments due to user errors, however only Operation users should be allowed to make this cancellations. However all users should be allowed to make cancellations of payment.

CRM.COM Solution

  • Configuration

    2 Financial Transaction Type of Classification Payment Cancellation will need to be configured in the system.

    • Payment Cancellation
    • Payment Cancellation Special

    Both types will be configured in exactly the same way apart from the "Allow Selection only for Units" tab.

    For the Payment Cancellation Special the "Operations" Unit will be added.

    In this way, when cancelling a payment the Payment Cancellation Special type will only be available to users that belong to the Operations unit; type: Payment Cancellation on the other hand will be available for all users to select

 

Note
5Creation of Credit Note 2Invoice 2Credit Note 2 allocated on Invoice 2FIFO and Against Item200
4Cancellation of Invoice 1 

 

 

   
4a

Credit Note 1 de-allocated from Invoice 1

 N/ADe-allocation100
4b

Creation of Cancellation Invoice 1

 Invoice 1 allocated on Cancellation Invoice 1Against Item100
4cCredit Note 1 allocated on Invoice 3 Credit Note 1 allocated on Invoice 3FIFO1010
Note

More Information on FIFO Versus FIFO & Against Item Principle can be found at Understanding the Allocation Principles.

 

Payment Methods accepted by Company ZX

 

Panel
nameblue
titlePayment Methods accepted by Company ZX

Business Requirement

Company ZX only allows its customers to pay using Cash and Credit Cards.

A

It wants to introduce a new way of

payment will be introduced

Payment in order to allow customers to also pay via PayPal

and these

. This type of

payments

Payments would need to be distinguished on the Payment level as

in the future more ways

more types of online Payment other than Paypal might be added

for online payments apart from Paypal

in the future.

CRM.COM Solution

  • Configuration
3 Payments

  • Three Payment Types will need to be configured in the system:

    • Cash
    • Credit Card
    • PayPal
On the Financial Transaction Types configuration module 2

  • Two different Payment Types should be created

.

  • in the Financial Transaction Types Configuration Module:

    • Normal Payment
    • Online Payment

    For each of the 2 Payment Types different Allowed

payment

  • Payment Methods will be configured:

    • Normal Payment
      • Cash
      • Credit Card
    • Online Payment
      • Paypal
Note

More Information on Payment Methods can be found at

:

Configuring Payment Methods.

 


Rejecting Payments Options 

 

Panel
nameblue
titleRejecting Payments Options

Business Requirement

Company ZX allows rejection on payments on Payments to be rejected in the following occasionscases:

  • Agent Error
  • System Error
  • On customer Requestrequest

CRM.COM Solution

  • Configuration

    In CRM.COM 4 different rejection reason should be setup in the system and to be used by the personnel when rejecting a paymentThe following four reasons for Payment rejection should be set up for use in the system:

    • Agent Error
    • System Error
    • On customer Request
    • Other (in this case the user can write the related information give an explanation for the rejection in the "Issue Reason free " text "box

 

Note

More Information on Rejecting Payments Options can be found at : Configuring Rejection Reasons.

Panel
namegrey

Related Areas

Filter by label (Content by label)
showLabelsfalse
spacesV4Manual
showSpacefalse

excerpt

true

labelsfinancial-transactions-basics-r7,financial-transactions-advanced-r7,financial-transactions-admin-r7

Panel
namegrey

Popular Labels

Popular LabelsspaceKeyV4Manualstyleheatmap