Bank transaction rule sets

A rule set acts as a container for matching and creating rules. The rules determine how to match incoming bank transactions or create new transactions for reconciliation in Sage Intacct.

List bank transaction rule sets

get/objects/cash-management/bank-txn-rule-set

Returns a collection with a key, ID, and link for each rules. This operation is mostly for use in testing; use query to find objects that meet certain criteria and to specify properties that are returned.

Permissions and other requirements
SubscriptionCash Management
User ypeBusiness
PermissionsList Bank transaction rule sets
SecurityOAuth2
Responses
200

OK

400

Bad Request

Request samples 
Response samples 
application/json
{
  • "ia::result": [
    • {
      • "key": "1",
      • "id": "1",
      • "href": "/objects/cash-management/bank-txn-rule-set/1"
      },
    • {
      • "key": "2",
      • "id": "2",
      • "href": "/objects/cash-management/bank-txn-rule-set/2"
      },
    • {
      • "key": "3",
      • "id": "3",
      • "href": "/objects/cash-management/bank-txn-rule-set/3"
      }
    ],
  • "ia::meta": {
    • "totalCount": 3,
    • "start": 1,
    • "pageSize": 100,
    • "next": null,
    • "previous": null
    }
}
Create a bank transaction rule set
post/objects/cash-management/bank-txn-rule-set
Creates a new bank transaction rule set.



Permissions and other requirements



SubscriptionCash Management


User ypeBusiness


PermissionsAdd Bank transaction rule sets







SecurityOAuth2 
Request 
Request Body schema: application/json
ruleSetId
required
string
ID for the bank transaction rule set.


 
 Example:  "ruleSet-1"
name
required
string  <= 100 characters 
Name of the bank transaction rule set.


 
 Example:  "rule-set-for-credit-cards"
description
string
Description of the bank transaction rule set.


 
 Example:  "Rule set for all card accounts"
accountType
string
 Default:  "bank"
Type of the associated account.


 Enum: "bank" "creditcard"  
 Example:  "creditcard"
object
Location where the bank transaction rule set was created.


 
key
string
System-assigned key for the location.


 
 Example:  "122"
id
string
ID for the location.


 
 Example:  "1-Lyon"
status
string
 Default:  "active"
Object status. Active objects are fully functional. Inactive objects are essentially hidden and cannot be used or referenced.


 Enum: "active" "inactive"  
 Example:  "active"
Array of objects
List of the rules in this rule set.


 
 Array 
ruleOrder
integer
Order of rule in the rule set.


 
 Example:  1
object
A bank transaction rule.


 
Responses 
201
Created rule set


400
Bad Request


Request samples 
application/json
{
  • "ruleSetId": "Txn-Rule-Set-004",
  • "name": "MBB Rule Set",
  • "description": "Primary rule set for MBB",
  • "accountType": "creditcard",
  • "location": {
    • "key": "1"
    },
  • "status": "active"
}
Response samples 
application/json
{
  • "ia::result": {
    • "key": "5",
    • "id": "5",
    • "href": "/objects/cash-management/bank-txn-rule-set/5"
    },
  • "ia::meta": {
    • "totalCount": 1
    }
}
Get a bank transaction rule set
get/objects/cash-management/bank-txn-rule-set/{key}
Returns detailed information for a specified bank transaction rule set.



Permissions and other requirements



SubscriptionCash Management


User ypeBusiness


PermissionsList, View Bank transaction rule sets







SecurityOAuth2 
Request 
path Parameters
key
required
string
System-assigned key for the bank transaction rule set.


 
 Example:  11
Responses 
200
OK


400
Bad Request


Request samples 
Response samples 
application/json
{
  • "ia::result": {
    • "id": "2",
    • "key": "2",
    • "ruleSetId": "BankRuleSetChase",
    • "name": "Rule set for chase bank",
    • "description": "Primary rule set for CB",
    • "accountType": "bank",
    • "numberOfAccounts": 7,
    • "numberOfRules": 1,
    • "status": "active",
    • "location": {
      • "key": "5"
      },
    • "audit": {
      • "createdDateTime": "2022-01-26T00:15:14Z",
      • "modifiedDateTime": "2023-03-24T21:41:10Z",
      • "createdBy": "68",
      • "modifiedBy": "68"
      },
    • "rules": [
      • {
        }
      ],
    • "href": "/objects/cash-management/bank-txn-rule-set/2"
    },
  • "ia::meta": {
    • "totalCount": 1,
    • "totalSuccess": 1,
    • "totalError": 0
    }
}
Update a bank transaction rule set
patch/objects/cash-management/bank-txn-rule-set/{key}
Updates an existing bank transaction rule set by setting field values. Any fields not provided remain unchanged. Updating a rule set affects matches for incoming transactions going forward for every associated account that uses the rule set. Updating a rule set does not affect transactions that have already been matched.



Permissions and other requirements



SubscriptionCash Management


User ypeBusiness


PermissionsList, Edit Bank transaction rule sets







SecurityOAuth2 
Request 
path Parameters
key
required
string
System-assigned key for the bank transaction rule set.


 
 Example:  11
Request Body schema: application/json
ruleSetId
string
ID for the bank transaction rule set.


 
 Example:  "ruleSet-1"
name
string  <= 100 characters 
Name of the bank transaction rule set.


 
 Example:  "rule-set-for-credit-cards"
description
string
Description of the bank transaction rule set.


 
 Example:  "Rule set for all card accounts"
accountType
string
 Default:  "bank"
Type of the associated account.


 Enum: "bank" "creditcard"  
 Example:  "creditcard"
object
Location where the bank transaction rule set was created.


 
key
string
System-assigned key for the location.


 
 Example:  "122"
id
string
ID for the location.


 
 Example:  "1-Lyon"
status
string
 Default:  "active"
Object status. Active objects are fully functional. Inactive objects are essentially hidden and cannot be used or referenced.


 Enum: "active" "inactive"  
 Example:  "active"
Array of objects
List of the rules in this rule set.


 
 Array 
ruleOrder
integer
Order of rule in the rule set.


 
 Example:  1
object
A bank transaction rule.


 
Responses 
200
OK


400
Bad Request


Request samples 
application/json
{
  • "status": "inactive"
}
Response samples 
application/json
{
  • "ia::result": {
    • "key": "4",
    • "id": "4",
    • "href": "/objects/cash-management/bank-txn-rule-set/4"
    },
  • "ia::meta": {
    • "totalCount": 1
    }
}
Delete a bank transaction rule set
delete/objects/cash-management/bank-txn-rule-set/{key}
Deletes a bank transaction rule set.



Permissions and other requirements



SubscriptionCash Management


User ypeBusiness


PermissionsList, Delete Bank transaction rule sets







SecurityOAuth2 
Request 
path Parameters
key
required
string
System-assigned key for the bank transaction rule set.


 
 Example:  11
Responses 
204
No Content


400
Bad Request


Request samples 
Response samples 
application/json
{
  • "ia::error": {
    • "code": "invalidRequest",
    • "message": "Malformed URL",
    • "supportId": "sQrM9%7EYdh5oDEWVb80mrn9xuHjoAAAABBQ",
    • "details": [
      • {
        }
      ]
    }
}
Query bank transaction rule sets
post/services/core/query
Queries an object for filtered data.


SecurityOAuth2 
Request 
Request Body schema: application/json
object
string
Object type to query, in the form <application-name>/<object name>. For custom objects use platform-apps/nsp::<object-name>.


 
 Example:  "cash-management/bank-txn-rule-set"
fields
Array of strings
List of fields to include in the response. Can be any combination of these:


    

  • The name of a field in the object that you are querying, such as id.
    

    • 

  • The name of a field in a related object, using the form relatedObjectName.fieldName, such as vendor.id.
    

    • 

  • The result of an aggregate function run against the values in the returned objects. Use the form function:fieldName, such as min:startDate to return the earliest starting date. Valid function names are:
    

      

    • count
      • 

    • avg
      • 

    • sum
      • 

    • min
      • 

    • max
      • 

    

    • 

  • The result of an aggregate function run against the values in related objects, using the form function:relatedObjectName.fieldName, such as max:vendor.creditLimit. The same functions are supported as for object fields.
    

    • 



 
 Example:  ["key","id","max:vendor.creditLimit"]
Array of equal (object) or not equal (object) or less than (object) or (less than or equal (object)) or greater than (object) or (greater than or equal (object)) or in (object) or not in (object) or between (object) or not between (object) or contains (object) or does not contain (object) or starts with (object) or does not start with (object) or ends with (object) or does not end with (object)
Filter conditions to select the objects to return based on their field values. You use operators and conditions to build your filter, such as {"$eq":{"status":"active"}} to select objects in which status is equal to "active".


 
 Example:  [{"$eq":{"status":"active"}},{"$gt":{"totalDue":"1000"}},{"$contains":{"name":"Acme"}}]
 Array 
Any of:
Field value must be equal to this specified value.


For date fields, you can use these macro values that are relative to the current date or the asOfDate in filterParameters, if set:







    

  • today

  • currentWeek

  • currentMonth

  • currentQuarter

  • currentYear





    

  • yesterday

  • lastWeek

  • priorMonth

  • priorQuarter

  • priorYear









These are most useful for queries that you want to save and use repeatedly, such as for views or reports. Just change the asOfDate each time to retrieve the same data set for different time periods.


For example, {"eq":{"postingDate":"priorYear"}}.


object
The field name and value to be compared with object values.


 
 Example:  {"status":"active"}
filterExpression
string
 Default:  "and"
Logical operators to apply when there are multiple filter conditions. The conditions in the filters array are implicitly numbered starting at 1. Supports and, or, and grouping with parentheses.


Shortcuts:


    

  • and by itself means that all conditions must be true.
    • 

  • or by itself means that at least one condition must be true.
    • 



 
 Example:  "(1 and 2) or 3"
object

Pre-defined filter options.


 
asOfDate
string <date> 
The "as of" date to use with any relative date comparisons in filters. For example, if asOfDate is set to "2022-04-01" then priorMonth will be "03".


The current date is used if asOfDate is not set.


 
 Example:  "2022-04-01"
includeHierarchyFields
boolean
 Default:  false
Set to true to include hierarchical structure information with each object in the response.


 
 Example:  false
caseSensitiveComparison
boolean
 Default:  true
Queries are case-sensitive by default. Set to false to ignore case in a query.


 
 Example:  true
includePrivate
boolean
 Default:  false
By default, in a multi-entity company, queries from the top-level entity do not access data in private entities. Set includePrivate to true if you want to query data in private entities.


 
 Example:  false
Array of objects
Set the order of the results by specifying field names to sort by and whether they should be in ascending or descending order.


 
 Example:  [{"totalDue":"asc"},{"lastPaymentMadeDate":"desc"}]
 Array 
property name*
additional property
string
 Enum: "asc" "desc"  
start
integer
First record of the result set to include in the response.


 
 Example:  1
size
integer
Number of records to include in the response.


 
 Example:  100
Responses 
200
OK


400
Bad Request


Request samples 
application/json
{
  • "object": "cash-management/bank-txn-rule-set",
  • "filters": [
    • {
      • "$eq": {
        }
      }
    ],
  • "fields": [
    • "key",
    • "id",
    • "ruleSetId",
    • "description",
    • "numberOfAccounts",
    • "numberOfRules"
    ],
  • "orderBy": [
    • {
      • "id": "asc"
      }
    ]
}
Response samples 
application/json
{
  • "ia::result": [
    • {
      • "key": "1",
      • "id": "1",
      • "ruleSetId": "Txn-Rule-Set-001",
      • "description": "Primary rule set for Propser bank account",
      • "numberOfAccounts": 6,
      • "numberOfRules": 1
      },
    • {
      • "key": "3",
      • "id": "3",
      • "ruleSetId": "Txn-Rule-Set-003",
      • "description": "Create IET",
      • "numberOfAccounts": 0,
      • "numberOfRules": 1
      },
    • {
      • "key": "4",
      • "id": "4",
      • "ruleSetId": "Txn-Rule-Set-004",
      • "description": "Primary rule set for MBB",
      • "numberOfAccounts": 0,
      • "numberOfRules": 0
      }
    ],
  • "ia::meta": {
    • "totalCount": 3,
    • "start": 1,
    • "pageSize": 100,
    • "next": null,
    • "previous": null
    }
}