BillingSplit

When there is not a one-to-one relationship between a billed charge (slip) and record of another type, billing split [BillingSplit] objects are used to record to many-to-one or one-to-many lookup. The one-to-one relationship is still modeled with the embedded slip_id field.

—	XML	SOAP	REST	Database table
Object	`BillingSplit`	`oaBillingSplit`	—	`billing_split`
Supported Commands	`Read`	`read()`	—	—

—

XML

SOAP

REST

Database table

Object

BillingSplit

oaBillingSplit

—

billing_split

Supported Commands

Read

read()

—

The BillingSplit object has the following properties:

XML / SOAP	XML / SOAP	Description
`created`	`created`	[Read-only] Time the record was created. See Date Fields
`id`	`id`	[Read-only] Unique ID. Automatically assigned by SuiteProjects Pro.
`project_billing_transactionid`	`project_billing_transaction_id`	[Read-only] The ID of the associated project billing transaction.
`slipid`	`slip_id`	[Read-only] The ID of the slip that was created.
`taskid`	`task_id`	[Read-only] The ID of the associated task.
`updated`	`updated`	[Read-only] Time the record was updated. See Date Fields

XML / SOAP

Description

created

[Read-only] Time the record was created.

See Date Fields

id

[Read-only] Unique ID. Automatically assigned by SuiteProjects Pro.

project_billing_transactionid

project_billing_transaction_id

[Read-only] The ID of the associated project billing transaction.

slipid

slip_id

[Read-only] The ID of the slip that was created.

taskid

task_id

[Read-only] The ID of the associated task.

updated

[Read-only] Time the record was updated.

See Date Fields