Discussions about property management edition features
- 15 Topics
- 39 Replies
I have some leases with multiple monthly charges, but they add up together as one item on the statement
RE: LEASE/CHARGESI have some leases with multiple monthly charges, but they add up together as one item on the statement. Am I missing how to separate these charges so they appear seprate and not together?For example, in very simple terms: Let’s say this tenant pays two monthly charges per month:Rent $5Tax $5I want these to appear just like this on our monthly statements, but instead they are added up as one item and looks like this:Lease Billing $10How can I get these to appear as two separte charges? Because it’s very confusing for some of our tenants. Or is there another way to do multiple monthly charges?
I have some leases with expiring ‘BILL END DATES,’ yet their Charges expire years from now a well as their ‘LEASE END DATE.’ I was wondering if anyone had a method for updating these Bill End Dates, because I don’t know if that means these leases will no longer get invoices.Also, what exactly does Bill End Date mean? As far as I am concerned, the invoices should still produce based on the charge codes, etc. Any insight? Thank you!
Hello, I am new to Acumatica and trying to figure this all out. We created a new Company, Branches, ledgers, etc and from that we created our Customer and Lease. We are trying to post a payment, but we are getting this error message:Inter-Branch Transactions feature is disabled.What does this mean? Thank you.
Next Lease Billing Date does not match my Charge Codes Schedule or BILL DATE when I created these leases
I have this issue everytime I create a new Lease with the system. The NEXT BILLING DATE is always wrong and does not match the BILL STATE DATE that I create under DATES in the LEASES panel.In these cases:Lease ID LS00292 - under summary, it says the next lease billing date is 10/15/2022, but I need it to be 10/01/2022Lease ID LS00293 - under summary, it says the next lease billing date is 10/15/2022, but I need it to be 10/01/2022In both these cases, I did create the Leases on August 15th. But for the Charge Schedule, I wanted the rent to start 09/01/2022. I tried to correct the dates, ran Contact Billing and now they both say Next Lease Billing Date is 10/15/22. How do I get off this mid-month schedule? I just need these leases to be on a scheudle where the Next Billing Date is on the 1st of the month. I am not sure why this mistake happens every time lol.
After upgrade to 2021 R2 According to above screenshot you can see that once click on close button from action then its going to update data and then disable the button of close then its show dilogbox so once click on ok button then its display error that close button disable
We can no longer post payments to our system. There was apparently some update which gave us this error message on our login screen: Warning: customization failed to apply automatically after the upgrade.In all honesty, this system is too buggy to be used. I am seriously thinking of switching to a program like Yardi, which specializes in Real Estate. Imperiam is just a mess. Anyone else having this issue where items are not loading in Payment and Applications? This has happened in the past because of an update.
I cannot advance the "Next Billing Date" for one of my leases. I get an error message, as described in the thread.
“Next Billing Date” for one of my leases says 06/01/2022. I am trying to advance it to 7/1/2022, or even better 8/1/2022, since I ran July invoices already.On the LEASE page, I tried to run Contract billing, but I get this error message: Unable to cast object of type 'PX.Data.PXCommandPreparingException' to type 'PX.Data.PXOuterException'.I also tried to change the dates on my Charge Schedule, but it didn’t work.
Bear with me on this -- I’ll eventually get to the real question… Acumatica has recently acquired Imperium, a property management module. Installation of Imperium also includes and requires a license manager. I have discovered that this license manager prevents other customizations from being published if they include database scripts which include certain T-SQL that it considers prohibited. What I’d like to know is if this license manager can be configured to stop prohibiting other customizations from publishing, and what T-SQL it considers prohibited, and if there is no way to turn it off, will it always be the case that use of Imperium will be limiting database script content?
I ran into an error when publishing a customization project that I haven’t seen before: “The '<project name>' customization project contains a prohibited database script”. The customization has published without errors and the db script in it executes fine on many different Acumatica instances except for this particular one. The db script just drops a view if it exists, and then creates the view. The Acumatica build is 21.115.0017. The error shows up right away after selecting Publish. Did I miss something in the release notes somewhere where certain db commands are no longer allowed in scripts, or could it be a licensing or permissions issue of some kind?
Login to the community
Social LoginLogin with your Acumatica account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.