Category: Uncategorized

  • Interest Processing

    The interest posting creates an interest document, which contains an interest supplement.

    The interest supplement contains the items for which interest was calculated, as well as the relevant amounts, intervals, and the interest key. This allows you to identify which factors were used for interest calculation and posting.

    The interest key can be assigned to the contract account but can also be stored in the dunning level (if it was calculated in the dunning run) or entered in the relevant item (manually or automatically) which has the highest priority.

    The interest key consists of all control parameters for interest calculation and posting:

    • Parameters for item selection.
    • Reference to a calculation rule.
    • Period Control (The baseline date for interest calculation is Due Date + Grace Period + Transfer Days):
      • The tolerance days (grace period) is the minimum number of days that must have passed since the due date for net payment of a receivable before interest can be calculated. If the receivable is cleared within the tolerance period, no interest calculation or interest posting can take place. The tolerance period isn’t taken into account for interest calculations in the future (such as installment plan interest).
      • The calculation frequency determines the earliest point at which interest is calculated for an item if interest has already been calculated.
      • The transfer days refer to the period that it takes a bank to clear a payment and provide the clearing information. This ensures that interest calculation doesn’t take place on a receivable for which payment is delayed by the bank.

    nutanix certification malaysia

  • Installment Plan

    The installment plan can be created for one or more open items of the same contract account, provided they have the same currency. When selecting open items for installment plans, the priority with which original items of the plan are cleared when payments are received, can be specified.

    The installment plan creation requires the number of installments within the plan and the interest key. The interest key controls the grace period, interest frequency, interest interval unit, and the interest calculation rule. You can store frequently recurring installment terms and conditions in the system as default installment plans (installment plan types).

    When you create an installment plan, you can specify the percentage amount of the total amount that is to be used as the first installment. The system calculates the remaining installments as required.

    When you create an installment plan, you can also specify partial amounts.

    If the agreement for payment in installments is canceled, you can deactivate the installment plan manually. The original receivable is then active again. The link between the original receivables and the installment plan is deleted.

    Interest is calculated for the duration of the installment plan. Interest can be recalculated and posted if customers fall behind with their payments again. For example, a customer phones and requests an installment plan with 6 installments from Jan 1 to June 1. However, on Aug 1, the customer still has an outstanding balance. It is possible to calculate and post interest on the unpaid balance that exists after June 1.

    about

  • Dunning Run

    The dunning proposal- and activity run are started in the same way: entering the parameters and scheduling the start.

    The dunning activity run results in the dunning activities execution such as correspondence creation, note to agent or realease to collection agency.

    The dunning activity run results in charge and interest postings and in dunning history update as well.

    The dunning levels and appropriate dunning activities are determined during the dunning run based on the:

    • Dunning history on item level.
    • Dunning grouping on contract account level.
    • Dunning procedure on contract account or item level.

    The dunning activity run can’t be deleted after execution like a proposal run, even if the intended action wasn’t carried out. Instead, you must reverse the entire dunning run with the SAP Fiori App Reverse Dunning Notices Run or cancel dunning for certain individual items.

    The dunning proposal- and activity run are controlled by the dunning procedure on contract account or item level (see next figure).

    affiliation

  • SAP Cash Application and Machine Learning

    The SAP Cash Application enables an intelligent incoming payment processing powered by machine learning.

    The SAP Cash Application learns matching criteria from payments history and automatically creates matching proposals for incoming payments. It takes advantage of machine learning to enable an effortless setup and to increase automatic matching rates.

    The SAP Cash Application provides the following key points for your business:

    • SAP Cash Application is a cloud service that is tightly integrated with the SAP S/4HANA Cloud for Contract Accounting and Invoicing.
    • SAP Cash Application contributes essentially to the Total Cost of Ownership reduction because it provides higher automation rates than the classical approaches without any configuration effort. It boosts efficiency of the traditionally very labor-intensive clearing process, being executed with nearly no user interaction.
    • This higher automatization level allows you to focus more and more on strategic tasks for your business.

    rooms

  • Clarification Processing

    The SAP Fiori App Clarify Incoming Payments provides the following clarification possibilities:

    • You can correct the data to identify the item to be cleared and restart the posting.
    • You can clear manually. Partial clearings can be posted more than once. It is also possible to transfer posting items by using a short account assignment. In connection with this a workflow sends an e-mail to the department receiving the posting.
    • You can post the payment from the clarification account to the contract account, if the contract account can be found, but not the open item. This is called “posting on account”.
    • You can post the payment from the clarification account to an interim account (from where it could be selected later for a repayment run), if the contract account cannot be found.
    • You can create a repayment request if you could not assign the payment at the end. In this case, the amount is posted from the clarification account or interim account to a repayment clearing account.

    careers

  • Explaining the Customer-Initiated Payment Lot

    Customer-initiated payments are initiated by the customer because the customer determines when he wants to pay his debts to the company.

    Customer-initiated payments are only incoming payments.

    Incoming payments that can be assigned to an open item, clear that item as much as possible either by full payment, partial payment, or overpayment. Most of the open items are cleared automatically via the flexible and configurable clearing control.

    Incoming payments that can’t be assigned to an open item, are placed in the clarification list to be reviewed. From there, you can further process the payment either by posting it to an interim account (if the contract account cannot be found) or on account (if the contract account can be found, but not the open item) or by triggering a repayment.

    The clarification processing is explained in the respective lesson of this unit.

    Customer-initiated payments are processed by payment lots, check lots or, the cash journal.

  • SAP Digital Payments

    The SAP Digital Payments add-on should be used for the secure and compliant handling of credit card payments of your business partners and the payments processing via payment service providers (PSP).

    The SAP Digital Payments add-on provides the following key points for your business:

    • Automation means, that you can increase efficiency and reduce errors in reconciliations in the finance department.
    • Compliance means, that sensitive payment method data is stored out of your system to avoid PCI audit requirements.
    • SAP S/4HANA Integration means, that SAP Digital Payments is tightly integrated with the SAP S/4HANA Cloud for Contract Accounting and Invoicing.
    • Total Cost of Ownership reduction means, that future-proof services can be used across your system infrastructure.

    contact

  • Describing the SAP Digital Payments Add-On

    The SAP Digital Payments add-on should be used for the secure and compliant handling of credit card payments of your business partners and the payments processing via payment service providers (PSP).

    The SAP Digital Payments add-on provides the following key points for your business:

    • Automation means, that you can increase efficiency and reduce errors in reconciliations in the finance department.
    • Compliance means, that sensitive payment method data is stored out of your system to avoid PCI audit requirements.
    • SAP S/4HANA Integration means, that SAP Digital Payments is tightly integrated with the SAP S/4HANA Cloud for Contract Accounting and Invoicing.
    • Total Cost of Ownership reduction means, that future-proof services can be used across your system infrastructure.
  • Explaining the Returns Processing

    The posting logic of the returns lot is as follows:

    1. The receivable posting in contract accounting creates – after reconciliation key transfer – a posting on the general ledger’s receivable and the revenue account (tax is not shown).
    2. The company-initiated payment run is triggered in contract accounting and clears – after reconciliation key transfer – the general ledger’s receivable account against the bank clearing account and creates the outgoing payment medium.
    3. The payment in general ledger accounting clears the bank clearing account against the bank account.
    4. The incoming bank statement in general ledger accounting post the incoming returns on the bank account against the returns clearing account and creates a returns lot when it is uploaded. In this example, the returns total amount is 10 EUR higher than the original payment which is considered later as a bank charge.
    5. The returns lot processing in contract accounting distributes all returns of the lot to re-open the items (clearing reversal) and – after reconciliation key transfer – in the general ledger’s receivable account as well.
    6. The difference amount of 10 EUR is posted in general ledger accounting on the returns expenses account against the returns clearing account.
    7. The difference amount of 10 EUR is passed on to the business partner in contract accounting and – after reconciliation key transfer – on the returns receivable account against the returns revenue account in general ledger accounting.
    8. The returns charge is posted in contract accounting and – after reconciliation key transfer – on the returns receivable account against the returns revenue account in general ledger.

    php and mysql training courses malaysia

  • Payment Run Control

    The payment run control data is specified in the master data and in the line item to be payed. The payment run control data on line item level override the data on contract account level.

    The paying company code is used for the definition of house banks and payment methods. The payment methods are country-specific. For this reason, it’s only possible to select company codes within a country that has the same currency in each payment run.

    The payment run control data are divided into outgoing and incoming payment methods in the contract account master data, which flexibly refer either to one or more bank account with IBAN and SEPA mandate or to one or more payment card ID of the contract account’s business partner.

    The payment can be locked and default values for the lock duration can be configured. Furthermore, when debit memos fail, automatic debits can be prevented until a processing lock date is reached.

    The alternative payer pays all his contract accounts items together. Payment methods, banks, and locks are determined using this offsetting contract account.

    The payment run’s posting date is applied as the baseline date for determining the due date, except in the following cases:

    • If a deferral date has been entered in an item, it is always used to determine the due date.
    • If the cash discount date is prior to the posting date, the cash discount due date is used to determine the due date and the item is paid minus the cash discount.
    • If the cash discount period has expired, the due date for net payment is used.

    The due date for an item that is determined in this manner must fall within the due date interval entered in the payment run parameters.

    The grouping ensures, that items with the same term, for example items of the same invoice, are paid together.

    red hat openstack training courses malaysia