Get Even More Visitors To Your Blog, Upgrade To A Business Listing >>
Idioma: En

SAP Account Receivable


  1. Accounts Receivables

Sales OrderCaptures sales information ( Material, Quantity, Price, Delivery dates)
Delivery Note Entered based on SO information. It initiates picking and packing associated with delivering material to customer. Each delivery initiates goods issue transaction for recording goods stock change ( COGS Debit and Inventory Credit)
Billing DocumentLast document in SD. GL accounts decided based on account determination
Vendor InvoiceTriggered by billing document

Related Articles





  1. Define Acct group with screen layout (Customers)
  • Tcode: OBD2
  • Explanation:
  • When creating a customer master need to specify customer account group
  • Customer account group determine:
    • Customer account number
    • Whether the customer number is assigned internally by the system or externally by the user
    • Whether it's a onetime account
    • Which fields are ready for input when creating & changing customer master (Field status)






  1. Enter Accounting clerk identification code for customers
  • Tcode: SPRO – FA – ARAP – CA – MR – Preparation for creating customer master record – Enter accounting clerk identification code
  • Explanation:
    • Enter identification code (01) & clerk name (Mohit) for a company code (100)
    • Code entered in customer master record
    • Helpful in evaluation






  1. Define Industries
  • Tcode: Tcode: SPRO – FA – ARAP – CA – MR – Preparation for creating customer master record – Define industries
  • Explanation:
    • Define industry
    • Specify what industry a business partner belongs to by entering industry key in customer master record.
    • Helpful in evaluation, e.g. generate customer list for a industry












  1. Sales order to Cash Cycle
  • Sales Order – Delivery Note – Picking & Packing – Goods Issues (COGS Dr to Inventory Credit) – Billing document (Triggers AR Invoice in FI) – AR Invoice (Customer Dr to Sales Cr, Dunning Letters) – Customer Payments




  1. Create number range for customer accounts
  • Tcode: XDN1
  • Explanation:
    • Can create internal or external number range.
    • Internal : System automatically allot the number
    • External: User assigns the number in the specified range.

     




  1. Assign number range to Customer Acct group
  • Tcode: OBAR
  • Explanation:
    • We assign number ranges created in (XDN1) to customer account group (OBD2). Thus customer number for this customer a/c group can be selected from this range








  1. Alternative Recon Account for Down Payment: Refer TFIN Notes




  1. Extending Customers to Other company code
  • Tcode: FD15
  • Explanation:
    • Similar to Vendors discussed earlier






  1. Create customer master record
  • Create Customer Master : FD01
  • Display Customer Master : FD03
  • Display Customer Master : XD03
  • Display Customer Master : VD03
  • Display customer Credit Management : FD33
  • Change customer credit management : FD32
    • Choose the Central data screen and enter the following data:
      • Total amount
      • Individual limit
      • Currency
    • You can enter the central data in any currency you choose, independently of the currencies of the control areas.
    • The fields in the section entitled Current credit limit assigned show to what extent (as a percentage) the customer has exhausted the amount of credit granted to him and in which credit control area the maximum individual credit limit has been exhausted to the greatest extent.
    • - The Last general info field displays when the last information on the customer was obtained.
    • Now access the Customer Credit Management Change: Status screen and enter the individual credit limit for the customer.
  • Data:
Company codeCustomerRecon A/C
10003471140000
1000T-L69B09140000





  1. Posting a Customer Invoice
  • Tcode: FB70
  • Explanation:
    • Allows entering of customer invoices
    • If one time customer, required to enter customer name & address also






  1. Posting a credit memo with ref. to Invoice
  • Tcode: FB75
  • Explanation:
    • Business scenario: Customer overcharged & requested refund.
      • Exp/ Sales DR
      • To Customer CR






  1. Posting customer incoming payment manually
  • Tcode: F-28
  • Explanation:
    • Post customer incoming payment manually & clear OI
    • This transaction allows posting customer payments by referencing against a customer Invoice. This process is known as clearing. Where only a partial payment against customer invoice is received following options exist:
      • Partial Payment: Customer Invoice untouched. Payment on account created with reference to this invoice. In dunning both original unpaid invoice & payments are identified.
      • Residual Item: Here SAP system clears the original invoice but creates a new Invoice for the balance payment with reference to the original invoice






  1. Displaying customer account balances.
  • Tcode: FD10N






  1. Displaying and changing line items in a customer account
  • Tcode : FBL5N
  • Explanation:
    • Report can be exported to excel/ word
    • Can display / change line items
    • Can set filter to define additional search criteria for documents displayed. E.g. doc type



     
  1. Manual Clearing
  • Tcode: F-32
  • Explanation
    • Some customer invoices & payments received from customers, balance not zero. Use to clear these transactions. Clearing document generated with no real posting




  1. Clear customer down payment against customer invoice
  • Tcode: F-39
  • Explanation:
    • For installment payment of vendor invoice select payment term Z910
    • To block 2nd installment : Put payment block in maintain terms of payment of 2nd installment






  1. Customer Invoices
  • Park Customer Invoice : FV70
  • Post parked customer invoice : FBV0
  • Enter Customer invoice : F-22 / FB70
    • Use this SAP transaction to create a customer invoice or chargeback manually
  • Post customer incoming payment : F-52
    • Post incoming payments on both customer/ vendor
    • Allows to clear OI
    • Doc type : DZ ( Customer payment)
  • Customer down Payment life cycle : << Refer TFIN>>






  1. Display blocked SD documents
  • Tcode: VKM1
  • Table VBUK ( VKM1 display table)






  1. Customer Dunning Notices
  • Tcode: FI50
  • Explanation:
    • << Refer TFIN>>
    • A customer does not settle dues on time. Payment reminders to customers are known as dunning notices
    • Can send dunning notices to individual customers or a list of customers




  1. Customer due date analysis
  • Tcode: S_ALR_87012168
    • Due date analysis of customers (Invoices, credit memos)








  1. Configure Down Payment Received from customer
  • Tcode: OBXR / FBKP
  • Explanation:
    • Refer TFIN






  1. Reason Codes:
  • Tcode :OBBE
  • Tcode: FA – AR/AP – BT – Outgoing Payments – Manual outgoing payments – Overpayments/ Underpayments – Define Reason codes
  • Map Reason codes to GL Accounts: OBXL
  • Reason codes table: T053R
  • Explanation:
    • << Refer TFIN>>
    • RC explains the reason for diff between vendor invoice & payment doc amt. diff. Also this diff. amt. gets posted to different G/L accounts based on RC assigned

    • DescriptionReason CodeShort text of RCCorrespondence TypeHere we send notice to the customer for short payment. Can specify the type of notice that has to be associated with this RCCharge off diff. via separate a/cIf selected diff. charged off to the GL a/c selected for this RCDDisputed Item














  1. Define Accounts for payment Differences
  • Tcode: FA – AR/AP – BT – Outgoing Payments – Manual outgoing payments – Overpayments/ Underpayments – Define Accounts for payment differences
  • Explanation:
    • If no reason codes only a single entry is required, else separate accounts for various reason codes


S_ALR_87009895VAT ReportUse this SAP transaction to view VAT reporting and to post VAT settlement.

Transaction is run at month end after transactions have been completed. When settlement is run the balances of the 11005001 output tax and 22010000 input tax accounts are zeroed out and the balance of each is moved to the 12600000 VAT Settlement account.
SM35 Batch Input MonitoringUse this SAP transaction to monitor and process batch input sessions to post all the applicable documents and perform all the database updates.


This post first appeared on OM SAP, please read the originial post: here

Share the post

SAP Account Receivable

×

Subscribe to Om Sap

Get updates delivered right to your inbox!

Thank you for your subscription

×