ChargedLocationInfo represents a location in a school system. It can be used to associate accounts and purchase orders with particular schools or other cost centres.

The SIF unique identifier for the location.

Defines whether the location is a school or a non-school location.

Specific site category.

Examples
Prep Site
Satellite
Central Kitchen
Warehouse
Storage
Central Office
Other

Text name of the location.

Description about the location.

The locally-assigned identifier for this location.

The state-assigned identifier for this location.

A ChargedLocationInfo instance could be related to another ChargedLocationInfo. This element will help create that relation.

The RefId of a corresponding SchoolInfo object.

This element has the ChargedLocationInfo address information.

The location's phone numbers.

This object is used to capture general information about debtors.

Debtor Id.

The Local Id of this debtor.

Id of the entity referred to by this object (e.g., student, employee, organization).

SIF object referenced by BilledEntity.

Addresses of the debtor to be used for billing. These addresses override any addresses found in the Billed Entity.

Name of the entity to be used for billing (e.g. company name rather than individual name).

Note about billing requirements.

Any discount amount applicable to this debtor (e.g. family discount for scholarship, number of children enrolled). Is a percentage.

Debtor's BSB number.

Debtor's account number.

Debtor's account name.

This object communicates information about a financial account.

GUID that identifies this financial account.

The Local Id of Financial Account.

Identifier of a parent account of the account. Can be used to construct a hierarchical tree of nesting accounts, e.g. "Revenue" -- "Revenue-Grant" -- "Revenue-Grant-Commonwealth".

Location associated with the account

Account number used for ledger.

Name of the account.

Description of the account.

The class of the account

Account code charged to this item.

Account creation date.

Account creation time.

This object contains an amount to be invoiced to an outside entity (typically a creditor or debtor). This object can include school fees. The object is also used for payments to an outside entity (using debit amounts), where those payments are not for goods and services (PurchaseOrder object): e.g. credit notes, reimbursements, rebates.

GUID for this transaction. The application that owns this object is responsible for generating this unique Id.

The Local Id of this Invoice.

Id of the entity being billed for this billing activity.

RefId of SIF object referenced by Invoiced Entity.

Invoice number assigned locally by the system issuing the invoice.

Date of the transaction.

Description of the transaction.

Gross amount to be billed, including any tax. Can be credit (e.g. for family credit notes, reimbursements, rebates).

The associated ledger for this transaction

Id of the location billed for this billing activity.

Net amount billed, excluding any tax. Should be BilledAmount minus TaxAmount.

Rate of tax included in the billed amount.

Tax type (e.g. G11 vs NP6)

Amount of tax included in the billed amount

Authority or person who created the invoice

Authority or person who approved the invoice

Details of items invoiced (free text)

Due date for payment.

List of RefIds of the Associated Financial Accounts.

List of Codes of the Associated Financial Accounts.

The accounting period against which the transaction is billed.

An invoice purchase order related to this invoice (e.g. an invoice raised for the delivery of goods on a purchase order).

Listing of line items from original purchase order. Included to indicate any variation between the items, item cost, or item quantity ordered, and what has been delivered.

Whether the billing is voluntary (applies to some school fees).

This object is used to adjust balances between accounts. It is typically used to correct chart of account coding errors (e.g. created invoices for parents against the maths chart of account code when it should have been English).

Journal Id.

The Local Id of the journal.

RefId of account to debit.

RefId of account to credit.

Account to debit.

Account to credit.

RefId of the originating transaction which requires adjustment. This could be an Invoice, PaymentReceipt or PurchaseOrder.

Amount to transfer between the two accounts.

Original GST code for journal transfer (if required).

Replacement GST code for journal transfer (if required).

Note about the journal.

Details of the Adjustment if it requires more than one line.

Date on which journal was created.

Date on which journal was approved.

Authority or person who created the journal.

Authority or person who approved the journal.

This object complements the Invoice object, and contains information about the payment of an Invoice object.

GUID for this payment or receipt. The application that owns this object is responsible for generating this unique Id.

The Local Id of this payment or receipt.

Type of transaction.

A pointer back to the Invoice object corresponding to this payment. Is omitted for general ledger transactions, creditor receipts and debtor payments. To be used if this payment is only for one invoice.

A List of pointers back to the Invoice object corresponding to this payment. Is omitted for general ledger transactions, creditor receipts and debtor payments. To be used when this payment is associated with more than one invoice.

A pointer back to the vendor associated with the Invoice object, if applicable.

A pointer back to the debtor associated with the Invoice object, if applicable.

Id of the location billed for this transaction.

Date transaction was made.

Amount received.

Memo transaction Id from other vendor software.

List of RefIds of financial account codes.

List of financial account codes.

Description of the transaction.

Rate of tax included in the billed amount.

Amount of tax included in the billed amount.

Method through which transaction was made (e.g. cash, credit card). If a receipt is made using two receipt methods (e.g. $20 in cash and $80 on credit), two PaymentReceipt objects are expected to be created, rather than a single object with mixed receipt method.

The cheque number issued, if paying creditors by cheque.

Note about the receipt or payment.

The accounting period against which the transaction is billed.

This object provides information down to the line item level for purchase orders.

Transaction GUID for this purchasing activity. The application that owns this object and is responsible for generating this unique Id.

The Local Id of this purchase order.

Purchase order number.

This object references the VendorInfo object being billed.

The location Id for this purchasing activity.

The employee Id for the originator of this purchasing activity.

Information about the item/s delivered.

Date on which purchase order was created.

Rate of tax included in the billed amount.

Amount of tax included in the billed amount.

Total amount billed.

Date on which the object was last updated.

Flag that order has been fully delivered.

Original purchase order that this purchase order updates (e.g. to cancel line items).

This object contains basic vendor information (commonly known as creditors).

Vendor Id.

The Local Id of this vendor.

Name of the vendor.

Contact information.

Account number or other Id.

Australian Business Number.

The vendor is registered to collect GST.

The vendors payment terms (typically expressed as number of days e.g. 14 days).

BPay Id.

Vendor's BSB number.

Vendor's account number.

Vendor's account name.