Unique identifier for the assignment related to the expense report, typically assigned to a person responsible for submitting or reviewing the report.

Code that categorizes the type of audit applied to the expense report, such as audits based on original receipts or image-based receipts.

Describes the reason for returning the expense report to the individual, usually due to missing or incorrect documentation during the audit process.

Indicates whether the expense report includes corporate card transactions where the payment liability is split between both the company and the individual.

Identifier for the individual who is currently responsible for approving the expense report.

Type of exchange rate used to calculate the reimbursable amounts for foreign currency expenses.

The date the expense report was saved or submitted, typically representing the end of the reporting period.

A unique identifier for the expense report, used for referencing and operations like updates and deletions.

A unique identifier for the expense report used during insert, update, and delete operations, ensuring proper tracking across systems.

A unique reference number for the expense report that adheres to company-specific numbering conventions.

The total amount of the expense report, calculated in the reimbursement currency. Also includes the total in the approver’s preferred currency if applicable.

Current approval status of the expense report, such as Approved, Pending Manager Approval, or Paid.

The date when the expense report transitioned to its current approval status.

The date on which the expense report received final approval from all necessary approvers.

The date when receipts for the expense report, in the form of images, were received and processed.

Status code representing the current state of imaged receipts for the expense report, such as 'Required', 'Missing', or 'Received'.

Explanation for why imaged receipts are not included with the expense report, potentially due to issues like receipt clarity or submission delays.

Unique identifier for the business unit or department to which the expense report belongs.

Identifier for the initial approver selected by the individual submitting the expense report, prior to any reassignments.

Identifier of the parent expense report, if the current report is a revision or related to another earlier report.

Code representing the method of payment used for the expenses on this report, such as 'check', 'cash', or 'credit card'.

Unique identifier for the individual who owns the expense report, often tied to their employee or user account.

Identifier for the person who created the expense report, typically the individual submitting the expenses for review and approval.

Description of the business purpose or activities that justify the expenses submitted in the report.

A unique filing number for receipts, manually entered by the auditor to track and verify receipts submitted with the report.

The date on which receipts for the expense report were physically received or digitally submitted for auditing.

Status of the receipts for the expense report, indicating whether receipts are 'Missing', 'Required', or 'Received'.

Currency code representing the currency used for reimbursing the individual for expenses incurred.

Indicates how the expense report was created, for example, via a mobile app on iOS or Android.

The date the expense report was formally submitted for review and approval.

Identifier for the business trip associated with the expense report, which helps link the report to travel-related costs.

Explanation for why an outstanding cash advance has not been applied against the current expense report.

Reason why an outstanding cash advance has not been deducted from the current expense report's total amount.

Indicates the user who created the expense report or row in the system, typically a person responsible for data entry.

Timestamp indicating when the expense report or row was initially created in the system.

Timestamp showing the last time the expense report or row was modified, reflecting any updates or changes.

Login session identifier associated with the user who last updated the record.

Name or identifier of the user who made the most recent update to the expense report or row.

Indicates the specific business unit or department within the organization associated with the expense report.

Indicates whether the expense report is ready to be submitted for review, often depending on the completion of required fields and validations.

Indicates whether corporate card transactions can be matched to corresponding expenses in the report to ensure accurate reimbursement.

Lists any errors or issues that occurred during the submission process, such as missing required fields or incorrect data.

Name of the individual for whom the expense report was created, typically matching their employee or user account information.

The status of the original receipts required for the expense report, indicating whether they are 'Required', 'Missing', or 'Received'.

The status of the imaged receipts required for the expense report, indicating whether they are 'Required', 'Missing', or 'Received'.

Overall status of the expense report, which could be 'Draft', 'Submitted', 'Approved', 'Paid', or other relevant stages.

Lookup value describing the meaning of the Audit Code, providing clarity on the type of audit applied.

List of individuals who are currently waiting for approval or are responsible for approving the expense report.

This field is reserved for insert operations only; for updates or deletions, appropriate child table operations should be used.

This field is reserved for insert operations only; for updates or deletions, appropriate child table operations should be used.

This field is reserved for insert operations only; for updates or deletions, appropriate child table operations should be used.

This field is reserved for insert operations only; for updates or deletions, appropriate child table operations should be used.

This field is reserved for insert operations only; for updates or deletions, appropriate child table operations should be used.

This column is used as a generic reference, possibly tied to specific search operations or queries.

Date associated with the system’s effective date for data operations, possibly used to ensure accurate historical data retrieval.

Query parameter that helps fetch records which are effective as of the specified start date.