Journals
The Journal object is linked to an authorization and is created by vendors from the raw data available from their services.
This object contains the following attributes:
id
string
A unique identifier for the journal. No nesting exists for this identifier.
Example: BJO-1234-5678
name
string
The name of the journal.
Example: 29 Nov 2024 #1
externalId
string
The external identifier or reference number. This is an optional value to assist vendors in matching the journal with external ERP systems.
Example: bill-12345609
notes
string
Journal notes added by the vendor when creating the journal.
Example: This is new billing data for November.
status
enum
The status of the journal with one of these possible values: Draft, Deleted, Validating, Validated, Error, Ready, Review, Enquiring, Generating, Generated, Accepted, or Completed.
vendor
A reference to the Vendor Account object completed during the creation of a journal.
Example:
dueDate
dateTime
The due date of a journal. Possible values are generated according to Authorization.
Example: 2024-12-29T09:09:30.087Z
currency
string
The currency of the journal.
Example: EUR
price
The price summary including the aggregated price values for all journal charges. Not all fields are visible to all actors.
Example:
upload
The journal upload summary, including the total charges and counts of split, ready, and error charges. Only visible to SoftwareOne Operations and Vendor accounts.
Example:
processing
The journal processing summary including the total charges and counts of ready, error, split, cancelled, and completed charges. Only visible to SoftwareOne Operations.
Example:
PriceSummary
This object contains the following attributes:
totalPP
decimal
A sum of all purchase price values of all charges in the billing object. Only visible to SoftwareOne Operations and Vendor accounts.
Example: 229.8
markup
decimal
The average markup value among all charges in the billing object. Only visible to SoftwareOne Operations.
Example: 0.5013
margin
decimal
The average margin value among all charges in the billing object. Only visible to SoftwareOne Operations.
Example: 0.3339
totalSP
decimal
A sum of all the selling price values of all charges in the billing object. Only visible to SoftwareOne Operations and Vendor accounts.
Example: 356.7
JournalUploadSummary
This object contains the following attributes:
total
integer
The number of charges in the billing object.
Example: 150
split
integer
The number of split charges.
Example: 4
ready
integer
The number of ready charges.
Example: 144
error
integer
The number of error charges.
Example: 6
ProcessingSummary
This object contains the following attributes:
total
integer
The total number of charges within the billing object.
Example: 150
ready
integer
The total number of ready charges.
Example: 140
error
integer
The total number of error charges.
Example: 6
split
integer
The total number of split charges.
Example: 4
cancelled
integer
The total number of cancelled charges.
Example: 2
completed
integer
The total number of completed charges.
Example: 0
Example
Last updated
Was this helpful?