Skip to end of metadata
Go to start of metadata

KSA generates billing statements and exports them as XML. This record is kept in BILL_RECORD (the fact that a bill was raised, and produced as XML). An external statement processor can take the bill, produce a bill in a new format (HTML, PDF, etc., referred to as the statement) and register that copy with KSA for bill presentment purposes.


Table: BILL_RECORD

Stores the existence of a bill having been produced.

Column

Description

ID

Autonumbered primary key.

CREATOR_ID

User who created the bill.

CREATION_DATE

Timestamp of creation.

ACNT_ID_FK

Account implicated in the bill.

BILL_DATE

Accounting date for the bill.

START_DATE

Start date of transactions.

END_DATE

End date of transations.

UNBILLED_TRANSACTIONS

Bill only shows transactions that have not previously been billed.

DEFERMENTS

Bill shows deferments.

INTERNAL_TRANSACTIONS

Bill shows internal transactions.

DEPENDENTS

Bill includes dependent support.

MESSAGE

Message on the bill.

XML_BILL

XML formatted version of the bill.

Table: BILL_RECORD_TRANSACTION

Stores the relationship between bills and transaction, to allow bills to only contain those transactions that have not already been billed, if required.

Column

Description

BILL_RECORD_ID_FK

FK Reference to BILL_RECORD

TRANSACTION_ID_FK

FK Reference to TRANSACTION

Table: EXTERNAL_STATEMENT

Maps locations where externally generated statements are stored, to allow user access to the statements.

Column

Description

ID

Autonumbered primary key.

BILL_RECORD_ID_FK

Pointer to the BILL_RECORD

FILETYPE

Mime type for the file (for example application/pdf)

URI

Resource locator for the statement. It is expected that KSA will have the privilege to be able to access this file.

IS_REDIRECT

Boolean that tells the system whether the URI should act as a redirect, or if the system should fetch the file at the location and send it to the user.

  • No labels