Reporting periods are used when creating reports and budgets, and when opening and closing books. They limit the information in a report to specific time ranges.
Returns a collection with a key, ID, and link for each period. This operation is mostly for use in testing; use the query service to find reporting periods that meet specific criteria and to specify the properties that you want in the response.
Subscription | General Ledger |
---|---|
User type | Business, Employee, Approver |
Permissions | List Reporting Periods |
OK
Bad Request
{- "ia::result": [
- {
- "key": "1",
- "id": "Current Month",
- "href": "/objects/general-ledger/reporting-period/1"
}, - {
- "key": "2",
- "id": "Next Month",
- "href": "/objects/general-ledger/reporting-period/2"
}
], - "ia::meta": {
- "totalCount": 2,
- "start": 1,
- "pageSize": 100,
- "next": null,
- "previous": null
}
}
Creates a new reporting period.
Subscription | General Ledger |
---|---|
User type | Business |
Permissions | Add Reporting Periods |
Reporting period to create
id required | string Name of the reporting period. The name cannot be changed after the reporting period is created. Example: "Current Month" |
columnHeader1 required | string The first line to be shown on the report, such as "Quarter Ended". Example: "Quarter Ended" |
columnHeader2 | string or null The second line to be shown on the report, such as "April 2023". Example: "April 2023" |
startDate | string or null <date> The starting date of the reporting period. Example: "2023-04-01" |
endDate | string or null <date> The ending date of the reporting period. Example: "2023-06-30" |
isBudgetable | boolean Default: false Set to Example: true |
status | string Default: "active" Object status. Active objects are fully functional. Inactive objects are essentially hidden and cannot be used or referenced. Example: "active" |
Created
Bad Request
{- "startDate": "2023-01-01",
- "endDate": "2023-12-31",
- "id": "Current Year 2023",
- "columnHeader1": "Current Year",
- "isBudgetable": false
}
{- "ia::result": {
- "key": "1023",
- "id": "Current Year 2023",
- "href": "/objects/general-ledger/reporting-period/1023"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Returns detailed information for a specified reporting period.
Subscription | General Ledger |
---|---|
User type | Business, Employee, Approver |
Permissions | View Reporting Periods |
key required | string System-assigned unique key for the reporting period. Example: 240 |
OK
Bad Request
{- "ia::result": {
- "id": "Current Year 2023",
- "key": "1023",
- "href": "/objects/general-ledger/reporting-period/1023",
- "startDate": "2023-02-01",
- "endDate": "2023-12-31",
- "isBudgetable": false,
- "reportingPeriodType": "custom",
- "dateType": 99,
- "columnHeader1": "Current Year",
- "columnHeader2": null,
- "status": "active",
- "audit": {
- "createdDateTime": "2024-10-08T13:29:18Z",
- "modifiedDateTime": "2024-10-08T13:29:18Z",
- "createdByUser": {
- "key": "34",
- "id": "Admin",
- "href": "/objects/company-config/user/34"
}, - "modifiedByUser": {
- "key": "1",
- "id": "Aman",
- "href": "/objects/company-config/user/1"
}
}
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Updates an existing reporting period by setting field values. Any fields not provided remain unchanged.
Subscription | General Ledger |
---|---|
User type | Business |
Permissions | Edit Reporting Periods |
key required | string System-assigned unique key for the reporting period. Example: 240 |
columnHeader1 | string The first line to be shown on the report, such as "Quarter Ended". Example: "Quarter Ended" |
columnHeader2 | string or null The second line to be shown on the report, such as "April 2023". Example: "April 2023" |
startDate | string or null <date> The starting date of the reporting period. Example: "2023-04-01" |
endDate | string or null <date> The ending date of the reporting period. Example: "2023-06-30" |
isBudgetable | boolean Default: false Set to Example: true |
status | string Default: "active" Object status. Active objects are fully functional. Inactive objects are essentially hidden and cannot be used or referenced. Example: "active" |
OK
Bad Request
{- "startDate": "2023-01-01",
- "endDate": "2023-11-30",
- "columnHeader1": "Current Year till nov",
- "isBudgetable": false
}
{- "ia::result": {
- "key": "1023",
- "id": "Current Year 2023",
- "href": "/objects/general-ledger/reporting-period/1"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Deletes a reporting period.
Subscription | General Ledger |
---|---|
User type | Business |
Permissions | Delete Reporting Periods |
key required | string System-assigned unique key for the reporting period. Example: 240 |
No Content
Bad Request
{- "ia::result": {
- "ia::error": {
- "code": "invalidRequest",
- "message": "A POST request requires a payload",
- "errorId": "REST-1028",
- "additionalInfo": {
- "messageId": "IA.REQUEST_REQUIRES_A_PAYLOAD",
- "placeholders": {
- "OPERATION": "POST"
}, - "propertySet": { }
}, - "supportId": "Kxi78%7EZuyXBDEGVHD2UmO1phYXDQAAAAo"
}
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 0,
- "totalError": 1
}
}
Queries an object for filtered data.
object | string Object type to query, in the form Example: "general-ledger/reporting-period" | ||||||||
fields | Array of strings List of fields to include in the response. Can be any combination of these:
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 has (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 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
These are most useful for queries that you want to save and use repeatedly, such as for views or reports. Just change the For example,
| |||||||||
filterExpression | string Default: "and" Logical operators to apply when there are multiple filter conditions. The conditions in the Shortcuts:
Example: "(1 and 2) or 3" | ||||||||
| |||||||||
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
| |||||||||
start | integer First record of the result set to include in the response. Example: 1 | ||||||||
size | integer Number of records to include in the result set, 4000 maximum. Example: 100 |
OK
Bad Request
{- "object": "general-ledger/reporting-period",
- "filters": [
- {
- "$eq": {
- "isBudgetable": true
}
}
], - "fields": [
- "key",
- "id",
- "startDate",
- "endDate"
], - "orderBy": [
- {
- "startDate": "asc"
}
]
}
{- "ia::result": [
- {
- "key": "82",
- "id": "1001",
- "startDate": "2023-02-01",
- "endDate": "2023-02-28"
}, - {
- "key": "83",
- "id": "1002",
- "startDate": "2023-03-01",
- "endDate": "2023-03-31"
}
], - "ia::meta": {
- "totalCount": 2,
- "start": 1,
- "pageSize": 100,
- "next": null,
- "previous": null
}
}