⚠️ Important: This is a pre-release MVP version made available to a limited number of early access testers. If you have found a new issue not listed in our Known Issues or just want to provide general feedback kindly use this link to provide feedback.

This article covers every formula available in Financial Reporting. All formulas begin with the XAVI. prefix and pull live data from your connected NetSuite account.

Dates are passed as parameters to XAVI formulas. This section explains how date and period values in Excel are interpreted by the add-in and sent to the backend as accounting periods.

TLDR; CloudExtend parses your dates and passes them as actual period names to NetSuite. If you're passing a date as a parameter to a XAVI formula enter it as 1/1/2025 in your Excel cell and format it in the way you prefer to present it (ie MM-YYYY). If you're manually adding a date to a XAVI formula enter as (XAVI.BALANCE("Jan 2025"...). If your periods do not align with months, then pass the period name in with quotes (see bullet point 4 below).

When you enter a date for a period parameter, the add-in does not treat that date as “transactions on that single day” by default. Instead, it determines which calendar month and year that date falls in, converts that to an accounting period and sends that period to the server. The server then uses NetSuite’s period definition*(including the period’s real start and end dates) when it runs the request.

You can use any of the following (including as a cell value or as a cell reference to a value):

Tip: The most reliable approach is to use a true Excel date (date serial) or a clearly unambiguous Month YYYY text string. If you rely on plain text, use a space between month and year (for example Jan 2025) rather than punctuation-only variants, unless you have confirmed they parse correctly in your environment.
​

NetSuite alignment: The period label sent to the server (for example May 2025) must match how periods are named in your NetSuite accounting calendar. If your NetSuite period names differ from a simple English month and year, use the names NetSuite expects (or the supported period identifiers your organization uses with the add-in).

You can drive many formulas from a single year input cell so you do not have to edit every formula manually.

Pattern A — year only: Point from and to period arguments at the same cell that contains 2025. Because of the year-only rules above, that typically behaves like Jan 2025 through Dec 2025 when used as from/to respectively.

Pattern B — explicit months (more control): Keep a year in a cell (for example $B$1), and build dates with Excel functions, for example:

Any day within the month is fine for resolving the month; many users use the first day of the month for clarity.

When you change $B$1, Excel recalculates dependent formulas, and the add-in receives the updated values on the next calculation.

Values like January, Jan-2025, mmm-yyyy, or mmmm yyyy are usually Excel number formats applied to a real date. Changing Format Cells only changes how the date looks; Excel still stores a date serial number underneath.

Because the add-in reads the cell's actual value (the serial) when Excel supplies it that way, you can make the sheet look any way you want — full month name, abbreviated month, month-year with a hyphen, and so on — without changing which period the add-in resolves, as long as the underlying stored value remains the correct date.

If a cell contains text that only looks like a date (not a true Excel date), the add-in may parse that text if it is in a supported form (for example Jan 2025 or January 2025). For the most predictable behavior, prefer real Excel dates plus formatting for appearance.

The most used formula, XAVI.BALANCE, returns the GL account balance for a specific period or date range. This is the core formula for building financial reports.

⚠️ Important Note About Balance Sheet Accounts

The From Period should always be skipped (replace it with a comma) since Balance Sheet Accounts sum from the beginning of time.

Returns the GL account balance with explicit currency control. Use this for multi-currency consolidation scenarios where you need to specify the target currency.

Important: Note that currency is in position 5, between subsidiary and department. This differs from XAVI.BALANCE.

⚠️ Not all currency/subsidiary combinations are valid. The currency must be a valid consolidation root for the filtered subsidiary. Invalid combinations return INV_SUB_CUR (balance = 0).

TIP - The best way to see which currencies are availabel for a subsidiary is use the task pane, selected a Subsidiary Context, and then select currency to see which currencies are available for the BalanceCurrency formula.

BALANCECURRENCY applies NetSuite's consolidation logic at the presentation layer. It does not override transaction posting logic or introduce alternate FX assumptions.

Returns the budget amount for an account and period. Supports wildcards and all the same dimensional filters as XAVI.BALANCE.

Returns the account name for a given account number. Useful for building dynamic report labels.

Returns the account type (Income, Expense, Bank, etc.) for a given account number.

Returns the parent account number for a sub-account. Useful for navigating account hierarchies.

These formulas calculate values that NetSuite computes dynamically — they are not stored as standard account balances.

⚠️ Important note on XAVI.NETINCOME: This formula always computes a period range. If you supply only one period, XAVI treats it as a single-period range (from = to), returning only that month's P&L — which will typically not match Balance Sheet Net Income. To match year-to-date Net Income, always pass both periods explicitly:

Returns the total balance for all accounts of a specific account type or special account type. This formula is used by the CFO Flash Report and is ideal when you want to summarize by financial category rather than by account number.

For full documentation on XAVI.TYPEBALANCE, including account type values, special account type values, and examples, see the dedicated XAVI.TYPEBALANCE Reference article.