Transfer of Night Audit Data
Operationcode: ACC
ACC
Message
This data in the XML-structure covers:
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4718</TN>
<OC>ACC</OC>
<ADAYLIST>
<DAY>
<DATE>YYYY-MM-DD</DATE>
<MANDATORID></MANDATORID>
<CURRENCY></CURRENCY>
<AREVLIST>
<REV>
<ACCCODE></ACCCODE>
<CONTRAACCCODE></CONTRAACCCODE>
<COSTCENTER></COSTCENTER>
<SAPCOSTCENTER></SAPCOSTCENTER>
<REVACCOUNT></REVACCOUNT>
<REVAREA></REVAREA>
<BRUT></BRUT>
<NET></NET>
<DESCR></DESCR>
<TAXPERC></TAXPERC>
<TAXDESCR></TAXDESCR>
<TAXCODE></TAXCODE>
<SAPTAXCODE></SAPTAXCODE>
</REV>
…
</AREVLIST>
<ACLLIST>
<CL>
<ACCCODE></ACCCODE>
<CONTRAACCCODE></CONTRAACCCODE>
<AMOUNT></AMOUNT>
<PAYMENT-TYPE></PAYMENT-TYPE>
<DESCR></DESCR>
<INVIOCEDATE></INVOICEDATE>
<INVOICENO></INVOICENO>
<INVOICESET></INVOICESET>
<CARDNO></CARDNO>
<EXP></EXP>
<FBC></FBC>
<DEBTORNO></DEBTORNO>
<EXTRESREF></EXTRESREF>
<NN1></NN1>
<VOUCHERNO></VOUCHERNO>
<GID></GID>
<HQGID></HQGID> <!-- for HQ-Installation -->
<PAYMENT-ID></PAYMENT-ID>
<OP-ID></OP-ID>
<AGUESTLIST>
<GUEST>
<NAME></NAME>
<ROOM></ROOM>
<ARRIVAL></ARRIVAL>
<DEPARTURE></DEPARTURE>
</GUEST>
…
</AGUESTLIST>
</CL>
…
</ACLLIST>
<APAYMENTLIST>
<PAYMENT>
<ACCCODE></ACCCODE>
<CONTRAACCCODE></CONTRAACCCODE>
<AMOUNT></AMOUNT>
<PAYMENT-TYPE></PAYMENT-TYPE>
<DESCR></DESCR>
<DOCUMENTNO></DOCUMENTNO>
<!-- uncompressed, see details -->
<DOCUMENTDATE></DOCUMENTDATE>
<!-- uncompressed, see details -->
<PAYMENT-ID></PAYMENT-ID>
<!-- uncompressed, see details -->
<OP-ID></OP-ID>
<!-- uncompressed, see details -->
<CARDINFO>
<!-- uncompressed, see details -->
<EXTERNAL-PROCESSING-DATE></EXTERNAL-PROCESSING-DATE>
<TERMINAL-ID></TERMINAL-ID>
<TRACE-NO></TRACE-NO>
</CARDINFO>
<RESNO></RESNO>
<!-- uncompressed, see details -->
<RESSUBNO></RESSUBNO>
<!-- uncompressed, see details -->
<ARRIVAL></ARRIVAL>
<!-- uncompressed, see details -->
<DEPARTURE></DEPARTURE>
<!-- uncompressed, see details -->
<HQGID></HQGID>
<!-- for HQ-Installation -->
<!-- uncompressed, see details -->
<DEBTORNO></DEBTORNO>
<!-- uncompressed, see details -->
<DIRECTDEBIT>
<!-- uncompressed, see details -->
<BANK-ID></BANK-ID>
<ACCOUNT-ID></ACCOUNT-ID>
</DIRECTDEBIT>
</PAYMENT>
…
</APAYMENTLIST>
<AOPPAYMENTLIST>
<OPPAYMENT>
<ACCCODE></ACCCODE>
<CONTRAACCCODE></CONTRAACCCODE>
<AMOUNT></AMOUNT>
<PAYMENT-TYPE></PAYMENT-TYPE>
<DESCR></DESCR>
<TYPE></TYPE>
<DOCUMENTNO></DOCUMENTNO>
<!-- See details -->
<OP-ID></OP-ID>
</OPPAYMENT>
…
</AOPPAYMENTLIST>
<ASTATISTICLIST>
<STATISTIC>
<ID></ID>
<SUB>
<KEY></KEY>
<DESC></DESC>
</SUB>
<SUBSUB>
<KEY></KEY>
<DESC></DESC>
</SUBSUB>
<SUBSUBSUB>
<KEY></KEY>
<DESC></DESC>
</SUBSUBSUB>
<VALUE></VALUE>
<DESCR></DESCR>
</STATISTIC>
…
</ASTATISTICLIST>
<ACOMMINVOICELIST>
<COMMINVOICE>
<INVOICEDATE></INVOICEDATE>
<INVOICENO></INVOICENO>
<INVOICESET></INVOICESET>
<BRUT></BRUT>
<NET></NET>
<GID></GID>
<HQGID></HQGID>
<!-- for HQ-Installation -->
</COMMINVOICE>
…
</ACOMMINVOICELIST>
<APROFILELIST>
<PROFILE>
<HQGID></HQGID> <!-- for HQ-Installation -->
<GID></GID>
<DEBTORNO></DEBTORNO>
<TITLE></TITLE>
<SN></SN>
<CN></CN>
<LN></LN>
<VIP></VIP>
<STREET></STREET>
<CITY></CITY>
<ZIP></ZIP>
<COUNTRY></COUNTRY>
<PHONE></PHONE>
<FAX></FAX>
<EMAIL></EMAIL>
<DOB></DOB>
<SEX></SEX>
<TAXID></TAXID>
<PASSWD></PASSWD>
<MATCHCODE></MATCHCODE>
<GT></GT>
<TT></TT>
</PROFILE>
…
</APROFILELIST>
<!-- See details -->
<AWRITEOFFPROTOCOL>
<WRITEOFF>
<OP-ID-SRC></OP-ID-SRC>
<OP-ID-DEST></OP-ID-DEST>
<TIME></TIME>
</WRITEOFF>
…
</AAWRITEOFFPROTOCOL>
<!-- See details -->
<AOPTRANSFERS>
<OPTRANSFER>
<OP-ID></OP-ID>
<TIME></TIME>
<ACCCODE-DEST></ACCCODE-DEST>
</OPTRANSFER>
…
</AOPTRANSFERS>
</DAY>
…
</ADAYLIST >
<ORG>disp_4711</ORG>
</SIHOT-Document>
Attributes Message
The interface can be enhanced by two addition Tags: AWRITEOFFPROTOCOL and AOPTRANSFERS
To use these functions some requirements have to be fulfilled:
- No partial write Offs are possible. Each write off operation will generate a new OP-Posting.
- All the payments have to be transferred by details, in order to have the
<PAYMENT-ID>and<OP-ID>. - The accounting system has to take care that all operations in SIHOT
are tracked correctly in the accounting system. That means that the
Messages
<AWRITEOFFPROTOCOL>and<AOPTRANSFERS>have to be followed exactly by the TIME. Because it is a difference if you transfer a posting first to an different account and write it off or vice versa. - These functions have to be activated by GUBSE.
<HQGID> is the unique id of this guest profile in the HQ-database
PAYMENT-ID and OP-ID
The <PAYMENT-ID> is a unique number for any payment made in the
Front-Office area of SIHOT. This ID can be used to track any payments in this area.
In case that this is a debit payment (City Ledger) SIHOT generates a second ID, called <OP-ID>. This id has to be used in case that any OP-Payment has to be tracked, e.g. write-off’s.
DIRECTDEBIT
If a payment type is configured as “directdebit”, there are further
elements in the element <PAYMENT>:
<DEBTORNO>is the debtor number of the payment’s invoice holder or account holder.<DIRECTDEBIT>contains the debtor’s bank details in two elements:<BANK-ID>is the bank identification number<ACCOUNT-ID>is the bank account identification number
AWRITEOFFPROTOCOL
This protocol has all write off operations of a day.
AOPTRANSFERS
This protocol has transfers of posting from a city-ledger account to different ones (destinations).
Response
This could be the answer to the above operation.
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-Document>
<TN>4718</TN>
<OC>ACK</OC>
<RC>0</RC>
<ORG>disp_4711</ORG>
</SIHOT-Document>