Rutter Integration
Unlocking Seamless Financial Integrations with Treasury Prime and Rutter
Treasury Prime has partnered with Rutter to deliver seamless financial (accounting, e-commerce, banking) integrations, making it easier than ever for developers to build innovative fintech solutions. Using the integration methods outlined in this guide, fintechs can enable their end users to effortlessly sync their bank transactions with accounting platforms and ERPs.
To get started with this integration, first get in touch with the Rutter team.
Empowering Developers with Cutting-Edge Financial Connectivity
With Rutter’s Bank Feeds product, fintechs can sync end users’ transactions on their bank account or payment card created on the Treasury Prime platform to their accounting system of choice. Whether end users use QuickBooks, Xero, Sage, or NetSuite, Rutter enables fintechs to send transactions to any accounting platform with just one integration. Here are some of the benefits for end users:
- Live Data
- Automatically sync your customers’ bank or card transactions into their accounting systems, ensuring financial data is precise and current.
- Time Saving
- Eliminate manual data entry for your customers, reducing the risk of errors in the accounting process and saving them time and effort.
- Seamless Reconciliation
- Simplify the process of reconciling accounting transactions with bank data for your customers, enhancing accuracy and precision in record-keeping.
- Native Experience
- Push bank or card transaction data directly into any accounting system your customer uses, all with just one integration.
Read more here about the benefits and possibilities of enabling a Bank Feeds integration for your customers.
Integration Overview
Making use of Rutter’s Bank Feeds API alongside your existing Treasury Prime integration is straightforward. Here are the steps:
-
Get listed as a bank in the accounting platforms your customers need:
- Follow Rutter’s bank feeds guides to get onboarded to the platforms of your choice.
- Rutter can help you onboard to Intuit, Xero, NetSuite, and Sage Intacct.
-
Retrieve bank transactions via Treasury Prime:
- Use our documentation to retrieve the transactions associated with the accountholders who would like to send bank transactions to their accounting platforms.
-
Manage your end user’s authentication:
- Follow Rutter’s bank feeds guides to meet each platform’s specific authentication requirements.
-
Send Treasury Prime transactions to Rutter:
- Create a new Rutter connection for each customer who would like to make use of Bank Feeds.
- Using Rutter’s Bank Feed Accounts, create accounts that correspond to those customers’ accounts.
- Finally, create bank feed transactions associated with the appropriate accounts using Rutter’s Bank Feed Transactions.
-
Test out your end-to-end flow:
- Use sample credentials to ensure the flow works as expected, and transactions appear in the platform of your choice.
Treasury Prime Objects to Ruttter Objects
| Treasury Prime | Rutter | Notes |
|---|---|---|
account.available_balance | current_balance | |
transaction.id | transactions.transaction_id | |
transaction.extended_timestamp | transactions.posted_at | Transaction.extended_timestamp represents the timestamp when the object in question is first created in Treasury Prime and not necessarily the “posted date”. To determine a posted date, we recommend excluding transactions with a status of “hold” (since those transactions have not yet been posted by definition). |
transaction.extended_timestamp | transactions.transaction_date | Transaction.extended_timestamp represents the timestamp when the object in question is first created in Treasury Prime and not necessarily the “posted date”. To determine a posted date, we recommend excluding transactions with a status of “hold” (since those transactions have not yet been posted by definition). |
transaction.amount | transactions.amount | |
transaction.human_readable_description | transactions.description | |
transaction.type (requires additional mapping, see below) | transactions.transaction_type | |
transaction.type (requires additional mapping, see below) | transactions.debit_credit_memo | |
transaction.amount WHERE category = “interest” | transactions.interest_amount | |
transaction.description | transactions.memo | |
counterparty.id where id prefix contains ‘cp’ | transactions.payee | cp_ prefixes indicate “counterparty”. These represent counterparties to originated ACH and Wire payments. |
transaction.amount WHERE category != (“interest”|“fees”) | transactions.principal_amount |
Transaction Types Mapping
Required for the Rutter fields transactions.debit_credit_memo and transactions.transaction_type.
Treasury Prime - data.type | Rutter - transaction.transaction_type | |
|---|---|---|
| deposit | deposit | |
| hold | n/a - do not send, only send posted transactions | |
| hold_release | n/a - do not send, only send posted transactions | |
| interest | interest | |
| payment | payment | |
| reversal | credit | |
| withdrawal | debit | |
| null | n/a |
Rutter Integration
Unlocking Seamless Financial Integrations with Treasury Prime and Rutter
Treasury Prime has partnered with Rutter to deliver seamless financial (accounting, e-commerce, banking) integrations, making it easier than ever for developers to build innovative fintech solutions. Using the integration methods outlined in this guide, fintechs can enable their end users to effortlessly sync their bank transactions with accounting platforms and ERPs.
To get started with this integration, first get in touch with the Rutter team.
Empowering Developers with Cutting-Edge Financial Connectivity
With Rutter’s Bank Feeds product, fintechs can sync end users’ transactions on their bank account or payment card created on the Treasury Prime platform to their accounting system of choice. Whether end users use QuickBooks, Xero, Sage, or NetSuite, Rutter enables fintechs to send transactions to any accounting platform with just one integration. Here are some of the benefits for end users:
- Live Data
- Automatically sync your customers’ bank or card transactions into their accounting systems, ensuring financial data is precise and current.
- Time Saving
- Eliminate manual data entry for your customers, reducing the risk of errors in the accounting process and saving them time and effort.
- Seamless Reconciliation
- Simplify the process of reconciling accounting transactions with bank data for your customers, enhancing accuracy and precision in record-keeping.
- Native Experience
- Push bank or card transaction data directly into any accounting system your customer uses, all with just one integration.
Read more here about the benefits and possibilities of enabling a Bank Feeds integration for your customers.
Integration Overview
Making use of Rutter’s Bank Feeds API alongside your existing Treasury Prime integration is straightforward. Here are the steps:
-
Get listed as a bank in the accounting platforms your customers need:
- Follow Rutter’s bank feeds guides to get onboarded to the platforms of your choice.
- Rutter can help you onboard to Intuit, Xero, NetSuite, and Sage Intacct.
-
Retrieve bank transactions via Treasury Prime:
- Use our documentation to retrieve the transactions associated with the accountholders who would like to send bank transactions to their accounting platforms.
-
Manage your end user’s authentication:
- Follow Rutter’s bank feeds guides to meet each platform’s specific authentication requirements.
-
Send Treasury Prime transactions to Rutter:
- Create a new Rutter connection for each customer who would like to make use of Bank Feeds.
- Using Rutter’s Bank Feed Accounts, create accounts that correspond to those customers’ accounts.
- Finally, create bank feed transactions associated with the appropriate accounts using Rutter’s Bank Feed Transactions.
-
Test out your end-to-end flow:
- Use sample credentials to ensure the flow works as expected, and transactions appear in the platform of your choice.
Treasury Prime Objects to Ruttter Objects
| Treasury Prime | Rutter | Notes |
|---|---|---|
account.available_balance | current_balance | |
transaction.id | transactions.transaction_id | |
transaction.extended_timestamp | transactions.posted_at | Transaction.extended_timestamp represents the timestamp when the object in question is first created in Treasury Prime and not necessarily the “posted date”. To determine a posted date, we recommend excluding transactions with a status of “hold” (since those transactions have not yet been posted by definition). |
transaction.extended_timestamp | transactions.transaction_date | Transaction.extended_timestamp represents the timestamp when the object in question is first created in Treasury Prime and not necessarily the “posted date”. To determine a posted date, we recommend excluding transactions with a status of “hold” (since those transactions have not yet been posted by definition). |
transaction.amount | transactions.amount | |
transaction.human_readable_description | transactions.description | |
transaction.type (requires additional mapping, see below) | transactions.transaction_type | |
transaction.type (requires additional mapping, see below) | transactions.debit_credit_memo | |
transaction.amount WHERE category = “interest” | transactions.interest_amount | |
transaction.description | transactions.memo | |
counterparty.id where id prefix contains ‘cp’ | transactions.payee | cp_ prefixes indicate “counterparty”. These represent counterparties to originated ACH and Wire payments. |
transaction.amount WHERE category != (“interest”|“fees”) | transactions.principal_amount |
Transaction Types Mapping
Required for the Rutter fields transactions.debit_credit_memo and transactions.transaction_type.
Treasury Prime - data.type | Rutter - transaction.transaction_type | |
|---|---|---|
| deposit | deposit | |
| hold | n/a - do not send, only send posted transactions | |
| hold_release | n/a - do not send, only send posted transactions | |
| interest | interest | |
| payment | payment | |
| reversal | credit | |
| withdrawal | debit | |
| null | n/a |