[Feature] Add subsidiary currency and transaction amount

[jmongerlyra]

Is there an existing feature request for this?

• I have searched the existing issues

Describe the Feature

Please add the subsidiary currency and transaction amount to the balance sheet and income statement models. The fields are useful when reporting on amounts in the functional currency alongside the consolidated (i.e. converted_amount) results.

How would you implement this feature?

See related PR.

Describe alternatives you've considered

Adding the fields in a downstream repository. However, these would be useful for any customer using NetSuite One World.

Are you interested in contributing this feature?

• Yes.
• Yes, but I will need assistance.
• No.

Anything else?

No response

[fivetran-avinash]

Hey @jmongerlyra , thanks for submitting this issue and concurrent PR!

Before proceeding forward, just wanted to check if you were able to leverage the balance_sheet_transaction_detail_columns and income_statement_transaction_detail_columns variable configuration you can use to pull transaction detail columns (see README details here)? Both transaction_amount and subsidiary_currency_symbol are available there, so wondering if you could test out that functionality and see if those figures match.

I do see that the transaction_amount logic might be different, so would be interested to see what your findings are if you try bringing in those values to the balance sheet and income statement. If they don't match your expectations, I think we can probably bring your PR in for review in a future sprint.

[jmongerlyra]

@fivetran-avinash We included in the models directly because the sign of transaction_amount doesn't match converted_amount in the two models when passing through from transaction_details.

subsidiary_currency_symbol could be passed in. However, it made sense to include in the model directly since without it the currency of transaction_amount is unknown.

[fivetran-avinash]

Thanks for the context @jmongerlyra ! We did some digging and agreed that using the *_transaction_detail_columns feature wouldn't necessarily work here as there is too much logic transformation that can disrupt the actual conversion of the data here.

So we think your suggestion works best and your request is well in scope to bring into a coming sprint. We plan to fold your updates into our next release of the dbt_netsuite package. We will let you know when we kick off work on this!

[fivetran-jamie]

This is live in v0.17.0 of the package!