API Changes Summary

GET / POST /v1/accountingcolumnconfig/query

Returns the fixed Nitra-managed accounting column catalog merged with the org's enable config, scoped to the columns available on the org's connected accounting platform.

• Auth: Must be logged in
• Roles: member
• Permissions: none

Request body

Response (200)

{
  "status": 200,
  "success": true,
  "accountingColumns": [
    {
      "id": 1,            // AccountingColumnConfigs row id, or null if no config row exists yet
      "columnKey": "glaccount",
      "name": "GL Account",
      "enabled": true,
      "required": true    // platform "Always On" column; cannot be disabled
    }
  ]
}

Errors

GET / POST /v1/accountingcolumnconfig/update

Batch-update the enabled status for accounting columns and cascade the change into each member's customized display column lists. All-or-nothing within a single transaction.

• Auth: Must be logged in
• Roles: member
• Permissions: none (org of caller is enforced — see below)

Request body

Response (200)

{
  "status": 200,
  "success": true
}

Errors

GET / POST /v1/ruttercustomfieldconfig/update Breaking request change

Update enabled status for Rutter custom fields for the organization — now accepts a batch array instead of a single field.

• Auth: Must be logged in
• Roles: member
• Permissions: none (org of caller is enforced)

What changed

• remove Top-level id / rutterCustomFieldDefinitionId / enabled fields removed.
• add New required customFields array (min 1); each item is { id | rutterCustomFieldDefinitionId, enabled } with the same xor rule as before.
• change Now applies all updates in a single transaction (all-or-nothing).
• remove Success response no longer returns the rutterCustomFieldConfig object — it now returns only { status, success }.
• change Replaced generic FORBIDDEN failures for missing platform/definition with specific 400 error codes (see Errors).

Request body — before

{
  "id": 12,                          // OR rutterCustomFieldDefinitionId (xor)
  "rutterCustomFieldDefinitionId": 5,
  "organizationId": 99,
  "enabled": true
}

Request body — after

Response (200)

{
  "status": 200,
  "success": true
}

Errors

POST /v1/rutteraccountingplatforms/update New optional field

Update accounting platform settings. Adds a transaction-specific auto-match-vendor toggle, independent of the existing (now bill-scoped) autoMatchVendor flag.

• Auth: Must be logged in
• Roles: member.ADMIN, member.BOOKKEEPER
• Permissions: RUTTER_ACCOUNTING_PLATFORM_UPDATE_INTEGRATION

What changed

• add New optional request field autoMatchVendorOnTransaction (BOOLEAN, nullable) — gates auto-vendor-matching for transactions.
• change autoMatchVendor is now documented as bill-scoped (no behavior change to the field itself; transactions no longer read it).
• change The .or() rule now also accepts autoMatchVendorOnTransaction as a sole field in the request.

Request body

Response (200)

{
  "status": 200,
  "success": true,
  "platform": { "id": 1, "autoMatchVendor": true, "autoMatchVendorOnTransaction": true, ... }
}

Errors

AccountingColumnConfig New table

New table AccountingColumnConfigs — one row per organization + column key.

• add organizationId — INTEGER, NOT NULL (FK to organization).
• add columnKey — STRING, NOT NULL.
• add enabled — BOOLEAN, NOT NULL, default true.
• add Standard createdAt / updatedAt / deletedAt (paranoid).

Surfaced to the FE via /accountingcolumnconfig/query as { id, columnKey, name, enabled, required } (name and required are derived from the catalog/platform, not stored on the row).

RutterAccountingPlatform New column

New column on the existing RutterAccountingPlatforms table.

• add autoMatchVendorOnTransaction — BOOLEAN, nullable, default null. No backfill — all existing rows start null.

Surfaced to the FE via /rutteraccountingplatforms/read (the full platform object is serialized). Settable via /rutteraccountingplatforms/update.

GET / POST /v1/rutteraccountingitems/updatesyncstatus Behavior only

Auto-match-vendor step added to the Rutter sync flow. Request and response contracts are unchanged.

• add When the org's accounting platform has autoMatchVendorOnTransaction enabled and the line item is CARD_TRANSACTION / REFUND / NITRA_MART_TRANSACTION / NITRA_MART_REFUND, items whose AI vendor-coding confidence is LOW/VERY_LOW are auto-matched to a Rutter vendor by merchant name.
• change The gate now reads the new autoMatchVendorOnTransaction flag instead of the shared autoMatchVendor. Orgs that had autoMatchVendor = true must enable the new flag to resume transaction auto-matching.
• add If no matching vendor exists, the vendor is created on Rutter (except QuickBooks Desktop, which is pushed to failedAccountingItems for now); the matched/created vendor is assigned to every split item.