Receiving NetSuite Export Error: "The payable category/account '' does not exist in NetSuite."

MShell

We recently added a new credit card policy in our Expensify and integrated it with NetSuite. We added the appropriate Expense Categories and synchronized everything over to Expensify; charges came in from the credit card and were able to be coded using these Expense Categories. However, when we go to Final Approve and export these transactions, we get the following error:

"The payable category/account '' does not exist in NetSuite."

It looks like this error is supposed to tell us which category can't be found but it doesn't. So far I have tried each of the following with no success:

1) Ensured each category we're using is listed on the Expense Categories list in NetSuite.

2) Each of those expenses are also going to the right subsidiary.

3) Each Expense Category for NetSuite has been successfully synced to the Expensify policy.

4) Compared each Expense Category to an Expense Category on one of our other policies (that's been working fine) and didn't notice any difference in the setups.

Is there a step we're missing to get this to export to NetSuite?

Thank you!

Sonia Liapounova

Hi @MShell 👋

Thank you for detailing your troubleshooting steps!

I see that you're exporting company card expenses as Journal Entries. Could you please try navigating to Settings > Domain > [Domain Name] > Company Cards > click Export Option next to card in question and then select the desired export account from the card menu.

I see that you currently have "default card" selected which sometimes doesn't pick up the account and throws that error. If you specify the export account that should allow you to export without an error. If you have multiple cards on the report, please set the desire export options for both cards. If you'd like your export to go to the default account then select this account in the menu.

Let me know if you run into any further trouble!

MShell

Thank you, @Sonia Liapounova! That seemed to fix the problem. Just out of curiosity, is there a reason one policy can have the export accounts set to "Default Card" and another policy cannot? Can only one policy at a time have the "Default Card" selected?

Thanks!

MShell

@Sonia Liapounova, I do have a follow-up question.

When this export went through to NetSuite, it recorded the transactions as one entry using the latest date of the report. However, with our other policy the export created an individual entry for each line item on the Expensify report and each transactions date in NetSuite matched the individual transaction's date in Expensify.

Is there a way to change this new policy to do the same thing (export each transaction as it's own individual journal entry and date)?

Thank you!

Sonia Liapounova

@MShell hmm, do you per chance have a higher submission frequency enabled in the other policy so that expenses are submitted individually or in smaller batches and so they export as smaller JEs?

MShell

@Sonia Liapounova, not that I'm aware of. How would I check on that?

We don't don't use Scheduled Submit if that's what you're referring to.

MShell

Hi @Sonia Liapounova, I think I figured it out! This doc helped get me to the right menu (the NetSuite Configuration menu).

Once there I saw that our new policy that was having issues was set to post entries as "Single, itemized entry for each report" rather than "Single entry for each individual expense" like our older policy. I think this will fix the issue, but let me know if there's anything else I should check.

I'm still curious about the difference regarding why one policy works with a "Default Card" export account option and the other policy needed the card specified in its export account option. Do you have any thoughts on that?

Thank you!