Changelog

[2024-04-15] Coverage Updates

  • [NetSuite] GET /bills - added support for currency_rate.
  • [NetSuite] POST /bills - added support for currency_rate.
  • [NetSuite] PATCH /bills - added support for updating the line_items.
  • [NetSuite] GET /bill_payments - added support for currency_rate.
  • [NetSuite] POST /bill_payments - added support for currency_rate.
  • [QuickBooks] GET /bills - added support for currency_rate.
  • [QuickBooks] POST /bills - added support for currency_rate.
  • [QuickBooks] POST /customers - added support for parent_id field.
  • [QuickBooks] POST /expenses - added support for customer_id field on the line_items.
  • [QuickBooks] POST /journal_entries/:id/attachments - new endpoint for QuickBooks.

For more information, visit our API Reference.

[2024-04-08] Coverage Updates

  • [Dynamics 365] GET /bills/:id/attachments - new endpoint for Dynamics 365.
  • [NetSuite] GET /bills/:id/attachments - new endpoint for NetSuite.
  • [NetSuite] PATCH /accounts - new endpoint for NetSuite.
  • [NetSuite] PATCH /bills - supports updating of line_items.
  • [NetSuite] POST /expenses - added support for customer_id field on the line_items.
  • [NetSuite] PATCH /invoices - supports updating of line_items.
  • [NetSuite] PATCH /vendors - new endpoint for NetSuite.
  • [QuickBooks] PATCH /customers - new endpoint for QuickBooks.
  • [QuickBooks] GET /sales_orders - new endpoint for QuickBooks.
  • [QuickBooks] POST /sales_orders - new endpoint for QuickBooks.
  • [QuickBooks] GET /vendors - updated status from unknown to archived when vendors are no longer active.
  • [Xero] POST /expenses - added support for additional_fields.tax_inclusive for line amount to be tax inclusive.
  • [Zoho Books] DELETE /expenses - new endpoint for Zoho Books.

For more information, visit our API Reference.

[2024-04-10] QuickBooks Desktop Sync History

We're excited to announce that QuickBooks Desktop connections now have sync history available. To access the sync history, head to the "Connections" tab on your Rutter dashboard, and select a specific connection. Then, click on the "Sync History" tab. Sync history will not appear for the first data sync (the initial sync) on a QBD connection. Sync history will begin appearing for all syncs (incremental syncs) afterwards.

For more information, visit our documentation:

[2024-04-01] Coverage Updates

  • [QuickBooks] PATCH /invoice_payments - new endpoint for QuickBooks.
  • [QuickBooks] DELETE /invoice_payments - new endpoint for QuickBooks.
  • [QuickBooks] PATCH /items - new endpoint for QuickBooks.
  • [QuickBooks] PATCH /vendors - new endpoint for QuickBooks.
  • [QuickBooks Desktop] POST /invoices - added support for class_id on line_items.
  • [Xero] GET /accounts - added support for balance .
  • Added webhooks support for EXPENSE_CREATED and EXPENSE_UPDATED

For more information, visit our API Reference.

[2024-04-04] Exposing POST Input Validation Rules for Expenses and Bills Endpoint

When using our POST API endpoints, sometimes you may encounter validation errors (HTTP status code 400) that indicate the data submitted is not considered valid. To help you understand why your request is being rejected and show you all the input validation rules that applies to a specific platform, we've added a new section to our documentation (under "Support by integration" for each endpoint) that outlines the input validation rules for a specific endpoint. Currently, we've added this for the POST /bills and POST /expenses endpoint documentation but we will be adding this to other endpoints in the future.

For more information, visit our documentation:

[2024-03-24] Coverage Updates

  • [QuickBooks] POST /expenses - added support for tax_inclusive (via additional_fields). Posted amounts within the line items will now be inclusive of the tax.
  • [QuickBooks] GET /journal_entries - added support for vendor_id, customer_id, and class_id on line_items (via additional_fields).
  • [QuickBooks] POST /journal_entries - added support for class_id on line_items (via additional_fields).

For more information, visit our API Reference.

[2024-03-21] Docs website redesign

The Rutter Docs website has been redesigned to improve visual consistency and the ability to easily find the content you need to build with Rutter. You can utilize either our navigation system or the search feature to look up any docs you need.

Quickstart

A quick Postman reference to get set up on Rutter.

API Reference

Contains info for all Rutter objects and endpoints. The API reference also includes a Basics section that covers fundamentals of using the Rutter API, including our versioning policy, how to handle errors and rate limiting, webhooks, idempotency, and more.

Platform Guides

Guides for configuring and retrieving data for each platform supported by Rutter.

Features

Learn how to use Rutter functionality, like the Rutter Link component for user authentication, or the Rutter sandbox for platform testing.

Use cases

Guides explaining how to use Rutter for common accounting workflows, such as Expense Management or AR Automation.

[2024-03-01] Duplicate Bank Feed Transaction IDs are Now Accepted [NetSuite]

When using the POST /bank_feeds/transactions API for NetSuite, you are now able to include Bank Feed Transaction transaction_id's within a POST request that have already been synced to Rutter without receiving an input rejection error. You'll see that the post succeeds, and in the response there will be a field duplicate: boolean which indicates whether a transaction has been previously synced or not. If duplicate: true, you'll see the metadata from the already synced transaction. The new transaction input will not override the existing data if it differs.

With this change, you do not need include error handling for the case where an already synced transaction causes an entire list of transactions to be rejected. Previously, you would have had to regenerate a valid input by removing the already synced transactions from the rejected input, and retry the post request to ensure the rest of the transactions would get synced. Rutter now handles deduplication of transactions internally before syncing them to Netsuite, which simplifies your implementation of our integration.

For more information, visit our documentation:

[2024-02-27] Delete Monitoring [QuickBooks Online, NetSuite]

Rutter will now track when resources are deleted in the QuickBooks Online and NetSuite platforms. When a resource is deleted in the platform (instead of through Rutter's API), Rutter will detect these changes during the incremental sync process. Deleted entities will no longer appear in subsequent API responses. In addition, webhooks will be sent out at the moment deletes are detected, and a log of all deleted entities for each connection will be available through our new /events API.

With this change, QuickBooks Online and NetSuite users can enjoy a more streamlined data management process in Rutter.

For more information, visit our documentation: