User_NG9BL Red Ribbon

Thank you for your feedback, but as I understand it, all of the above applies to A/R and not A/P as mentioned above. Does the Consolidated Billing feature apply to both A/P & A/R?

My question is in a similar vein but applies to vendors. Did anyone find a resolution to the above? The use case is where one subsidiary is paying for another subsidiary's vendor bills, and in most cases the vendor bill is in another currency. The concept is "Intercompany Payment on behalf of" - SAP S/4 (I know, I know) by…

Did anyone ever get an answer on this? And is there a possibility to establish a SuiteTax Tax code that defines the tax basis as the taxable amount? I have a client who is forced to use SuiteTax as one of their 20 subsidiaries is in India, but with SuiteTax we don't seem to be able to identify a different tax basis

This is a possible answer if someone comes up with this problem again. I was able to tie this to someone having inactivated specific roles that could be affected by localization packages. Reactivating those roles resolved the problem

Is there any way to add the UoM to the kit/package in NetSuite? This is a required field for Mexico electronic invoices to the tax authority. The current work-around is to break out each kit/package into their individual pieces and re-price the units. It's painfully slow and not scalable as we enter the Xmas rush

Ok - this has been reported since January '23 as a result of the 2022.2 bug on Consolidated Exchange Rates. To go over the same information again on the proposals above and how it worked correctly prior to this bug. A Direct Rate is to be used for entities(subsidiaries) with transactions while a Derived Rate is used for…

This is actually related to the derived rates. With the 2022.2 average and historical consolidated rates bug, the entities below the region are now using derived rates instead of the system calculated ones for that given level. When correcting the errors, one has to manually calculate the average and historical exchange…

I've run into the same issue. Support/Product Mgr advised us to recalculate all transactions for all periods manually then update at the regional level which will be inherited by the Region's children. In one case, this was/is tens of thousands of transactions per month and they do not have the Average Consolidated…

Given the dates on this thread, you may want to check which exchange rate is being used. As a result of a bug in 2022.2, there are multiple issues with Consolidated Exchange Rates. Should one run a report in the current period (e.g. post close of the previous period), many reports are calculating the values using the…

OK - for anyone else who runs into this fun problem with the latest Brazil localization package released in late 2022. Bundle 219484 is one of those config bundles that cannot be removed. However, removing Bundles 219479 and 219480 (co-installed with 219484) then allows the new SuiteApps from the SuiteApp Marketplace to be…

No, I think I can manage, but thank you very much for the offer. I'm writing up where I'm finding issues with the documentation - it most likely is just due to being a new release

Perhaps the following will help clarify what our team is looking at. I have reviewed both the instructions in Portuguese as well as the English version starting on Page 16 below. Also see the caveat expressed on Page 5. Remember this is a customer with operations in 20+ countries and the issue cited initially is that the…

Believe it or not, the latest Brazil localization package (updated last year and announced by Evan in Brazil in October if I remember correctly - it was a couple of weeks after the announcement at SuiteWorld) documents that the FF PRM packages are required. It's a bit unusual, I know but I can forward you the documentation…

Customer is live on the edition but the issue is that the Brazil localization is failing as it depends on the SuiteApps instead of the bundle version. So no, we can't just leave it as is. Can anyone confirm that these two packages have been deprecated for an implementation with SuiteTax? There is a reference to a new…

I believe I've found the answer on this. If one defaults the Expense account on the vendor profile, the HSN/SAC is not populated. However, if the default expense account is removed from the vendor profile and manually entered on the transaction, the HSN/SAC is populated as a result of adding the GL account number.

Just an FYI, the fix to this was to modify the JEs with a csv import and adding the Vendor under the Name field where it previously had only appeared in the memo field. Given that there were several hundred line items over several years affected by this it took some time and the greatest risk was to ensure an exact match…

Clara - thank you for the link and please forgive me for taking so long to respond. The client in question has OneSource with Legacy Tax as opposed to SuiteTax, and the links above were only to sales material as opposed to implementation or end user documentation. We've muddled through, and were unable to receive the same…

I'm running into what I believe is a related problem. India's IHSN/SAC codes are assigned at the CoA level, but are not appearing on transactions. If one enters the SAC on an individual vendor bill line item, taxes calculate correctly, but if not, the tax calculations fail. Based on the last statement, I believe the GST…

Ely- I apologize for taking so long to get back to you, but the last few days have been hectic. Yes, I believe you're on the right track and I plan to test this either today or tomorrow and will respond. THANK YOU!

I just received an update from Support this afternoon. It appears that this issue is not tied specifically to the LRCFM but instead to an excess number of scripts running on the transactions such as Cash Sale, Invoice, etc. In this case it made sense to disable the LRCFM as it had limited value to the operation.

Thank you for the response Ely. Yes, the approach above would eliminate the "No Vendor" transactions but would still leave the offset entry. Part of the problem is that these unreconciled A/P transactions are still out there...... Reports generated in this manner would not balance to the G/L account balance, correct? I've…

Please note the following as well. Please check the Help page for Records Supporting LRCFM by Localization Assistant SuiteApp and note the other record types that can be affected. I found that Cash Sale definitely needed to be adjusted in the same manner in order to issue the Mexico Factura Electronica

Is the Copy To Account functionality currently working? I've been trying over the past few days to copy custom roles from SB1 to Prod during UAT. Error message is at first stage of Copy To (dependencies) and response is "Error Unexpected error (#l6oz0h9og3r5noo5k38o): An unexpected error has occured and there is…

Micah- I've been checking for the past two days and still don't see the ANZ SuiteApp update and with that the unlocking of the scripts we need to modify. Any idea what is happening with this change? Do we have a new timeline? Thank you

Thank you. Will wait until the 24th :-)

Dominica- The issue for Mexico's transactions is not just the financial impact in NS. Each transaction must be reported to the local tax authority and that is failing as well. I appreciate the feedback though!

I honestly haven't tried this with the EUR/USD example above, but the issue may honestly be within the Mexican customer forms and how open invoices are called as part of the problem. When changing the currency on the Payment form after populating the customer name, only the invoices in the MXN currency appear. It is not…

The issue is tying the A/R payment back to the invoice. How is that done?