Restaurant365 · Schema
JournalEntry
A general ledger journal entry line submitted to the R365 API. Debits and credits must balance across the entry.
RestaurantAccountingInventoryInvoicesReportingOData
Properties
| Name | Type | Description |
|---|---|---|
| BatchId | string | Optional batch identifier grouping records. |
| userId | string | Optional submitting user identifier. |
| JENumber | string | Journal entry number; auto-generated if omitted. |
| Date | string | Journal entry date. |
| JEComment | string | Journal entry comment. |
| JELocation | string | Journal entry header location. |
| Account | string | GL account for the line. |
| Debit | number | Debit amount; debits must balance credits. |
| Credit | number | Credit amount; credits must balance debits. |
| DetailLocation | string | Location for the detail line. |
| PayrollJournalEntry | boolean | Whether this is a payroll journal entry. |
| PayrollStartDate | string | Payroll period start date; required for payroll entries. |
| PayrollEndDate | string | Payroll period end date; required for payroll entries. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/restaurant365/main/json-schema/r365-api-journal-entry-schema.json",
"title": "JournalEntry",
"description": "A general ledger journal entry line submitted to the R365 API. Debits and credits must balance across the entry.",
"type": "object",
"required": ["Date", "JELocation", "Account", "Debit", "Credit", "DetailLocation"],
"properties": {
"BatchId": { "type": "string", "description": "Optional batch identifier grouping records." },
"userId": { "type": "string", "description": "Optional submitting user identifier." },
"JENumber": { "type": "string", "description": "Journal entry number; auto-generated if omitted." },
"Date": { "type": "string", "description": "Journal entry date." },
"JEComment": { "type": "string", "description": "Journal entry comment." },
"JELocation": { "type": "string", "description": "Journal entry header location." },
"Account": { "type": "string", "description": "GL account for the line." },
"Debit": { "type": "number", "description": "Debit amount; debits must balance credits." },
"Credit": { "type": "number", "description": "Credit amount; credits must balance debits." },
"DetailLocation": { "type": "string", "description": "Location for the detail line." },
"PayrollJournalEntry": { "type": "boolean", "description": "Whether this is a payroll journal entry." },
"PayrollStartDate": { "type": "string", "description": "Payroll period start date; required for payroll entries." },
"PayrollEndDate": { "type": "string", "description": "Payroll period end date; required for payroll entries." }
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/r365-api-journal-entry"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.