Production availability​

• ARHistoricalData is disabled in Production. The arHistoricalData query and its fields appear in the GraphQL reference, but the corresponding ETL is not enabled in Production. This documentation does not announce production availability for AR historical data.
• InventoryItems is enabled in Production. Use the inventoryItems query to retrieve inventory item data.

Production ETL availability​

• ARHistoricalData is disabled in Production. The AR_HISTORICAL_DATA enum value and API reference are present, but the ETL is not enabled in Production.
• InventoryItems is enabled in Production. The INVENTORY_ITEMS ETL is enabled for inventory item synchronization.

New Endpoints​

Both are marked EXPERIMENTAL: they may change or be removed without notice, and they are not yet recommended for production integrations. They are published now so you can evaluate them and give feedback on the pagination contract before it is fixed.

• generalLedgerBalancesForwardByGroupV2 - Forward-period expansion paginated by group, replacing generalLedgerBalancesForwardByGroup. Same arguments and same response shape; the difference is that page cost no longer grows with the size of your company's dataset.
• generalLedgerBalancesByPeriodV2 - The latest balance at or before a given financial period, one row per ledgerId / branchId / accountId / subaccountId group, replacing generalLedgerBalancesByPeriod.

Location.paymentBy is now nullable​

The deprecated paymentBy field on the Location type has changed from Int! to Int:

• paymentBy: Int - returns the raw ERP payment by code (0 = Due Date, 1 = Discount Date), and null when the ERP holds no value.

The underlying ERP column is nullable, so the previous non-null declaration could not be guaranteed. In practice existing locations all carry a value; clients that read the deprecated paymentBy field should nevertheless handle null. The recommended field remains paymentByType: String, which is unchanged and returns "Due Date", "Discount Date", or null when the ERP holds no value or a value outside the known set.

The descriptions of both paymentBy and paymentByType have been updated accordingly.

Location sync reports missing Payment By values as null​

Locations with no Payment By value in the ERP now sync with paymentBy and paymentByType set to null. Previously a missing value was silently reported as the default Due Date, which could not be distinguished from a real setting. Locations with an unrecognised Payment By code continue to sync with paymentByType: null while keeping the raw code in paymentBy.

New query: financialPeriods​

The financialPeriods query and the FinancialPeriod type are now available, exposing the company's financial calendar:

• Core fields: finPeriodId, startDate, endDate, description, active, year.
• Per-module close flags: closedInGeneralLedger, closedInSupplierLedger, closedInCustomerLedger, closedInInventoryManagement, closedInCashManagement, closedInFixedAssets.

New ETL: Financial Periods​

The FinancialPeriods collection is now synced from the ERP. Each document describes a period in the company's financial calendar:

• finPeriodId, startDate, endDate, description, active and year.
• Per-module close flags: closedInGeneralLedger, closedInSupplierLedger, closedInCustomerLedger, closedInInventoryManagement, closedInCashManagement and closedInFixedAssets.

The collection supports deletion tracking and reconciliation (deletedDatabaseRecord).

Budget type now uses the full composite key​

The Budget type has been updated so that its GraphQL key matches the full GLBudgetLine primary key:

• branchId, ledgerId and financialYear are now marked as part of the key (@partOfKey).
• A new non-nullable field parentGroupId: String! has been added and is also part of the key.

This aligns the schema with the underlying ETL collection, which has been reimported with the same composite key. Clients querying the Budget type should add parentGroupId to their selection sets where the parent budget line is relevant.

Budgets collection reimport​

The Budgets collection has been updated to use the full GLBudgetLine composite key (companyId, branchId, ledgerId, financialYear, groupId, parentGroupId). Sibling budget lines that share a groupId but differ in parentGroupId were previously collapsed under a single document, causing related rows to be lost.

Data Quality Improvements​

• Deletion tracking is now available for all collections except Budgets, GeneralLedgerBalances, and JournalTransactions. The API exposes an includeDeleted filter so integrations can choose whether soft-deleted records are included in query results.