Update bill
The Update bill endpoint updates an existing bill for a given company's connection.
Bills are invoices that represent the SMB's financial obligations to their supplier for a purchase of goods or services.
Integration-specific behavior
Required data may vary by integration. To see what data to post, first call Get create/update bill model.
Query parameters
Time limit for the push operation to complete before it is timed out.
When updating data in the destination platform Codat checks the sourceModifiedDate against the lastupdated date from the accounting software, if they're different Codat will return an error suggesting you should initiate another pull of the data. If this is set to true then the update will override this check.
Request body
Identifier for the bill, unique for the company in the accounting software.
User-friendly reference for the bill.
In Codat's data model, dates and times are represented using the <a class="external" href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 standard</a>. Date and time fields are formatted as strings; for example:
2020-10-08T22:40:50Z
2021-01-01T00:00:00
When syncing data that contains DateTime fields from Codat, make sure you support the following cases when reading time information:
- Coordinated Universal Time (UTC): 2021-11-15T06:00:00Z
- Unqualified local time: 2021-11-15T01:00:00
- UTC time offsets: 2021-11-15T01:00:00-05:00
Time zones
Not all dates from Codat will contain information about time zones.
Where it is not available from the underlying platform, Codat will return these as times local to the business whose data has been synced.
In Codat's data model, dates and times are represented using the <a class="external" href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 standard</a>. Date and time fields are formatted as strings; for example:
2020-10-08T22:40:50Z
2021-01-01T00:00:00
When syncing data that contains DateTime fields from Codat, make sure you support the following cases when reading time information:
- Coordinated Universal Time (UTC): 2021-11-15T06:00:00Z
- Unqualified local time: 2021-11-15T01:00:00
- UTC time offsets: 2021-11-15T01:00:00-05:00
Time zones
Not all dates from Codat will contain information about time zones.
Where it is not available from the underlying platform, Codat will return these as times local to the business whose data has been synced.
Array of Bill line items.
Total amount of the bill, excluding any taxes.
Amount of tax on the bill.
Amount of the bill, including tax.
Amount outstanding on the bill.
Any private, company notes about the bill, such as payment information.
An array of payment allocations.
The date when the record was last fetched from the accounting software, commerce software, or open banking provider and updated in Codat’s data cache.
Use it to identify and retrieve records that have changed since your last fetch. For example, filtering modifiedDate to today will provide new records updated in Codat today.
This date is populated for all data types except for attachments, balance sheets, company information, and profit & loss reports (read more).
In Codat's data model, dates and times are represented using the <a class="external" href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 standard</a>.
The date when a record was last modified in the accounting software, usually by the business or a business process. For example, when payments are made against an invoice.
It is not populated (read more) when:
- Pulling attachments
- The accounting software does not provide modification dates for a data type
- A record has been deleted from the source platform and Codat doesn't have a record of when the deletion occurred
- A record has been voided. For certain platforms that soft delete records, isDeleted metadata is used to identify void records
In Codat's data model, dates and times are represented using the <a class="external" href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 standard</a>.
Response
Success
Contains a single entry that communicates which record has changed and the manner in which it changed.
Available data types
A unique identifier generated by Codat to represent this single push operation. This identifier can be used to track the status of the push, and should be persisted.
In Codat's data model, dates and times are represented using the <a class="external" href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 standard</a>. Date and time fields are formatted as strings; for example:
2020-10-08T22:40:50Z
2021-01-01T00:00:00
When syncing data that contains DateTime fields from Codat, make sure you support the following cases when reading time information:
- Coordinated Universal Time (UTC): 2021-11-15T06:00:00Z
- Unqualified local time: 2021-11-15T01:00:00
- UTC time offsets: 2021-11-15T01:00:00-05:00
Time zones
Not all dates from Codat will contain information about time zones.
Where it is not available from the underlying platform, Codat will return these as times local to the business whose data has been synced.
In Codat's data model, dates and times are represented using the <a class="external" href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 standard</a>. Date and time fields are formatted as strings; for example:
2020-10-08T22:40:50Z
2021-01-01T00:00:00
When syncing data that contains DateTime fields from Codat, make sure you support the following cases when reading time information:
- Coordinated Universal Time (UTC): 2021-11-15T06:00:00Z
- Unqualified local time: 2021-11-15T01:00:00
- UTC time offsets: 2021-11-15T01:00:00-05:00
Time zones
Not all dates from Codat will contain information about time zones.
Where it is not available from the underlying platform, Codat will return these as times local to the business whose data has been synced.
Number of minutes the push operation must complete within before it times out.
Number of seconds the push operation must complete within before it times out.
A message about the error.
Push status code.