If your business is planning to make a move from an accounting solution like QuickBooks or Sage 50 to an enterprise resource planning ERP solution like SAP Business One, mastering the art of reporting is essential. Out of the box, SAP Business One contains many useful reports that provide business with great insight into their business performance, or in some cases their customers. With an Accounts Receivable Aging Report, you can gauge the financial health of your customers by categorizing accounts receivable according to how long an invoice has been outstanding.
Companies can see customers with zero balance, as well as those customers who that have the potential to create risk to your business. It is a critical report and yet is simple enough to generate and for decision makers in your business to analyze. Here's a few use cases of the Accounts Receivable Aging report:. It evaluates the credit quality of your customers and manages your cash flow.
To help you generate the report, Vision33 has created a guide with a step-by-step process. To access this free step-by-step guide as well as many other useful SAP Business One guides click the link below.
Vision33 Inc. Here's a few use cases of the Accounts Receivable Aging report: They determine if certain customers are credit risks. This can help businesses decide if they should or should not continue doing business with a customer that is frequently late paying their invoices, if at all. It is useful in determining the amount of bad debt to report on financial statements and how much should be written off. Aging Reports are valuable in establishing better business practices.
Companies can use this report to understand why they are having difficulty collecting on accounts, and how to improve their credit policies.
Quick Links. Contact Us. Customer Portal. Back to the Top. Sign up for the next demo!It displays documents together with the respective receivables. The report provides the value of the debt the customer has acquired and the length of time that the debt has remained unpaid. This topic documents fields and other elements in this window that either are not self-explanatory or require additional information.
If a document contains three installments, each installment is displayed in a separate row, and this field displays the value 1, 2, or 3, accordingly. Displays the original document total, the original total of the installment, or the total value of a manual journal entry line.
Figures in brackets indicate the payments received from customers that have not been applied for the period. Displays all open receivables owed by the customer according to the date selected in the Age By field and for which the date specified in the Aging Date field has not yet been reached.
In the Age By field, Due Date is selected. The Aging Date field is set to April 28th.
Customer Aging Report for HANA
Since the invoice is due after the aging date, the invoice amount is displayed in the Future Remit column. Displays the code of the project to which the document's journal entry is assigned.
Displays the code of the default payment method assigned to the business partner on the Accounting tab of the Business Partner Master Data window. SAP Business One displays the relevant open receivables in columns representing the specifications you made in the Interval field in the selection criteria window. The amount of future remit is first subtracted from the total sum of receivables.
The last column in each category includes open receivables for the respective category prior to the first columns. Days — Each column represents the number of days entered in the selection criteria window, starting from the aging date and moving back. Months — Each column represents one month, starting from the aging date month and moving back. Select the checkbox in this column to create a dunning letter for that document. The calculation for this field depends on the definitions in the Doubtful Debts - Setup window.
The sum of the invoices for each range of days is multiplied by the percentage defined for this range of days. In this report you are able to issue a journal entry to credit the customer for the doubtful debt. To create a journal entry for a doubtful debt, proceed as follows:.
Right-click the row and choose Journal Entry. A Journal Entry window opens.We would only want a simple display one line per customer like:. Customer code, Customer Name, Open balance per each due periods 30, 60, 90, I posted the same question, but for vendors, about three weeks ago.
I'm sorry to tell you that there is no standard report to meet your requirements. Check the archives. At my company, we had to develop a custom report for both vendor and customers.
Thanks for your feedback Guillaume, your proposed solution was explored and it did not fit our requirements. It might for Peter, there are several posted messages in the archives regarding aging reports, that is why I suggested Peter to take a look at those. Anyway, modification is always required to get a "good looking" aging report, there is no standard. Some name 15k Followers. Tech Sign In Page.
Forgot Password? Don't have an account? Sign up. We would only want a simple display one line per customer like: Customer code, Customer Name, Open balance per each due periods 30, 60, 90, Best Regards.
Follow Tech Sign In Page. Hi Peter, I posted the same question, but for vendors, about three weeks ago. August 20, PM. Something went wrong on our end. Please try again later. August 21, PM. August 22, PM. Sign In to Post a Comment. Sign In.I have tried one of the aging queries posted in the forum, but the results are incorrect for some customers. The logic from that query has some problems. It is not easy to understand the originators intention though. The misery is: it was marked problem solved.
I don't think it can bring the right result. Try correct it by yourself first. If you are unable to modify it, post your question here. I have used the query by Ken and modified the fields for SBOwhich can provide me the total pending. Not what you're looking for?
Customer Receivables Aging SQL query
Search community questions. This question has been deleted. This question has been undeleted. Former Member. Posted on Mar 02, at PM 1. Kindly help me with a query to generate a customer aging covering; 1. Invoices 2. Credit Memos 3. Payments 4.
Manual Journal Entries I have tried one of the aging queries posted in the forum, but the results are incorrect for some customers. Thanks in advance, Avinash. SAP Business One. Add comment. Related questions. Sort by: Votes Newest Oldest. This answer has been deleted. This answer has been undeleted. Posted on Mar 02, at PM. Post the query you tried here so that we can start troubleshooting. Thanks, Gordon. Alert Moderator. You already have an active moderator alert for this content.
Mar 02, at PM.I accidentally omitted this from the code I initially posted. The calculated date should add X days to January 1st of What's the reference to the beginning of the last century about? Wouldn't you rather say something like:. The logic that you have provide me is correct and easier then what I started out with, however after making the changes, the query runs with no errors, but returns no lines. The statement in its current form is rather confusing as a lot of code is duplicated and it is not easy to see what the intention is.
Not what you're looking for? Search community questions. This question has been deleted. This question has been undeleted.
Vinolan Pillay. Posted on Sep 02, at PM Views. Add comment. Sep 03, at AM. The error that I get is incorrect syntax near " " Line 7 Column Sep 04, at AM. Can you please verbally describe the rule you want to implement?
Wouldn't you rather say something like: "if the due date is days or more away from today then Sep 04, at PM. Hi Lars, The logic that you have provide me is correct and easier then what I started out with, however after making the changes, the query runs with no errors, but returns no lines. Thank you for all your assistance in helping me so far.It is the basic outline and can be used as base to modify as per customer requirements. CardCode, T1. CardName, T1. CreditLine, T0. RefDate, T0.
Customer Aging Report query
Debit- T0. CardCode, T0. MsgLevel 16, State 1, Line Try to run in SAP's Query generator to get the correct results! These will display error message when you wun query in SQL. This is a brilliant script. But is there a way of making this script as a summary. As im looking to make this detailed aged debtor as a summary aged debtor. Please note that the above query is semantically incorrect at least for version 9. All receivables with a partial reconciliation go missing in the above query!
You perform this query and use Instead, you don't see the position at all. You can't use the DueAmount from JDT1 either, because it only gives the current due amount, not the one it had back then.
So here is my proposal it's HANA syntax! It tested it against the standard report and it worked so far. I hope there are no mistakes while reducing the additional fields back to the original examples. I give no guarantees. Use it on your own risk. I just wanted to say thank you for posting this.
I have spent the last two months trying to analyse and join tables using the sales transactions tables.Any one can help to get data through aging report query? You can define custom aging buckets and publish report. Are you looking for how to define custom buckets or sql query to generate the data? Thanks for your reply. The customer number parameter and the currency parameter were given in the query as part of our requirement, so we added it. I found this query is quite useful and always matches with the standard receivable customer account figures always.
I used the optimizer hints for the speedy execution of the query. If we have Oracle Projects along with the financials and if we were to show the projects information, how do we do this?
Did anyone have this kind of scenario? Are you not able to get this info using standard aging report with custom buckets you can add using UI?
Please clarify. I am not sure that you can get aging report in 1 query. You have to write different cursor's for each bucket and all programs should be in part of same package. Dear Maha, The query which I gave is single query which will get you details of the customer aging.
Regarding writing a procedure and all, if you need to develop a report, you can straight away use my query in report, no procedure is required. You need to check if there are open transactions for which receipt has to be made in AR.
Then only I guess Aging report will return the data. Big Data. Tech Sign In Page. Forgot Password? Don't have an account? Sign up. Follow Tech Sign In Page. June 11, AM. Something went wrong on our end.
Please try again later. Regards, Mahalakshmi. Hi Maha, You can define custom aging buckets and publish report.
Please provide additional info about requirement. Srinivas Grandhi. Regards, Anil. Dear Maha, It's very simple create a procedure and follow the blow, it will fulfill your requirement. If you you have any questions, please don't hesitate to ask.