In this release:

• Supplier documents, payments and payment lines: new fields on SupplierDocument, SupplierPayment and SupplierPaymentLine.
• APHistoricalData: new query, disabled in Production while testing is in progress.

In this release:

• Supplier documents, payments and payment lines: synchronization of the new supplier document, payment and payment-line fields, with historical backfills.
• APHistoricalData: new ETL, disabled in Production while testing is in progress.

In this release:

• Customers: field values, new fields, notes, related-data lookups and reimport.
• Locations: nullable GLN and historical data refresh.
• Contacts: date of birth, Employee lookup and historical data availability.
• Branches: branch name and Employee lookup.
• SalesOrders: removed fields and replacement lookups.
• Employees: employee fields, related-data lookups and the attributes identifier.
• Customer and supplier IDs on lines: new customerId and supplierId fields on sales order, document and payment lines.
• GeneralLedgerBalances: new deletedDatabaseRecord field and includeDeleted argument; removed balances no longer returned by default.
• CustomerPayments and CustomerPaymentLines: cash-document inclusion remains disabled.
• ARHistoricalData: remains disabled in Production.

In this release:

• Customers: field values, customer fields, notes, related-data lookups and reimport.
• Locations: nullable GLN and historical data refresh.
• Contacts: date-of-birth synchronization and historical backfill.
• Branches: branch-name synchronization and historical backfill.
• SalesOrders: field removal and reimport.
• Employees: full-refresh synchronization, soft deletion and attributes identifier import.
• Customer and supplier IDs on lines: line synchronization imports the customer or supplier ID and backfills existing lines.
• GeneralLedgerBalances: removed balances are now marked as deleted, with a one-time cleanup of existing data.
• CustomerPayments and CustomerPaymentLines: cash-document inclusion remains disabled.
• ARHistoricalData: remains disabled in Production.

Contact date of birth​

The Contact type now includes a nullable dateOfBirth field sourced from the contact's date of birth. Values use the YYYY-MM-DD calendar format with no time or timezone. A missing source value is returned as null.

The field is available in environments where the updated Contacts API and ETL are deployed.

Production availability​

• ARHistoricalData is disabled in Production while testing is in progress. 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 while testing is in progress. 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.